We join them to the domain but we only do 3 or 4 a month so it's no big deal but our naming convention requires a machine to be identified by the office it's in so that's a major factor in just doing it when it's sitting in its final resting place.
John W. Cook Systems Administrator Partnership For Strong Families 315 SE 2nd Ave Gainesville, Fl 32601 Office (352) 393-2741 x320 Cell (352) 215-6944 Fax (352) 393-2746 MCSE, MCTS, MCP+I,CompTIA A+, N+ From: Joe Heaton [mailto:[EMAIL PROTECTED] Sent: Thursday, September 18, 2008 2:39 PM To: NT System Admin Issues Subject: new computers When you guys build new PCs, do you create the AD object first, or simply join the domain from the PC afterwards? I've always created the PC, then joined the domain, but our desktop guy just mentioned that our manager wanted him to create the AD object first. My first instinct is to say no, because then you're creating an AD object for something that doesn't exist yet, but other than that, I didn't have a real reason. Anyone have a better reason? Joe Heaton AISA Employment Training Panel 1100 J Street, 4th Floor Sacramento, CA 95814 (916) 327-5276 [EMAIL PROTECTED] ________________________________ CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
