Life of a techno-guru
Thursday, September 25, 2008
Retrieving a list of SCCM SP1 compatible vPro /AMT clients
If you're running System Center Configuration Manager 2007 SP1 and you have the ConfigMgr client deployed, and you have Intel vPro clients, you may want to know how many clients you have. Here is a quick script that you can use to get a list of Intel vPro clients that are running AMT firmware version 3.2.1 or greater, and are natively supported by ConfigMgr OOB (out-of-band) management. Replace the SiteServer and SiteCode variables, and you'll be good to go!
Option Explicit
dim SiteServer, SiteCode, AMTQuery, svcs, AMTAgent, AMTAgents
SiteServer = "SCCMServer"
SiteCode = "LAB"
AMTQuery = "select * from SMS_G_System_AMT_Agent " & _
"join SMS_G_System_Computer_System on SMS_G_System_AMT_Agent.ResourceID = SMS_G_System_Computer_System.ResourceID " & _
"where AMT not like '3.0%' " & _
"and AMT not like '2%' " & _
"and AMT not like '1%' "
set svcs = GetObject("winmgmts:\\" & SiteServer & "\root\sms\site_" & SiteCode)
set AMTAgents = svcs.ExecQuery(AMTQuery)
for each AMTAgent in AMTAgents
wscript.echo AMTAgent.SMS_G_System_Computer_System.Name & vbtab & AMTAgent.SMS_G_System_Computer_System.Model & vbtab & AMTAgent.SMS_G_System_AMT_Agent.AMT
next
wscript.echo vbcrlf & vbcrlf & "Total count of ConfigMgr SP1 compatible vPro clients: " & AMTAgents.Count ¶ 3:51 PM 0 comments
Option Explicit
dim SiteServer, SiteCode, AMTQuery, svcs, AMTAgent, AMTAgents
SiteServer = "SCCMServer"
SiteCode = "LAB"
AMTQuery = "select * from SMS_G_System_AMT_Agent " & _
"join SMS_G_System_Computer_System on SMS_G_System_AMT_Agent.ResourceID = SMS_G_System_Computer_System.ResourceID " & _
"where AMT not like '3.0%' " & _
"and AMT not like '2%' " & _
"and AMT not like '1%' "
set svcs = GetObject("winmgmts:\\" & SiteServer & "\root\sms\site_" & SiteCode)
set AMTAgents = svcs.ExecQuery(AMTQuery)
for each AMTAgent in AMTAgents
wscript.echo AMTAgent.SMS_G_System_Computer_System.Name & vbtab & AMTAgent.SMS_G_System_Computer_System.Model & vbtab & AMTAgent.SMS_G_System_AMT_Agent.AMT
next
wscript.echo vbcrlf & vbcrlf & "Total count of ConfigMgr SP1 compatible vPro clients: " & AMTAgents.Count ¶ 3:51 PM 0 comments
Wednesday, September 10, 2008
Testing OSD in Configuration Manager (ConfigMgr) 2007
If you are developing and testing your ConfigMgr 2007 OSD process, and you're running into a message saying "There are no task sequences available for this computer," then you might not want to have to completely reboot WinPE to restart the process.
After you fix your task sequence / policy problem, you can restart the task sequence engine / wizard without exiting WinPE. Here's how:
1. Enable the F8 command prompt in your Boot Image
2. When the wizard fails in PE, press F8 to invoke the command prompt
3. Run task manager by typing "taskmgr"
4. Kill the process named "TsmBootStrap.exe"
5. Start "TsBootShell.exe" (note the name difference) from the "x:\sms\bin\i386" folder
The task sequence wizard should restart!
NOTE: Do not kill the main instance of TsBootShell.exe! This will disable WinPE and force you to reboot into it!
¶ 9:49 AM 0 comments
After you fix your task sequence / policy problem, you can restart the task sequence engine / wizard without exiting WinPE. Here's how:
1. Enable the F8 command prompt in your Boot Image
2. When the wizard fails in PE, press F8 to invoke the command prompt
3. Run task manager by typing "taskmgr"
4. Kill the process named "TsmBootStrap.exe"
5. Start "TsBootShell.exe" (note the name difference) from the "x:\sms\bin\i386" folder
The task sequence wizard should restart!
NOTE: Do not kill the main instance of TsBootShell.exe! This will disable WinPE and force you to reboot into it!
¶ 9:49 AM 0 comments
