Friday, January 27, 2012

AD computer Numbers vs SCCM Computer Numbers

read here more http://smsug.ca/blogs/garth_jones/archive/2008/12/03/how-to-add-ad-data-to-configmgr-reporting.aspx

AD it just another database, just like SQL server is. With that in mind there is nothing stopping you from using SQL to link to AD to give you data about your AD environment!

1) Create Linked Server using SSMS

exec master.dbo.sp_addlinkedserver 'ADSI', 'Active Directory Service Interfaces', 'ADSDSOObject', '<DC Name FQDN>'

2) Modify the security for ADSI using SSMS

exec master.dbo.sp_addlinkedsrvlogin @rmtsrvname = N'ADSI', @locallogin = NULL , @useself = N'False', @rmtuser = N'<Domian>\<User Id>', @rmtpassword = N'<Password>'

3) The hard part is over!

4) Create query to query AD and ConfigMgr

This query will list all PCs within AD that are NOT within ConfigMgr (or SMS)

select

AD.cn as 'PC Name(AD)',

AD.operatingSystem as 'OS (AD)',

AD.operatingSystemServicePack as 'SP (AD)'

from

openquery (ADSI,

'SELECT cn,

operatingSystem,

operatingSystemServicePack

FROM ''LDAP://<DC Name FQDN>''

WHERE objectCategory = ''Computer''') as AD

Where

AD.cn not in (Select name0 from v_GS_Computer_System as CS)

order by

AD.cn,

AD.operatingSystem,

AD.operatingSystemServicePack

This query will give you a count of all OS that are NOT within ConfigMgr (or SMS)

select

AD.operatingSystem as 'OS (AD)',

count(AD.operatingSystem)

from

openquery (ADSI,

'SELECT cn,

operatingSystem,

operatingSystemServicePack

FROM ''LDAP://gartek-dc.gartek.tst''

WHERE objectCategory = ''Computer''') as AD

Where

AD.cn not in (Select name0 from v_GS_Computer_System as CS)

Group by

AD.operatingSystem

order by

AD.operatingSystem

So what does this report look like.

image

So there you have it.

Wednesday, January 25, 2012

ClientIDManagerStartup.log Error: 0x80040225 & Error 3

Failed to send registration request message. Error: 0x80040225

also when you see in the error 3 in ClientIDManagerStartup log

RegTask: Server rejected registration request: 3    ClientIDManagerStartup    26/01/2012 1:07:43 AM    7904 (0x1EE0)

 

You might also see (not in all cases) in ccmexec.log

System task 'ClientRegistrationStartup' returned error code 0x80040222.    CcmExec    26/01/2012 1:10:03 AM    7904 (0x1EE0)

Solution: Remove the Client authentication and SMS certificates Certificates of from Certificates console and request new certificates

PXE-T00: Unspecified file opening error detected

Found the error: While deploying 7 with the SCCM 2007 and MDT 2010.

sccm PXE-T00: Unspecified file opening error detected
PXE-E36:Error Received from TFTP server

 

image

Solution:This is not related to SCCM / WDS Issue.. it was with Symantec Ghost caused the issue, once the service was stopped the issue is resolved.