SCCM 2012 RC Design Question

[lee_SCCM]

I am moving my beta lab into RC now and starting to think a little more about design now for production.

 

In the ConfigMgr 2007 world I have the following:

 

A Central Site which houses SRS and SUP along with a couple of other roles, it is also the main source for original media for my software repository.

 

I have a Primary Site which looks after all of my remote sites ( they have DP's, except 2 secondaries in slow link areas).

 

As you can see a nice simple topology at the company im at currently :-)

 

Moving into the 2012 world:

 

I see the DP's becoming 2012 DP's, the Secondaries becoming DP's ( utilizing the throttling capability), my question is around the whole CAS/Primary.

 

With my current design, the Central Site is used to as a single point of all changes that flows down, it does however have the capability to be brought up as a DP, if I lose my primary which would serve the site with the largest amount of clients ( London), the other boundaries can then easily be brought into the Central Site and clients will report into them.

 

Now in the 2012, the CAS does not have the ability to accept client requests which poses the dilemma of how best to tackle this and still provide a good level of fault tolerence.

 

So far I have devised the following:

 

Most Overkill - 1 CAS ( as the 2007 central could do more), 2 Primaries ( simulating what I have now), and my 20+ DP's.

 

Another Idea was, 1 CAS, 1 Primary and my 20+ DP's, the issue is how to have a safe guard in place fo if my primary goes down and the clients at them sites ( who dont have local DP's) to get content.

 

Curious to know if anyone can shed any ideas on this, as the structure is small at the moment and I dont want to over complicate it.

 

My only concern with having NO CAS at all is surely your cutting your ties straight away to ever have two primaries in the same site?????

 

Appreciate any feedback

 

Regards