Solved

SCCM 2012 R2 Upgrade

Posted on 2014-04-14
4
90 Views
Last Modified: 2016-06-04
Hi I was running SCCM 2012 SP1 with the one primary site and a distribution point and a management point in a non-trusted forest. I have upgraded the primary site to R2, but the upgrade of the DP and MP in non-trusted forest is failing with the following errors. The re install keeps failing.

I have tried-
1. To add the server account from the second forest to the group "SMS_SiteSystemToSiteServerConnection_MP_DPC" but unable to do as it is from another forrest
2. Check the firewall
3. Added a entry in the host file to resolve the FQDN

Errors in order-

1. Site Component Manager failed to add machine account SV-MP-SCCM.[DOMAIN NAME] to the user group SMS_SiteSystemToSiteServerConnection_MP_DPC, this must be done manually.

2. Site Component Manager failed to install this component, because the Microsoft Installer File for this component (MP.msi) could not install.

3. Site Component Manager failed to reinstall this component on this site system.

Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the reinstallation in 60 minutes. To force Site Component Manager to immediately retry the reinstallation, stop and restart Site Component Manager using the Configuration Manager Service Manager.

Please help. Thank you.
0
Comment
Question by:PremCab
  • 2
4 Comments
 
LVL 31

Expert Comment

by:merowinger
ID: 40001067
Is the Primary Site Server local Administrator on the remote MP and DP Server?
Is there a trust between the Forests? You should be able to add the MP's Machine Account to the specific SCCM group
0
 

Author Comment

by:PremCab
ID: 40002925
Thank you for your reply. There is no trust between the forests. So no I can't add the Primary site server to the local admin group on the DP/MP.
0
 

Accepted Solution

by:
PremCab earned 0 total points
ID: 40002944
For those who might be interested I have fixed the issue. I don't have an explanation on how the fix worked.

After trying several different things including,
1. Fiddling with Forrest discovery
2. Changing the install account for the MP/DP

I managed to fix it by installing a new role on the MP/DP server. I installed the USMT role just to see if that would give the install process a kick in the gut and it worked. The roles are properly installed now. No errors. Thank you.
0

Featured Post

The Eight Noble Truths of Backup and Recovery

How can IT departments tackle the challenges of a Big Data world? This white paper provides a roadmap to success and helps companies ensure that all their data is safe and secure, no matter if it resides on-premise with physical or virtual machines or in the cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Are you one of those front-line IT Service Desk staff fielding calls, replying to emails, all-the-while working to resolve end-user technological nightmares? I am! That's why I have put together this brief overview of tools and techniques I use in o…
Scenario: Your operations manager has discovered an anomaly in your security system. The business will start to suffer within 15 minutes if it is a major IT incident. What should she do? We have 6 recommendations for managing major incidents (https:…
Two types of users will appreciate AOMEI Backupper Pro: 1 - Those with PCIe drives (and haven't found cloning software that works on them). 2 - Those who want a fast clone of their boot drive (no re-boots needed) and it can clone your drive wh…
Nobody understands Phishing better than an anti-spam company. That’s why we are providing Phishing Awareness Training to our customers. According to a report by Verizon, only 3% of targeted users report malicious emails to management. With compan…

776 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question