ConfigMgr WebService – Version 1.6.0 released

We’re proud to announce the release of ConfigMgr WebService 1.6.0.

NOTE – If you’re using ConfigMgr OSD FrontEnd together with ConfigMgr WebService, wait for ConfigMgr OSD FrontEnd 1.4.0 to be released before you upgrade to ConfigMgr WebService 1.6.0.

What’s new

Below is a list of the added web methods in this release, divided by product:

Configuration Manager

  • GetCMOSImageForTaskSequence
  • GetCMDeviceUUIDByName
  • GetCMTaskSequence
  • RemoveCMDeviceByUUID
  • RemoveCMDeviceByName
  • RemoveCMDeviceByResourceID

Microsoft Deployment Toolkit

  • GetMDTComputerByName
  • RemoveMDTComputerBySerialNumber

Active Directory

  • GetADComputerDescription
  • GetADOrganizationalUnits
  • GetADDomain
  • GetADGroupMemberByComputer

Download ConfigMgr WebService

In order to get your hands on the bits for this web service, you have some options. You can download the source code from our GitHub page, and compile the web service yourself. For installation instructions, follow what’s outlined in the file in the repository. You can visit our GitHub page from the link below:

The second option is to download a compiled version of the web service, ready for use. This version can be downloaded from the URL below:

ConfigMgr WebService 1.6.0

We’ve published the source code for the purpose of making it available for those organisations that cannot leverage untrusted publishers, but also if you’d want to get your hands dirty and have a look at it.

Update instructions

If you already have ConfigMgr WebService installed in your environment, you can update it simply by replacing the ConfigMgrWebService.dll file in the bin folder of where you’ve placed the web service files. Please note though, that since version 1.1.0, three new Application Settings was introduced that you need to add manually, or replace the web.config file with the existing one and re-enter the values for each application setting.

If ConfigMgr WebService has been installed by using the included wizard driven installation, run the wizard again and the upgrade process will begin. From version 1.4.0 and onwards, the upgrade experience has improved and previously configured values will now be populated automatically within the wizard. See the documentation embedded in the download package from TechNet Gallery for more information.

Installation instructions

Please refer to the ConfigMgr WebService 1.6.0 – Installation Guide PDF attached in the download package.


Also attached in the download package is the documentation for each method currently available in the latest version of ConfigMgr WebService. Please refer to ConfigMgr WebService 1.6.0 – Documentation PDF for more information.

Nickolaj Andersen

Chief Technical Architect 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. 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 such as Microsoft Ignite, NIC Conference and IT/Dev Connections including nordic user groups.


  • Hi Nickolaj

    Thanks for creating this solution. It’s going to make driver administration so much easier and am looking forward to trying out the OS driver update feature.

    The auto install didn’t work for me, failing at ‘configuring iis…’ but got it up and running with the manual install instructions. Thanks for providing those.

    For anyone else who comes across this problem: I had some trouble with the service account the ConfirMgrWebService application pool runs under. After receiving “An error occured while calling ConfigMgr WebService for a list of available packages” I change the service account to Local System and provided read rights on the ConfigMgrWebService folder to the computer account. This resolved the problem.

  • I thought I had already commented here, but it seems to have disappeared 🙁
    I really appreciate the stuff you guys are doing for SCCM, but I current have a problem with the OSD FrontEnd, but I think the cause is the web service. It seems that while methods like GetCMApplication work, GetCMTaskSequence just returns
    PackageName :
    PackageID :
    AdvertisementId :
    AdvertFlags : 0
    Description :
    BootImageID :
    and GetCMHiddenTaskSequenceDeployments returns nothing. This is stopping OSD FrontEnd from returning task sequences to deploy. Out of interest GetCMPackage also returns no data.

    We are running SCCM 1806 – is this the reason, or have we broken something? I’d really like ot get this working as it will really assist our Windows 10 rollout.



Categories use cookies to ensure that we give you the best experience on our website.