protection against standalone primary site failure

Hi Team,

[Apologies for a long question]

I am working on designing a SCCM 2012 R2 SP1 for our organization. We have about ~6000 clients across multiple locations. There are three major locations US, India and Europe and there are 5 micro sites in APAC region.

US and India has about 2500 clients each

Europe has 600 clients

APAC has about 200 clients

All the three major sites have good WAN link and its working fine for our existing SCCM 2007 setup (CAS & 1 Primary in US, 1 Primary in India and 1 Secondary in Europe)

Now the design i am proposing is 1 Standalone primary in US, 1 DP /w PXE or secondary in India, 1 DP /w PXE in Europe. Other micro sites in APAC can have DP /w PXE for OSD reasons.

NOW, there is another suggestion in the org to have a CAS in US, 1 Primary in US, 1 Primary in India, 1 DP /w PXE in Europe and micro sites in APAC can have DP /w PXE for OSD reasons.

The problem is i am not sold on introducing the CAS for the reason that we have only ~6000 clients and don't expect a exponential growth in clients in next 3-4 years. I am being told that if our stand alone primary fails, this can put us in trouble. to protect us from such situation we can introduce a CAS, 1 primary in US & India regions so that in case of a primary server failure in US, clients can redirect to India primary server.

I would like to know the suggestions from this forum on how feasible this proposal is and is it necessary to have a DP /w PXE for sites which have fewer than 20 clients for OSD?

Thanks.

Kailash

June 23rd, 2015 8:44am

A CAS won't protect you from any failures at all. "Redirecting client" is also no high availability solution.
Free Windows Admin Tool Kit Click here and download it now
June 23rd, 2015 8:51am

Torsten,

Thanks for the response.

I have another question. I plan to introduce 'Application catalog' feature for users software requirements. Will this impact my hierarchy design?

US & India are two major sites with 2500 devices each. I understand that 'Application catalog webservice point' and 'Application catalog website point' roles can only be deployed on a primary site. Now, will installing a primary site in India with these roles a better choice than let India users access 'application catalog' through US servers?

Thanks.

June 25th, 2015 8:22am

"Primary site" does not mean "Primary site server" and there is no such thing "on a primary site". A primary site is a collection of all the resources within it some of which may be "on the primary site server" and some may be "on a site system"; both of these are therefore "within the primary site".

You can install any role on a remote site system that is within the primary site including both App Catalog roles.

Free Windows Admin Tool Kit Click here and download it now
June 25th, 2015 8:44am

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

Other recent topics Other recent topics