Discussion on:
View:
Show:
Also provides some interesting information when doing your MS-LDAP house cleaning.
Tells me that I am connected to a domain that doesn't support this query. Hmm... it's a domain controller on Windows 2003, not replicated or anything else. Very simple setup.
Same here simple 2003 domain setup. "dsquery computer" works fine, but does not with the inactive switch?
2008 R2 DCs but at 2003 functional level.
What functional level are you at, DWalker88001 and jshelton? What happens when you type dsquery /? Did you try to specify an OU? Might want to give that a shot too.
What functional level are you at, DWalker88001 and jshelton? What happens when you type dsquery /? Did you try to specify an OU? Might want to give that a shot too.
Your domain functional level needs to be win2003 (or higher).
To determine this, see:
http://www.windowsnetworking.com/articles_tutorials/determining-functional-level-windows-server-2003.html
To determine this, see:
http://www.windowsnetworking.com/articles_tutorials/determining-functional-level-windows-server-2003.html
I added a line to dump the results in a text file "dsquery computer ???inactive 16 >c:\textfile.txt"
I use a utility called OldCmp, looks at either password age or LLTS, can export to csv, html, dhtml, etc. It will disable accounts and then you can run it again in 30 days to delete the disabled accounts. Can also be used against user accounts.
http://www.joeware.net/freetools/tools/oldcmp/index.htm
http://www.joeware.net/freetools/tools/oldcmp/index.htm
Hi
I would like to know how do you go about doing the following.
Creating a script to identify stale computers (8 Weeks) and moving the identified computers to an OU called Disabled Computers once moved to the container the Computer gets disabled automatically. (Powershell and Cmd based script)
I would like to know how do you go about doing the following.
Creating a script to identify stale computers (8 Weeks) and moving the identified computers to an OU called Disabled Computers once moved to the container the Computer gets disabled automatically. (Powershell and Cmd based script)
Try reposting this in the 'Q&A' forum. The 'Discussion' forum is for matters of general discussion, not specific problems in search of a solution. The 'Water Cooler' is for non-technical discussions. You can submit a question to 'Q&A' here:
http://www.techrepublic.com/forum/questions/post?tag=mantle_skin;content
There are TR members who specifically seek out problems in need of a solution. Although there is some overlap between the forums, you'll find more of those members in 'Q&A' than in 'Discussions' or 'Water Cooler'.
Be sure to use the voting buttons to provide your feedback. Voting a '+' does not necessarily mean that a given response contained the complete solution to your problem, but that it served to guide you toward it. This is intended to serve as an aid to those who may in the future have a problem similar to yours. If they have a ready source of reference available, perhaps won't need to repeat questions previously asked and answered. If a post did contain the solution to your problem, you can also close the question by marking the helpful post as "The Answer".
http://www.techrepublic.com/forum/questions/post?tag=mantle_skin;content
There are TR members who specifically seek out problems in need of a solution. Although there is some overlap between the forums, you'll find more of those members in 'Q&A' than in 'Discussions' or 'Water Cooler'.
Be sure to use the voting buttons to provide your feedback. Voting a '+' does not necessarily mean that a given response contained the complete solution to your problem, but that it served to guide you toward it. This is intended to serve as an aid to those who may in the future have a problem similar to yours. If they have a ready source of reference available, perhaps won't need to repeat questions previously asked and answered. If a post did contain the solution to your problem, you can also close the question by marking the helpful post as "The Answer".
If the remote or (home user) never authenticate's with AD the PC/laptop will appear to be stale. In our case we find some users can work for weeks and not actually authenticate with AD in some cases. If other authentication tools are in play it gets worse. A remote computer that uses Safeguard for example and lets say the computer is removed in error and it was a remote computer..that piece of hardware may end up having to travel to the head office location to be re connected to the domain..in some cases... $$
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
