There are scenarios in company merger situations (and others I am sure) where the management of both locations has not been consolidated down to one location yet and is not going to be done as part of the deployment or upgrade. Have to be copied up to the remote primary site and then distributed back down. Any time Admin B needed to add an app or image it would Admin A at the primary site would not experience any issues but Admin B would be in for a lot of work and waiting. If you do indeed have distinct admins managing their own images and apps in remote locations then I see the benefit of a CAS.Ī remote ConfigMgr console connecting to a primary site would perform poorly. The book goes over installing multiple primaries if there are different administrative teams in different regions and to provide a local point of connection.Įven though I am going to be strung up for even saying this, I do agree there is a use for a CAS outside of 100,000 users. ![]() Single primary site with child sites in other regions is the other design? Offices in EU and KR have their own IT staff that would manage their own primary site, but IT staff in the US would like overall management and monitoring of all child primary sites. ![]() I'm just referencing the MS materials 10748A saying a CAS would allow centralized management and monitoring of child primary sites.
0 Comments
Leave a Reply. |