General discussion

Locked

Should be Easy, BUT.....

By quintar51 ·
Hi Everyone,

I should not even be here asking this question, however, it has me stumped.

I installed w2k pro, clean installation, on NTFS partition. I then joined a domain. So far so good.

The problem is when one of my users logs in, he is unable to view/change the display properties.
"The system administrator has disabled display properties in the control panel" is the message that comes up.

He is also prohibited from viewing/changing the taskbar properties.

He is able to go into system, device manager, network settings, anywhere he wants.

This person is part of the domain admins group for the domain, and I also added him to the local administrators groups just to test it. Problem still persits.

If anyone else logs into the domain on that workstation, they're able to change the display properties. I also checked his profile and it's a roaming NOT mandatory one.

Nothing appears in the event viewer either.

Any Ideas?

This conversation is currently closed to new comments.

9 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Should be Easy, BUT.....

by j_o_blair In reply to Should be Easy, BUT.....

sounds like someone has put a policy in place against this one particular user. If memory serves, policies override user privilege.
Find out if they ever played with the policy editor, and remove the policy against them.
the other part is that ifit is a policy, just clearing a box will not undo the policy: It has to be set back.

Collapse -

Should be Easy, BUT.....

by quintar51 In reply to Should be Easy, BUT.....

There are no policies that are being used. I'm the one who installed the O/S and configured it. It's a brand new install.

Collapse -

Should be Easy, BUT.....

by quintar51 In reply to Should be Easy, BUT.....

Point value changed by question poster.

Collapse -

Should be Easy, BUT.....

by therock_3333 In reply to Should be Easy, BUT.....

hmmmmm
that is bizarre
no GPO affecting this user?
part of an OU or something that has those restrictions?
in a situation like that i would chalk it up to ms and reinstall

Collapse -

Should be Easy, BUT.....

by quintar51 In reply to Should be Easy, BUT.....

Thanks for the suggestion. Reinstalling will be my last resort. I just want to mention that there are no OUs whatsoever, as this is an NT domain, no AD or 2k servers at all.

Collapse -

Should be Easy, BUT.....

by pacaleala In reply to Should be Easy, BUT.....

this reminds me of an old nt bug

which hits you when joining
a nt computer to a domain and
you install network components
at the same time.


The fix is to logon to the ws
using the admin account
and
add the Domain Administrators groupto the
local Administrators group.

hth

Collapse -

Should be Easy, BUT.....

by quintar51 In reply to Should be Easy, BUT.....

The network components were installed during the installation. I only have client for ms networks, file and print sharing, tcp/ip. As I mentioned, This person is already part of the local admins group.

Collapse -

Should be Easy, BUT.....

by quintar51 In reply to Should be Easy, BUT.....

The problem here appears to be a corrupt profile. I deleted user's domain profile, and when he logged back in, the issue was resolved.

Collapse -

Should be Easy, BUT.....

by quintar51 In reply to Should be Easy, BUT.....

This question was closed by the author

Back to Windows Forum
9 total posts (Page 1 of 1)  

Related Discussions

Operating Systems Forums