syswow64 blog

To provide a resource for the IT community.

Change the drive used for offline servicing of OSD images Offline Servicing OSD images wihin SCCM is a useful feature.  I have heard SCCM Professional say it is good and bad but this post is is specifically around changing the default location used to stage the Windows image. By default SCCM will use the drive in which the Configuration Manager is installed (i.e. Drive E) even if it is running low on diskspace.  But assuming you have a new drive F: with plenty of space the procedure below will details how to change this. Assuming your site code is P01 Launch wbemtest.exe and connect to:  root\sms\site_P01 Click Query and enter: SELECT * FROM SMS_SCI_Component WHERE SiteCode=’P01’ AND ItemName LIKE ‘SMS_OFFLINE_SERVICING_MANAGER%’ Double click the  query result Double click Props (Scroll down second from bottom) Click View Embedded There will be four entries listed. Through a process of trial and error double click each one looking for PropertyName field "Staging...

Change the drive used for offline servicing of OSD images Offline Servicing OSD images wihin SCCM is a useful feature.  I have heard SCCM Professional say it is good and bad but this post is is specifically around changing the default location used to stage the Windows image. By default SCCM will use the drive in which the Configuration Manager is installed (i.e. Drive E) even if it is running low on diskspace.  But assuming you have a new drive F: with plenty of space the procedure below will details how to change this. Assuming your site code is P01 Launch wbemtest.exe and connect to:  root\sms\site_P01 Click Query and enter: SELECT * FROM SMS_SCI_Component WHERE SiteCode=’P01’ AND ItemName LIKE ‘SMS_OFFLINE_SERVICING_MANAGER%’ Double click the  query result Double click Props (Scroll down second from bottom) Click View Embedded There will be four entries listed. Through a process of trial and error double click each one looking for PropertyName...

1.       If you embed the following script into the task sequence (new command line with package) it will output all variables and you can confirm the value applied. http://deploymentresearch.com/Research/Post/475/List-Task-Sequence-Variables-in-SCCM-2012 cscript EnumTSVariables.vbs > X:\Result.txt ‘Script Dim oTSEnv Set oTSEnv = CreateObject("Microsoft.SMS.TSEnvironment") Dim oVar For Each oVar In oTSEnv.GetVariables     WScript.Echo " "     WScript.Echo "  "& oVar & vbTab & oTSEnv(oVar) & vbTab Next

1.       If you embed the following script into the task sequence (new command line with package) it will output all variables and you can confirm the value applied. http://deploymentresearch.com/Research/Post/475/List-Task-Sequence-Variables-in-SCCM-2012 cscript EnumTSVariables.vbs > X:\Result.txt ‘Script Dim oTSEnv Set oTSEnv = CreateObject("Microsoft.SMS.TSEnvironment") Dim oVar For Each oVar In oTSEnv.GetVariables     WScript.Echo " "     WScript.Echo "  "& oVar & vbTab & oTSEnv(oVar) & vbTab Next

System.Net.WebException: The request failed with HTTP status 404: Not Found.~~   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber) Overview: I was recently working with a customer who was receiving a HTTP 404 error in the WCM.log. Confirmed the following ports are open (80,443,135,445,8530,8531) WSUS sites are accessible via URL HTTP Boundaries and Boundary groups for content and site assignment are configured correctly for DEV domain. Distribution Point and Management Point roles are fully functionality WSUS on Server2.dev.local manually synchronized from the Internet Remote Registry and remote WMI tested with success. Lab Environment Expected behaviour: In my lab environment I have two forests/domains “Contoso.local” and “DEV20.local”; untrusted; Windows firewall ON with default values. I have added the Site S...

System.Net.WebException: The request failed with HTTP status 404: Not Found.~~   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber) Overview: I was recently working with a customer who was receiving a HTTP 404 error in the WCM.log. Confirmed the following ports are open (80,443,135,445,8530,8531) WSUS sites are accessible via URL HTTP Boundaries and Boundary groups for content and site assignment are configured correctly for DEV domain. Distribution Point and Management Point roles are fully functionality WSUS on Server2.dev.local manually synchronized from the Internet Remote Registry and remote WMI tested with success. Lab Environment Expected behaviour: In my lab environment I have two forests/domains “Contoso.local” and “DEV20.local”; untrusted; Windows firewall ON with default values. ...