|
Mr.
Richards..... welcome to the party. ;-)
Rick Kingslan MCSE, MCSA, MCT From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joe Sent: Wednesday, June 11, 2003 8:54 PM To: [EMAIL PROTECTED] 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
|
Title: Message
- [ActiveDir] Installing Windows 2003 servers to Windows ... Pennell, Ronald B.
- RE: [ActiveDir] Installing Windows 2003 servers to... Joe
- RE: [ActiveDir] [OT] Installing Windows 2003 s... Rick Kingslan
- RE: [ActiveDir] [OT] Installing Windows 20... Joe
- RE: [ActiveDir] [OT] Installing Window... Rick Kingslan
- RE: [ActiveDir] [OT] Installing W... Joe
- RE: [ActiveDir] [OT] Installi... Rick Kingslan
- RE: [ActiveDir] [OT] Inst... Joe
- RE: [ActiveDir] [OT] Inst... Rick Kingslan
- RE: [ActiveDir] [OT] Inst... Joe
