Start Layout not applying correctly

[gsk]

Hi All,

 

I've gone down the route of specifying a start layout. I've exported this through powershell and copied to a share on SYSVOL. The template applies but only one icon out of the 20-odd is shown. Where might I be going wrong?

 

This is all on the same PC. Start Layout is generated as local admin, then delete profile of test student login. Then login as test student to test.

 

Thanks,

[sted]

do the shortcuts to say word exist in the pupils start menu (redirected or otherwise) try your test user where you don't disable access to the all user start menu as well

[3s-gtech]

I also found that the links had to be in the redirected Start Menu as well as in the Start layout for the them to show (and actually be active links, as above).

[gsk]

They didn't exist, but do now and still nothing on the start layout.

[sjatkn]

At the moment we are suffering similar issues. They seem to get better but not perfect when we install the 1511 update and its associated cumulative update.

 

I've also found that touching the date stamp on the XML file and restarting has fixed a few of them. Microsoft says this in https://technet.microsoft.com/en-us/library/mt431718(v=vs.85).aspx.

 

Important

If you disable Start Layout policy settings that have been in effect and then re-enable the policy, users will not be able to make changes to Start, however the layout in the .xml file will not be reapplied unless the file has been updated. In Windows PowerShell, you can update the timestamp on a file by running the following command:

(ls ).LastWriteTime = Get-Date

 

As you can tell I've not found a consistent fix, but various things seems to have fixed some but not all. All the machines have come from the same image and are exactly the same hardware so there shouldn't be any differences!!

[sjatkn]

After considerable effort getting the 1511 & its cumulative update for Windows 10 applied we have found the start menu layout is applying fairly reliably. Where were did have a problem we deleted the user\%username% profile and the next time it worked properly.

 

Prior to the updates we did adjust URL hardening for \\*\SYSVOL & \\*\NETLOGON as well as the wait for network stuff you will see in the thread about GPO's not applying. They did help get the menu applying through GPO, though it still frequently came up looking wrong.