DRS Initialization In Configuration Manager 2012

Posted over 2 years ago

by

Sudheesh N

25 Comments

DRS Initialization In Configuration Manager 2012

When a site is first installed it establishes an initial synchronization with the sending site so that subsequent data changes are applied to an identical data set as that at the sending site.

By default the first replication group processed is the Replication Configuration group - this group effectively 'bootstraps' the receiving site with the remaining configuration for other replication groups.

The site initializes by sending an 'init' request to the sending site for the desired replication group.

When the sending site receives the 'init' request it uses the bcp application to extract all of the data from the tables that make up the replication group being initialized. At the same time a rowcount of the number of exported rows is also taken and stored in a .rowcount file. This allows the receiving site to ensure it has imported the same number of rows as the sending site exported for import.

The sending site sets the receiving site as a subscriber to the replication group and RCM begins sending any changes to tables in the replication group to the receiving site. The bcp files are replicated to the receiving site via the standard content sender.

Once the bcp files have arrived at the receiving site, RCM on the receiving site is notified of the files in its inbox and begins a cycle of actions for each table in the replication group:

Any existing data in the destination table that overlaps with the received data from the sending site is deleted from the table.
BCP is used to import the data from the sending site into the receiving site database.
After the import has completed the rowcount from the bcp process is compared to the row count in the .rowcount file. Assuming the values match the next table is processed.

Once all the tables have been processed the group status is changed to active and the site begins processing any messages in the queue.

We will also try re-initialization if we see any error on any specific group. When you run replication analyzer it will try auto remediate once and that particular group will be re-initialized.

We can also re-initialize putting a .pub file in RCM.box . The file <replicationgroupname>.pub works fine for Global Data. But for site-data where the CAS is the subscriber you have to add the sitecode to the file name, so it is like <replicationgroupname>-<sitecode>.pub, this is so the CAS knows which primary to re-init from.

Global data eg: configuration data.pub => Drop these on Primary server RCM.BOX

Site Data eg: hardware_inventory_8-PR1.pub => Drop these on CAS server RCM.BOX

This is all theory, Now what it if it is failing to re-initialize. The question we all have is, where to look and how to track. The remaining part of this document will go through that.

Always exec spdiagdrs is always a way to know if the replication is active. I will not be going to the details of the output here but will take you through the flow of re-initialization of a particular group.

Once we find that a particular group is having error in the output of spdiagdrs you will find that the following in the hierarchy information as well

This means that there is a Site data replication issue. Also under monitoring you will find the same information with a Link error for site data with Link error

So now to solve this we will re-initialize the group and track the flow. In this I am taking hardware_inventory_8 as an example. To re-initiate a specific group there are various method the safe method according to me is to put <Groupname>-<SITECODE>.pub in our case eg : hardware_inventory_8-PR1.pub

I enable enhanced logging to get more information so that it will be helpful to understand what happened when we see error again and again

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Components\SMS_REPLICATION_CONFIGURATION_MONITOR ==>Verbose Logging : 2

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Tracing ==>Sqlenabled : 1

We have two kind of logging in ConfigMgr 2012. For DRS initialization we can use the rcmctrl.log and inside the database vlogs view. For the database I used the following query to get the data out of it while I was performing this action.

Select * from vLogs where LogTime >GETDATE()-1 and ProcedureName <> 'spDRSSendChangesForGroup' ORDER BY LogTime DESC

To re-initialize the group put the file in \Microsoft Configuration Manager\inboxes\rcm.box .In some time we will see that vanishing from the box and the RCM will take control.Once the same happens you will see the following in the rcmctrl.log in CAS

Processing replication group Hardware_Inventory_8. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:02:24 1820 (0x071C)

Current status is Active. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:02:24 1820 (0x071C)

Requesting initialization for replication group Hardware_Inventory_8. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:02:24 1820 (0x071C)

Checking if initialization request is needed for replication group Hardware_Inventory_8 from site PR1. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:02:27 1820 (0x071C)

LogLine	LogTime	ComponentName	MachineName	ProcedureName	LogText
429508	02:24.9	Microsoft SQL Server Service Broker Activation		spRCMActivation	INFO: Received DRS_SubscriptionInvalid from Site CAS for replication group: Hardware_Inventory_8 and fulfilling site: PR1 and requesting site: CAS
429509	02:24.9	Microsoft SQL Server Service Broker Activation		spRCMActivation	INFO: DRS_SubscriptionInvalid is for full initialization - marking required replication group.
429510	02:24.9	Microsoft SQL Server Service Broker Activation		spRCMActivation	INFO: Finished processing DRS_SubscriptionInvalid from Site CAS for replication group: Hardware_Inventory_8

Now on the primary server on the rcmctrl.log you will see

Processing replication role: DrsReplicationSite, child SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:03 3364 (0x0D24)

Processing replication group Hardware_Inventory_8. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:03 3364 (0x0D24)

Current status is PendingCreation. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:03 3364 (0x0D24)

Checking if we need to create an initialization package for replication group Hardware_Inventory_8 for site CAS. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:04 3364 (0x0D24)

STATMSG: ID=7802 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_REPLICATION_CONFIGURATION_MONITOR" SYS=CMLABPRI.CMLAB.COM SITE=PR1 PID=5060 TID=3364 GMTDATE=Sat Oct 20 09:03:04.342 2012 ISTR0="CAS" ISTR1="Hardware_Inventory_8" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:04 3364 (0x0D24)

Flushing DRS queue messages coming from CAS for replication group Hardware_Inventory_8. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:04 3364 (0x0D24)

Changed the status of ConfigMgrDRSSiteQueue to OFF if it exists. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:04 3364 (0x0D24)

Changed the status of ConfigMgrDRSSiteQueue to ON if it exists. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:07 3364 (0x0D24)

Files will be copied to directory C:\Program Files\Microsoft Configuration Manager\inboxes\rcm.box\a4ba357d-1cb4-408c-9e89-681686974194. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:07 3364 (0x0D24)

Cab File to be sent will be copied to directory C:\Program Files\Microsoft Configuration Manager\inboxes\rcm.box\CabFiles. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:07 3364 (0x0D24)

XML CreateTime: 20-10-2012 09:02:31 LastModifyTime: 20-10-2012 09:02:31 SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:07 3364 (0x0D24)

Creating version file C:\Program Files\Microsoft Configuration Manager\inboxes\rcm.box\a4ba357d-1cb4-408c-9e89-681686974194\781708.version SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:07 3364 (0x0D24)

Creating trackingGuid file C:\Program Files\Microsoft Configuration Manager\inboxes\rcm.box\a4ba357d-1cb4-408c-9e89-681686974194\d74dc244-a526-4387-86b0-efacf67df680.trackingGuid SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:07 3364 (0x0D24)

Creating pubName file C:\Program Files\Microsoft Configuration Manager\inboxes\rcm.box\a4ba357d-1cb4-408c-9e89-681686974194\Hardware_Inventory_8-PR1.pubName SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:07 3364 (0x0D24)

………………………..

……………………….

Calling BCP out with SELECT BINFILEVERSION00, BINPRODUCTVERSION00, DESCRIPTION00, FILENAME00, FILEPROPERTIESHASH00, FILEPROPERTIESHASHEX00, FILEVERSION00, LOCATION00, PRODUCT00, PRODUCTVERSION00, PUBLISHER00, STARTUPTYPE00, STARTUPVALUE00, MACHINEID, INSTANCEKEY, TIMEKEY, REVISIONID, AGENTID, ROWVERSION~FROM AUTOSTART_SOFTWARE_HIST where (MachineID between 16777216 and 33554431) , C:\Program Files\Microsoft Configuration Manager\inboxes\rcm.box\a4ba357d-1cb4-408c-9e89-681686974194\AUTOSTART_SOFTWARE_HIST.bcp, C:\Program Files\Microsoft Configuration Manager\inboxes\rcm.box\a4ba357d-1cb4-408c-9e89-681686974194\bcpErrors.errors. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:07 3364 (0x0D24)

………………………………..

……………………………….

Successfully created BCP file [C:\Program Files\Microsoft Configuration Manager\inboxes\rcm.box\a4ba357d-1cb4-408c-9e89-681686974194\AUTOSTART_SOFTWARE_DATA.bcp] with rows [6] based on SQL query [SELECT BINFILEVERSION00, BINPRODUCTVERSION00, DESCRIPTION00, FILENAME00, FILEPROPERTIESHASH00, FILEPROPERTIESHASHEX00, FILEVERSION00, LOCATION00, PRODUCT00, PRODUCTVERSION00, PUBLISHER00, STARTUPTYPE00, STARTUPVALUE00, MACHINEID, INSTANCEKEY, TIMEKEY, REVISIONID, AGENTID, ROWVERSION~FROM AUTOSTART_SOFTWARE_DATA where (MachineID between 16777216 and 33554431) ] SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:07 3364 (0x0D24)

BCP out result is 0. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:07 3364 (0x0D24)

Table XML: <TABLE NAME="AUTOSTART_SOFTWARE_HIST"><COLUMN COLUMN_ID="1" NAME="BINFILEVERSION00" TYPENAME="nvarchar" TYPEID="231" MAX_LENGTH="510" IS_NULLABLE="1" HAS_DEFAULTVALUE="0" /><

………………………..

…………………………

SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:07 3364 (0x0D24)

This shows the BCP out commands being fired and also you will see the files like shown in the figure below. The Version file ,trackinguid file, Errors file ,pubnamefile and then for each table in the group .bcp file and .row count file.

.

In the database on the primary you will see the following .

