DotVBS | Windows Systems Management

The End of an Era: VBScript, WMIC, and the "Feature on Demand" Future of Windows Server 2025

2025-12-09T08:02:00.000-08:00

For nearly two decades, the safety net of any Windows Administrator was the assumption that "it's just built-in." No matter how locked down a server was, you could always count on Notepad, Calculator, and the Windows Scripting Host (CScript/WScript) being there. With the release of Windows Server 2025 last year, that assumption is officially dead. Now that many organizations are moving past the

From .vbs to .ps1: Why We Are Still Talking About VBScript in the Cloud Era (And How to Finally Let Go)

2025-12-07T08:11:00.000-08:00

It has been a long time since the golden era of SMS 2003 and SQL Server 2005. If you are reading this on DotVBS, you likely landed here for one of two reasons. First, you might be maintaining a legacy environment that simply refuses to die. You have a server rack somewhere running an OS that hasn’t seen a patch in a decade, and a critical login script just failed. You needed that specific WMI

Reading the SCCM Client GUID

2012-03-27T15:43:00.002-07:00

Recently I encountered an issue with the SCCM client GUID missing from the %windir%\SMSCFG.INI file. We wanted to write a script to put the GUID back, so I was asked how to read the SCCM Client GUID from a script or command line. VBScript: Set objWMIService = GetObject("winmgmts:\\.\root\ccm") Set colItems = objWMIService.ExecQuery("Select ClientID From CCM_Client")

How to Troubleshoot SMS Client Install Errors

2008-11-06T13:59:00.000-08:00

Often time, I'm asked how to troubleshoot SMS client installation errors. First thing I would recommend is to check WMI by running wmidiag.vbs on the troubled computer, be sure to run it under admin context. The beauty of wmidiag is, it tells you how to fix the problem. Secondly, if WMI is fine, look through the installation or client logs. About the Author

SMS SQL for Last Hardware Inventory

2008-08-05T20:33:00.000-07:00

The following SQL Query will return last HW Inventory date for a specific computer. Code is based on the client health queries by Paul Thomsen. -- Last hardware inventory select Name0, LastHWScan as 'HW Inventory' from v_R_System sys full join v_RA_System_SMSAssignedSites ass ON ass.resourceID=SYS.resourceID full join v_GS_WORKSTATION_STATUS WS ON WS.resourceID=sys.resourceID where

SMS SQL for Last Discovery

2008-08-01T21:31:00.000-07:00

