For various reasons. 1. They don't ALWAYS re-use the old name. 2. The Tool also includes the option for "REMOVE COMPUTER" which lets the individual delete the computer from AD IF he/she was the original creator. He/She will then use the "CREATE COMPUTER" option to recreate the computer, if he/she wants to re-use the name. It's a round-about way to accomplish the same thing you are proposing. 3. Where were you when I was laying out the project 2 years ago? I sure could have used the help :-P Sincerely,
D�j� Ak�m�l�f�, MCSE MCSA MCP+I Microsoft MVP - Directory Services www.readymaids.com - we know IT www.akomolafe.com Do you now realize that Today is the Tomorrow you were worried about Yesterday? -anon ________________________________ From: [EMAIL PROTECTED] on behalf of joe Sent: Fri 8/6/2004 8:29 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] default containers Hey Deji, why don't you just have the QA guys resetting the computer account they already have? One of the rights you give to join should be reset password so they should have all they need.... joe -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, August 05, 2004 7:40 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] default containers What I do here is put up a web interface to a script that does the pre-creation in the background. I have 2 flavors. One is for the Helpdesk Admins. They log into the website, type in a computer name, type in the name of the computer's owner, pick the site/location of the owner (from a drop-down) list and hit "Submit". The script then create the computer account, put it in the associate OU, and ACL the computer object, giving the specified user the ability to join THAT computer to the Domain. The other flavor is for a QA domain where people reimage computers daily. The QA guy logs in, the login process takes the guy's name/location. The QA guys types in a computer name and the script goes and create/ACL the computer in the relevant OU, giving the QA guy the rights to join it to the Domain. I can share the code with you offline, but you have to promise not to tell, you-know-who :) Sincerely, D�j� Ak�m�l�f�, MCSE MCSA MCP+I Microsoft MVP - Directory Services www.readymaids.com - we know IT www.akomolafe.com Do you now realize that Today is the Tomorrow you were worried about Yesterday? -anon ________________________________ From: [EMAIL PROTECTED] on behalf of Creamer, Mark Sent: Thu 8/5/2004 9:48 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] default containers Thanks all for the responses - We're 2000 presently, so I'll look at the scripted or pre-create options. Thanks again <mc> ________________________________ From: joe [mailto:[EMAIL PROTECTED] Sent: Thursday, August 05, 2004 11:58 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] default containers If you are using Windows 2003 AD you can use redircmp to change the default computers container targeted by the legacy join calls. The more robust method though, is to script the join. joe ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Creamer, Mark Sent: Thursday, August 05, 2004 11:21 AM To: [EMAIL PROTECTED] Subject: [ActiveDir] default containers Is there a way to change the default location for a computer when it gets added to the domain to be a specific OU, rather than the Computers container? Or would this have to be done by scripting the add computer process? Mark Creamer List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