LogLine	LogTime	ComponentName	MachineName	ProcedureName	LogText
7E+16	02:24.9	Microsoft SQL Server Service Broker Activation		spRCMActivation	INFO: Received DRS_SubscriptionInvalid from Site CAS for replication group: Hardware_Inventory_8 and fulfilling site: PR1 and requesting site: CAS
7E+16	02:24.9	Microsoft SQL Server Service Broker Activation		spRCMActivation	INFO: DRS_SubscriptionInvalid is for full initialization - marking required replication group.
7E+16	02:24.9	Microsoft SQL Server Service Broker Activation		spRCMActivation	INFO: Finished processing DRS_SubscriptionInvalid from Site CAS for replication group: Hardware_Inventory_8
7E+16	02:31.4	Microsoft SQL Server Service Broker Activation		spRCMActivation	INFO: Received DRS_InitRequest from Site CAS for replication group: Hardware_Inventory_8
7E+16	03:08.4	SMS_REPLICATION _CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION _MONITOR	Creating init package for replication group Hardware_Inventory_8 for site CAS. -- 10/20/2012 02:03:04
7E+16	03:08.4	SMS_REPLICATION _CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION_ CONFIGURATION _MONITOR	INFO: Flushing DRS queue messages coming from subscriber CAS for replication group Hardware_Inventory_8. -- 10/20/2012 02:03:04
7E+16	03:08.4	SMS_REPLICATION _CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION _MONITOR	INFO: Turned off DRS queue ConfigMgrDRSSiteQueue on publisher PR1. -- 10/20/2012 02:03:04
7E+16	03:08.4	SMS_REPLICATION _CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION _MONITOR	INFO: Turned on DRS queue ConfigMgrDRSSiteQueue on publisher PR1 . -- 10/20/2012 02:03:07
7E+16	03:08.4	SMS_REPLICATION _CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION _MONITOR	INFO: Init package XML CreateTime: 20-10-2012 09:02:31 LastModifyTime: 20-10-2012 09:02:31 for replication group Hardware_Inventory_8 for site CAS. -- 10/20/2012 02:03:07
7E+16	03:08.5	SMS_ REPLICATION_ CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION _MONITOR	INFO: Created version file for init package for replication group Hardware_Inventory_8 for site CAS. -- 10/20/2012 02:03:07
7E+16	03:08.5	SMS_REPLICATION _CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION _MONITOR	INFO: Created tracking GUID file for init package for replication group Hardware_Inventory_8 for site CAS. -- 10/20/2012 02:03:07
7E+16	03:08.5	SMS_REPLICATION _CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION _MONITOR	INFO: Created pub file for init package for replication group Hardware_Inventory_8 for site CAS. -- 10/20/2012 02:03:07
7E+16	03:08.5	SMS_REPLICATION _CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION _MONITOR	Calling BCP out for table AUTOSTART_SOFTWARE_DATA. -- 10/20/2012 02:03:07
7E+16	03:08.5	SMS_REPLICATION _CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION _MONITOR	BCP out result for table AUTOSTART_SOFTWARE_DATA is 0. -- 10/20/2012 02:03:07
7E+16	03:08.5	SMS_REPLICATION _CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION _MONITOR	Calling BCP out for table AUTOSTART_SOFTWARE_HIST. -- 10/20/2012 02:03:07
7E+16	03:08.5	SMS_REPLICATION _CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION _MONITOR	BCP out result for table AUTOSTART_SOFTWARE_HIST is 0. -- 10/20/2012 02:03:07
7E+16	03:08.5	SMS_REPLICATION _CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION _MONITOR	Calling BCP out for table BROWSER_HELPER_OBJECT_DATA. -- 10/20/2012 02:03:07
7E+16	03:08.6	SMS_REPLICATION _CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION _MONITOR	BCP out result for table BROWSER_HELPER_OBJECT_DATA is 0. -- 10/20/2012 02:03:07
7E+16	03:08.6	SMS_REPLICATION _CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION _MONITOR	Calling BCP out for table BROWSER_HELPER_OBJECT_HIST. -- 10/20/2012 02:03:07
7E+16	03:08.6	SMS_REPLICATION _CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION_ MONITOR	BCP out result for table BROWSER_HELPER_OBJECT_HIST is 0. -- 10/20/2012 02:03:07
7E+16	03:08.6	SMS_REPLICATION _CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION _MONITOR	Calling BCP out for table SW_LICENSING_PRODUCT_DATA. -- 10/20/2012 02:03:07
7E+16	03:08.6	SMS_REPLICATION _CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION _MONITOR	BCP out result for table SW_LICENSING_PRODUCT_DATA is 0. -- 10/20/2012 02:03:07
7E+16	03:08.6	SMS_REPLICATION _CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION _MONITOR	Calling BCP out for table SW_LICENSING_PRODUCT_HIST. -- 10/20/2012 02:03:07
7E+16	03:08.6	SMS_REPLICATION _CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION _MONITOR	BCP out result for table SW_LICENSING_PRODUCT_HIST is 0. -- 10/20/2012 02:03:07
7E+16	03:08.6	SMS_REPLICATION _CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION _MONITOR	Calling BCP out for table SW_LICENSING_SERVICE_DATA. -- 10/20/2012 02:03:07
7E+16	03:08.6	SMS_REPLICATION _CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION _MONITOR	BCP out result for table SW_LICENSING_SERVICE_DATA is 0. -- 10/20/2012 02:03:08
7E+16	03:08.7	SMS_REPLICATION _CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION _MONITOR	Calling BCP out for table SW_LICENSING_SERVICE_HIST. -- 10/20/2012 02:03:08
7E+16	03:08.7	SMS_REPLICATION _CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION _MONITOR	BCP out result for table SW_LICENSING_SERVICE_HIST is 0. -- 10/20/2012 02:03:08
7E+16	03:08.7	SMS_REPLICATION _CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION _MONITOR	Calling BCP out for table USB_DEVICE_DATA. -- 10/20/2012 02:03:08
7E+16	03:08.7	SMS_REPLICATION _CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION _MONITOR	BCP out result for table USB_DEVICE_DATA is 0. -- 10/20/2012 02:03:08
7E+16	03:08.7	SMS_REPLICATION _CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION _MONITOR	Calling BCP out for table USB_DEVICE_HIST. -- 10/20/2012 02:03:08
7E+16	03:08.7	SMS_REPLICATION _CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION _MONITOR	BCP out result for table USB_DEVICE_HIST is 0. -- 10/20/2012 02:03:08
7E+16	03:08.7	SMS_REPLICATION _CONFIGURATION_ MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION _MONITOR	Sending the init package for replication group Hardware_Inventory_8 to subscriber CAS. -- 10/20/2012 02:03:08
7E+16	03:08.7	SMS_REPLICATION _CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION _MONITOR	Send result for init package for replication group Hardware_Inventory_8 to subscriber CAS is 0. -- 10/20/2012 02:03:08
7E+16	03:08.8	SMS_REPLICATION _CONFIGURATION _MONITOR	CMLABPRI	SMS_REPLICATION _CONFIGURATION _MONITOR	Init package created and sent for replication group Hardware_Inventory_8 for site CAS. -- 10/20/2012 02:03:08

Once the BCP out is completed the compression will happen and file will be stored in the CABFiles folder as shown below

The rcmctrl.log will have the following

Calling drs_init_send method now with parameters C:\Program Files\Microsoft Configuration Manager\inboxes\rcm.box\a4ba357d-1cb4-408c-9e89-681686974194 and CAS. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:08 3364 (0x0D24)

Starting to compress files under folder [C:\Program Files\Microsoft Configuration Manager\inboxes\rcm.box\a4ba357d-1cb4-408c-9e89-681686974194\] to [C:\Program Files\Microsoft Configuration Manager\inboxes\rcm.box\CabFiles\CAS_4C7EB459-2631-455B-93C1-8C08926BAD07.cab] ... SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:08 3364 (0x0D24)

Deleting all files under folder [C:\Program Files\Microsoft Configuration Manager\inboxes\rcm.box\a4ba357d-1cb4-408c-9e89-681686974194]. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:08 3364 (0x0D24)

Created minijob to send compressed copy of DRS INIT BCP Package to site CAS. Tranfer root = C:\Program Files\Microsoft Configuration Manager\inboxes\rcm.box\CabFiles\CAS_4C7EB459-2631-455B-93C1-8C08926BAD07.cab. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:08 3364 (0x0D24)

drs_init_send returned 0. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:08 3364 (0x0D24)

STATMSG: ID=7803 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_REPLICATION_CONFIGURATION_MONITOR" SYS=CMLABPRI.CMLAB.COM SITE=PR1 PID=5060 TID=3364 GMTDATE=Sat Oct 20 09:03:08.373 2012 ISTR0="Hardware_Inventory_8" ISTR1="CAS" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:08 3364 (0x0D24)

Current status is PackageCreated. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:08 3364 (0x0D24)

Found 1 replication roles. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:08 3364 (0x0D24)

Now once this is done the sender will send the files to the CAS server.

Sender.log

=======

Passed the xmit file test, use the existing connection SMS_LAN_SENDER 20-10-2012 02:03:33 5012 (0x1394)

Package file = C:\Program Files\Microsoft Configuration Manager\inboxes\rcm.box\CabFiles\CAS_4C7EB459-2631-455B-93C1-8C08926BAD07.cab SMS_LAN_SENDER 20-10-2012 02:03:33 5012 (0x1394)

Instruction file = C:\Program Files\Microsoft Configuration Manager\inboxes\schedule.box\tosend\00000085.I59 SMS_LAN_SENDER 20-10-2012 02:03:33 5012 (0x1394)

Checking for remote file \\CMLABCAS.CMLAB.COM\SMS_SITE\1003PPR1.PCK SMS_LAN_SENDER 20-10-2012 02:03:33 5012 (0x1394)

Checking for remote file \\CMLABCAS.CMLAB.COM\SMS_SITE\1003PPR1.SNI SMS_LAN_SENDER 20-10-2012 02:03:33 5012 (0x1394)

Checking for remote file \\CMLABCAS.CMLAB.COM\SMS_SITE\1003PPR1.TMP SMS_LAN_SENDER 20-10-2012 02:03:33 5012 (0x1394)

Attempt to create/open the remote file \\CMLABCAS.CMLAB.COM\SMS_SITE\1003PPR1.PCK SMS_LAN_SENDER 20-10-2012 02:03:33 5012 (0x1394)

Created/opened the remote file \\CMLABCAS.CMLAB.COM\SMS_SITE\1003PPR1.PCK SMS_LAN_SENDER 20-10-2012 02:03:33 5012 (0x1394)

Attempt to create/open the remote file \\CMLABCAS.CMLAB.COM\SMS_SITE\1003PPR1.PCK SMS_LAN_SENDER 20-10-2012 02:03:33 5012 (0x1394)

Created/opened the remote file \\CMLABCAS.CMLAB.COM\SMS_SITE\1003PPR1.PCK SMS_LAN_SENDER 20-10-2012 02:03:33 5012 (0x1394)

Sending Started [C:\Program Files\Microsoft Configuration Manager\inboxes\rcm.box\CabFiles\CAS_4C7EB459-2631-455B-93C1-8C08926BAD07.cab] SMS_LAN_SENDER 20-10-2012 02:03:33 5012 (0x1394)

Attempt to write 1024 bytes to \\CMLABCAS.CMLAB.COM\SMS_SITE\1003PPR1.PCK at position 0 SMS_LAN_SENDER 20-10-2012 02:03:33 5012 (0x1394)

