Blog Image

Blog - Dries Willems - Freelance IT Consultant

About the blog

The main reason I use this blog, is to help myself tackling similar issues. You can see this as a very small online documentation library.
Also it is useful for others who experience the same issues.

SCCM User/System Query

IT Posted on 01/28/2014 16:31:46

Reminder for myself 😉

Device Collection:
select * from SMS_R_System where SMS_R_System.SystemGroupName = “DATA\\GG_SDC_IBM_Notes_ML_PROD”

User Collection (managedby):
select SMS_R_USER.ResourceID,SMS_R_USER.ResourceType,SMS_R_USER.Name,SMS_R_USER.UniqueUserName,SMS_R_USER.WindowsNTDomain from SMS_R_User where SMS_R_User.DistinguishedName in (select SMS_R_System.managedBy from SMS_R_System where SMS_R_System.SystemGroupName = “DATA\\Domain Computers”) and SMS_R_User.UserGroupName = “DATA\\GG_SDV_FreeMind_FreeMind_ML_PILOT”

AD Computer Object: Managedby field must be filled in!



SMSTS.LOG

IT Posted on 01/28/2014 12:07:14

Reminder for myself 🙂

During OS Deployment

Before your hard drive is formatted and partitioned

X:\windows\temp\smstslog\

After your hard drive is partitioned formatted

X:\smstslog\ and then is in C:\_SMSTaskSequence\logs\smstslog\

Within Windows

Within Windows before the SCCM agent is installed:

C:\_SMSTaskSequence\logs\smstslog\

Within Windows after the SCCM agent installed:

C:\windows\system32\ccm\logs\smstslog\

When the Task Sequence completes on a x86

C:\windows\system32\ccm\logs\

For x64 Systems

C:\windows\SysWOW64\ccm\logs\

You will need to enable your boot.wim with f8 support to retrieve the log if it bombs out before apply OS stage so that you can bring up the command prompt and copy the log to a share on the network.