-

SCCM 2012 Migration Connector stops working and gathering of data fails from destination Site.


Cause-

 Check if you have multiple SMS Provider exist in your CM 2012 Hierarchy and that's only causing the issue.


Resolution- 

Uninstall all the additional SMS Providers and reset the site (happens automatically upon removal).


 Pre_Checks-

You can just open up a Powershell on one SMS Provider you know (you always know at least one) and execute the following query:

(Get-WmiObject -class SMS_ProviderLocation -Namespace root\SMS).Machine
This will give you something like this:

SMS_ProviderLocation


Steps for removing a SMS Provider
1) Open the Start Menu on the ConfigMgr server and select Microsoft System Center 2012 > Configuration Manager > Configuration Manager Setup
2) Getting Started > Select "Perform site maintenance or reset this Site" and click Next
3) Site Maintenance > Select "Modify SMS Provider configuration" and click Next
4) Manage SMS Providers > Select "Uninstall a SMS provider" and "Enter the FQDN of the server where the SMS Provider is to be Uninstalled" and click Next
Then start gathering the data again...

Comments

Post a Comment

Popular posts from this blog

SCCM: Determining installed applications last use time_ SQL Query.

-
ConfigMgr will definitely be able to let SCCM admins know what are installed in the environment regardless if it is a server or workstation. SCCM by default comes with a set of reports that SCCM admins can utilize to gather information. The one that I am going to mention today is , "Computers that has a metered program but have not run the program since a specific date". What is so special about this report you may think, I had the same thinking as you but it is pretty interesting to know how is this data derived. The data set for this is based on Software Inventory and this means gathering file types that are on machines. The last used time is gathered asp art of software metering. This report will provide the information based on the files inventoried and their respective last used date. Nothing unique right? Here comes the interesting part, picture the scenario as below. All of us will know that in order for Microsoft Office to be used, it has to be inst
Read more

Unable to read existing WUA Group Policy object. Error = 0x80004005.

-
Image
Wanted to share.. It will be helpful to achieve maximum rate of patching compliance. As we often face issues to troubleshoot the systems with  "Enforcement Status Unknown" state. Issue Some of the servers / workstations are appearing as “ Enforcement Status Unknown ” in Patching Deployment Report. Logs mentioned below. Unable to find or read WUA Managed server policy. Unable to read existing WUA Group Policy object. Error = 0x80004005. Failed to Add Update Source for WUAgent of type (2) and id ({6219E813-D37D-4D15-ADA7-3E4DADF55C9E}). Error = 0x80004005. Resolution Issue appears to be with corrupt policy info locally on the machine.  Please go to c:\windows\system32\grouppolicy\machine and delete the registry.pol  file.  Run GPUpdate /force command after that .
Read more

SQL Query to find the detailed Enforcement Status of a Software Update Deployment for Patching.

-
Please find the query below. select vrs.name0, a.Assignment_UniqueID as DeploymentID, a.AssignmentName as DeploymentName, sn.StateName as LastEnforcementState, assc.StateTime , a.CollectionName, assc.Lasterrorcode from v_CIAssignment a join v_AssignmentState_Combined assc on a.AssignmentID=assc.AssignmentID join v_StateNames sn on assc.StateType = sn.TopicType and sn.StateID=isnull(assc.StateID,0) join v_R_System vrs on vrs.ResourceID=assc.ResourceID where a.AssignmentID=" Put the Assignment ID of the deployment "
Read more