……………………….

S.CMLAB.COM\SMS_SITE\1003PPR1.TMP SMS_LAN_SENDER 20-10-2012 02:03:33 5012 (0x1394)

Created/opened the remote file \\CMLABCAS.CMLAB.COM\SMS_SITE\1003PPR1.TMP SMS_LAN_SENDER 20-10-2012 02:03:33 5012 (0x1394)

Sending Started [C:\Program Files\Microsoft Configuration Manager\inboxes\schedule.box\tosend\00000085.I59] SMS_LAN_SENDER 20-10-2012 02:03:33 5012 (0x1394)

Attempt to write 650 bytes to \\CMLABCAS.CMLAB.COM\SMS_SITE\1003PPR1.TMP at position 0 SMS_LAN_SENDER 20-10-2012 02:03:33 5012 (0x1394)

Wrote 650 bytes to \\CMLABCAS.CMLAB.COM\SMS_SITE\1003PPR1.TMP at position 0 SMS_LAN_SENDER 20-10-2012 02:03:33 5012 (0x1394)

Sending completed [C:\Program Files\Microsoft Configuration Manager\inboxes\schedule.box\tosend\00000085.I59] SMS_LAN_SENDER 20-10-2012 02:03:33 5012 (0x1394)

Renaming remote file \\CMLABCAS.CMLAB.COM\SMS_SITE\1003PPR1.TMP to \\CMLABCAS.CMLAB.COM\SMS_SITE\1003PPR1.SNI SMS_LAN_SENDER 20-10-2012 02:03:33 5012 (0x1394)

Rename completed [\\CMLABCAS.CMLAB.COM\SMS_SITE\1003PPR1.TMP] SMS_LAN_SENDER 20-10-2012 02:03:33 5012 (0x1394)

Sending completed successfully SMS_LAN_SENDER 20-10-2012 02:03:33 5012 (0x1394)

COutbox::TakeNextToSend(pszSiteCode) SMS_LAN_SENDER 20-10-2012 02:03:33 5012 (0x1394)

We have 0 active connections SMS_LAN_SENDER 20-10-2012 02:03:38 4784 (0x12B0)

Checking for sending capacity. Used 0 out of 5. SMS_LAN_SENDER 20-10-2012 02:03:38 4784 (0x12B0)

Connecting to C:\Program Files\Microsoft Configuration Manager\inboxes\schedule.box\outboxes\LAN. SMS_LAN_SENDER 20-10-2012 02:03:38 4784 (0x12B0)

COutbox::TakeNextToSend(pszSiteCode) SMS_LAN_SENDER 20-10-2012 02:03:38 4784 (0x12B0)

No (more) send requests found to process. SMS_LAN_SENDER 20-10-2012 02:03:38 4784 (0x12B0)

Waiting for new/rescheduled send requests, Maximum Sleep Time = 60 minutes SMS_LAN_SENDER 20-10-2012 02:03:38 4784 (0x12B0)

One the database logs you will find the following

LogLine	LogTime	ComponentName	MachineName	ProcedureName	LogText
7.20576E+16	03:08.7	SMS_REPLICATION_ CONFIGURATION_ MONITOR	CMLABPRI	SMS_REPLICATION_ CONFIGURATION_ MONITOR	Sending the init package for replication group Hardware_Inventory_8 to subscriber CAS. -- 10/20/2012 02:03:08
7.20576E+16	03:08.7	SMS_REPLICATION_ CONFIGURATION_ MONITOR	CMLABPRI	SMS_REPLICATION_ CONFIGURATION_ MONITOR	Send result for init package for replication group Hardware_Inventory_8 t o subscriber CAS is 0. -- 10/20/2012 02:03:08
7.20576E+16	03:08.8	SMS_REPLICATION_ CONFIGURATION_ MONITOR	CMLABPRI	SMS_REPLICATION_C ONFIGURATION_ MONITOR	Init package created and sent for replication group Hardware_Inventory_8 for site CAS. -- 10/20/2012 02:03:08

Now once the CAS receives the files the despooler will start pressing the files inside RCM.box\<GUID> just like it created in Primary. The despooler.log will show you the same

Despoolr.log

=========

Waiting for ready instruction file.... SMS_DESPOOLER 20-10-2012 02:03:38 3972 (0x0F84)

Decompressed C:\Program Files\Microsoft Configuration Manager\inboxes\despoolr.box\receive\ds_fl24a.pkg to C:\Program Files\Microsoft Configuration Manager\inboxes\rcm.box\DBAF3A0C-9FE0-4A93-B771-E2DD3784E755\ SMS_DESPOOLER 20-10-2012 02:03:38 3376 (0x0D30)

Despooler successfully executed one instruction. SMS_DESPOOLER 20-10-2012 02:03:38 3376 (0x0D30)

Once it is decompressed the RCM will start processing . It will compare and see the tracking GUID and if publication matches and then will delete the old data BCP in (Bulk copy)the values after verifying with the rowcount files .

RCMctrl.log

===========

Processing replication group Hardware_Inventory_8. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:41 1820 (0x071C)

Current status is PackageCreated. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:41 1820 (0x071C)

Checking if initialization request is needed for replication group Hardware_Inventory_8 from site PR1. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:41 1820 (0x071C)

Checking if there are bcp file to apply for replication group Hardware_Inventory_8 from site PR1. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:41 1820 (0x071C)

found a tracking guid, searching through .init files. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:41 1820 (0x071C)

Checking bcpDirectory C:\Program Files\Microsoft Configuration Manager\inboxes\rcm.box\DBAF3A0C-9FE0-4A93-B771-E2DD3784E755 SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:41 1820 (0x071C)

Found files for publication Hardware_Inventory_8-PR1. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:41 1820 (0x071C)

Publication names match. Checking vesrion. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:41 1820 (0x071C)

Found our tracking guid SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:41 1820 (0x071C)

Setting deadlock priority level to high. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:41 1820 (0x071C)

Initializing to version number 781708. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:41 1820 (0x071C)

Publication Hardware_Inventory_8 has ID 30. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:41 1820 (0x071C)

Flushing DRS queue messages coming from PR1 for replication group Hardware_Inventory_8. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:41 1820 (0x071C)

Executing pre-snapshot stored procedures for group Hardware_Inventory_8. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:42 1820 (0x071C)

Pre-snapshot stored procedures for group Hardware_Inventory_8 finished. Applying bcp files. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:42 1820 (0x071C)

Removing old data for site table ... [EXEC spSMSTruncatePartitionTable 'AUTOSTART_SOFTWARE_DATA', 1;] SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:42 1820 (0x071C)

Rowcount from file [C:\Program Files\Microsoft Configuration Manager\inboxes\rcm.box\DBAF3A0C-9FE0-4A93-B771-E2DD3784E755\AUTOSTART_SOFTWARE_DATA.bcp.rowcount] is [6]. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:42 1820 (0x071C)

Successfully bulk copied file [C:\Program Files\Microsoft Configuration Manager\inboxes\rcm.box\DBAF3A0C-9FE0-4A93-B771-E2DD3784E755\AUTOSTART_SOFTWARE_DATA.bcp] into table [AUTOSTART_SOFTWARE_DATA] with rows [6]. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:43 1820 (0x071C)

Removing old data for site table ... [EXEC spSMSTruncatePartitionTable 'AUTOSTART_SOFTWARE_HIST', 1;] SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:43 1820 (0x071C)

Rowcount from file [C:\Program Files\Microsoft Configuration Manager\inboxes\rcm.box\DBAF3A0C-9FE0-4A93-B771-E2DD3784E755\AUTOSTART_SOFTWARE_HIST.bcp.rowcount] is [0]. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:43 1820 (0x071C)

‘’’’’’’’’’’’’’’’’’’’’’’

Setting deadlock priority level to normal. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:45 1820 (0x071C)

Current status is Active. SMS_REPLICATION_CONFIGURATION_MONITOR 20-10-2012 02:03:45 1820 (0x071C)

--------------

In the database logs also you will find this

