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: