Replacing the primary site server, SCCM 2012 R2

Hi,
Setup is currently SCCM 2012 R2 with the primary site server on Windows 2008 R2 on a Hyper-V VM with a separate physical SQL server on 2008 R2 (Windows and SQL). I'm not making any changes to the SQL server at this stage.
I want to completely replace the primary site server VM completely with a brand new VM using Windows 2012 R2.
I was looking to run the SCCM setup and using the Expand an existing stand-alone primary into a hierarchy option but it wont let me do that due to "The site code you specified should not be the same as the primary site's site code".
So seems this Expand an existing option isn't the right option for me?
Do I just add the new server in the SCCM console and add all roles and test and then delete the roles from the old server?
Thanks
EDIT: I have 7 Secondary sites, so I dont want to just start over by doing some sort of backup and restore to the new server unless someone can tell me that wont break my hierarchy.

a backup and recovery is the correct way to do this, but there are a few things you should keep in mind.
Do a backup of your current environment and shut everything down.
install new vm, ensure the configuration is identical, (dns, hostname, etc...); install the same software and pre-requisites,
do a recovery
check the following links on how to do a backup and restore:
http://www.windows-noob.com/forums/index.php?/topic/7403-how-can-i-backup-system-center-2012-configuration-manager/
and
http://technet.microsoft.com/en-us/library/gg712697.aspx

Similar Messages

There is a problem connectiong to the specified reporting Server SCCM 2012 SSRS

hi,
I'm Trying to install reporting services point SCCM 2012, I configured the
site system role without problems, but when I tried to configure the report options I get this error:
"There is a problem connectiong to the specified reporting, please check the conection and make sure SQL Reporting Service is running on the especified server. "
The reporting service is running on remote server, I'm using SQL SERVER 2008.
Two Questions:
1: Which is the cause of the error?
2: Which right permissions must have the reporting services point account?
Thanks.

Are you allowing port 1433 through the firewall?
Which release of SQL Server are you using and have you applied the relevant minimum CU? Details here
http://sccmentor.wordpress.com/2013/12/31/sql-server-site-database-configuration/
Which version of SRS is installed? If 10.50.1600.1 you will need to get this updated to above 2500 level.
http://www.mssccmfaq.de/2012/05/15/srs-not-detected-as-running/
Cheers
Paul | sccmentor.wordpress.com

Cannot Reinstall Site Server - SCCM 2012 R2

We just upgraded to SCCM 2012 R2. Everything went fine until the one secondary site server failed to upgrade. After fiddling for awhile we just wiped the site out, reinstalled the server and rebuilt the site (same Server Name and Site Code).
However, the fresh server is serving up the same errors as the old install attempt. It would seem that there is something leftover preventing the install. It is for sure not working because it cannot detect the .NET 3.5 and 4 we have installed
on the server and instead returns an error on the prerequisite checks. I tried using preinst.exe to delete the site and I took a look at the hman.box for the deletion list but there was nothing there.
Has anyone had this trouble before?

If I'm reading your comments correctly, I'm not sure what you were expecting preinst.exe to do for you. If a site fails to install due to not being able to pass the prereq checker, preinst has nothing to do with that.
It sounds like the appropriate features are not enabled in Server Manager for the .NET 3.5 and 4.0. Have you checked the documentation library for the requirements for a server to become a secondary site? They should all be listed. Until you get all those
additional features installed, then yes, you'll not be able to pass the prereq checker, and won't be able to install the computer as a site server.
Wally Mead

SCCM 2012 Primary Site server is piling up so huge

Hello Folks,
We recently implemented SCCM in our environment for a month ago. Its a stand-alone primary site model running DB on the primary site server itself. But, have segregated the drives for content, DB, and C drive for holding up the SCCM server related
installations. I haven't noticed the data growth on the server, as a result the C drive ran out of space yesterday and increased 40 GB more than the earlier. As of now, C drive has about 120 gb in total and there is only 25% left on whereas it had 33%
after expanding to 120 GB. When digging through the blogs, I doubted it could be BAD MIF inbox folder(screenshot attached), so went ahead and ran space check on the server, and looks like the major % of drive space is being occupied by the inbox folder and
also it is increasing day by day. I need further more directions on how this can be monitored to find out growth % and fix this.
I checked basic stuffs like clearing up profile & recycle bin data and any of this kind.
Step by step guide in detail should be more helpful in this regard. And, I hope this should be helpful for a larger SCCM admin crowd like me in the universe.
I also want to know what are the settings in SCCM console associates with these folders so that the settings can be streamlined to match the best practices (like inventory schedule for every 1 week & software inventory best practices) if at all, if we
have enabled in the implementation phase to receive fast & large results.
Thanks, V@s!m

We are seeing a stable disk size nowadays.
With that hopefully, this is a time to sum up the actions taken.
1. SCCM 2012 implemented a couple of months ago.
2. During the implementation phase, Client & Discovery settings were enabled to be quite an aggressive schedules to get good amount of results in a short period.
3. Implementation had been successfully completed and the system was running just fine until I noticed the space crunch
4. I thought it was normal and increased the disk space by 50% which got ate up in a couple of days and that's when I started suspecting about something is going wrong
5. As an interim solution, have increased the disk space by 70% and started troubleshooting the SCCM buddy.
6. Discovery settings were brought down to not to be aggressive (but this wasn't the issue) - still the issue was going on
7. Inventory settings were too brought down to be nominal (Useful :
http://www.informit.com/articles/article.aspx?p=1912064&seqNum=8)
8. By this time, I brought my colleague who was involved during the Implementation. We did the clean-up on server, went through the Inbox\Auth folders and were trying to figure out still what is going wrong.
9. We couldn't notice much improvement about the situation though we gave enough time for each and every fix that we applied.
10. Through some warnings and errors in the site system status, remembered that the 'Configuration.mof' was modified for testing some customized inventory classes, during the implementation phase which was getting mismatched data from lot of different clients.
- "Potential cause figured out"
11. Replaced the original Configuration.mof, and we started noticing big differences - the space was no more increasing.
12. Still we could see lot of old files in sub-folders of Inbox\Auth folder, we hope all these files would try to process for the information that we added in the 'Configuration.mof' > will fail > will go to respective 'Bad/Corrupt' folders and
eventually will be removed as per the clean-up cycle.
I will update the thread if anything goes wrong beyond this point. But, we believe it wouldn't as we have found the culprit and fixed.
**** I appreciate all your responses to help me with this situation. Happy SCCMing..!
Thanks, V@s!m

Package content on Primary Site Server (no Distribution Point Role)

Hey,
I have the situation that there are 3 Servers with following roles installed:
1.File Server
2.SCCM 2012 R2 CU3 Primary Site Server / Database Server (Was a distribution Point previously to update to CU3)
3.Distribution Point
Our packages are all stored as "source" on the File Server.
Now some SCCM Applications / packages are created and distributed to the distribution point.
Unfortunately on the Primary Site Server the folder "SCCMContendLib" extends as it does on the distribution point (so this means that all packages are distributed to the primary site server, too.
My question is now- why? :)
Is this really needed (I see no reason for it) or is it a problem in the infrastructure (if yes - how can I resolve it)?
Thank you for help
Kind Regards

Not a problem with your infrastructure. What you're describing it the default behavior for ConfigMgr, in terms of storing content on the primary.
-Nick O.

Overloaded Standalone Primary Site Server

Hi,
Some colleagues of mine are working on an account that has a Primary Site Server that is running at maximum capacity or almost maximum capacity.
Replacing the full Site server (backup restore on new hardware is not an option right now), so I was looking for suggestions to help or provide an quick fix for the medium term.
I was thinking they could offload the client facing roles like the DP and MP and maybe the SUP. But the challenges I see are
1) if the SUP changes they need to consider the problem of the clients downloading the full catalog again which could put unnecessary load on the network. So should they retain the existing SUP as well or maybe just retain the original SUP and only offload
the DP and MP
2) Offloading the MP on its own won't offload all client requests so they could consider an SQL replica on the new site server box.
Or the other solution is to only offload the SQL from the site server and retain the SUP, DP and MP?
Any other suggestions that I'm not thinking of?
Thanks

First, define "maximum capacity". That's a completely meaningless statement.
I always design non-trivial architectures with a "client-facing" site system that hosts all client-facing roles. In this way, the primary site server never handles any client traffic. Additionally, simply creating two of these "client-facing"
site systems now gives you instant HA at the client layer as well as additional scalability for those roles.
1) A one-time hit is an acceptable trade-off for a long-term issue.
2) Yes, SQL Replicas are generally a good thing also when hosting the MPs on a site system.
Moving SQL server is more pain than its worth -- in fact, I would say that it's not worth anything:
https://stevethompsonmvp.wordpress.com/2014/12/20/why-you-should-not-use-remote-sql-server-with-configmgr-2012/
Jason | http://blog.configmgrftw.com | @jasonsandys

Primary site server a single point of failure?

I'm installing ConfigMgr 2012 R2, and employing a redundant design as much as possible. I have 2 servers, call them CM01,CM02, in a single primary site, and on each server I have installed the following roles: Management Point, Distribution Point, Software
Update Point, as well as the installing the SMS Provider on both servers. SQL is on a 3rd box.
I am now testing failover from a client perspective by powering down CM01 and querying the current management point on the client: (get-wmiobject -namespace root\ccm -class ccm_authority).CurrentManagementPoint . The management point assigned to
the client flips to the the 2nd server, CM02, as expected. However, when I try to open the CM management console, I cannot connect to the Site, and reading SMSAdminUI log reveals this error: "Provider machine not found".
Is the Primary site server a single point of failure?
Why can't I point the console to a secondary SMS provider?
If this just isn't possible, what is the course of action to restore console access once the Primary Site server is down?
Many Thanks

Yes, that is a completely false statement. Using a CAS and multiple primaries in fact will introduce multiple single points of failure. The only technical Eason for a CAD a multiple primary sites is for scale out; i.e., supporting 100,000+ managed systems.
HA is achieved from a client perspective by adding multiple site systems hosting the client facing roles: MP, DP, SUP, App Catalog.
Beyond that, all other roles are non-critical to client operations and thus have no built-in HA mechanism. This includes the site server itself also.
The real question is what service that ConfigMgr provides do you need HA for?
Jason | http://blog.configmgrftw.com

Can we assign 2 IPs for a SCCM 2012 primary site server and use 1 IP for communicating with its 2 DPs and 2nd one for communicating with its upper hierarchy CAS which is in a different .Domain

Hi,
Can we assign 2 IPs for a SCCM 2012 primary site server and use 1 Ip for communicating with its 2 DPs and 2nd one for communicating with its upper hierarchy CAS . ?
Scenario: We are building 1 SCCM 2012 primary site and 2 DPs in one domain . In future this will attach to a CAS server which is in different domain. Can we assign 2 IPs in Primary site server , one IP will use to communicate with its 2 DPs and second
IP for communicating with the CAS server which is in a different domain.?
Details:
1)Server : Windows 2012 R2 Std , VM environment .2) SCCM : SCCM 2012 R2 .3)SQL: SQL 2012 Std
Thanks
Rajesh Vasudevan

First, it's not possible. You cannot attach a primary site to an existing CAS.
Primary sites in 2012 are *not* the same as primary sites in 2007 and a CAS is 2012 is completely different from a central primary site in 2007.
CASes cannot manage clients. Also, primary sites are *not* used for delegation in 2012. As Torsten points out, multiple primary sites are used for scale-out (in terms of client count) only. Placing primary sites for different organizational units provides
no functional differences but does add complexity, latency, and additional failure points.
Thus, as the others have pointed out, your premise for doing this is completely incorrect. What are your actual business goals?
As for the IP Addressing, that depends upon your networking infrastructure. There is no way to configure ConfigMgr to use different interfaces for different types of traffic. You could potentially manipulate the routing tables in Windows but that's asking
for trouble IMO.
Jason | http://blog.configmgrftw.com | @jasonsandys

Using a custom certificate store for SCCM 2012 clients and primary site server

I have read what seems to be all the pki related documentation out there for SCCM 2012. I have a PKI infrastructure up and running issueing certificates with an offline root through group policy autoenrollment. The problem that i'm faced with is we are migrating
from SCCM 2007 that was in native mode and we chose not to use the CA that we used for the old SCCM environment. When the clients attempt to communicate with the M.P. it runs through all of the different certificates and adds a tremendous amount of overhead
to the M.P. We will have ten's of thousands of clients by migration end. Could someone please point me to a document that goes over how to leverage a custom certificate store that I could then tell the new 2012 environment to use? I know that it's in there,
I've seen it in the console. The setup is one primary site server with SQL on box and the pki I just mentioned as well as the old 2007 environment that is still live.
I read that you can try and use SAN as a method of identifying the new certs but I haven't found a good document covering exactly how that works. Any info you could provide I would be very grateful for. Thanks.

Jason, thank you for your reply. I'm getting the impression that you have never been in the situation where you had to deal with 2 different PKI environments. Let me state that I understand what your saying about trust. We have to configure the trusted root
CA via GPO. That simply isn't enough, and I have a valid example to backup this claim. When the new clients got the advertisement and began the ccmsetup process I used the /pki switch among others. What the client end up doing was selecting a certificate that
had the longest validity period which was issued by our old CA. It checked the authentication chain, found it to be valid and selected it for communication. At that point the installation failed, period, no caveats as you say. The reason the install failed
because the new PKI infrastructure is integrated into the new environment, and the old is not. So when you said " that
are trusted and they can use *any* cert that is trusted because at the end of the day, there is no
difference between two valid certs that have the same purpose as long as they are trusted. "
that is not correct. Both certs are trusted, and use the same certificate template, but only one certificate would allow the install to complete successfully.
Once I started using the CCMCERTISSUERS
switch the client install went swimmingly. The only reason I'm still debating this point is because someone might read this thread see your comments and assume "well I've got my new PKI configured as a trusted root CA, I should be all set" and their
deployment will fail, just as my pilot did.
About Intune I'm looking forward to doing a POC in the lab i built with my Note 3. I'm hoping it goes well as I really want to have our MDM migrated into ConfigMgr... I think the
biggest obstacle outside of selling it to management will be the actual device migration from the current MDM solution. From what I understand of the enrollment process manual install and config is the only path forward.
Thanks Jason for your post and discussion.

Database instance for SCCM 2012 and WSUS on a single primary site server

I am going to install SCCM 2012 and its SQL database on a single physical server. This is going to be a single primary site server. The default SQL instance will be dedicated to SCCM 2012 with no other named instances to be added on the SQL server down
the road.
During the WSUS server role installation, there is the Database Options page asking for using (1) Windows Internal Database, (2) existing db server on this computer, or (3) an external db server.
Since SCCM 2012 doesn't share db instance with others, how should I handle the WSUS db that's going to be hosted on the same SCCM/SQL physical server? Do I really need to create a separate SQL instance just for the WSUS db?
Thanks and regards.

Even though you can do it, it is the best practice to have SCCM 2012 and WSUS installed on separate instances.
http://technet.microsoft.com/en-us/library/hh692394
When the Configuration Manager and WSUS databases use the same SQL Server and share the same instance of SQL Server, you cannot easily determine the resource usage between the two applications. When you use a different SQL Server instance
for Configuration Manager and WSUS, it is easier to troubleshoot and diagnose resource usage issues that might occur for each application.

Running WMI repair script on SCCM 2012 primary site server

Hi,
running WMI rebuilding repository script on SCCM 2012 primary site server. Any idea what kind of issue on SCCM environment it will cause.
Regards,
Gopi

Gah! did you already do so? I hope your resume is up to date. As to what kind of issues: it'll break everything, and nothing will ever work right ever again. Ever. Again.
Standardize. Simplify. Automate.

SCCM CAS & Primary Site Server - Same SQL Database and Reporting Instance

Hi Fellows,
I need to know whether, for SCCM CAS, a dedicated/seperate SQL instance for SCCM CAS a mendatory requirement or recommendation?
Or we can use the same SQL instance used by Primary Site Server?
J.A

There no technical reason not to have the CAS and Primary database in separate instances of the same remote SQL server. However if you are going to deploy a CAS that would suggest a very large number of clients and a very busy infrastructure. In that case
I would RECOMMEND separate SQL servers.
This is a good guide for SQL sizing (but it is only a guide)
http://blog.coretech.dk/kea/system-center-2012-configuration-manager-sql-recommendations/
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

SCCM - Uninstalling Primary site server

Hi All,
After we uninstall a primary site server from SCCM architecture, are there any changes that we need to make in AD, so that there should be no junk entry objects in AD that are related to this primary site server.
Rgs,

Hi,
Clear up all the objects in System\System Management that points to the Primary site you are uninstalling and it roles.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

Effect on OSD if remove primary site from SCCM heirarchy

Wanna ask, just a theory question, im currently planning to decommission and upgrade my current primary site server. The process will take roughly a few days. At the same time, I also have other site system server that also acts as an MP (has MP role). So,
for the time being I would not have an active primary site for a couple of days.
Question is, during that timeframe (when primary site not available), am I able to still do OSD? Was thinking the only issue of not having a primary site at that time, my user client machine will not be able to get the latest policy
cause any new policy will be push down from the primary site right...but the client will only be able to get the old TS advertisement correct... Question as below
Does the client machine still able to run the old advert advertised to it?
Does the client machine cache the TS advert and store it locally on their machine?
All the OSD content (boot image, OS image etc) is available in the DP, so it should be able to PXE boot and execute the TS correct if the primary site is not available?
Read the net on PXE boot flow at
http://blogs.technet.com/b/pingpawan/archive/2014/01/12/deep-dive-pxe-boot-flow-for-sccm-2007-2012.aspx. Its says as below. What I don't understand is isn't the primary server is the only one that can access the DB? Don't quite get it when it says
WDS can also access the DB....?
WDS/PXE sever runs a stored procedure, LOOKUPDEVICE for the client machine against SCCM DB. If the machine is found in the DB or If there is an advert for Unknown collection, WDS signals client to proceed with the PXE
boot.

Which roles are installed on the site server?
Torsten Meringer | http://www.mssccmfaq.de
Roles installed on my primary site is
Management point
SUP
Site System
Component Server
Site Server

Client Upgrade on Primary Site Server

This should be an easy question but I really want confirmation.
When you perform a Cumulative Update does the Update upgrade the client also on your primary site server? If so do when you create a device collection for x86/x64 clients do you exclude the site server from getting push?

Hi,
No the SCCM Client stays at version 5.00.7958.1000 on the primary site.
If you wanted you could upgrade the SCCM client on the primary manually by running.
C:\Program Files\Microsoft Configuration Manager\hotfix\KB2970177\Client\x64\configmgr2012ac-r2-kb2970177-x64.msp and then exclude it from the below collection or let it go out automatically.
This is from an older version but the principle is still the same.
http://www.ronnipedersen.com/2013/06/installing-sccm-2012-sp1-cu2-quick-start-guide/
You can go straight from R2 to CU2. You do not need to install CU1 first.

Replacing the primary site server, SCCM 2012 R2

Similar Messages

Maybe you are looking for