Title: Message
I agree with Rick completely. I work for a very large organization and policy is policy. Not only will we not let you put them into our Active Directory, I have a script that will find them and throw the machine objects into an Enterprise Admin Access only OU and disable and smack the ACL of the offending object if you someone sneak one in. So not only do they not get to use the server anymore, they can't even use that server name again. We catch more than a couple of occurrances of this and we take away their ability to add anything and let their managers know that we did it and why.
 
While I understand why people want to put them in (I in fact want to as well), we want a centralized controlled IT structure and the best way to maintain or reduce costs is to have a handle on what is in production. We do not have an official company load for W2K3 yet with all of the certified drivers and antivirus software so we don't want anyone deploying anything on it because anything they deploy we know will have to be revisited and is a possible breeding ground of viri, worm's, and support issues with no escalation paths.
 
Tough love I guess.
 
  joe
 
 
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rick Kingslan
Sent: Wednesday, June 11, 2003 7:24 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Installing Windows 2003 servers to Windows 2000 Domain

Justifying it technically is going to be a problem, as there are no real 'downfalls'.
 
However - if they don't want them - stick to your guns.  Policy says NO.  If there are any questions, refer to latter statement.

Rick Kingslan  MCSE, MCSA, MCT
Microsoft MVP - Active Directory
Associate Expert
Expert Zone - www.microsoft.com/windowsxp/expertzone
 



From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pennell, Ronald B.
Sent: Wednesday, June 11, 2003 2:48 PM
To: [EMAIL PROTECTED]

Has anyone come across any problems with installing the new windows 2003 servers to the Windows 2000 site.

Running W2K with SP3 and Exchange 2000 all in native modes.  Our company is having a storm of interns coming in and wanting to run projects on a W2k3 server.    Other than it is against company policy not to allow users to install servers, or even there own systems.   Management is trying to come up with some negatives to this, other than just saying it is against company policy.

 

Ron Pennell

[EMAIL PROTECTED]

Reply via email to