The following SQL Query will return last discovery date for a specific computer. Code is based on the client health queries by Paul Thomsen.-- Last discovery dateselect Name0, AgentTime as 'Discovery'from v_R_System sys full join v_RA_System_SMSAssignedSites ass ON ass.resourceID=SYS.resourceID full join (select ResourceId, MAX(AgentTime) as AgentTime from v_AgentDiscoveries where agentname<>'SMS

VBScript to Set SMS Client Cache Location

2008-07-24T17:05:00.000-07:00

Need to set the SMS Client Cache Location? Well it's pretty easy, here's a basic VBScript to help you get started. This will set the Advanced Clients Cache Location, just be careful to set it correctly. Test, Test, Test! I'd suggest an SMS Package with different cache locations passed via command line (in seperate programs) for maximum flexibility. ---- Begin VBScript ----On Error Resume NextDim

SMS SQL for Duplicate Collection Names

2008-07-23T21:49:00.000-07:00

Recently, I've found many collections with duplicate names. The dupes can cause problems when managing those collections. I quickly created the following SQL to find the offending collections.-- This SQL query will show collections with duplicate names.Select parentCollectionID, ParentCollection.Name, v_Collection.CollectionID, v_Collection.Name from v_Collectionleft outer

SMS 2003 Error 10035, What to Do

2008-07-05T08:17:00.000-07:00

Error 10035, or Waiting for Content, seems to be one of the most frequent errors people encounter. Clients often generate this error even when they succeeed. When things go bad, it's important to understand how to troubleshoot error 10035, and know how to fix it.How to troubleshoot 10035 Waiting for Content ErrorsList of Status Message IDs About the Author

SMS SQL for Program Failed Run Time Exceeded 10070

2008-07-05T08:11:00.000-07:00

To create a query or collection of SMS clients which return a status of 10070, or program failed due to the runtime being exceeded, use the following WQL (replace advertID with your advertisement ID): select stat.*, ins.*, att1.*, att1.AttributeTime from SMS_StatusMessageasstat left joinSMS_StatMsgInsStrings as ins on stat.RecordID = ins.RecordID left joinSMS_StatMsgAttributes as att1on

SMS "Program failed (run time exceeded)" 10070

2008-07-05T08:05:00.000-07:00

When a program fails due to error 10070, it does so because the Run Time was Exceeded. SMS Allows a program to run for 12 hours, afterwhich it will issue the failed status message if the program hasn't completed successfully.Note: The Maximum allowed run time within program properties is generally a guide for users running the program themselves, and is not enforced. About the Author

Rename an SMS Site

2008-06-18T13:56:00.000-07:00

Not long ago, I had to rename an SMS Site, here are the steps I used, from Jase T. Wolfe's blog.If an SMS Primary Site server, stop the SMS_SITE_COMPONENT_MANAGER, SMS_EXECUTIVE, SMS_SERVER_LOCATOR_POINT, and SMS_SQL_MONITOR services.If an SMS Secondary Site server, stop the SMS_SITE_COMPONENT_MANAGER and SMS_EXECUTIVE services.Open the "\SMS\inboxes\sitectrl.box\sitectrl.ct0" site control

Scriptomatic Becomes Self Aware

2008-06-18T13:52:00.000-07:00

Well, not quite, but the scripting guys would prob add that feature if they could. The script-o-matic is a priceless tool that helps create a variety of scripts. Including making WMI easy for the WMI Challenged.Download Scriptomatic from Microsoft. About the Author Emmanuel Tsouris is a Systems Management veteran and Developer Advocate

SQL 2000 Support End is Near

2008-06-18T13:48:00.000-07:00

Have you upgraded your SMS SQL 2000 installations yet?With the end of SQL 2000 support just around the corner, now is a good time to move if you havn't already. Check out Brian Tucker's blogcast on upgrading. About the Author Emmanuel Tsouris is a Systems Management veteran and Developer Advocate specializing in PowerShell and Cloud

SMS System Health: SQL Performance Counters

2008-06-18T13:45:00.000-07:00

When examining your SMS Systems health, a few good counters to look at include the following: Memory Physical Disk Processor Access Methods Buffer Manager Cache Manager Databases General Stats Latches Locks Memory Manager SQL Stats SQL Settable Also take a look at the SMS operations Guide, which talks about the cache hit ratio. About the Author

SQL Reporting Services and SCCM R2

2008-06-12T23:27:00.000-07:00

I can't wait to try out reporting services in SCCM R2, for those of you with very large SMS and SCCM installations, this will hopefully bring a bit of relief from the old ASP SMS Web Reporting. One particular feature I'm eager to try out, is the conversion tool which will convert SMS Web Reports into Reporting Services Reports.Get the SCCM R2 Beta from Microsoft Connect About the Author

Configuration Manager 2007 Videos

2008-02-12T09:32:00.000-08:00

Check out the SCCM 2007 videos on the Blogcast Repository. About the Author Emmanuel Tsouris is a Systems Management veteran and Developer Advocate specializing in PowerShell and Cloud Automation. He maintains DotVBS to preserve legacy knowledge for the "archaeologist admin." Ready to

SMS Client Health Monitor Tool: Inactive

2008-02-02T19:49:00.000-08:00

Brian Tucker demonstrates how to find inactive clients in SMS 2003 using the Client Health Monitoring Tool. About the Author Emmanuel Tsouris is a Systems Management veteran and Developer Advocate specializing in PowerShell and Cloud Automation. He maintains DotVBS to preserve legacy knowledge for the "archaeologist admin."

SMS WQL for All Clients where Last Status is Waiting for User Condition

2008-02-02T19:45:00.000-08:00

select sys.ResourceID,sys.ResourceType,sys.Name,sys.SMSUniqueIdentifier,sys.ResourceDomainORWorkgroup,sys.Client from SMS_R_System as sys join SMS_ClientAdvertisementStatus as stat on sys.ResourceID=stat.ResourceIDwhere stat.AdvertisementID='advertisementID' and stat.LastStatusMessageID=10036--10036 is Waiting for User Condition, replace advertisementID with your advertisement ID. About

SMS "Waiting for User Condition" 10036

2008-02-02T19:39:00.000-08:00

Status Message ID 10036, or "Waiting for User Condition" can occasionally grind advertisements to a halt. Make sure the environment and user condition settings for a particular program have been configured appropriately and are not excluding a large portion of your intended audience.Related ArticlesSMS WQL for All Clients where Last Status is Waiting for User Condition SMS Status Message ID's

SMS "Waiting for content" 10035

2008-02-02T19:29:00.000-08:00

Status Message ID 10035, or "Waiting for content" is a common error which can drive you up the wall when testing a package deployment.Have you checked your site boundaries? Often a client is located in a IP Subnet which hasn't been configured within Site or Roaming Boundaries.Has the software been deployed to the clients local DPs? Check the reports and console, make sure the package has been

SMS SQL for Collections with Duplicate Names

2008-02-02T19:21:00.000-08:00

/* The following SQL will display any collections which appear to have a duplicate name. In some cases this may be normal, however this is a good way to find problems and inconsistencies.*/SELECT col.[CollectionID],[Name],[parentCollectionID],[Comment],[OwnedByThisSite],[ReplicateToSubSites],[LastChangeTime],[LastRefreshTime],[RefreshType],[CurrentStatus],[MemberClassName],[

Response_Buffer_Limit_Exceeded

2008-01-23T20:44:00.000-08:00

With large SMS Systems, it's common to exceed the response buffer limit when running certain SMS Web Reports.Microsoft provides this article regarding the problem.http://support.microsoft.com/kb/925764To max out the buffer, basically set the aspbufferinglimit to -1 About the Author Emmanuel Tsouris is a Systems Management veteran and

SMS WQL for All Clients where Last Status is Time Exceeded

2007-09-29T16:52:00.000-07:00

select sys.ResourceID,sys.ResourceType,sys.Name,sys.SMSUniqueIdentifier,sys.ResourceDomainORWorkgroup,sys.Client from SMS_R_System as sys join SMS_ClientAdvertisementStatus as stat on sys.ResourceID=stat.ResourceIDwhere stat.AdvertisementID='advertisementID' and stat.LastStatusMessageID=1007010070 is Time Exceeded, replace advertisementID with your advertisement ID. About the Author

SMS Status Message IDs

2007-09-29T16:51:00.001-07:00

10050 Cache too small10061 Download failed (retrying)10003 Failed (bad environment)0 No messages have been received10054 Not enough space in cache10045 Not enough space in cache10034 Program cancelled by user10022 Program completed successfully (reboot pending)10009 Program completed with success10008 Program completed with success10004 Program