Cannot see drives, run comand etc

This might be something I am doing wrong, but I am a local admin to this Windows Server 2003 R2 Enterprise box and when I log in remotely (RDP), I cannot see any drives, run command and applications...Almost like I do not have priviliages...

Any ideas?
LVL 1
Dr_EgoAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

moss_guruCommented:
Does the same thing happen if you RDP to the CONSOLE session?  Are there any inherited Group Policies that may affect group membership to this server?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Dr_EgoAuthor Commented:
I tried connecting
mstsc /v:serverName /console and I still cannot see drives or right click on My computer.

There isnt any group policies. I am able to log in as another user and perform any action.
0
moss_guruCommented:
So this problem is only happening with one user account?  Other Domain Admins or Local Admins work fine?
0
Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

Dr_EgoAuthor Commented:
Yes. Another regular user works fine as well. However, I tried with 3 other users who are local admin to the box and get the same.

The server is under "Computers" in AD same as other servers I can successfully log onto.
0
moss_guruCommented:
So you have working Domain accounts and non-working domain accounts?  Or are the working ones local accounts?  You may want to try removing the server from the domain, rebooting, adding it back in, rebooting, and then checking the access...
0
Dr_EgoAuthor Commented:
That is correct. I am having working Domain accounts and non-working domain accounts.
0
Dr_EgoAuthor Commented:
I did notice "Personalized Settings" keep coming up every time I log in. When I log in with the user that works, I dont get that.
0
moss_guruCommented:
Hmmm... Could be a corrupt profile issue for those non-working accounts...  You may want to try loggin in as a working account and deleting the profiles of those accounts that don't work...
0
Dr_EgoAuthor Commented:
I see under profiles is Mandatory profile instead of local
0
Dr_EgoAuthor Commented:
How do I change my profile to "local" in User Profiles instead of "Manadatory". ?
0
moss_guruCommented:
I was referring to the physical profiles in the "C:\Documents and Settings" dir...  As long as they are not locked from being logged in (either directly via RDP or console, or indirectly via a service), they should be deletable directly from the explorer.
0
Dr_EgoAuthor Commented:
I deleted the profiles from the directory. (c:documents and settings). Also tried from User Profiles in System management. When I go into my user's directory i see the ntuser.man. If I changed it to .dat still no change. I suspect maybe that is causing an issue?
0
moss_guruCommented:
Possibly... If I remember correctly, that makes the profile read only or sets some kind of special template-type settings on the profile.  That's probably why you see the Personalized Settings message each time they log in...

So if you log in as a user that had a profile deleted you get a ntuser.man profile created instead of the normal .dat profile?
0
Dr_EgoAuthor Commented:
Yes. That is correct. I see the .man instead of the  normal .dat
0
moss_guruCommented:
Are the afflicted user accouts using roaming profiles?  If so, their network profile path may contain a ntuser.man file that is being pulled down...
0
Dr_EgoAuthor Commented:
Would that affect me on other servers (about 20 others)  that I able to log on successfully? This is the only server giving me this issue.
0
moss_guruCommented:
I would have thought so...  Is the network profile using an ntuser.man file?  Is there anything (beside this issue) that makes this server unique?
0
Dr_EgoAuthor Commented:
Yes it is using a MAN file. Nothing obvious that makes this server unique.
0
Dr_EgoAuthor Commented:
I noticed that my accoutn in AD had the Terminal Service Profile directing to a profile path. This was disallowing me to log onto that one server as"local" and giving me only a mandatory profile.

Thank you for the help.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.