Wayne Miller Consultant Microsoft Soap Clorox Comet Murphy 2012

Housekeeping steps needed to prepare to transition Package/Programs to SCCM 2012 Soap Clorox Comet Murphy 2012

Preparation for SCCM 2012 Transition existing Packages/Program from SCCM 2007 to SCCM 2012 Relate the new App Model to how deployments will be different in SCCM 2012 Convert existing Packages/Programs into the new App Model

Active Directory Team Active Directory Naming Standards for AD Groups (SCCM Admin Groups, Users Groups, Computer Groups) Review AD to see about Role Based Software Deployments Communication Team Plan – Users System Center Configuration Team Roles and Responsibilities especially with multiple sites/hierarchies being flattened SCCM Naming Standards (Collections, Packages, Programs) Program Name should reference Package Name Prefix Names with Organization that created them

Move from SCCM Web Reporting to SQL Reporting Services SCCM 2007 SP2 Become familiar with 64 BIT OS (Server 2008 or 2008 R2) Required All SCCM Roles except DP SQL 2008 (64 bit) or SQL 2008 R2 Ensure Licensed for Proper Version of SQL CASS SQL Standard – 50 K Entire Hierarchy CASS SQL Enterprise – 400 K Entire Hierarchy

Recommend Enabling BranchCache on DPs Minimize Network Traffic in existing 2007 Environment One Less Thing to Do During Migration Slowly Copy Content to the Distribution Point Minimize the DP Footprint Recommend using clean OS Load Copy Only Packages that have Active Advertisements

Prereqs – SCCM 2007 SP2 Step 1 –Package/Programs Migration to SCCM 2012 Step 2 –Application Migration to SCCM 2012 App Model via PCM

Built-in Migration Tool Migration Job Types: Collection based Migration (Select a collection and migrate associated objects) Object Migration (collections, software distribution packages, boundaries, metering rules etc.) Schedule Migration Migrate Changed Objects Content functionality: Re-use of existing ConfigMgr 2007 content (DP Sharing) Distribution Point Upgrade – No Longer Supports SCCM 2007

These Objects Can Migrate Direct Membership Dynamic Collections Migrate These Objects Can Not Migrate Empty Collections (Folders) Collections that exclude or include other collections by CollectionIDs (ex. Select ResourceID from SMS_CM_RES_COLL_S ) Heterogeneous Collections - Collection with users and devices Packages with a Source Directory – That Use Drive Letter on Site Server

LAB TEST Minimal Risk – Use Existing Central Site Verify that backup is running. Attempt Disaster Recovery Schedule Migration off peak; after backup is completed Ultra Conservative – New Site 2007 Attach as Child Site -> Detach Perform Migration from that site

Determine Active Advertisements Advertisement Naming Standard (Should Reference Package/Program) Download and Execute if Possible (Supports Branch Cache) Packages Naming Standards Source Directory is UNC IF possible ensure MSI only 2 Programs Exists (Install / Uninstall) and Import MSI Code Program Naming Standards (Not Default MSI name Can rename after converting to new App Model) Maximum Runtime set Restrict Program to proper OS Investigate Package / Program Setting for Dependent Programs Collections Naming Standards Logic – Requirements If going from decentralized to centralized environment ensure collections are scoped correctly

Prereqs – SCCM 2007 SP2 Step 2 –Application Migration to SCCM 2012 App Model via PCM

Manage applications; not scripts Application Management: Detection method – re-evaluated for presence: Required application – reinstall if missing Prohibited application – uninstall if detected Requirement rules – evaluated at install time to ensure the app only installs in places it can, and should Dependencies – relationships with other apps that are all evaluated prior to installing anything Supersedance – relationships with other apps that should be uninstalled prior to installing anything Update an app – Automatic revision management Unique Collections for every app NOT Required

General information about the software application

Solution Accelerator Kit Free Download from Microsoft Converts Packages/Programs to new Model Creates Requirements based on Collection Logic

Detection Method Importance App will either always install App will never install Can only be automatically derived from MSI’s EXEs = Manual MSI’s with multiple product IDs Pick the first one Uninstall Programs will be discarded Automatically derived for MSI

Coordinate SCCM Deployment with Multiple Teams Start implementing BranchCache Move from web reporting to SQL Reporting Services Clean Up Old Environment Collections should be computers or users Packages Use UNC for source path instead of local path Programs Add Operating Systems, App Dependency, Maximum Run Time, MSI if Possible (1) Migrate Active Packages/Programs Use Package Conversion Manager convert apps in LAB. Export/Import into Production

Need more information on DMVMUG Visit or send a question to Need more information on DMVMUG Visit or send a question to

SCCM 2007 / SCCM 2012 Answer Administrative Control – Role Based Security Different Client Settings - Global Settings / Collection Settings Impact to Environment losing a site Need to control bandwidth (Primary and Secondary) – Control Bandwidth on DP like Site Politics Regulatory Size of environment SCCM 2012 Impact to Environment losing CAS (Deploy Separate Hierarchies in different regions) Politics Regulatory Size of environment

Central management for security Role-Based Administration lets you map the organizational roles of your administrators to defined security roles: Removes clutter from the console Supports “Show me what’s relevant to me” based on my Security Role and Scope FunctionalityConfigMgr 2007ConfigMgr 2012 What types of objects can I see and what can I do to them? Class rightsSecurity roles Which instances can I see and interact with?Object instance permissionsSecurity scopes Which resources can I interact with?Site specific resource permissions Collection limiting

CA – 25 Child Primary Sites SQL Enterprise – 400 K Clients SQL Standard – 50 K Clients Each Primary No Child Primaries 50K (SQL Local) / 100K (SQL Remote) 10 MP (each MP Supports 25K, more than 4 for redundancy) 1 Fallback Status Point 4 SUP (SUP on SS 25K clients, Remote 100K) 250 Secondary Sites (Sites Less than < 500 use DP) 250 DPs (each supporting 4K clients) Maximum of 5K total DPs including Secondary Sites DPs

Secondary Sites 2.5 K Clients 1 MP and must be installed on Site Server 250 DPs (each supporting 2.5K clients) Application Catalog website point Each Instance 400k Improved performance 50k per instance Should coexist with Application Catalog web service point

Distributed Cache Mode (SCCM Supported) 1 st client downloads from DP Subsequent clients download from 1 st client Reduces need for DP at Branch Offices Lightens the load on DP for subsequent requests by other clients

Using Server Manager install Branch Cache Feature Either On or Off Configure Group Policy – Clients (Computer Configuration-> Administrative Template-> Network -> BranchCache) Turn on BranchCache – Enabled Set BranchCache Distributed Cache mode – Enabled Set BranchCache Hosted Cache mode – Not Configured (Not supported SCCM) Configure BranchCache for network files – Round Trip network latency Set percentage of disk space used for client computer cache (5% default) Add Firewall Rules

Server DP Requirements - Windows Server 2008 R2 with BITS enabled Clients Supported Server 2008 R2 & Windows 7 (Natively Supported) Server 2008 SP1/SP2 & Windows Vista SP1 (BITS 4.0 required) Packages must be Set to Download and Execute

SCCM 2007 – Central Site Child Primary had ability to create packages, advertisements, etc Client Objects flowed up the hierarchy Collection, Packages, Advertisement Flowed down the hierarchy SCCM 2012 All administration has to be done at CAS If CAS is down no new packages, deployments (advertisements) etc All objects replicate throughout the hierarchy