Windows Task Bar

Microsoft Windows
Hi All: I have a strange problem that?s driving me crazy, no cracks about it being a short trip. I have a Domain with GPO?s active and on some of my systems the user, includes the administrators, do not have the ability to right click and change the Task Bar while on other system they do. Those that do not work include Windows 2000 Advanced Servers both DC?s and member servers. Those that do work include Windows 2003 Standard Servers all member servers and Windows XP clients. For the Windows 2000 member servers if I login as the local administrator the task bar works fine but not when I login as a Domain Admin. All my group memberships are in correct order. I think it has something to do with how GPO?s are being applied but I just can not see it. Any ideas? Thanks in advance for you help RWJ

Answer Wiki

Thanks. We'll let you know when a new response is added.


The first things I would look at would be your policy structure. Where is the policy applied, at the domain level or by OU? Is there a common factor among the computers not receiving policy such as, are they all part of the same group or OU? If so, check your policy links. Are you blocking policy inheritance at any level?

If your satisfied with your initial config, use the GP Results Wizard (GP Management mmc => GP Results)and run it against the computers that are not getting the policy. This tool will confirm or deny that policy is being applied to a given computer. It is possible some of your computers are simply not receiving GP properly or at all. If that’s the case, don’t rule out checking your communications path as it could be related to a faulty port or ports on a switch.

Good luck!

Discuss This Question: 3  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • OngBak
    If it were me, I'd open a command prompt on a machine that is not affected and run the 'gpresult' command. Then I would do the same on a machine that is having the issue and compare the results. Since the issue does not occur when the local Administrator is logged on then the GPO that you are looking for will almost certainly be in the "User Configuration" section of the gpresult output. I'd look for a GPO that is listed on the affected computer, but not listed on the unaffected PC. Then I'd install the Group Policy Management Console on one of the DC's and find that policy and look at where it is being applied. Obviously the two PCs must be in different OU's or the GPO has some kind of security filtering applied to it. If the GPO does nothing more than configure restrict the Taskbar settings, then I'd just delete it, or remove it from being applied anywhere.
    0 pointsBadges:
  • Swiftd
    Some of the ADM templates apply to Windows 2000 and others to Windows XP/2003. The previous posters, while correct to check gpresult, may not turn anything up since the settings may not apply to those systems. Another possible option is to put the computer and user that you are using into the Computers and Users OU respectively and see if you are getting the same results. If that turns up working on both systems, you definately know it's a GPO setting. You can create a test OU that you can apply one by one to find out the offending setting. Either that or install/run Group Policy Manager on your DC and print out the Report to see what may be different between them. Again, however, it may simply be that the ADM template is applied different from Win2k to Win2k3/XP. Good luck
    0 pointsBadges:
  • Rjournitz574
    Hi All: I was hoping for the quick fix something like go to this policy, use this setting, and all your problems will be fixed but alas it was not to be. Thanks to all that replied. You were all correct in your suggestions which basically stated you are going to have to do it the long way. After much research and testing I was able to find the policy that was causing the problem I described and the offender is the: Turn on Classic Shell which was set to enable. The last line in the descriptive part of the explanation reads: As a result, the user interface looks and operates like the interface for Windows NT 4.0, and users cannot restore the new features. Never ceases to amaze me that no matter how many years of experience one may have you can still read things the way you want not they way they read. The last thing I wanted to accomplish was to have ones desktop react like Windows NT rather I wanted to insure all desktops react in Classic view as stated from Windows 2000 on up. What floored me was the different reaction of W2k systems from W2k3 and Win-XP to this policy being enabled. For the 2 later OS?s they had some Active Desktop capabilities while for W2k they had none what-so-ever. So the moral of this story is there are no shortcuts in troubleshooting, read descriptions a couple of times before deciding what they actually mean, test and re-test, remember that policies sometimes apply to one OS and not to others, and most of all remember that a policy may or will have a different reaction depending of the OS it gets applied against. Thanks again for you help. RWJ
    0 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: