Moderated by:Sponsored by: Kim Oppalfens, Microsoft ConfigMgr MVP Maintaining your Application Deployment History when Re-deploying a Workstation 11 August 2011

Welcome Introduction BDNA & myITforum Kim Oppalfens: Maintaining your Application Deployment History when Re-deploying a Workstation Q&A Wrap Up Agenda

Constantin Delivanis, CEO BDNA ~ Normalize & SCCM

Rod Trent, myITforum –All things “System Center” –Since 1999 –Large and growing community (120,000 visitors a day) –Huge storehouse of System Center knowledge –Noobies to experts –Even Kim is hanging around at myITforum myITforum

Kim Oppalfens Innovativ.Be Principal consultant Author of SccmAutodoc & Instant Delivery Nickname: “The quiet shy guy” according to my MVP buddies Favorite quote: The M in WMI stands for Magic! 7th year ConfigMgr MVP Co-Founder System Center user group Belgium MyitForum mssms list member Happily married and proud father of Lennart & Lauren Hobbies: WMI Magician Blog: wmiguy wmiguy Twitter: TheWMIGuy

Why would you want to maintain your application deployment history? How can you maintain your application deployment history? –Retaining the client’s resourceID –Retaining the client’s dynamic collection membership –Rebuilding the application deployment history using task sequence variables Q&A Agenda

Machine in an as ready as possible state when delivered to the end user. Why not? –Licensing cleanup –Application rationalisation Why?

Start re-imaging process from live OS – upgraded-to-windows-7-using-osd-might-generate-a-new-sms-guid.aspxhttp://blogs.technet.com/b/configmgrteam/archive/2011/02/14/computers- upgraded-to-windows-7-using-osd-might-generate-a-new-sms-guid.aspx –Pro’s: Native functionality –Con’s: Some challenges to prevent end-user re-imaging themselves, Not always feasible or practical Implement native mode –Client will retain identity if client cert has the same subject name. –Pro’s: Native functionality –Con’s: A bit of overhead on the implementations “Manually resolve conflicting records” –Merging “obsolete” records: records-in-configuration-manager-2007/ records-in-configuration-manager-2007/ –Pro’s: Auto-handled solution –Con’s: Some security concerns 1 Retain the Client’s resourceID 1

Run Tranguid.exe (Sms 2003 Toolkit2) to backup smscfg.ini identitySms 2003 Toolkit2 –Tranguid.exe /G %computername%.ini – scenario-issues-solutions-with-tranguid-exe-part-1.aspxhttp://scug.be/blogs/sccm/archive/2008/10/27/sccm-in-place-upgrade-refresh- scenario-issues-solutions-with-tranguid-exe-part-1.aspx –Con’s: Requires tranguid command line to run prior to ReImaging Not confirmed to be working with Windows 7 Retain the Client’s ResourceID 2

Retaining the resourceID will help till the next collection eval cycle. Build dynamic collections based on computername using the list value criterion type –Pro’s: Real easy –Con’s: can become challenging to manage really fast. Build dynamic collections based on Active Directory Groups –Pro’s: Uniform way of managing through Active Directory –Con’s: Introduces delay waiting for ConfigMgr System Group discovery and collection Evaluation Cycle Delta discovery in ConfigMgr 2007 R3 + Dynamically add new resources to collection helps for OS Deployment Delta discovery & Dynamically add new resources doesn’t do squat for adhoc software distributions Retaining dynamic collection membership

Explaining Tasksequence Basevariables 1.Define a base variablename (Eg:Applications) 2.Create variables (Collecion, Machine or TS) 1.(Eg: Applications001 & Applications002) –Condition1: Variable Name has to end with 3 digits –Condition2: The 3 digit sequence has to be un-interrupted (EG: 001,002,003) NOT (001,002,004) 3.Set variable values to PkgID:Programname 1.(Eg:P :OSDInstall 1.Condition1: Program runs as admin, whether or not user is logged on, and without user Interaction 2.Condition2: Program is configured to Allow installation from tasksequence without being advertised. Rebuilding the application deployment history using task sequence variables

The UI for base variables isn’t the best: 1.Need to know packageID’s & Program Names by heart (No Browse) 2.VariableNames cannot be altered (Requires deletion and re-creation 1.Annoying combined with the fact that your 3-digit code needs to be sequential Collection & Machine variables are static Rebuilding the application deployment history using task sequence variables – Issue

1.ConfigMgr Console is easilly extended, as it is all WMI (and some XML) –Introducing the TaskSequence BaseVariable UI 2.Using the Taskseqence Variable COM Object to dynamically generate BaseVariables (Only 2 lines of code) dim osd: set env = CreateObject("Microsoft.SMS.TSEnvironment") env(“Applications001") = "Eg:P :OSDInstall" Rebuilding the application deployment history using task sequence variables – Fixes

Active Directory groups ConfigMgr Hardware Inventory/ Asset Intelligence –Caveat: Working based on Add/remove program display names can be challenging BDNA Normalizes ConfigMgr data and uploads it as queryable WMI data Client registry (Uninstall/windows installer) CCM_Softwaredistribution in WMI –Caveat: Contains all received advertisements... Application history by Vbscript – Potential sources for info

MDT uses its own mechanism using a Package Mapping table to dynamically create Task Sequence variables –Populates the UDI Wizard with pre-detected apps MDT 2010 Update1 Package Mapping

Elegant solution –Pro’s: applications are used by users, user usually doesn’t change with a redeployment –Con’s When user logs on to a different workstation -> Installation hell * Application installs not ready when machine is delivered to end-user * * Both issues are fixed in ConfigMgr 2012 using the App model’s Global conditions and User device affinity integration into OSD Deploy to Users or Usergroups

Static Collections Dynamic Collections Scripted TS Variables Users or Usergroups No Scripting knowledge required Apps installed on Finished TS 1 Apps installed before user logs on 2 2 Allows for Application upgrades Overall Pro’s & Cons 1 Yes, With ConfigMgr 2012 user centric deployment & User device affinity 2 Introduce waiting period in provisioning to allow normal Machine Policy based advertisements to run

Active Directory Computer group deployments Coupled with a TaskSequence script to enumerate computer group memberships Keep package names and Active Directory groups identical Create standardized OSDInstall program that meets the OSD program requirements Personal Preference

For System Center Enthusiasts: For deployment enthusiasts: For people that love to play with new stuff: BDNA Normalize as a service: Microsoft Evaluations: For people interested in SccmAutodoc or SCCM Instant delivery : Contact me for quotes: Call to Action

Next SCCM GURU Webcast: September 14, 2011 John Nelson, SCCM MVP & President, Minnesota System Center User Group  Wrap Up

To thank you for participating in our SCCM GURU webcast, we’d like to offer EVERYONE on the webcast a super cool SCCM GURU Webcast T-shirt. Please register here:  Thanks for attending!

Questions, Contact Info BDNA Matt Lefer +1 (650) myITforum Rod Trent +1 (513) Inovativ.be Kim Oppalfens Twitter: theWMIGuy

Below are the links to the downloads that matter the most in FY12. System Center Configuration Manager 2012 Beta 2 System Center Configuration Manager 2007 R3 System Center Data Protection Manager 2010 System Center Operations Manager 2007 R2 System Center Virtual Machine Manager 2008 R2 SP1 System Center Virtual Machine Manager 2012 Beta Hyper-V Server 2008 R2 SP1 Windows Server 2008 R2 SP1 Microsoft Eval Downloads