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

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.

主站蜘蛛池模板: 五台县| 玉门市| 文山县| 青浦区| 军事| 遵化市| 靖西县| 南城县| 马山县| 四川省| 铜川市| 左贡县| 江永县| 丹阳市| 苏州市| 巴林左旗| 吉水县| 福泉市| 淅川县| 太康县| 苏尼特左旗| 阳谷县| 临江市| 微博| 崇左市| 双辽市| 夏津县| 青河县| 廉江市| 如东县| 来凤县| 岳普湖县| 西和县| 勃利县| 唐山市| 广昌县| 达日县| 奉新县| 武功县| 库尔勒市| 池州市|