Windows 10 Mandatoy Profile - Broken Start Menu

[FN-GM]

Hi,

 

I have created a Windows 10 mandatory start menu. I did the Microsoft way by syspreping and having an .xml with the copy option.

 

It seems to work, however when a user logs in the start menu doesn't open. If I press the button nothing happens. The search is also broken. Switching to a local profile and the issue is fixed.

 

Using the same profile as a default profile instead of Mandatory profile seems to work ok as well.

 

Any ideas please?

 

Thanks

Edited October 16, 2015 by FN-GM

[cybergoldfish]

Was CopyProfile set to true when sysprepping? This can cause the start menu to break. We spent a week battling this issue when testing our deployment.

[FN-GM]

It was, but this is needed to capture the profile?

[cybergoldfish]

That's the culprit then. Setting copyprofile to false will solve the issue with the start menu almost guaranteed.

[FN-GM]

If I do that though I won't be able to use the profile at all?

[gsk]

I'm just starting with Win10 and haven't come into this problem but this possible solution has come up while I've been researching the start menu...

 

Alternative method of applying a custom layout in the Deployment Task Sequence

 

My recommendation for Start Screen Customization is to use PowerShell to capture a customized Start Screen Layout and then copy the layout to the default user profile during the Deployment Task Sequence. The steps are detailed below:

 

On a reference machine manually customize the Start Screen layout to your requirements: SS_Blog_CustomSS

Once customized, run the following PowerShell CmdLet on the reference machine to generate a bin file:

Export-StartLayout –As BIN –Path .\AppsFolderLayout.Bin

Note: You must run the command in the logged on user context and generate a BIN file. You cannot use the XML format in an image deployment scenario.

 

Source: https://deploymentpros.wordpress.com/2013/11/02/management-and-customization-of-the-windows-8-1-start-screen/

[JRowley]

I don't have roaming/mandatory profiles set up but apparently this can be caused by the "delete cached roaming profiles" option being enabled.