syswow64 blog

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...

The script below will check if you have a version of SQLServer insalled and Echo the Edition Skuname and process Architecture.  This is particulary useful if you deem SQL Server on workstations to be a non-compliant trigger.  Now you can validate whether the echoed line is not allowed i.e SQL Server Enterprise On Error Resume Next ' First try SQL Server 2008/2008 R2: Set objWMIService = GetObject("WINMGMTS:\\.\root\Microsoft\SqlServer\ComputerManagement10") If Err.Number <> 0 Then     ' Next, try SQL Server 2005:     Set objWMIService = GetObject("WINMGMTS:\\.\root\Microsoft\SqlServer\ComputerManagement")     If Err.Number <> 0 Then         ' Next, try SQL Server 2012:         Set objWMIService = GetObject("WINMGMTS:\\.\root\Microsoft\SqlServer\ComputerManagement11")     End If End If Set colItems = objWMIService.ExecQuery( _ ...

The script below will check if you have a version of SQLServer insalled and Echo the Edition Skuname and process Architecture.  This is particulary useful if you deem SQL Server on workstations to be a non-compliant trigger.  Now you can validate whether the echoed line is not allowed i.e SQL Server Enterprise On Error Resume Next ' First try SQL Server 2008/2008 R2: Set objWMIService = GetObject("WINMGMTS:\\.\root\Microsoft\SqlServer\ComputerManagement10") If Err.Number <> 0 Then     ' Next, try SQL Server 2005:     Set objWMIService = GetObject("WINMGMTS:\\.\root\Microsoft\SqlServer\ComputerManagement")     If Err.Number <> 0 Then         ' Next, try SQL Server 2012:         Set objWMIService = GetObject("WINMGMTS:\\.\root\Microsoft\SqlServer\ComputerManagement11")     End If End If Set colItems = objWMIService.ExecQuery...