Here a little tip from experience: If a server starts acting funny, check the disk space. If you are almost out of space, Windows won't be able to function correctly. Symptoms of this may be slow time to remote desktop in, or a host of other "weird" things that you are unable to explain. In fact, some .Net applications may fail to run with a "Can't find XXX assembly" error. The assembly is where it's supposed to be, but if .Net can't allocate space for the shadow copy, then it can't start the application (yes, I've had this happen to me).
The more free space the better, and if the server is approaching the megabytes of free space on the main drive, ask your IT people to correct it before trying to do anything with that server. You'll waste your time if you really need the server for something, and it won't cooporate. You can beg and plead as much as you want, but a server without free disk space won't care that you have a major deadline rapidly approaching.