LogLine	LogTime	ComponentName	MachineName	ProcedureName	LogText
429511	02:31.4	Microsoft SQL Server Service Broker Activation		spRCMActivation	INFO: Received DRS_InitRequestReceived for replication group: Hardware_Inventory_8
429512	02:32.8	SMS_REPLICATION_ CONFIGURATION_MONITOR	CMLABCAS	SMS_REPLICATION_ CONFIGURATION_MONITOR	INFO: Creating initialization request for 10 articles in replication group Hardware_Inventory_8 from site PR1. -- 10/20/2012 02:02:27
429513	02:32.8	SMS_REPLICATION_ CONFIGURATION_MONITOR	CMLABCAS	SMS_REPLICATION_ CONFIGURATION_MONITOR	Built the init request XML for replication group Hardware_Inventory_8 for site PR1. -- 10/20/2012 02:02:31
429514	03:08.3	Microsoft SQL Server Service Broker Activation		spRCMActivation	INFO: Received DRS_InitPackageCreated for replication group: Hardware_Inventory_8
429516	03:45.0	SMS_REPLICATION_ CONFIGURATION_MONITOR	CMLABCAS	SMS_REPLICATION_ CONFIGURATION_MONITOR	Applying the BCP for replication group Hardware_Inventory_8 from site PR1. Tracking guid d74dc244-a526-4387-86b0-efacf67df680. -- 10/20/2012 02:03:41
429517	03:45.0	SMS_REPLICATION_ CONFIGURATION_MONITOR	CMLABCAS	SMS_REPLICATION_ CONFIGURATION_MONITOR	BCP version number for replication group Hardware_Inventory_8 from site PR1 is 781708. -- 10/20/2012 02:03:41
429518	03:45.0	SMS_REPLICATION_ CONFIGURATION_MONITOR	CMLABCAS	SMS_REPLICATION_ CONFIGURATION_MONITOR	Flushing DRS queue messages coming from site PR1 for replication group Hardware_Inventory_8.-- 10/20/2012 02:03:41
429519	03:45.1	SMS_REPLICATION_ CONFIGURATION_MONITOR	CMLABCAS	SMS_REPLICATION_ CONFIGURATION_MONITOR	Executing pre-snapshot stored procedures for replication group Hardware_Inventory_8. -- 10/20/2012 02:03:42
429520	03:45.1	SMS_REPLICATION_ CONFIGURATION_MONITOR	CMLABCAS	SMS_REPLICATION_ CONFIGURATION_MONITOR	Pre-snapshot stored procedures for replication group Hardware_Inventory_8 finished. Applying bcp files. -- 10/20/2012 02:03:42
429521	03:45.1	SMS_REPLICATION_ CONFIGURATION_MONITOR	CMLABCAS	SMS_REPLICATION_ CONFIGURATION_MONITOR	Disable foreign keys for replication group Hardware_Inventory_8. -- 10/20/2012 02:03:42
429522	03:45.1	SMS_REPLICATION_C ONFIGURATION_MONITOR	CMLABCAS	SMS_REPLICATION_ CONFIGURATION_MONITOR	Removing old data for site table .. . [EXEC spSMSTruncatePartitionTable 'AUTOSTART_SOFTWARE_DATA', 1;] -- 10/20/2012 02:03:42
429523	03:45.1	SMS_REPLICATION_ CONFIGURATION_MONITOR	CMLABCAS	SMS_REPLICATION_ CONFIGURATION_MONITOR	Removing old data for site table ... [EXEC spSMSTruncatePartitionTable 'AUTOSTART_SOFTWARE_HIST', 1;] -- 10/20/2012 02:03:43
429524	03:45.1	SMS_REPLICATION_ CONFIGURATION_MONITOR	CMLABCAS	SMS_REPLICATION_ CONFIGURATION_MONITOR	Removing old data for site table ... [EXEC spSMSTruncatePartitionTable 'BROWSER_HELPER_OBJECT_DATA', 1;] -- 10/20/2012 02:03:43
429525	03:45.1	SMS_REPLICATION_ CONFIGURATION_MONITOR	CMLABCAS	SMS_REPLICATION_ CONFIGURATION_MONITOR	Removing old data for site table ... [EXEC spSMSTruncatePartitionTable 'BROWSER_HELPER_OBJECT_HIST', 1;] -- 10/20/2012 02:03:43
429526	03:45.2	SMS_REPLICATION_ CONFIGURATION_MONITOR	CMLABCAS	SMS_REPLICATION_ CONFIGURATION_MONITOR	Removing old data for site table ... [EXEC spSMSTruncatePartitionTable 'SW_LICENSING_PRODUCT_DATA', 1;] -- 10/20/2012 02:03:43
429527	03:45.2	SMS_REPLICATION_ CONFIGURATION_MONITOR	CMLABCAS	SMS_REPLICATION_ CONFIGURATION_MONITOR	Removing old data for site table ... [EXEC spSMSTruncatePartitionTable ' SW_LICENSING_PRODUCT_HIST', 1;] -- 10/20/2012 02:03:43
429528	03:45.2	SMS_REPLICATION_ CONFIGURATION_MONITOR	CMLABCAS	SMS_REPLICATION_ CONFIGURATION_MONITOR	Removing old data for site table ... [EXEC spSMSTruncatePartitionTable 'SW_LICENSING_SERVICE_DATA', 1;] -- 10/20/2012 02:03:43
429529	03:45.2	SMS_REPLICATION_ CONFIGURATION_MONITOR	CMLABCAS	SMS_REPLICATION_C ONFIGURATION_MONITOR	Removing old data for site table . .. [EXEC spSMSTruncatePartitionTable 'SW_LICENSING_SERVICE_HIST', 1;] -- 10/20/2012 02:03:44
429530	03:45.2	SMS_REPLICATION_ CONFIGURATION_MONITOR	CMLABCAS	SMS_REPLICATION_ CONFIGURATION_MONITOR	Removing old data for site table .. . [EXEC spSMSTruncatePartitionTable 'USB_DEVICE_DATA', 1;] -- 10/20/2012 02:03:44
429531	03:45.2	SMS_REPLICATION_ CONFIGURATION_MONITOR	CMLABCAS	SMS_REPLICATION_ CONFIGURATION_MONITOR	Removing old data for site table ... [EXEC spSMSTruncatePartitionTable 'USB_DEVICE_HIST', 1;] -- 10/20/2012 02:03:44
429532	03:45.2	SMS_REPLICATION_ CONFIGURATION_MONITOR	CMLABCAS	SMS_REPLICATION_ CONFIGURATION_MONITOR	Applied the BCP files for replication group Hardware_Inventory_8 from site PR1. -- 10/20/2012 02:03:44
429533	03:45.2	SMS_REPLICATION_ CONFIGURATION_MONITOR	CMLABCAS	SMS_REPLICATION_ CONFIGURATION_MONITOR	Enable foreign keys for replication group Hardware_Inventory_8. -- 10/20/2012 02:03:44
429534	03:45.3	SMS_REPLICATION_ CONFIGURATION_MONITOR	CMLABCAS	SMS_REPLICATION_ CONFIGURATION_MONITOR	Restore table's identity value for replication group Hardware_Inventory_8. -- 10/20/2012 02:03:44
429535	03:45.3	SMS_REPLICATION_ CONFIGURATION_MONITOR	CMLABCAS	SMS_REPLICATION_ CONFIGURATION_MONITOR	Executing post-snapshot stored procedures for replication group Hardware_Inventory_8. -- 10/20/2012 02:03:44
429536	03:45.3	SMS_REPLICATION_ CONFIGURATION_MONITOR	CMLABCAS	SMS_REPLICATION_ CONFIGURATION_MONITOR	Post-snapshot stored procedures for replication group Hardware_Inventory_8 finished. -- 10/20/2012 02:03:44
429537	03:45.3	SMS_REPLICATION_ CONFIGURATION_MONITOR	CMLABCAS	SMS_REPLICATION_ CONFIGURATION_MONITOR	Finished applying the BCP for replication group Hardware_Inventory_8 from site PR1. -- 10/20/2012 02:03:45

Once the same is completed then on the primary server you will find the replication is finished.

LogLine

LogTime

ComponentName

MachineName

ProcedureName

LogText

7.20576E+16

03:44.8

Microsoft SQL Server

Service Broker Activation

spRCMActivation

INFO: Received DRS_InitFinished from

Site CAS for replication group:

Hardware_Inventory_8 with Version 135769

Once the same happens you will see the link moving from initialization to active in the monitoring phase.

Sudheesh Narayanaswamy

Support Escalation Engineer

Microsoft System Center Support

Unable to Open the SCCM CONSOLE

Posted over 5 years ago

by

Sudheesh N

6 Comments

We had issues in which when we try to Open the SCCM CONSOLE we were getting the

Error message
============
"The ConfigMgr console could not connect to the ConfigMgr site database. Verify that this computer has network connectivity to the SMS Provider computer and that your user account has Remote Activation permissions on both the ConfigMgr site
server and SMS Provider computers. For more information, see "How to Configure DCOM Permissions for Configuration Manager Console Connections" in ConfigMgr Help"

On the SMSADMINUI.log you will have the following information

SMSADMINUI.log
=============
Error Code:
InvalidClass
\r\nSystem.Management.ManagementException\r\nInvalid class \r\n at
System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus
errorCode)
at
System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()

at
Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsO
bject.<GetEnumerator>d__0.MoveNext()\r\nManagementException details:
instance of __ExtendedStatus
{
Operation = "ExecQuery";
ParameterInfo = "SELECT * FROM SMS_Site WHERE
ReportingSiteCode = ''";
ProviderName = "WinMgmt";
};
\r\n
[4][8/8/2008 1:09:29 PM] :Failure while loading required 'WQL' query engine, console cannot connec

Troubleshooting

=============

For troubleshooting this issue

· Go to start ->run -> Wbemtest

· Cick to Connect to root\sms --> Enum Classes-->Select recursive- -->Select
SMS_ProviderLocation () Click on instances

· In case you find that there was no entry for this, Please re-compile smsprov.mof using the command mofcomp smsprov.mof

Note: if mofcomp has to run the path needs to be set to C:\Windows\System32\wbem. SMSprov.mof will be inside the bin folder where you had installed the SCCM \program files\Microsoft Configuration Manager\bin\i386

Hope this information will be useful

Sudheesh Narayanaswamy | Support Engineer

How to install SCUP and configure

Posted over 3 years ago

by

Sudheesh N

5 Comments

How to install SCUP and configure

This will show the steps on how to install SCUP and also configure a third party catalogue, (EH Adobe Flash player) and deploy the clients reporting to SCCM server.

You can download the SCUP from the following link http://www.microsoft.com/downloads/en/details.aspx?FamilyID=0446cce9-94a4-4fb0-b335-e7516044063d&displaylang=en

On the SCCM server or on any other server you can install System Center Updates Publisher.

The perquisite is to have SQL server. You can use the express installation or use any other SQL server.

Updates Publisher is supported on the following operating systems:

· The Microsoft Windows® XP Professional operating system with Service Pack 2 (SP2)
· The Microsoft Windows® XP Professional x64 Edition operating system
· The 32-bit versions of the Microsoft Windows Server®°2003 operating systems with Service Pack 1 (SP1)
· The x64-based editions of the Microsoft Windows Server®°2003 operating systems
· The 32-bit versions of the Microsoft Windows Server®°2003 R2 operating systems
· The x64-based editions of the Microsoft Windows Server®°2003 R2 operating systems
· The Windows Vista™ operating systems
· The x64-based editions of the Windows Vista™ x64 Edition operating systems

Software Requirements

