The idea of this chapter was to give you a view of what the important factors are when planning the deployment of ConfigMgr 1706. We went through a few topics such as the following:
- Software prerequisites when planning an upgrade
- Description of available site roles and to what extent we can scale them
- Important factors when planning a hierarchy
- Possible hybrid scenarios with Azure
- What the possibilities are for HA when planning the infrastructure
- New features available for reporting
This chapter gave you a good overview of the available deployment scenarios, so you can go ahead and install ConfigMgr in your environment.
As we've reached the end of this chapter, let's now go straight to the chapter where you install your own instance of ConfigMgr 1706.
The following factors should always be considered when designing an environment:
- The number of endpoints managed by the environment
- The number of locations where these endpoints reside
- Features the environment should support
- Administrative factors, for instance, separating the management of servers and workstations
- Political factors; for instance, each country has separate ConfigMgr server
- Organizational factors; for instance, each AD domains should be managed by separate hierarchy
- Network latency and quality; the poorer the network conditions, the more servers we need in the environment
- Installing MS SQL Server on a separate machine to provide optimal efficiency for the ConfigMgr database
ConfigMgr is a very complex product; consequently, this book focuses mainly on fundamental configuration. It does not contain information about cooperation with systems other than Windows.