Classic Shell: Forum

Does Classic Shell yield to Group Policy Object rules such as the redirection of the Start Menu and managed applets appearing in Control Panel?

I am just having a few problems getting it to work so I just need to know if it is a limitation of Classic Shell.

I also tried to use the Custom Folder option where I entered a unc path to a set of shortcuts on a server share (so I can dynamically manage content).

Link: \\server-name\share

Label: IT Programs



When I expand the folder the contents expecting to see the shortcut entries, it is empty.

Do I need complete the Command Field and if so what is the correct entry?

I have checked the permissions on the share and all is well.

Can anyone advise?

Classic Shell respects the group policies that have an API to retrieve them: http://msdn.microsoft.com/en-us/library/windows/desktop/bb762534(v=vs.85).aspx

It also gets the location of the Start Menu and Programs folders from the system, instead of hard-coding paths. I don't know if your particular method of redirection will work.

I tried using a UNC path on my home network and it works just fine. The icon shows correctly and the contents show up in a sub-menu. I only used the Link and the Label fields.

In your case, does the [empty] sub-menu open right away? If you double-click on the item itself, does the correct folder open in Explorer? Also, is it possible your files are hidden or system? Such files don't show up in the menu.

From what some other users have reported in the forum, you must log off after you redirect the folders so Classic Start Menu picks up the new paths. But gpupdate.exe /force run as administrator might also work instantly. But please report if it isn't working as it's untested. Some other users *have* also reported that it doesn't work if folders are redirected using Group Policy. (There are other ways to redirect too such as by using the 'Location' tab from the folder's properties.)

It seems that in Classic Shell 4.0 to 4.0.2, entering a UNC path for the Link field is broken if the path is: \\ServerName\<ShareName>\<some folder>. It works correctly if directly the share is linked to e.g. \\ServerName\<ShareName> but not for a folder inside it. Similar situation for mounted drive letters. Suppose I mount a share to Z:\, then adding Z:\ as a link works but Z:\<some folder> shows the empty submenu. I just confirmed that everything works correctly in Classic Shell 3.6.8, so this is a regression.

_________________
Links to some general topics:

● Compare Start Menus

● Read the Search box usage guide.

I am a Windows enthusiast and helped a little with Classic Shell's testing and usability/UX feedback.

Classic Shell 4.0.4 introduces Group Policy support for all of its settings. Amongst those are new Group Policies to control menu redirection, independent of the OS settings. Extract the ADML and ADMX files from C:\Program Files\Classic Shell\PolicyDefinitions.zip to C:\Windows\PolicyDefinitions folder (for Local Group Policy). If you have Active Directory domain, extract the files to %logonserver%\sysvol\%userdnsdomain%\policies\PolicyDefinitions\. The 4 policies to redirect the menu are:

- Start Menu folder
- Programs folder
- Common Programs folder
- Common Start Menu folder

You must exit the Start menu by right clicking the Start button or by running "C:\Program Files\Classic Shell\ClassicStartMenu.exe" -exit and then start it again from "C:\Program Files\Classic Shell\ClassicStartMenu.exe".

_________________
Links to some general topics:

● Compare Start Menus

● Read the Search box usage guide.

I am a Windows enthusiast and helped a little with Classic Shell's testing and usability/UX feedback.

This is fantastic news and makes this product even better now there are solutions for managing this in an Enterprise.

The empty submenus problem when a UNC network folder was added is also fixed in Classic Shell 4.0.4.

_________________
Links to some general topics:

● Compare Start Menus

● Read the Search box usage guide.

I am a Windows enthusiast and helped a little with Classic Shell's testing and usability/UX feedback.