· Updates Publisher has the following software requirements:
· Microsoft Management Console 3.0 (MMC). MMC 3.0 must be installed prior to running the Updates Publisher Setup. You can download the MMC 3.0 from the Microsoft Download Center Web site (http://go.microsoft.com/fwlink/?linkid=21788).
· For Updates Publisher 4.5, WSUS 3.0 SP2SP1 Administration Console. If WSUS 3.0 SP2 is not already installed on the local computer, the WSUS 3.0 SP2 Administration Console must be installed prior to running the Updates Publisher Setup. You can download the WSUS 3.0 SP2 Administration Console from the Windows Server Update Services Web site
· Microsoft Internet Explorer 6 SP1 or later. A supported version of Internet Explorer must be installed prior to running the Updates Publisher Setup. You can download Internet Explorer 6 SP1 from the Microsoft Download Center Web site (http://go.microsoft.com/fwlink/?linkid=21788).
· Microsoft Windows Installer 3.1. The Updates Publisher Setup installs Windows Installer 3.1, if required.
· Microsoft .NET Framework 2.0. The Updates Publisher Setup installs .NET Framework 2.0, if required.
· Microsoft SQL Server 2005 SP1 or Microsoft SQL Server 2005 Express Edition SP2. The Updates Publisher Setup installs SQL Server 2005 Express Edition SP2, if required.

How to install SCUP

Double click the SystemCenterUpdatesPublisher45.exe.

Click next and it will ask to select local database or install SQL express edition. DO the same

Once clicked next it will install the perquisite and then will proceed the installation

Select The folder

Installation will proceed and will complete the installation

Once done complete the installation click on finish.

How to configure SCUP

Once the installation is over open the console of SCUP.

Click on import updates from the right side. You can download the adobe flash player catalogue from the following link http://fpdownload.adobe.com/get/flashplayer/current/licensing/win/AdobeFlashPlayerCatalog_SCUP.cab

Click on Single Catalogue Import

Point to the CAB file downloaded.

IT will then start uploading

Click on Accept

Once you have completed this you will find adobe flash player as shown below.

Now the set the Publish flag. On the Adobe flash player select settings and then do the following configuration. Select the update server if locally installed the same one or you can select the remote in case you install SCUP.

First, you have to configure SCUP to sign patches with the WSSC. To do that, select the settings option from the console screen

On the Update Server tab, select create to create the WSSC

Once complete, you should have a new WSSC as shown

This action creates the WSSC in the WSUS > Certificates note of the Certificates.msc as shown

So the certificate we need is now created, but we aren’t ready to go yet. Next we have to make sure the WSSC cert is included in the Trusted Publishers > Certificates and the Trusted Root Certificate Authorities > Certificates store.Simple process to export the cert and import it to the other two stores. To export the cert, just right click on it and select to export – take all the defaults and save the cert to a .cer file. To import, just right click on the Trusted Publishers and Trusted Root Certificate Authorities nodes, respectively, and select to import and point to the file.

One this is completed On the SCUP console please do the following. Click on Publish updates

Click on Accept

Once successfully published run the Synchronization in the SCCM server

Once the synchronization is completed the security update you would see the adobe flash layer

Now on the SCCM server Download the update and then create a deployment

Select the DP

Create a Deployment

Now on the clients do the following settings

So now SCUP should be configured to sign updates with the WSSC and publish updates to the SCCM Software Update point and you can deploy them to clients. But, the clients aren’t ready to receive them and will reject the update if it arrives. To get the client ready to receive updates you need to transfer the WSSC to the clients certificate store as well. You can do this manually or even through software distribution using the certutil command.

To deploy the certificate with software distribution, do the following.

Export the WSUS Publishers Self-signed certificate and public key to a directory on the local computer.
Copy the Certutil.exe and Certadm.dll files to the same directory as the exported files. Certutil.exe is a command-line program that is installed as part of Certificate Services in the Windows Server 2003 family and both files are installed in %windir%\system32, by default.
Create a software distribution package containing the files from step 1 and step 2. For more information, see How to Create a Package (http://go.microsoft.com/fwlink/?LinkId=108444)
Add a software distribution program that runs the following command-line: certutil.exe -addstore TrustedPublisher wsus.cer, where TrustedPublisher is the name of the certificate store and wsus.cer is the name of the exported certificate. For more information about creating a software distribution program, see How to Create a Program (http://go.microsoft.com/fwlink/?LinkId=108446). For more information about certutil.exe, see the Certutil Web site on TechNet (http://go.microsoft.com/fwlink/?LinkId=108447)
Create an advertisement for distributing the package and program to the appropriate collection. For more information, see How to Create an Advertisement (http://go.microsoft.com/fwlink/?LinkId=108449).

You may also have to include the WSSC in the Trusted Root Certificate Authorities node as well, which can be done with easy adjustments to the package if needed. Be sure and test first to determine exactly what is needed for your environment.

Once you have the certificates deployed, now you just have to adjust local policy to allow signed cupdates from an intranet Microsoft update service location. You can find that setting as shown below.

To test that everything is working, deploy a SCUP patch to a test client and review the WUAHandler.log. If all is configured properly, you should see the patch install if needed. If there are problems you will notice errors similar to the following in the log.

In the server the updatepublisher.log in %temp% on the SCUP installed machine also help to check the error.

Hope this information would be useful

Sudheesh Narayanaswamy

Troubleshooting SCCM Part VII .......... OSD .... Part I

Posted over 1 year ago

by

Sudheesh N

7 Comments

Part I : PXE boot

Many have been asking to write a blog on how to tracks the logs for OSD so here it is . It is in two parts. Part I is PXE boot and Part II is After the Pxe Boot to Full blown OS. Since we are already in 2012 and 2007 has become obsolete, I will be taking 2012 logs to explain

Before we start troubleshooting OSD with Configuration Manager I would always say it saves a lot of time many times if the pre-requisites are to be checked, Especially if you find client is not PXE booting or if it fails after PXE boots immediately .

If the client is not PXE booting checking the SMSPXE.log on the server where you have the WDS and confirm if the WDS is initialized. You could start the WDS service and check the log flow.

This is how it should be

You would see Provider loading
It will show you the boot images in the WDS which will be opened ,files extracted and copied to boot folders which constitute the boot files for the WDS
Then you will find PXE provider finished loading

================= PXE Provider loaded. ===================== SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

Machine is running Windows Longhorn. (NTVersion=0X602, ServicePack=0) SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

Cannot read the registry value of MACIgnoreListFile (00000000) SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

MAC Ignore List Filename in registry is empty SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

Begin validation of Certificate [Thumbprint D04F5BDFFB9390BFEF89053A315F9D700462DAF5] issued to '02d1e460-a438-493c-b6c7-583601b1e087' SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

Completed validation of Certificate [Thumbprint D04F5BDFFB9390BFEF89053A315F9D700462DAF5] issued to '02d1e460-a438-493c-b6c7-583601b1e087' SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

PXEClientKey certificate valid. SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

Initializing PXEPerfObject. SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

Failed to get logging settings for 'ccmperf' from Registry (80070002) SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

Could not load logging configuration for component ccmperf. Using default values. SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

Client is set to use HTTPS when available. The current state is 224. SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

CLibSMSMessageWinHttpTransport::Send: URL: CM2012SP1.sudilab.com:80 GET /SMS_MP/.sms_aut?MPKEYINFORMATIONEX SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

CLibSMSMessageWinHttpTransport::Send: URL: CM2012SP1.sudilab.com:80 CCM_POST /ccm_system/request SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>

SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

Adding LAB00004.5 SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

Adding LAB00005.3 SMSPXE 20-09-2013 23:43:24 7068 (0x1B9C)

Found new image LAB00004 SMSPXE 20-09-2013 23:43:45 7068 (0x1B9C)

Opening image file C:\RemoteInstall\SMSImages\LAB00004\boot.LAB00004.wim SMSPXE 20-09-2013 23:43:45 7068 (0x1B9C)

Found Image file: C:\RemoteInstall\SMSImages\LAB00004\boot.LAB00004.wim

PackageID: LAB00004

ProductName: Microsoft® Windows® Operating System

Architecture: 0

Description: Microsoft Windows PE (x86)

Version:

Creator:

SystemDir: WINDOWS

SMSPXE 20-09-2013 23:43:45 7068 (0x1B9C)

Closing image file C:\RemoteInstall\SMSImages\LAB00004\boot.LAB00004.wim SMSPXE 20-09-2013 23:43:45 7068 (0x1B9C)

Creating BCD store: C:\RemoteInstall\SMSTemp\2013.09.20.23.43.45.01.{C48BA2BD-1E88-443D-9A6C-B06835F1BABF}.boot.bcd SMSPXE 20-09-2013 23:43:46 7068 (0x1B9C)

StoreFilePath: \??\C:\RemoteInstall\SMSTemp\2013.09.20.23.43.45.01.{C48BA2BD-1E88-443D-9A6C-B06835F1BABF}.boot.bcd SMSPXE 20-09-2013 23:44:02 7068 (0x1B9C)

Skipping creation of variables file for image LAB00004 SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\PXE\pxeboot.com to install queue SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\PXE\pxeboot.n12 to install queue SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\PXE\bootmgr.exe to install queue SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

File C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\PXE\bootmgr.exe has version info: 6.2.9200.16384 SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

File C:\RemoteInstall\SMSBoot\x86\bootmgr.exe has version info: 6.2.9200.16384 SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\PXE\wdsnbp.com to install queue SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\PXE\abortpxe.com to install queue SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\PXE\wdsmgfw.efi to install queue SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

File C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\PXE\wdsmgfw.efi has version info: 6.2.9200.16384 SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

File C:\RemoteInstall\SMSBoot\x86\wdsmgfw.efi has version info: 6.2.9200.16384 SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\EFI\bootmgfw.efi to install queue SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

File C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\EFI\bootmgfw.efi has version info: 6.2.9200.16384 SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

File C:\RemoteInstall\SMSBoot\x86\bootmgfw.efi has version info: 6.2.9200.16384 SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\Fonts\segmono_boot.ttf to install queue SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Copying font file C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\Fonts\segmono_boot.ttf->C:\RemoteInstall\Boot\Fonts\segmono_boot.ttf.

SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\Fonts\segoe_slboot.ttf to install queue SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Copying font file C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\Fonts\segoe_slboot.ttf->C:\RemoteInstall\Boot\Fonts\segoe_slboot.ttf.

SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\Fonts\segoen_slboot.ttf to install queue SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Copying font file C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\Fonts\segoen_slboot.ttf->C:\RemoteInstall\Boot\Fonts\segoen_slboot.ttf.

SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\Fonts\wgl4_boot.ttf to install queue SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Copying font file C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\Fonts\wgl4_boot.ttf->C:\RemoteInstall\Boot\Fonts\wgl4_boot.ttf.

SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Found new image LAB00005 SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Opening image file C:\RemoteInstall\SMSImages\LAB00005\boot.LAB00005.wim SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Found Image file: C:\RemoteInstall\SMSImages\LAB00005\boot.LAB00005.wim

PackageID: LAB00005

ProductName: Microsoft® Windows® Operating System

Architecture: 9

Description: Microsoft Windows PE (x64)

Version:

Creator:

SystemDir: WINDOWS

SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Closing image file C:\RemoteInstall\SMSImages\LAB00005\boot.LAB00005.wim SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Creating BCD store: C:\RemoteInstall\SMSTemp\2013.09.20.23.44.09.02.{B509443D-7FF2-42BD-A182-600F7D65F4BC}.boot.bcd SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

StoreFilePath: \??\C:\RemoteInstall\SMSTemp\2013.09.20.23.44.09.02.{B509443D-7FF2-42BD-A182-600F7D65F4BC}.boot.bcd SMSPXE 20-09-2013 23:44:26 7068 (0x1B9C)

Skipping creation of variables file for image LAB00005 SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\PXE\wdsnbp.com to install queue SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\PXE\abortpxe.com to install queue SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\PXE\pxeboot.com to install queue SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\PXE\pxeboot.n12 to install queue SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\PXE\bootmgr.exe to install queue SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

File C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\PXE\bootmgr.exe has version info: 6.2.9200.16384 SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

File C:\RemoteInstall\SMSBoot\x64\bootmgr.exe has version info: 6.2.9200.16384 SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\PXE\wdsnbp.com to install queue SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\PXE\abortpxe.com to install queue SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\PXE\wdsmgfw.efi to install queue SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

File C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\PXE\wdsmgfw.efi has version info: 6.2.9200.16384 SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

File C:\RemoteInstall\SMSBoot\x64\wdsmgfw.efi has version info: 6.2.9200.16384 SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\EFI\bootmgfw.efi to install queue SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

File C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\EFI\bootmgfw.efi has version info: 6.2.9200.16384 SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

File C:\RemoteInstall\SMSBoot\x64\bootmgfw.efi has version info: 6.2.9200.16384 SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\Fonts\segmono_boot.ttf to install queue SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Copying font file C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\Fonts\segmono_boot.ttf->C:\RemoteInstall\Boot\Fonts\segmono_boot.ttf.

SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\Fonts\segoe_slboot.ttf to install queue SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Copying font file C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\Fonts\segoe_slboot.ttf->C:\RemoteInstall\Boot\Fonts\segoe_slboot.ttf.

SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\Fonts\segoen_slboot.ttf to install queue SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Copying font file C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\Fonts\segoen_slboot.ttf->C:\RemoteInstall\Boot\Fonts\segoen_slboot.ttf.

SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\Fonts\wgl4_boot.ttf to install queue SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Copying font file C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\Fonts\wgl4_boot.ttf->C:\RemoteInstall\Boot\Fonts\wgl4_boot.ttf.

SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Begin validation of Certificate [Thumbprint D04F5BDFFB9390BFEF89053A315F9D700462DAF5] issued to '02d1e460-a438-493c-b6c7-583601b1e087' SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Completed validation of Certificate [Thumbprint D04F5BDFFB9390BFEF89053A315F9D700462DAF5] issued to '02d1e460-a438-493c-b6c7-583601b1e087' SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

PXEClientKey certificate valid. SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

PXE Provider finished loading. SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

If you see errors please act accordingly and make sure that the PXE provider finished loading

Few pointers

Make sure that Boot images are send to PXE point or DP which has PXE
Check for event viewer and make sure there are no errors or warning related to WDS
This is a wonderful article written by Frank Rojas which can help
you with PXE problems. http://blogs.technet.com/b/configurationmgr/archive/2011/01/05/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx

Once this part is done confirm the following

You have created a Tasksequence and that it has a deployment \ Advertisemnt
Deployment is for the PXE (it can be Madatory (Required) or Available)
Referenced Packages are distributed including the boot images
Network Access account is specified

Now that we confirmed that the PXE is loaded successfully. Let us now look at the SMSPXE when the client boots. In 2012 PXE message are pretty good , You could see the DHCP packet information.

DHCP message:

Operation:
BootRequest (1)

Hardware Address type: 1

Hardware Address Length: 6

Hop Count: 0

Transaction ID: 05078C5E

Seconds Since Boot: 4

Client IP Address: 192.168.001.023

Your IP Address: 000.000.000.000

Server IP Address: 000.000.000.000

Relay Agent IP Address: 000.000.000.000

Hardware Address: 00:15:5d:8c:07:05:

Magic Cookie: 63538263

Options:

Type = 53 DHCP Message Type: 3=DHCPRequest

Type = 55 Paramerter Request List:
01020305060b0c0d0f1011122b363c438081828384858687

Type = 57 Max DHCP Message Size: 04ec

Type = 97 UUID:
00562a3213a8399044918b6846be50c648

Type = 93 Client system Arch: IA x86 PC

Type = 94 UNDI: 010201

Type = 60 ClassIdentifier:
PXEClient:Arch:00000:UNDI:002001 SMSPXE 21-09-2013 00:09:17 1612 (0x064C)

CLibSMSMessageWinHttpTransport::Send:
URL: CM2012SP1.sudilab.com:80 GET
/SMS_MP/.sms_aut?MPKEYINFORMATIONEX SMSPXE 21-09-2013 00:09:17 6148 (0x1804)

CLibSMSMessageWinHttpTransport::Send:
URL: CM2012SP1.sudilab.com:80 CCM_POST
/ccm_system/request SMSPXE 21-09-2013 00:09:17 6148 (0x1804)

Client lookup reply:
<ClientIDReply><Identification Unknown="0"
ItemKey="0" ServerName=""
ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>

SMSPXE 21-09-2013 00:09:17 6148 (0x1804)

00:15:5D:8C:07:05, 13322A56-39A8-4490-918B-6846BE50C648: device is not in the database. SMSPXE 21-09-2013 00:09:17 6148 (0x1804)

CLibSMSMessageWinHttpTransport::Send:
URL: CM2012SP1.sudilab.com:80 GET
/SMS_MP/.sms_aut?MPKEYINFORMATIONEX SMSPXE 21-09-2013 00:09:17 6148 (0x1804)

Sending StatusMessage SMSPXE 21-09-2013 00:09:17 6148
(0x1804)

CLibSMSMessageWinHttpTransport::Send:
URL: CM2012SP1.sudilab.com:80 CCM_POST
/ccm_system/request SMSPXE 21-09-2013 00:09:17 6148 (0x1804)

DHCP message:

Operation:
BootReply (2)

Hardware Address type: 1

Hardware Address Length: 6

Hop Count: 0

Transaction ID: 05078C5E

Seconds Since Boot: 4

Client IP Address: 192.168.001.023

Your IP Address: 000.000.000.000

Server IP Address: 192.168.001.002

Relay Agent IP Address: 000.000.000.000

Hardware Address: 00:15:5d:8c:07:05:

BootFileName: smsboot\x86\wdsnbp.com

Magic Cookie: 63538263

Options:

Type = 53 DHCP Message Type: 5=DHCPAck

Type = 54 Server idenitifier:
192.168.001.002

Type = 97 UUID:
00562a3213a8399044918b6846be50c648

Type = 60 ClassIdentifier: PXEClient

Type = 250
02010105040000000203020014040200ba0626506c6561736520776169742e20534d53206973206c6f6f6b696e6720666f7220706f6c6963790b0101 SMSPXE 21-09-2013 00:09:18 6148 (0x1804)

DHCP message:

Operation:
BootRequest (1)

Hardware Address type: 1

Hardware Address Length: 6

Hop Count: 0

Transaction ID: 05078C5E

Seconds Since Boot: 0

Client IP Address: 192.168.001.023

Your IP Address: 000.000.000.000

Server IP Address: 000.000.000.000

Relay Agent IP Address: 000.000.000.000

Hardware Address: 00:15:5d:8c:07:05:

Magic Cookie: 63538263

Options:

Type = 53 DHCP Message Type: 3=DHCPRequest

Type = 60 ClassIdentifier: PXEClient

Type = 97 UUID:
00562a3213a8399044918b6846be50c648

Type = 93 Client system Arch: IA x86 PC

Type = 250
0d0208000e010101020006050400000002ff

Type = 55 Paramerter Request List: 03013c8081828384858687 SMSPXE 21-09-2013
00:09:18 1612 (0x064C)

Getting boot action for unknown machine: item key: 2046820353 SMSPXE 21-09-2013 00:09:18 6148 (0x1804)

CLibSMSMessageWinHttpTransport::Send: URL: CM2012SP1.sudilab.com:80 GET /SMS_MP/.sms_aut?MPKEYINFORMATIONEX SMSPXE 21-09-2013 00:09:18 6148 (0x1804)

CLibSMSMessageWinHttpTransport::Send:URL: CM2012SP1.sudilab.com:80 CCM_POST /ccm_system/request SMSPXE 21-09-2013 00:09:18 6148 (0x1804)

Client boot action reply:<ClientIDReply><Identification Unknown="0"ItemKey="2046820353" ServerName=""
ServerRemoteName=""><Machine><ClientID>0496841d-c8ba-4215-bc34-94da8ad4cd12</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime=""
OfferID="LAB20002" OfferIDTime="20-09-2013 10:07:00"
PkgID="LAB0000B" PackageVersion="" PackagePath="http://CM2012SP1.sudilab.com/SMS_DP_SMSPKG$/LAB00004"
BootImageID="LAB00004" Mandatory="0"/></ClientIDReply>

SMSPXE 21-09-2013
00:09:18 6148 (0x1804)

00:15:5D:8C:07:05,
13322A56-39A8-4490-918B-6846BE50C648: found optional advertisement LAB20002 SMSPXE 21-09-2013 00:09:18 6148
(0x1804)

Looking for bootImage LAB00004 SMSPXE 21-09-2013 00:09:18 6148
(0x1804)

BootImage LAB00004 needs
to be updated (new packageID=LAB00004) VersionUpdate=true SMSPXE 21-09-2013 00:09:18 6148
(0x1804)

PXE::CBootImageInfo::CBootImageInfo:
key=LAB00004 SMSPXE 21-09-2013 00:09:18 6148 (0x1804)

Removing Previous Image
from cache: LAB00004 SMSPXE 21-09-2013 00:09:18 6148 (0x1804)

Creating BCD store:
C:\RemoteInstall\SMSTemp\2013.09.21.00.09.18.03.{8E1D5018-7318-4741-B92A-E5B7005E2039}.boot.bcd SMSPXE 21-09-2013 00:09:18 6148 (0x1804)

StoreFilePath:
\??\C:\RemoteInstall\SMSTemp\2013.09.21.00.09.18.03.{8E1D5018-7318-4741-B92A-E5B7005E2039}.boot.bcd SMSPXE 21-09-2013 00:09:29 6148 (0x1804)

Saving Media Variables to
"C:\RemoteInstall\SMSTemp\2013.09.21.00.09.34.0001.{8E1D5018-7318-4741-B92A-E5B7005E2039}.boot.var" SMSPXE 21-09-2013 00:09:34 6148
(0x1804)

CLibSMSMessageWinHttpTransport::Send:
URL: CM2012SP1.sudilab.com:80 GET
/SMS_MP/.sms_aut?MPKEYINFORMATIONEX SMSPXE 21-09-2013 00:09:34 6148 (0x1804)

Sending StatusMessage SMSPXE 21-09-2013 00:09:34 6148
(0x1804)

CLibSMSMessageWinHttpTransport::Send:
URL: CM2012SP1.sudilab.com:80 CCM_POST
/ccm_system/request SMSPXE 21-09-2013 00:09:34 6148 (0x1804)

DHCP message:

Operation:
BootReply (2)

Hardware Address
type: 1

Hardware Address Length: 6

Hop Count: 0

Transaction ID: 05078C5E

Seconds Since Boot: 0

Client IP Address: 192.168.001.023

Your IP Address: 000.000.000.000

Server IP Address: 192.168.001.002

Relay Agent IP Address: 000.000.000.000

Hardware Address: 00:15:5d:8c:07:05:

BootFileName:
smsboot\x64\pxeboot.com

Magic Cookie: 63538263

Options:

Type = 53 DHCP Message Type: 5=DHCPAck

Type = 54 Server idenitifier:
192.168.001.002

Type = 97 UUID:
00562a3213a8399044918b6846be50c648

Type = 60 ClassIdentifier: PXEClient

Type = 243
024530140000000a000000100000000e66000000000000bc093c433d7f061c5fc88a1e181d6b8d0000000000000000000000005bee9d8efa37c0b84fd289dea97339f4833b1cff01515c534d5354656d705c323031332e30392e32312e30302e30392e33342e303030312e7b38453144353031382d37333172

Type = 252
5c534d5354656d705c323031332e30392e32312e30302e30392e31382e30332e7b38453144353031382d373331382d343734312d423932412d4535423730303545323033397d2e626f6f742e62636400 SMSPXE 21-09-2013 00:09:34 6148 (0x1804)

First you would find the PXE client broadcasting. You will find the DHCP request (1). This contains the MAC ID and SMBIOS GUID. Now once this is got the device is checked for its presence in the database so that it knows if it is known client or not. DHCP reply would go with the boot file wdsnbp.com which will be downloaded and architecture detection happens once the same is done then the pxe client will again request to the boot action. If we have a Mandatory advertisement then it will download PXEBootn12.com else
if there is no Mandatory then it will download PXEBoot.com

This checking is done by looking at against the configuration manager DB. In older version SMSPXE used to connect to DB and now it uses Management point to connect to DB and collect this information.

With Mandatory advertisement \ Deployment which is required

Without Mandatory advertisement \ Deployment which is available

This is the usual boot process

1) A client is directed (by using DHCP Options or the PXE Server response) to download Wdsnbp.com

2) Wdsnbp.com validates the DHCP/PXE response packet and proceeds to download PXEBoot.com or PXEBootn12.com.PXEBoot.com requires the client to press the F12 key to initiate PXE boot.

3) PXEBoot.com or PXEBootn12.com downloads Bootmgr.exe and the BCD store. The BCD store must reside in a \Boot directory in the TFTP root folder. Additionally, the BCD store must be called BCD.

4) Bootmgr.exe reads the BCD operating system entries and downloads Boot.sdi and the Windows PE image (Winpe.wim).

5) Bootmgr.exe begins booting Windows PE by calling into Winload.exe within the Windows PEimage.

