Steps for Manually Data Restore after PC REFRESH using USMT:-

Check if Recovery information is available for that specific computer in ‘Computer Association’ in respective site server.

Where,

\\SAPMSMSHUBUD001.CRB.APMOLLER.NET\SMPSTOREE_D18368C9$\B1A958D97DB24B5B92E065718C2282D0CEA67E4A8C9B8D3FBC7985D7D401BCA   - Path where the User State data stored on SMP.

D279953B-5454-469F-BB11-77A68E9D01B3   - Recovery key.

• Copy user state data and USMT package to user’s local drive viz. ‘C:\store’ and ‘C:\usmt’ resp. Also create folder named ‘temp’ where state restore logs will be stored.
• Open ‘Command Prompt’ and enter to ‘usmt’ directory. 
• Type following command  as,

C:\usmt>loadstate.exe c:\store /decrypt /key: D279953B-5454-469F-BB11-77A68E9D01B3 c /l:"C:temp\loadstate.log" /progress:"C:\temp\loadstateprogress.log” /i:"C:\usmt\MigApp.xml" /i:"C:\usmt\MigUser.xml" /i:"C:\usmt\MigSys.xml" /i:"C:\usmt\Custom.xml" /lac /lae

How to fetch the SMSTS LOG during OSD..

If you get any Error during installation then follow below steps for collecting the logs from Target PC.

1) Please create a folder on your PC and give full permission to every one. 

1) Press “F8” once the installation failed with Error.

2) Then you will get a Command Prompt.

3) Type "net use z:\\yourPC IP\sharefoldername"

4) Then type your user name and password

 

Please find the below Screen Print…

 

Clean-up your Inboxes!!!

look at is the folders in \Microsoft Configuration Manager\Inboxes.  These folders contain all the activity of ConfigMgr and typically consist of files which are coming and going.  However, some times things go wrong and a bunch of files can start accumulating in these folders, eventually running you out of disk space.  This is never good and you should look into the root cause to fix it before worrying to much about the files themselves.  However, some things fix themselves, or some files are left behind after fixing the problem, and those problems are a nuisance that needs to be cleaned up and removed.  I will try and provide a list of some of the folders I look at and recommend cleaning up if there are old files in them.

should make a note here that while you can just delete the files, and will be fine in most cases, it is a good practice to instead move the files to a temp folder long enough (a day or week) to make sure there are no negative repercussions from the file removals.  It is just smart to play it safe.

• Compsumm.box – This is for component summarizer messages.  If you have old stuff, it may not be relevant any more so remove the files.
• CIAMgr.box – Configuration items, probably related to patches but perhaps for other things.  If the files are older than a week, they have probably been forgotten and can be removed.
• Auth\dataldr.box\badmifs – Hardware inventory that was bad for some reason.  Often times the bad file will be a temporary thing and the system will self correct, leaving files behind.  Once you have investigated and solved the reason it is bad, feel free to remove the files.
• Hman.box – Don’t touch stuff in the subfolders, but if files in the root are old, site communication probably had a hiccup at some time and the files can be removed.
• Sinv.box\badsinv – Software inventory gone bad, similar to the dataldr.box\badmifs.  Remove files once any investigation is done.
• Statmgr.box – These are status messages and old files can be removed as they are probably no longer relevant.
• Auth\statesys.box\corrupt – Old status messages here should be removed .  They are probably out of date anyway.
• Auth\ddm.box\regreq\bad_ddrs - These are discovery records that couldn't process for some reason.

There are lots of inboxes, and I’m sure many of them also get file backlogs for various reasons.  these are just the ones I see most often.  As I see and validate them I will update this list as appropriate.

POST SC Client installtion....

Once the agent is available on the network and the client is installed, the client goes through the following actions as part of the reporting process:

• Client location services identify the site code and the MP it is supposed to connect to.
• The client connects to the Management Point and downloads the policies.
• Once the policies are downloaded it sends the heartbeat record to the server.
• Once the server receives this heartbeat record these are converted in to DDR and processed.  This will set the client flag to 1 which will make the client status display as Yes in the console.
• On a regular basis the agent will send the heartbeat and if no heart beat or inventory shows up for a length of time then the client flag will be marked as 0 by the client flag maintenance task, setting the client status to No.

 

SCCM Port Details

·         -- > indicates one computer initiates and the other computer always responds

·         < -- > indicates that either computer can initiate

 

How to Perform WMI Repair & Check WMI Health

To Repair WMI:

 To repair WMI follow the steps below, Please note that this is a destructive process and must only be used in the case where wmi is corrupt.

Step 1:
%windir%\system32\wbem\winmgmt /clearadap
%windir%\system32\wbem\winmgmt /kill
%windir%\system32\wbem\winmgmt /unregserver
%windir%\system32\wbem\winmgmt /reserver
%windir%\system32\wbem\winmgmt /resyncperf

Step 2:
net stop winmgmt /y

Step 3:
If exist %windir%\system32\wbem\repository.old rmdir /s /q %windir%\system32\wbem\repository.old
ren %windir%\system32\wbem\repository repository.old
regsvr32 /s %systemroot%\system32\scecli.dll
regsvr32 /s %systemroot%\system32\userenv.dll
for /f %%s in (‘dir /b /s %windir%\system32\wbem\

Step 4:
net start winmgmt /y

Note: Ensure that the Windows Management Instrumentation service is running after performing the above steps

To Check WMI health & connectivity :

 

How the Client works.

How the Client works....

Once the Setup program is complete, the SCCM Advanced Client obtains a site assignment, sends the heartbeat discovery information to the SCCM site server, and then contacts the default management point to retrieve the SCCM Advanced Client policy.

During the pre-installation phase, SCCM discovers the client computer and then generates a client configuration request Client Configuration Request file. The CCR file contains the client computer name and additional information.)

The SCCM Client Configuration Manager connects to the ADMIN$ share on the client. This is based on the information in the CCR file.

The Client Configuration Manager connects to the client registry and gathers information about the client. This process is displayed as a log entry in the Ccm.log as connecting to IPC$.

The SCCM core component files, MobileClient.tcf and Ccmsetup.exe, are located in the SMS\bin\I386\ folder. These files are downloaded to the %windir%\System32\ccmsetup folder on the client computer.

The Client Configuration Manager verifies that the Ccmsetup service started successfully before disconnecting. The CCR file is added to the SMS\Inboxes\Ccrretry.box folder for verification that the installation succeeded on the server. On a second verification pass, SCCM determines that the SMS Agent Host is running, and then deletes the CCR file.

If the Client Configuration Manager encounters any errors during this process, the CCR file is renamed to the name of the target client computer and is put in the SMS\Inboxes\Ccrretry.box folder. The Client Configuration Manager checks for files in this inbox folder every 60 minutes and tries to reprocess them 168 times (7 days) before they are discarded. This information is logged in the Ccm.log.