SMS to SCCM migration wrong MP
The clients should be getting the boundaries from the new SCCM server now. I guess I was just concerned over the MP. I have been getting errors like the following. Do you think they could be related?: SMS_INVENTORY_DATA_LOADER SMS Inventory Data Loader failed to process the delta MIF file "XHM8JM818.MIF" and has moved it to "C:\Program Files\Microsoft Configuration Manager\inboxes\auth\dataldr.box\BADMIFS\id310iq0.MIF." Possible cause: The file attempted to update inventory information in the SMS site database that does not already exist, or the file contains invalid syntax. Solution: The client inventory needs to be resynchronized, which will be done automatically. Look for the status messages 2714 and 2715, which indicate the resynchronization has begun. SMS_MP_CONTROL_MANAGER: ---------- MP needs to reload the hardware inventory class mapping table when processing Hardware inventory. The MP hardware inventory manager cannot find a WMI class definition in the mapping table when processing a report. This should only happen if new definitions beyond those known to the SMS are added to the collected classes. Possible cause: Inconsistent way the new definitions have been introduced. Solution: Check that the mapping tables contain the information consistent with the hardware definition tables and that the definitions have been propagated properly. Possible cause: Corruption of the data base. Solution: Check the consistency of the data base. -------------- MP has discarded a report when processing Ddr. Possible cause: Corruption or invalid user definition. Solution: Check the logs to identify the cause. If the problem is persistent raise the issue with Microsoft support ------------- MP could not find some class or property definitions when processing Hinv as they are apparently missing in sms_def.mof. Unknown classes and properties have been ignored and a MIF file generated with all the classes and properties that could be found. Possible cause: This might indicate that the report has become obsolete due to a new HW inventory policy or that a customer's private definitions haven't been properly propagated to the sms_def.mof at the PSS. Solution: See if the missing classes or properties are genuinely missing in the current sms_def.mof and find out why the client put them in the xml report. ------------ SMS Component Status Summarizer detected that the availability of component "SMS_MP_CONTROL_MANAGER" on computer "SERVERSCCM" has changed to Offline. Possible cause: This component is under maintenance or shutdown. Solution: Verify that maintenance is not being performed at this time and the component is running. If the component is not running, restart it using SMS Service Manager. ------------ This component started. ----------------- SMS Component Status Summarizer detected that the availability of component "SMS_MP_CONTROL_MANAGER" on computer "SERVERSCCM" has changed to Online. --- SMS_Software_Inventory_process SMS Software Inventory Processor failed to process software inventory file "C:\Program Files\Microsoft Configuration Manager\inboxes\auth\sinv.box\8XK68UUJ.SID," and has moved it to "C:\Program Files\Microsoft Configuration Manager\inboxes\sinv.box\BADSinv\cvbzsxi5.SID." Possible cause: The file attempted to update inventory information in the SMS site database that does not already exist, or the file contains invalid syntax. Solution: The client inventory needs to be resynchronized, which will be done automatically. Look for the subsequent message 3703, which indicates the resynchronization has begun.
March 16th, 2011 7:10pm

Hello, I am in the middle of doing a migration from SMS to SCCM and am using the following script http://blogs.catapultsystems.com/jsandys/archive/2010/12/30/updated-configmgr-startup-script.aspx to deploy the clients in a cross-forest enviroment involving 4 different domains. One domain will host the SCCM server and all servers. So far the migration has been going well. I specified the MP, SLP etc in the script and computers appear to be functioning. Lately I noticed errors with the MP in my status along with inventory etc. I checked the logs and it appears that the old SMS settings in active directory are overwriting the MP with the old server. I ended up having overlapping boundaries between SMS and SCCM during migration because I still needed to be able to work with systems I disabled client push and I figured that would have been enough. At this point I have most of my systems with the SCCM client isntalled with the correct site assignment, SLP etc but they keep getting the wrong MP from AD. I plan on decommissioning my SMS servers and deleting the offending objects from the systems management container in AD. Should this be enough to fix my problem. Will the clients automatically pick up the correct MP from SLP since they can't get it from AD anymore? If they will remain with the incorrect MP do I have any way of fixing this without reinstalling since the script above doesn't appear to have checks for the MP. DNS suffixes etc all have been taken care of so I know that they can resolve MP, SLP etc. Please advise. Thank you!
Free Windows Admin Tool Kit Click here and download it now
March 16th, 2011 8:31pm

You could remove all boundaries from the old SMS site. The only thing that does no longer work then will be auto-assignment and all DPs will be treated remote/slow.Torsten Meringer | http://www.mssccmfaq.de
March 16th, 2011 9:46pm

Hi, Would removing the old boundaries correct the MP issue? Do I have to do anything else or will the clients correct themselves? I am not concerned with auto assignment since the clients get installed via script. Why would all DPs be treated as remote/slow?
Free Windows Admin Tool Kit Click here and download it now
March 16th, 2011 9:56pm

It will most likely solve that issue, but that's hard to tell here in the forums. DPs are treated slow, because clients are not within any boundary then (because there are none). Each content location request will result in all DPs being treated slow. So double-check the advertisement settings ("slow -> do not run" would prevent the clients from installing anything).Torsten Meringer | http://www.mssccmfaq.de
March 16th, 2011 10:18pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics