Deploy RSAT (Remote Server Administration Tools) for Windows 10 1809 via SCCM – Installer

Beginning with 1809 the installation of the RSAT (Remote Server Administration Tools) changed. It’s no longer a separat download instead it’s now included in “Feature on Demand” and downloads it directly from Microsoft. You can install the features now as optional feature in the settings menu. But in my tests this is buggy and not very user frindly.  I decided to create my own installer based on the Powershell comands. The tool uses Get-WindowsCapability, Add-WindowsCapability and remove-WindowsCapability.

You can deploy the executable via SCCM. As application or package.

The tool looks like below in my Software-Center:

You can select single RSAT Tools or multiple or select all:


Same way to uninstall one or multiple RSAT Tools.

You can find the download here: click


Copy troubleshooting logs via “run a Script” ConfigMgr 1706

Target: Copy logs to troubleshoot OS-Deployments and Software-Deployments via “run a Script” in ConfigMgr 1706

With the release of ConfigMgr 1706 the feature to run Powershell Scripts was released. Sometimes it can be helpful to copy some logs to troubleshoot the OS-Deployment process or a Software-Deployment process. I created a small script which copys the smsts.log and some of the for me intressing Software-Deployment logs.

First step: create a network share and give everyone full-access.

Afterwards you can go in ConfigMgr to the Scripts section and create your script:


pushd \\server\smstslogs$

new-item $env:computername -ItemType directory -Force


Copy-Item $env:windir\CCM\Logs\smsts* -Force

Copy-Item $env:windir\CCM\Logs\app* -Force

Copy-Item $env:windir\ccmsetup\Logs\ccmsetup* -Force

Copy-Item $env:windir\Logs\Software\* -Force

Save the script – and approve it afterwards:

Then you can run the script against any collection you need / select the collection and select “Run Script”

Select your script and run it against your collection:

The result will look the following / on your network share you will find for each device which is online a new folder and the logs included:


Create Softwarecenter Shortcut in Start Menu via Configmgr

Target: Create Softwarecenter shortcut in start menu for all users and deploy it via Configmgr package

In my previous post I discripted howto create shortcuts in start menu and in the taskbar via Configmgr. In this post I’ll show you an example to create in Windows 10 start menu a shorcut to the softwarecenter of Configmgr.

You can download the package sources from the following link:

The package includes the Pinto10v2.exe and the powershell script to create the shortcut.


Source-Code of the .ps1:

#create shortcut and pinto Start-menu on Windows 10

.\PinTo10v2.exe /pinsm “$env:Homedrive\Windows\CCM\SCClient.exe”

#Rename the Shortcut

Get-ItemProperty “$env:Homedrive\Users\$env:USERNAME\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\SCClient.lnk” | Rename-Item -NewName {$ -replace “SCClient”,”Softwarecenter”} -PassThru

Howto deploy the package.

Create a new package:


With a program – as command line use the .ps1 file. Run the program with user rights:


In the first test you can set the visibility to “Normal” for production deployments set it to Hidden:


Limit the package to Win10:


Distribute the package to the required Distribution-Points. And deploy it the the required collection.

The result will look like below.

Before the script runs:




Create shortcuts in taskbar and start menu on Windows 10 via ConfigMgr

Target: Easily create shortcuts in taskbar and start menu on Windows 10 Professional

I wanted to create a few shortcuts in the taskbar and in the start menu on a few Windows 10 Professional devices.

As we cannot manage the shortcuts with the Windows 10 Professional version – I searched for a solution to manage it via an ConfigMgr package. I found a version of the already known PinTo application which had worked in Windows 7. The new version v2 works also in Windows 10 and the handling is realy easy.

The Sources for the Pinto10v2.exe can be downloaded here / created by Stuart Pearson:

The program is very easy to use - see the syntax below:

Syntax: PinTo10v2 [/pintb | /unpintb | /pinsm | /unpinsm] 'filename'

pintb   = Pin to the Task Bar

unpintb = Unpin from the Task Bar

pinsm   = Pin to the Start Menu

unpinsm = Unpin from the Start Menu


Pin powershell.exe to taskbar:

PinTo10v2.exe /pinsm "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe"

Unpin powershell.exe from taskbar:

PinTo10v2.exe /pintb "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe"

Pin powershell.exe to start menu:

PinTo10v2.exe /pinsm "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe"

Unpin powershell.exe to start menu:

PinTo10v2.exe /pinsm "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe"

In this post I’ll explain how to create a shortcut in the taskbar & start menu for Powershell and Internet Explorer.

First copy the PinTo10v2.exe in a folder and create a .cmd file with the required syntax of the Pinto10v2.exe:



Afterwards I created a package that runs in hidden mode:


Distribute the package afterwards to the required distribution-points. And deploy the package to the required collection.

In my case everything went smooth – start menu and taskbar before:


Start menu and taskbar afterwards:


The PinTo10v2.exe can also be used in powershell-script / for example in the App Deployment Toolkit.

Import “dynamic” start-menu during OSD SCCM

We had the need to import two different start-menus.

One which includes the Office Shortcuts and one without.

But this method you can also use to build your required “dynamic” start layout in Windows 10.

With MS Office installed:




The first step is that you export the two start-layouts with the following command:

export-startlayout –path <path><file name>.xml

Name it for example:




Afterwards create a small powershell script – the scripts copys the IE11 .Ink file and checks if Office 2013 (Office15)

is installed / if yes the start-layout with the Office Icons will be imported if not the default without Office will

be imported.


To Import the IE11 Icon again -> you need to copy also the file to the destination.

In the package place now the Internet Explorer.Ink file plus the two .xml Layouts and the powershell script:


Distribute the package to the required DP’s and you can run the import during the task-sequence:

2017-08-27 16_10_49-Import _dynamic_ start-menu during OSD SCCM - OneNote

Set default file association in windows 10 professional during OSD

Target: Set Internet explorer 11 as default Browser on windows 10 , Set Adobe Reader DC as default PDF-Explorer

On the Windows 10 professional device set your default file applications like you require it:
Afterwards start a command line as administrator and run the following command:
Dism /Online /Export-DefaultAppAssociations:c:\temp\AppAssoc.xml

Opening the xml file you will see that IE11 and Adobe PDF is now the default:

2017-08-27 15_23_19-How To set default file association in windows 10 - Microsoft OneNote

Now copy the AppAssoc.xml on your SCCM-Share and create a package for it / no program required. Distribute the package to the required distribution points.

In my case the package name is “Windows-10-Customizing”:

2017-08-27 15_23_53-How To set default file association in windows 10 - Microsoft OneNote

And the command line to do the import is the following:
Dism.exe /online /Import-DefaultAppAssociations:.\AppAssoc.xml

Then you can run your Windows10 Task-Sequence and you will see that IE11 is now the default web-browser and Adobe PDF the default PDF-Reader.