Configuration Manager 2007 Videos

Check out the SCCM 2007 videos on the Blogcast Repository.

SMS Client Health Monitor Tool: Inactive

Brian Tucker demonstrates how to find inactive clients in SMS 2003 using the Client Health Monitoring Tool.

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

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.

SMS "Waiting for User Condition" 10036

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 Articles

• SMS WQL for All Clients where Last Status is Waiting for User Condition
• SMS Status Message ID's

SMS "Waiting for content" 10035

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 deployed and is available to the clients.

Is the advertisement configured for download and execute? Check the DP, make sure BITS is enabled, and the web site is functioning properly.

Have you checked the logs? Start with the cas.log and execmgr.log on the client computer.

Related Articles

• Clients do not send a status message when an advertised program is disabled in Systems Management Server 2003
• SMS Status Message ID's

SMS SQL for Collections with Duplicate Names

/*
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]
,[LastMemberChangeTime]
FROM v_Collection col
left outer join
v_CollectToSubCollect sub
on col.collectionid = sub.subCollectionid
Where Name in
(
SELECT Name
FROM v_Collection
Group By Name
Having Count(*) > 1
)
order by name, collectionid