How can I determine if a Windows 2003 server is still being used by anyone/thing, and if it is, what it is being used for?
I'm drawing a blank on what else to check other than event viewer to see what accounts are connecting to the server.
How can I suppress giving a reason for shutdown on a Windows Server host?
Specifically, on 2008 R2, but all versions back to 2003 and up to 2012 would be appreciated.
A little background: We have several Windows servers (2003, 2008) for our department. We're a division of IT so we manage our own servers. Of the four of us here I'm the only one with a slight amount of IT knowledge. (Note the "slight amount".) My boss says the servers need to be restarted at least weekly. I disagree. Our IT Department says that because she restarts them constantly that's the reason why our hard drives fail and power supplies go out on them. (That's happened to a few of our servers a couple times over the last four years, and very recently.)
So the question is: How often does everyone restart their Windows servers? Is there an industry standard or recommendation? Is our IT department correct in saying that because we re-start that's why we're having hardware issues? (I need a reason if I'm going to change her mind!)
If I have a Windows server (typically 2000, 2003 or 2008), is there a simple way to list all local directories shared on that server?
I can find the shares themselves easily enough, but I would love a quick way to find the local directories they represent on disk.
Thanks!
Is there a way (when logged in as an administrator, or as a member of the administrators group) to masquerade as a non-privileged user? Especially in an AD environment.
e.g., in the Unix world I could do the following (as root):
# whoami
root
# su johnsmith
johnsmith> whoami
johnsmith
johnsmith> exit
# exit
I need to test/configure something on a user's account, and I don't want to have to know their password or have to reset it.
Edit:
runas won't cut it. Ideally, my whole desktop would become the user's, etc. and not just in a cmd window.