Once this is done you will find the Configuration Manager screen as shown below

This is the completion of the PXE boot and once done from here on we get rest of information from smsts.log which first gets created in X:\Windows\Temp\SMSTSLog\smsts.log

Hope this will be helpful.

Part II will cover from WinPE to full blown OS

--------------------------------------------------------------------------------

Sudheesh N

Administartive Checklist for Configuration Manager 2007

Posted over 3 years ago

by

Sudheesh N

13 Comments

Many have been asking for what i need to check to make sure SCCM is healthy. According to me if I were you these are things I would have checked :)

This might not be complete but had tried to include what ever I could think of.

Administrative Activities:

Daily Administrative Task

Daily Site Monitoring Tasks

To best maintain your system, perform the following monitoring tasks on a daily basis. If there is any indication of a problem, isolate and repair the problem to ensure that the site remains healthy.

Daily site monitoring tasks include:

Checking SCCM site database status.
Checking site server status.
Checking site systems status.
Checking client status.
Checking the operating system event log.
Checking the SQL Server error log.
Checking system performance.
Checking SCCM system folders.

Check SCCM Site Database Status

Use the SQL Server DBCC command to check the health of the SCCM site database. Use any other tools available to test the health of the SCCM site database.

Check Site Server Status

View site status summary information in the SCCM Administrator console, or create reports that summarize the server activity and status (such as the Clients that Received a Specific Advertised Program report). If necessary, check status messages of individual components. For further details, in case status messages indicate that a problem exists, view the relevant log files. Isolate and fix conditions that generate errors or warnings. If appropriate, reconfigure the status system so that only relevant and helpful messages are recorded.

