[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5127
  • Last Modified:

Group Policy - Force classic Start Menu

Using Server 2003.  I have a group policy that sets: User Configuration-Administrative Templates-Start Menu and Taskbar-Force  classic Start Menu to disabled.  This should force the New Style menu.  I have a test user that I set to the classic style before applying the policy.  After setting the policy, the test user is still on the classic style.  I use the resultant set to check for my test user, and the settings are correct.  I cannot right click to change it as another policy disables that ability.  I created a new test user and that user starts with the new style menu.  It seems the users who already had the classic menu still have it.  How can I force the users with the classic menu to the new menu?
0
wcsoctu
Asked:
wcsoctu
  • 3
  • 2
1 Solution
 
briancassinCommented:
The computers may need to be rebooted for policy to take effect did you try doing a gpupdate /force from the command prompt ?

Also do you have stuck user profiles on the machine ?

Have you tried changing the policy to not configured on the classic start menu then to not configured ?
0
 
wcsoctuAuthor Commented:
I rebooted and deleted the users local profile to force it to re-create as I am using roaming profiles and I get the same results.
0
 
bhnmiCommented:
How about when you run a report on the said user and machine from within the Group Policy Management Console? Does it show the setting as applied?
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
wcsoctuAuthor Commented:
It shows as disabled, as it should.  I ran the Resultant Set Of Policy (Planning) selecting the user and the machine, and the policy shows as disabled.
0
 
bhnmiCommented:
Drop the roaming profile, or rename it and then log back in.
0
 
wcsoctuAuthor Commented:
I deleted the roaming profile on the server, logged in from the workstation and same result.  I then deleted the roaming profile from the server and from the machine being logged into, and it worked.  Not as easy as I would like since I have 70 users sharing about 10 pc's that are in use 24/7, but it gets the job done.
0

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now