官术网_书友最值得收藏!

ConfigMgr hierarchy planning

As mentioned earlier, spending some time on planning and analyzing your business may significantly help you in building a solution that will meet the requirements without being an overkill. It is always good to include some growth in your design plans, but there is a significant difference between planned overhead and overkill in achieving the goal.

With ConfigMgr 2007 still in your environment, the administrator would need to go through an upgrade process to migrate to the 1706 version. For 2012, there is an in-place upgrade possibility. Note that upgrade process topics won't be covered in this book.

When it comes to hierarchy planning, ConfigMgr gives a few possible options. Since ConfigMgr 1511, Microsoft has supported running ConfigMgr on the cloud.

When considering your design, be aware that as of now, there is no support for using VM in Azure as a distribution point for WDS deployments using PXE. In such cases, use the on-premise distribution point.

SMS 2003 servers and ConfigMgr 2007 were supporting hierarchies made of many levels. It was causing a lot more issues related to data synchronization between servers. In ConfigMgr 2012, Microsoft introduced some significant changes. Hierarchy might consist of only three levels, and data synchronization is made directly between SQL Servers, which is a significant factor in improving the functioning of the entire system.

主站蜘蛛池模板: 澄城县| 新巴尔虎右旗| 周至县| 保康县| 且末县| 宜良县| 泊头市| 新营市| 来安县| 岗巴县| 南汇区| 泸溪县| 沧源| 许昌县| 海口市| 施秉县| 静乐县| 临漳县| 昌平区| 丹阳市| 闽清县| 辽中县| 津南区| 剑河县| 登封市| 方城县| 阿坝| 邯郸市| 哈尔滨市| 城固县| 浏阳市| 聊城市| 长汀县| 育儿| 满洲里市| 特克斯县| 嘉定区| 巢湖市| 林西县| 绍兴县| 光泽县|