Check the status of items such as:

Site components and services. Check if any site server component or service is experiencing any problems.
Packages and advertisements. Check the status of packages and advertisements in your site. Check package and advertisement status messages to ensure that package source files reach distribution points, and that advertised programs reach clients. Check status messages that are returned from clients to see whether the clients run programs successfully or not.
Site-to-Site Communication. Check communication between the site and its parent and child sites (if they exist). Check status messages and, if necessary, check log files of the Replication Manager, Scheduler, and Senders on the site to determine whether the site is having communication problems.

Check Site Systems Status

Check the state of site systems throughout the SCCM hierarchy. Use the status system and, if necessary, use log files to determine if site systems are having problems, such as:

Low level of available disk space.
SCCM components that cannot connect with a site system.

Check Clients Status

Check the state of clients in the hierarchy. Run queries on status messages to detect any problems that clients might be having, such as:

Client components are experiencing problems.
Clients are failing to install.
Clients are not reporting software inventory or hardware inventory.
Clients that are not reporting heartbeat discovery data regularly (or for the past x days).
Client count unexpectedly increasing or decreasing at a fast rate.

You can monitor a client's status only if it creates status messages, and these status messages reach the site server.To detect clients from which you are missing status messages, you need to run a query that returns all clients that have not reported a status message within the last <n> days. In this query, <n> is the length of time you would expect to receive a status message from that client (taking into account the frequency of hardware or software inventory and the regular time it takes for status messages to reach the site server.)

Check the Operating System Event Log

On key servers, check the application, system, and security system event logs. You can access those through the Event Viewer administrative tool. Look for messages that indicate error conditions or developing problems. Isolate and repair the conditions that generate error or warning messages.

When installing an SCCM site server, its default configuration is to write status messages to the event log. This helps you identify any developing problems with SCCM.

Note :When SCCM is configured to write status messages to Windows event logs, SCCM error status messages are written as Information events, not Error events.

Save instances of the most recent event log files for future comparison. When you can compare current log files with previous log files, it is easier to detect problems that are developing. After saving the log files, you can clear them from the event log so it is easier to detect new problems.

Check the SQL Server Error Log

Check the SQL Server error log in SQL Enterprise Manager. Look for messages that indicate error conditions. Isolate and repair the conditions that generate error or warning messages.

Check System Performance

To check whether the site server and component servers have sufficient resources and that SCCM site services are running optimally, you must monitor site server and component server performance. Use performance-monitoring tools such as System Monitor in the Performance console. Check the status of critical components on the site server, on the computer running SQL Server, and other SCCM site systems.

SCCM installs many performance monitor counters, but you can add, remove and configure counters as needed. You can also use the SQL Server performance counters.

Save performance log files for future comparison. It is easier to detect performance trends, and to identify potential bottlenecks, when comparing current performance log file to previous performance log files.

Check Status Filter Rules

Check whether it is possible to reduce the amount of traffic generated by status messages being replicated throughout the hierarchy. If the site is currently healthy, it might be possible to add status filter rules to prevent replication of status messages, which are not necessary.

Check the Inboxes to Monitor

Listed here is a list of the ConfigMgr 2007 inboxes that should be checked on a regular basis to ensure that your site(s) function as expected.
Auth\Dataldr.Box : A backlog of files can indicate problems accessing the site database.
Auth\Dataldr.Box\Process :A backlog of files can indicate problems accessing the site database.

Auth\Ddm.box\Bad_DDRs :A backlog of files can indicate a network corruption problem or a problem with the DDM
Auth\Sinv.Box :A backlog of files can indicate that the Software Inventory Processor cannot connect to the site database or that too many files were received.
Auth\Sinv.Box\Orphans :A backlog of files can indicate problems with specific clients, with management points, or with the network that could cause data corruption.
Compsumm.Box : A backlog of files can indicate that the Component Status Summarizer cannot process the volume of messages.
Dataldr.Box :A backlog of files can indicate problems accessing the Systems Management Server (SCCM) database
Dataldr.Box\Badmifs :A backlog of files can indicate a bad custom MIF file or that a client computer cannot transfer the file correctly.
Ddm.Box :A backlog of files can indicate a bad DDR is preventing other DDR’s to process.
Ddm.Box\Bad_DDRs :A backlog of files can indicate a network corruption problem or a problem with the DDM
OfferSum.Box : A backlog of files can indicate a performance problem that is caused by a large number of messages.
Policypv.Box :A backlog of files in the policypv.box folder indicates that the policy provider component is not running.
Replmgr.Box\Ready:A backlog of files can indicate that the Scheduler is backlogged or is already processing files of the same priority
Schedule.Box:A backlog of files can indicate that the Sender cannot connect to or cannot transfer data to another site.
Schedule.Box\Outboxes :A backlog of .srq files indicates that the sender cannot process the number of jobs scheduled for that sender or that the sender cannot connect to or transfer data to another site.
Schedule.Box\Tosend :A backlog of files can indicate that many send requests are not completed or that the Scheduler has not yet deleted the files.
Sinv.Box :A backlog of files can indicate that the Software Inventory Processor cannot connect to the site database or that too many files were received.
Sinv.Box\BadSinv :A backlog of files can indicate problems with specific clients, with management points, or with the network, causing data corruption.

SiteStat.Box :A backlog of files can indicate a performance problem. Examine status messages for the Site System Status Summarizer for possible problems.
Statmgr.Box\Futureq :A backlog of files can indicate that some site systems' clocks are not synchronized with the site server.
Statmgr.Box\Queue :A backlog of files can indicate a problem with the Status Manager or that the component is trying to process too many messages.
Statmgr.Box\Retry :A backlog of files can indicate problems with the connection to the computer that is running SQL Server.
Statmgr.Box\Statmsgs :A backlog of files can indicate a problem with the Status Manager or that the Status Manager is trying to process too many messages
Swmproc.Box :A backlog of .sum and .sur files can indicate that the Software Metering Processor component cannot connect to the SCCM database.

Check Daily Maintenance Task

Check and make sure that the daily Maintenance Task if any. We can use the smsdbmon.log for more details.

Weekly Administrative Task

