Hello,

I am trying to do make a customized start menu using the process of copying LayoutModification.xml file to the C:\Users\Default\AppData\Local\Microsoft\Windows\Shell folder. I am using a PowerShell script to do the copy xml file. The file copy is successful but when I login as a new user I do not see the customized start menu. I am doing the file copy in State Restore in the TS.

• Doing this on Win 10 Enterprise RTM joined to a domain
• Do I need to delete/rename the existing file?
• Do I need to rename my LayoutModification.xml file?
• I am doing the LayoutModification.xml file copy in the correct place in the TS

Hi There,

I have done something similar in the last few days. I am using a command line task using xcopy to copy in the LayoutModifcations.xml file, however I have my task running during the Post install phase, just after the add Windows Recovery (WinRE) task.  This then allows all the profiles to get the modifications as the none have really been created yet. I am also using xcopy as I have tried using powershell and found it a bit flaky, probably me and my syntax.

The Post Install phase seems to be good to add command line tasks like rewriting files, copying certain files before the OS is fully up and running. At least at this point the Folder structure is in place and it seems to accept files getting copied in. Do not try to run anything as an application, as it will still complain that it is in the Winpe phase.

One last thing, I have created the modifications file, however so far it has not displayed exactly as I had it configured. I used the Export-Layout command I think to create the mod file, I created 2 rows of icons but when its applied it comes out with 3. It looks ok, a bit like throwing a five but hoping for a six. I had previously tried using the copy profile method, this turned it all ugly, missing out the group names in most of the groups, merging some of the groups together, so I thought this was a better approach.

Lastly I would be interested to hear about your success with other customisations such as user pictures, desktop backgrounds etc. I am trying to use the defaults as much as possible, the last Corporate image customisations were a nightmare for our Windows 7 image, probably spent more time on these than all the apps and drivers put together.

Cheers

Ewen.

• Proposed as answer by Ty GlanderMicrosoft community contributor Thursday, September 03, 2015 10:47 PM
• Marked as answer by Norwood11 1 hour 34 minutes ago

Thanks for the advice. I will give this a try on Monday. We too are trying to keep things as default. We skipped Windows 8.x all together.<o:p></o:p>

For the desktop backgrounds and pictures and default login screen we found that making them in an MSI install worked best for us. We are an SCCM shop and we would run a query if you did not have the entry in programs and features SCCM would install it. A quick uninstall reverts the computer back default. As pinning icons to the task bar I plan on doing this the unattend.xml.<o:p></o:p>

Thanks

Paul.<o:p></o:p>

Quick question I tried to run the copy of the xml file in the post install using PowerShell. I am getting an error that PowerShell not detected. What are you using to copy the xml file to computer batch or vbs? If you do not mind can you please share what you are using?

Thanks

Paul

Quick update after redoing my base image I was able to get the start menu to work. While I was looking for some more help I came across these post on pinning icons. I am going to give them a try to see what happens.

http://www.osd-couture.com/2015/07/windows-10-pin-to-start-is-back.html

http://blogs.technet.com/b/deploymentguys/archive/2009/04/08/pin-items-to-the-start-menu-or-windows-7-taskbar-via-script.aspx

Hi there,

I am using a run command line task to copy the LayoutModifications file to its location. The command line I am using is as follows:

xcopy.exe /cherkyi "%DEPLOYROOT%\Applications\DummyFolder\CorpStartLayout\LayoutModifications.xml" "C:\Users\Default\AppData\Local\Microsoft\Windows\Shell"

I have created a Dummy folder location in the Applications folder and put all my custom file\scripts in there, you could substitute %SCRIPTROOT% root for %DEPLOYROOT% if you have got your xml stored in there. Our deployments are pretty much media based and I have had issues with leftover folders if they have been created in the %SCRIPTROOT% folder.

Your powershell script is maybe not working if you did not include the powershell module in your boot wim as the task is running in the WinPE phase. As a side note, I find xcopy to be more consistent when copying files into System olders etc. I am trying to do more with powershell, but if something works, it works.

Ewen.