08 May

Capture Image Pane Bug in Microsoft Deployment Toolkit 8443

As many individuals within the realm of operating system design and deployment know, Microsoft has moved to a new release schedule for Windows 10. As a result, many of the other tools and components are also falling in line with the new release schedule. This includes Assessment and Deployment Kit as well as Microsoft Deployment Toolkit. Both are essential to building Windows images outside of System Center Configuration Manager. Unfortunately, Microsoft Deployment Toolkit version 8443 has a bug that prevents you from seeing the capture image pane during the Lite Touch phase of the deployment process.

As you can see below, a normal Microsoft Deployment Toolkit interface will include Capture Image unless it is set to disabled in the CustomSettings.ini file. However, in 8443, even with the Capture Image pane enabled, it still doesn’t appear.

To correct this, open ZTIUtility.vbs in Notepad, located in the scripts directory of your deployment share. Search for the below code:

If (oTS.SelectSingleNode("//step[@type='BDD_InstallOS']") is nothing) and (oTS.SelectSingleNode("//step[@type='BDD_UpgradeOS']") is nothing) then

Replace this code with the following:

If (oTS.SelectSingleNode("//step[@type='BDD_InstallOS' and @disable='false']") is nothing) and (oTS.SelectSingleNode("//step[@type='BDD_UpgradeOS' and @disable='false']") is nothing) then

Save the file, rebuild your ISO, and then you will be able to capture an image!

11 Apr

Change BIOS to UEFI Using System Center 1610

We all know how painful it is to switch your desktop fleet from BIOS to UEFI. Until now, it has been a manual process. Microsoft introduced BIOS to UEFI conversion within SCCM 1610. This is a huge win as it allows technicians to stay hands off during a Windows 10 conversion. Check out the link below for more information on how to implement BIOS to UEFI with SCCM 1610.


Please note, you will still need the tool from each OEM that you have purchased hardware from to perform the actual conversion.

31 Mar

SCCM Management Point Shows Error 500 After Removing WSUS

Let me guess? You uninstalled the Software Update Point from SCCM and removed WSUS from the server… now your SCCM Management Point, which was likely on the same server as WSUS, is showing critical in SCCM and reporting IIS 500 errors within the SCCM logs. When uninstalling WSUS, sometimes the configuration information does not get removed from the IIS ApplicationHost.Config file. Because of this, IIS shows error 500 when it cannot locate suscomp.dll.

You can test this theory by opening Internet Explorer and browsing to http://[mpservername]/SMS_MP/.sms_sut?mplist. If you are able to successfully browse to this address, you will see an XML file with a list of management points. If, instead, you see an IIS 500 error, you can check to see if this is your issue.

Taking a look at ApplicationHost.Config, you will find the below entry:

<scheme name=”xpress” doStaticCompression=”false” doDynamicCompression=”true” dll=”C:\Program Files\Update Services\Webservices\suscomp.dll” staticCompressionLevel=”10″ dynamicCompressionLevel=”0″ />

In order to remove this entry from IIS, open Command Prompt as an administrator and enter the below command:

%windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /-[name='xpress']

Once this command is run, a confirmation of the removal will be displayed. Go back to http://[mpservername]/SMS_MP/.sms_sut?mplist and confirm that you see the XML file. If you do, your Management Point is back up!

28 Feb

Resurrection of the Tech Blog!

After neglecting the site for 2 years I decided to start from scratch and rebuild the site as a tech blog. Tons of articles to come!