Weekly Site Monitoring Tasks

To best maintain your system, perform the following monitoring tasks on a weekly basis. If there is any indication of a problem, isolate and repair the problem, to ensure that the site remains healthy.

Weekly site monitoring tasks include:

Checking SCCM site database available space.
Checking available disk space.

Check SCCM Site Database Available Space

To find the amount of space used by database devices, run the SQL Server stored procedure sp_spaceused against the SCCM site database. For more details about sp_spaceused, see the SQL Server Help. Check the tempdb device at peak usage, when several instances of the SCCM Administrator console are using the database and the site is actively processing objects.

Check Available Disk Space

Check the amount of available disk space on the site server, the SCCM site database server, and other SCCM servers. Ensure that the amount of free disk space is sufficient for SCCM and SQL Server to perform properly during regular and increased activity load.

To use the Status System to view information about site system disk space

In the SCCM Administrator console, navigate to Site System Status.

Configuration Manager > Site Database > System Status> Site Status> <site name>> Site System Status

In the details pane, view status information of site systems such as free disk space.

Weekly Site Maintenance Tasks

To best maintain your system, perform the maintenance tasks in this section on a weekly basis. You can automate some tasks by scheduling predefined maintenance tasks or custom maintenance tasks, as appropriate, to run on a weekly basis.

Weekly site maintenance tasks are:

Weekly automated tasks.
Delete unnecessary files.
Delete unnecessary SCCM objects.
Produce and distribute end-user reports.
Run disk defragmentation tools.
Back up application, security, and system event logs.

Weekly Automated Tasks

The following predefined maintenance tasks should be scheduled to run on a weekly basis. For more information about these tasks, see the "Predefined Site Maintenance Tasks" section earlier in this chapter.

Rebuilding Indexes
Monitor keys
Delete aged inventory history
Delete aged discovery data
Delete aged collected files
Delete aged software metering data
Delete aged software metering summary data
Summarize software metering data
Summarize software metering periodic usage data

Delete Unnecessary Files

If Management Information Format (MIF) files or IDMIFs are used to extend hardware inventory in your site, then any MIF files that are not valid are placed in the SCCM\inboxes\dataldr.box\BADMIFS folder and SCCM never removes them. You must empty this folder manually. If a large number of MIFs are placed in the BADMIFS folder, it is likely that a MIF generating tool is producing the MIFs with an incorrect format. Investigate and repair the cause of the bad MIFs.

Delete Unnecessary SCCM Objects

Delete objects such as collections, queries, and packages that are no longer needed at the site. Deleting unnecessary objects saves disk space, reduces intersite replications, and increases performance.

Caution :When deleting a collection, any advertisements to that collection are also deleted.

Run Disk Defragmentation Tools

Over time, disk volumes on SCCM site systems become fragmented. Site operations such as distributing large software packages might significantly increase fragmentation on site servers and distribution points. As fragmentation increases, disk operations take longer, thus, the overall site performance decreases.

Run disk defragmentation tools on the SCCM site server and all other site systems to maintain the performance level of disk operations.

Back Up Application, Security, and System Event Logs

Windows event logs can get full, and by default, new items will start to overwrite older items. To diagnose problems, and for other reasons, it might be necessary to refer to an older event log. It is recommended that you back up Windows event logs, and store the backups in a safe and accessible location. If necessary, increase default logs file size to accommodate larger amounts of data.

Periodic Administrative Task

Periodic Site Maintenance Tasks

To best maintain your system, perform the following tasks periodically. Use the predefined maintenance tasks when appropriate.

Periodic site maintenance tasks include:

Backing up account data.
Changing accounts and passwords.
Checking network performance.
Reviewing the security plan.
Reviewing the maintenance plan.
Performing recovery tests.

Back Up Account Data

To properly recover a site server, you must have information about the accounts that SCCM used before the site failed. Account data is stored in domain controllers.

Use Microsoft tools, such as the NTBackup.exe tool that comes with Windows Server, or third-party tools to back up account data as follows:

If there are multiple domain controllers in your infrastructure that contain the SCCM account database, you need to periodically back up the account database. (If Active Directory® directory service is implemented in your organization, then such a task might be included in the Active Directory maintenance plan.)
If the account database is stored on a single domain controller, then back up the account database frequently. Depending on the frequency of changes to account data, you might need to add this task to the site's daily or weekly maintenance tasks.
If the account data is stored on member servers, then regularly back up the whole operating system that contains the account data, using software that backs up account lists and the account database.
Whenever there is a change to the password of the Client Push Installation account or to the site system connection accounts, you should note that change. For security reasons, SCCM encrypts the Client Push Installation account and the site system connection accounts. You need to be able to retrieve these accounts' passwords so that you can re-enter them during a site recovery operation.
In between account database backups, document any changes to accounts. Write down and save any changes made to SCCM accounts and share rights so that you can apply those changes again after recovering the site.

Change Accounts and Passwords

To maintain the level of security in your hierarchy, you must periodically change the passwords and the accounts that SCCM sites use. Report any changes to the security staff so that security administrators know that these changes are planned and authorized.

To develop an effective security maintenance plan for your SCCM hierarchy, you must thoroughly understand how security is deployed in your hierarchy and make the following decisions:

Which accounts need to be changed, and for which accounts is it sufficient to change only the password.
How often to change passwords and accounts.
How to change passwords and accounts (such as by running SCCM site reset).
Which accounts cannot be configured by the administrator (either the account name cannot be changed, or the password cannot be manually modified).

Check Network Performance

Check the available bandwidth and error rates on the networks used by the SCCM hierarchy. Use Network Monitor to capture and analyze network frames so you can diagnose network problems and look for optimization opportunities.

Review the Security Plan

SCCM evolves with time. User roles change, and people might no longer need access to some or any of the SCCM functions. Although most changes in access permission should be implemented after role or staff changes, you should also periodically review the access for all users or groups to identify and delete unauthorized access permissions.

The security plan implemented for the SCCM hierarchy in your organization needs to support the risk assessment of your organization. As your organization changes, policies can become ineffective.

Review security-related settings such as:

Who has access to SQL Server and to the SCCM site database.
Who can download from SCCM distribution points.
Which accounts have permissions within SCCM security.
Periodically, re-evaluate the risk assessment of your organization, and then review and update the security plan accordingly.

Review the Maintenance Plan

Use the maintenance plan document to review the SCCM maintenance plan. SCCM evolves with time, and it might be necessary to adjust the maintenance plan to accommodate growth, development, and other changes in your organization.

If there were any changes in your organization's security strategy, backup and recovery strategy, or any other strategy that affects SCCM, then determine if the maintenance plan needs to be adjusted to reflect these changes.

Review maintenance tasks configuration. Check the amount of data in the site database and evaluate the usefulness of that data against the amount of space that it occupies in the database. If necessary, adjust the settings that determine the number of days that data is retained in the database.

Update the maintenance plan document to reflect any changes to the maintenance plan, and then distribute it to all SCCM administrators that are using it.

Perform Recovery Tests in a Test Lab

The best way to be fully prepared for a site recovery operation is to ensure that the recovery plan is adequate and that administrators are familiar with the recovery process. After you develop a recovery plan for your site, it is recommended that you perform periodic recovery tests in a test lab.

A recovery test should follow the recovery plan developed for the production environment. Plan to perform a recovery test of the central site, and of any other systems deployed in your hierarchy. A recovery test should test all phases of recovery, including:

Backing up a site.
Archiving the backup snapshot.
Simulating a site failure, such as by turning a server off.
Recovering the failed site.
Verifying the success of the recovery operation.
You might schedule periodic recovery tests. Company policy might require that new administrators always perform a recovery test. It is strongly recommended that you always include a recovery test when testing major changes to the hierarchy.
For example, before upgrading site server operating systems, you should probably first test the upgrade in the test lab. After completing the upgrade in the test lab, you should perform a recovery test to identify any issues or adjustments to the recovery plan associated with the operating system upgrade. This ensures that if you upgrade the servers in the production environment, you will still be able to successfully recover a failed site.
Include a recovery test in every major deployment test, such as:
A major operating system upgrade (not service pack).
A major change to the networking infrastructure.
New equipment deployment or building relocation.
An SCCM major version site upgrade.

Periodic Site Monitoring Tasks

To best maintain your system, perform the following monitoring tasks periodically. If there is any indication of a problem, isolate and repair the problem to ensure that the site remains healthy.

Periodic site monitoring tasks include:

Checking hardware.
Checking site's overall health.
Checking the backup snapshot.

Check Hardware

Even high-quality hardware occasionally fails. Sometimes, it fails gradually, so there might be early signs. Replacing hardware before it completely fails is a key step in preventing site failure. Both Windows and SCCM provide performance counters, which you can use to monitor the performance and state of the hardware used in the site.

As soon as you notice any signs of hardware-related unreliable behavior of an SCCM server, replace the hardware. To properly replace server hardware, you must use the Recovery Expert. For more information about swapping the computer of SCCM servers, see the "Swapping the Computer of a Site Server" section later in this chapter.

Check Site's Overall Health

It is recommended that you periodically perform a more thorough health check, as follows:

Ensure that all SCCM services are running.
Review the Status Message System for Critical status.
Ensure that all the latest service packs are installed.
Ensure that the latest critical security patches are installed.
Examine the System and Application Event logs for errors.
Note
- When SCCM is configured to write status messages to the system's event log, SCCM error status messages are written as information events, not error events.
Run a query to determine if discovery data is being updated correctly in the SCCM site database. The query should list all installed clients in which System Resource - Agent Time is not within the heartbeat interval. It is expected that some clients might be offline, but in other cases, it might indicate a problem.
Run a query to determine if software inventory data is being updated correctly in the SCCM site database. The query should list all installed clients in which Last Software Scan - Last Inventory Collection is not within the software inventory interval. It is expected that some clients might be offline, but in other cases, it might indicate a problem.
Run a query to determine if hardware inventory data is being updated correctly in the SCCM site database. The query should list all installed clients in which Workstation Status - Last Hardware Scan is not within the hardware inventory interval. It is expected that some clients might be offline, but in other cases, it might indicate a problem.

If any of these tests fail, you need to diagnose the problem and repair it.

Check the Backup Snapshot

At the end of every site backup cycle you should check the validity of the backup snapshot. Periodically, you should perform a more thorough check to ensure that the site's backup snapshots can be successfully used for recovery.

Restore a recent backup snapshot to a disk and examine file continuity, file size, and other file properties to ensure that they do not seem corrupted. Check critical files by restoring these files to their respective applications to ensure that the application can use the restored file.