Reporting service Point in SCCM can be really handy sometimes, when you need to lookup something in a AD domain. Specially when you will see how an deployment has been running.

I discover something strange on a customer’s reporting services. The SSRP Service has been created Loads of Folders with name ConfigMgr_SiteCode.OLD.0 And when I tried to Select every folders and remove them, the internet explorer hanged itself.


old reports

So I created this powershell script to remove all OLD folders.

Remove SCCM Reporting Services Folders ConfigMgr_SiteCode.OLD.*

This Script will help us to remove SCCM Reporting Services folder, that has name ConfigMgr_SiteCode.OLD.*


Enter the ConfigMgr Site Server Name:

Enter the Sitecode:



# Get data
$ConfigMgrServerName = Read-Host("Enter the ConfigMgr Site Server Name")
$ConfigMgrSiteCode = Read-Host("Enter the sitecode")

# Connect to Reporting Services
$URL = ("http://" + $ConfigMgrServerName + "/ReportServer/ReportService2005.asmx?WSDL")
$ConnectToReportService = New-WebServiceProxy -Uri $URL -UseDefaultCredential

# Get all report folders
$RemoveOldReportFolders = $ConnectToReportService.ListChildren("/", $True)

# Remove all Folder with name ConfigMgr_SiteCode.OLD.*
$RemoveOldReportFolders | Where-Object {$_.Name -like ("ConfigMgr_" + $ConfigMgrSiteCode + ".OLD.*")} | ForEach-Object {$ConnectToReportService.DeleteItem($_.Path); "Deleted Folder: " + $_.Name}

The Result:
old reports after

Windows To Go
lets you to boot and run Windows 8 (Enterprise) from a USB stick as well as allowing you to connect to your corporate infrastructure from that image.

So how to deploy Windows To Go in your organization?

Peter Daalmans (MVP in System Center Configuration Manager) has published a blog article in three parts about how to deploy Windows To Go (onto a Ironkey Workspace W500) using SCCM 2012.

Windows To Go, Ironkey and SCCM 2012 R2 better together – part 1
Windows To Go, Ironkey and SCCM 2012 R2 better together – part 2
Windows To Go, Ironkey and SCCM 2012 R2 better together – part 3

As an alternative, Mikael Nystrom has posted a comprehensive blog post about Deploying Windows To Go devices using PowerShell. He generously published the script as well. Thanks Mikael!

Happy deploying 2014!

During the installation of the new System Center Configuration Manager 2012 with Microsoft SQL Server 2012 I got the following error and the installtion couldn´t continue.

ERROR: Failed to get SID for user (NT Service\MSSQLSERVER)
ERROR: Failed to get the buffer size for LookupAccountName. Error= 1722


To fix it: I creat a domain account that has administrative right on the server and change the service account that the SQL services are running with to it and ran the setup again. This time it finished with no errors.

Här kommer lite information och tips hur man går tillväga att testa applikationer som system-konto.

1. Ladda hem verktyg PSTOOLS och packa upp till en mapp –

2. Ta PSTOOLS mappen och klistra in den på system disk C:\

3. Starta Kommandotolken som administratör

4. gå till PSTOOLS mappen. C:\PSTOOLS

5. Kör följande verktyg PSEXEC.EXE -i -d -s cmd <Tryck Enter>

6. Nu kommer en villkorsruta upp. <Tryck på knapp Agree>

7. Nu kommer en till kommandotolken fönster upp. Nu kan du testa din applikation i det nya kommandotolken fönstret som körs som System.

Mastering System Center 2012 Configuration Manager (SCCM)

The latest version of System Center Configuration Manager (SCCM) is a dramatic update of its predecessor Configuration Manager 2007, and this book offers intermediate-to-advanced coverage of how the new SCCM boasts a simplified hierarchy, role-based security, a new console, flexible application deployment, and mobile management. You’ll explore planning and installation, migrating from SCCM 2007, deploying software and operating systems, security, monitoring and troubleshooting, and automating and customizing SCCM 2012 with scripts.