You're kind of on the right path. We only give our application developers administrative rights to "their" servers when it's necessary (during initial installation, upgrades, etc.) other than that our Tech Support department is responsible for all other activities.
On 2/28/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > What kind of directions do you give to application > administrators/developers when you "give" them a new server. I am looking > for something similiar to this: > > 1. don't create local user accounts > 2. don't create shares > 3. don't change NTFS permissions > 4. all applications need to be installed on the D: (or whatever drive) > and not the OS drive > 5. all applications should be installed/configured to run as a service > and not as a foreground application > 6. don't use the server for general office productivity applications > 7. don't surf the internet from the server console except to download > application specific software such as patches or updates > 8. if the server needs to be rebooted you must notify the server team > > Any additions or suggestions would be appreciated or if anyone already has > this documented and would be will to share that would be nice too. > > > > Regards, > Greg > > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ > ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
