Do you know not to login as Administrator on any of the networks machines?
Last updated by Brady Stroud [SSW] 8 months ago.See historyWe've seen this happen too many times - a user wants to do something on a network server machine, and because the user hasn't got a profile setup on that machine, he end up using the Administrator password to log on as administrator.
This is not a good thing because:
- We cannot tell who currently is logged in remotely, so if another developer wants to change something on the server, we can't work out who is on it.
- This is particularly the case where a lot of the servers don't allow multiple concurrent users, so we need to know who to disconnect or kick to free up a remote connection license.
- A lot of applications are installed as 'administrator', and no one end up remembering what they installed, and thus the administrator profile is loaded with applications that most people don't use.
- If you check in/check out files from Source Safe, it may end up using the administrator account - which means we can't work out who made a change in source safe.
So log on using your own domain account.