Advertisements
TRENDING

Deploying a Customized Windows 10 Start Menu with MDT 2013

windows_10_start_menu_featured_img

When deploying Windows with MDT you want to customize everything during deployment. One customization that many system admin want to do during deployment is changing the way the Start Menu from Windows 10 looks. Check out the steps below to configure your next deployment to have a custom Start Menu.

Step 1: Open the Start Menu:

Step 2: Remove or Add items to the Start Menu:

Step 3: Open the command prompt as an Admin and create a folder. I placed my folder within the C drive, so I did a command of “mkdir c:\layout“:

Step 4: Once the folder is created you will have to get into PowerShell command, so type in “powershell” and hit enter:

Step 5: In the PS(PowerShell) command type in the following – export-startlayout -path c:\layout\layoutmodification.xml – Note: the folder path will be different on your part and you can call the *.xml file whatever name you want.

Step 6: I created a custom Run Command Line task to copy the *.xml file to the Windows temp folder.  %SCRIPTROOT%\BTNHD\StartMenu\LayoutModification.xml c:\Windows\Temp

Step 7: Create a PowerShell Script custom task to call out the PowerShell script: %SCRIPTROOT%\BTNHD\StartMenu\ApplyCustomMenu.ps1 (look at Step 8 for the ApplyCustomMenu.ps1 code)

Step 8: Within the ApplyCustomMenu.ps1 file will contain the following code: import-startlayout -layoutpath c:\Windows\Temp\LayoutModification.xml -MountPath $env:SystemDrive\

 

Advertisements
About BjTechNews (906 Articles)
An IT guy trying to learn everything about technology and sharing it with you all. I'm a blogger and video blogger who highlights daily news in the tech industry, promoting tips and hacks for fellow techies.

3 Comments on Deploying a Customized Windows 10 Start Menu with MDT 2013

  1. Abul Muzzaffer // August 24, 2016 at 11:44 am // Reply

    Hi,
    I have a question for you. It may be a sort of stupid question. Please bear with me. I am a novice user. I am trying to understand WDS and MDT2013. I have followed your videos for quiet some time and want to tell you, you are awesome. You are the best in the industry. Your videos are the best the best. In about 3 – 4 hours, I was able have build a full fledged MDT server with various OSs, Drivers, Applications, etc…. you name it I got it. (MDT Build , MDT Production, MDT Capture ….)

    Well to start with, let me give you a brief outline.

    I have updated my MDT server after adding OS and drivers and creating a task sequence. I have updated my WDS server with the latest Lite TouchPE_x64.wim and Lite TouchPE_x86.wim. I have restarted the WDS services. After this I am deleting both Lite Lite TouchPE_x64.wim and TouchPE_x86.wim files from MDTProduction\boot folder.

    My question is will I still be able to PXE boot and get an image?
    What is the actual role of WDS. I read it helps in PXE booting. That it is the vehicle for reaching the MDT server and asking for an image.
    I have checked in RemoteInstall folder for a PXE boot image. I couldn’t see anything there. Then how am I able to PXE boot and get an image? It is working for me.

    Many thanks for your patience and time.
    Hoping to hear from you soon.

    With warm regards
    Abul Muzzaffer.

  2. One thing I ran into was that I originally tried to use the CopyProfile setting in the Unattend.xml file. I found that these steps don’t work unless you turn that off! Hopefully this helps someone avoid my mistake.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s