Presentation is loading. Please wait.

Presentation is loading. Please wait.

Why migrate to it? Wally Mead Senior Program Manager Microsoft Corporation SYSTEM CENTER 2012 CONFIGURATION MANAGER.

Similar presentations


Presentation on theme: "Why migrate to it? Wally Mead Senior Program Manager Microsoft Corporation SYSTEM CENTER 2012 CONFIGURATION MANAGER."— Presentation transcript:

1 Why migrate to it? Wally Mead Senior Program Manager Microsoft Corporation SYSTEM CENTER 2012 CONFIGURATION MANAGER

2 CONFIGURATION MANAGER 2012 Unify Infrastructure Empower UsersSimplify Administration Empower people to be productive from anywhere on whatever device they choose Reduce costs by unifying IT management infrastructure Improve IT effectiveness and efficiency Device freedom Optimized, personalized application experience Application self-service Mobile, physical, and virtual management Security and compliance Service management integration Comprehensive client management capabilities Improved administrator effectiveness Reduced infrastructure complexity

3 REDUCING PRIMARY SITES Unique ConfigMgr 2007 Primary Site for: ConfigMgr 2012 solutions (no unique primary sites): Decentralized administrationRole Based Administration Logical data segmentationRole Based Administration Client settingsClient settings for the hierarchy and unique collections LanguageLanguage packs Content routing for deep hierarchiesSecondary Sites or Distribution Points

4 INFRASTRUCTURE CHANGES: CONTENT One Distribution Point – Throttling and scheduling of content to that location – Pre-stage of content and specify specific drives for storage – PXE Service Point – Increased scalability beyond the ConfigMgr 2007 limit of 75 PXE service points per site – Multicast option Improved Distribution Point Groups – Manage content distribution to individual Distribution Points or Groups – Content automatically added or removed from Distribution Points based on Group membership – Associate Distribution Point Groups with a collections to automate content staging for software targeted to the collection No Branch DPs - DPs can be installed on clients and servers now

5 MINIMUM SYSTEM REQUIREMENTS: ComponentMinimum Requirement Site Server and Site RolesWindows Server 2008 (64-bit ) Windows Server 2008 R2 (64-bit) DatabaseSQL Server 2008 SP2 & Cumulative Update 7 (64-bit) & KB SQL Server 2008 R2 with SP 1 & Cumulative Update 3 (64-bit) & KB Distribution PointWindows Server 2003 (including 32-bit) with limited functionality Windows Vista SP2 and later (including 32-bit) ClientWindows XP SP2 & SP3 (32-bit & 64-bit) Windows 2003 Server SP2 (32-bit & 64-bit) Vista SP2 (32-bit & 64-bit) Windows 7 RTM & SP 1 (32-bit & 64-bit) Windows 2008 SP2 (32-bit & 64-bit) Windows 2008 R2 RTM & SP 1 (64-bit) Admin ConsoleVista SP2 (32-bit & 64-bit) Windows 7 RTM & SP 1 (32-bit & 64-bit) Windows 7 SP1 (32-bit & 64-bit) Windows 2008 SP2 (32-bit & 64-bit) Windows 2008 R2 RTM & SP 1 (64-bit)

6 PREPARE FOR CONFIGURATION MANAGER 2012 Flatten hierarchy where possible Plan for Windows Server 2008 and SQL all 64-bit Start implementing BranchCache™ with Configuration Manager 2007 SP2 Move from web reporting to SQL Reporting Services with Configuration Manager 2007 R2/R3 Avoid mixing user and devices in collection definitions Use UNC (\\server\myapp) in package source path instead of local path (d:\myapp)

7 Will do a quick tour of the new Configuration Manager 2012 console Will show a few new features of interest DEMONSTRATION


Download ppt "Why migrate to it? Wally Mead Senior Program Manager Microsoft Corporation SYSTEM CENTER 2012 CONFIGURATION MANAGER."

Similar presentations


Ads by Google