I think that restructuring a worldwide ConfigMgr infrastructure goes beyond the possibilities of such a forum, because there are too many factors involved (business requirements, WAN links and capacity, administrational concept, etc. Plus: how should we be able to give advice without knowing at least the number of clients at each location?Torsten Meringer | http://www.mssccmfaq.de

Rather than getting a direct advise, my intention was to get an idea how to approach such a task. Of course this question has to many factors any forum could take care about. Therefore I was more interested about how such design I outlined above could look like and if it is working in general or someone had this challenge before. To give a better overview: We have about 500 servers in the UK and about 5,000 clients. The rest is splitted 50% in the US and the other 50% in the APAC region (approx. 50 servers each and approx. 2,000 clients). Between our major hubs we have 10Mbit lines and from this hubs to our biggest office at least 2Mbit. The branches have between 512 to 1Mbit. Each local site can maintain there own packages, only a few are replicated by the HQ.

There is no right answer but removing the hardware could also impact your network (WAN) thereby increasing your bandwidth cost. Or worst yet have a decrease in customer satisfaction. There are pros and cons to everything but If it was me, there better be an very completing reason to remove the existing hardware and sites. It is a huge amount of work to consolidate site and services, and to do it there needs to be some cost benefit in making the change, if there is not why do it. Plus, it is extremely difficult to re-deploy those service again. You even state that regional site “Each local site can maintain there own packages, only a few are replicated by the HQ.”. This means you have two more issues. Political and technical (more bandwidth for regional application form HQ, support model, how do you prevent Site x Admin from deploying to Site Y, etc… ) So … Yes, I do mean ConfigMgr 2012 (v.Next) upgrading is the perfect time for changes like these. http://www.enhansoft.com/

ConfigMgr with SQL Tech is cheap to license. Any money $$ you save in licence cost will be eat up by OT, outage cost, Time and Effort costs. So IMO unless there is a compelling reason to change at this time. I wouldn't do it, until you are ready to upgrade. http://www.enhansoft.com/

Hello together, I recently joined a new company and got a new project. We have currently an SCCM implementation in place which seems to be a bit over-designed from my point of view. As the old admin left before I joined no one knows why the design is as it is and if it is still feasible. So first of all some more details: 1x Central site in the UK 1x Primary site in Asia acting as MP, SLP, DP, SMP, PXESP, FSP and SHV - 1x Primary site in China - several BDP's in several cities in China - 1x Primary site in Korea - several BDP's in several cities in Korea . . . We have several other Primary sites in several other countries in Asia, following the same model outlined above, and the similar model in place in Europe and the US region. The majority of users and system reside in the UK, I would say approx. 65%. I just did a quick check regarding licensing etc. and saw that we have more than 20 SQL instances in place, just for SCCM. I am wondering if I can optimize this structure the way that I am able to save costs (licensing) and maybe get a better performance i.e. optimize the setup in general. Any help would be greatly appreciated as I am wondering what is now considered best practise. Maybe there is something like a questionaire I could go through to get a better impression of the environment? Regards, M.

Well, yes. But the operational costs in terms of hardware etc. come into play here as well. With Upgrade you mean -> vNext?