Modify the Windows 8.1 Start screen during OSD in ConfigMgr 2012
The new Start screen that came with Windows 8 gives users a fast way to access their applications and to search for anything they’d like. The way that Microsoft has pinned applications on the Start screen for the Default User may not suit all organizations, and you may want to change the applications being pinned by default. There are several ways to accomplish that task. In this post I’ll cover one of them where you’d on a Windows 8.1 system start of with modifying the Start screen as you wish and then copy the appsFolderLayout.bin (a file containing the layout) file to your Content Library. We’ll then apply this file during OSD with ConfigMgr 2012 R2.
- Create the Start screen layout
- Create a Package with the appsFolderLayout.bin
- Modify your OSD task sequence
Create the Start screen layout
If you havn’t got a Windows 8.1 system up and running, I suggest that you install a virtual machine in your lab environment to begin with. We’ll use this virtual machine to modify the Start screen layout and to grab the appsFolderLayout.bin file. Make sure that the virtual machine has network connectivity so you’re able to copy the file to a network share. Here’s how I’ve modified it for this post:
You now have two options on how to get your hands on the file containing the Start screen layout:
- Using sysprep
- Using PowerShell
Choose one the these methods. Both are supported on Windows 8.1.
1. On the virtual machine that you have modified the Start screen layout on, open an elevated PowerShell console.
2. Run the following command (change the path if necessary):
Export-StartLayout -As Bin -Path C:\Temp\appsFolderLayout.bin
3. You should now have a file called appsFolderLayout.bin in C:\Temp.
4. Copy the appsFolderLayout.bin to your Content Library folder.
1. Open an elevated command prompt on the virtual machine and browse to C:\Windows\System32\Sysprep.
2. Run the following command:
sysprep.exe /audit /reboot
The system will now reboot. Log in (if necessary) when it’s back up.
3. Open Windows Explorer and browse to:
C:\Users\<username>\AppData\Local\Microsoft\Windows (replace <username> with the logged on user name).
4. You should now see the appsFolderLayout.bin file. Copy this file to your a folder in your Content Library, e.g. \\CM01\ContentLibrary$\OSD\StartScreen.
Create a Package with the appsFolderLayout.bin
1. On your Primary Site server, open the ConfigMgr console and create a new Package.
2. Call the new package something like Start Screen Layout – Windows 8.1 Enterprise x64.
3. Enter the path to the folder where the appsFolderLayout.bin file is stored in the Source folder field. See the picture below how I’ve configured it:
4. Do not create a program for the package.
5. Finish the wizard and then distribute the package to your Distributions Points.
Modify your OSD task sequence
1. Edit your task sequence used for deploying Windows 8.1.
2. Add a Run Command Line step somewhere after the Setup Windows and Configuration step.
3. Call it something like Start Screen Layout modification.
4. As the Command line, enter the following:
xcopy appsFolderLayout.bin "%SystemDrive%\Users\Default\AppData\Local\Microsoft\Windows" /Q /Y
5. Put a check mark in the Package box and browse for the package that you created earlier containing the appsFolderLayout.bin file.
6. Apply the changes in your task sequence.
7. Start a new deployment of a system and let it complete.
8. Log on with a user account in your domain. The Start screen should now look like your modifications from the virtual machine used earlier.
Principal Consultant and Enterprise Mobility MVP since 2016. Nickolaj has been in the IT industry for the past 10 years specializing in Enterprise Mobility and Security, Windows devices and deployments including automation. Currently working for TrueSec as a Principal Consultant. Awarded as PowerShell Hero in 2015 by the community for his script and tools contributions. Creator of ConfigMgr Prerequisites Tool, ConfigMgr OSD FrontEnd, ConfigMgr WebService to name a few. Frequent speaker at conferences and user groups.