How to access an end user's PC on company network

Hello. I'm a desktop analyst and I need access to a remote PC on our network. The user has disabled remote access to his PC.
I need to see files on that PC and I planned on using \\domain\computername c$ but it says "could not connect". That command works on other PC's here, but not the one in question.
What can I do to enable access so that command works?
There is staffing changes being made and I need to do this without the end user knowing.
I have full access to AD and all servers here, if needed. Thanks for your help!

I don't have physical access to the machine (the user cannot know I accessed it). Is there any way I can make //domain/computername c$ work from my PC to access his? For some reason, it works on all other PCs here, but not his.

I also don't know "how" to use that command line you gave me. Where it goes, etc?

Then use psexec with the command I showed you in my previous post. As long as remote registry is running it will work

Downloaded psexec.... extracted.... and when I run it, a DOS window appears for a split second and disappears.

Psexec is a command line utility, it has no GUI so you can't just click on it. The easiest thing to do is put all the extracted files in your system32 directory so you can run it without specifying the path to it. See the following link for usage:

http://technet.microsoft.com/en-us/s.../bb897553.aspx

The ps suite is invaluable to admins, I'm surprised you've never used it before. Get to know all the tools and they will save you tons of time and effort

I agree with you logicearth, it sounds possibly suspicious. However, since the Internet gives us no background or insight into someone's position I'm inclined to give the OP the benefit of the doubt. As a network admin myself I can think of several reasons to access another computer silently, but I find it hard to believe that someone in the field would have a hard time figuring this out. Regardless, I have provided the steps I would use and hope they can be of use.

NO, the user is being laid off, but doesn't know. He may have suspicion that he is getting laid off and we need to backup some files on his HD before they are possibly harmed. I actually need to activate RDP in group policy for all PC's. I'm still spinning my wheels here.

http://www.seanlabrie.com/2011/use-g...-group-of-pcs/

That link tells me to Open Group Policy Management Console and create and link a new GPO to this OU (containing all the computers). I have a folder (OU) in AD called "Computers" with all PCs in it, but I can't figure out how to attach ALL the pcs to a Group Policy.
I created a GP called "Enable RDP" - went to properties, on scope tab, under Security FIltering, I hit "add", but it won't grab the entire folder called "computers", it's only letting me add individual computers. HOw do I get it to grab ALL pcs?