User Centric Application Delivery with SCCM 2012

Corey Hynes

What is Consumerization of IT• The movement towards per-user, not per-

infrastructure architecture• Scale up and Scale down• Introduce the App-Store• Installation free Apps• Total user and application virtualization

Today• Infrastructure upgrades to projected use not actual• No way to reclaim resources or money• Unsteady per-user cost

Tomorrow• User cost mirrors usage exactly• Pay per use or per user• Leverage cloud technologies

Public Cloud Technologies• Azure• Office 365• Lync and SharePoint Online• CRM Online• SQL Azure

• All are pay as you use them models

What is User-Centric Delivery• Past: We deploy Office as part of the OS• Future: We deploy Office only when a user needs it • Can be forced or requested

• Technically• Traditional SCCM deployment• Based on User collections• Incorporates device logic

Creating a Company App Store• Create an Application Catalog• Publish applications based on user collections• Set as “available”• Users browse the store website to find and install

applications• All standard deployment types supported• App-V preferred

Architecture

Case Study: Office via App-Store

1: Sequencing Office• You must use Volume edition office• http://support.microsoft.com/kb/983462• Follow this guide directly, take your time• Test test test

2: Installing App-V Deployment Tools• Install licensing for Office• Must be installed before Office• Download from http://

www.microsoft.com/download/en/details.aspx?displaylang=en&id=10386

• Guidance on installing in Sequencing guide• MISEXEC /I OFFVIRT.MSI PROPLUS=1

3: Create a Deployment Package• Dependencies and Conditions

are key• Office depends on Deployment

Tools• Deployment tools depend on OS

version/build

4: Implement User Collections• Implement User Discovery in SCCM• Create Collections based on users• Create deployments based on those collections

5: Create User Deployments• Create a new deployment• Deploy to a user collection• Mark deployment as “available” not “required”

6: Configure the App-Store• Add Application Catalog Web Service Point site

system role• Add Application Catalog Web Site Point site system

role• Navigate to http://<server>/CMApplicationCatalog

Advanced Topics

Deployment Types• We have focused on App-V, because it is better• Nothing bound to operating system• Easy to remove• Easy to manage• Easy to update

• MSI, Script, and other installation types are available• SCCM chooses deployment type based on rules

App-V Package Accelerators• Simplify the sequencing process using intelligent

proven defaults• Download from

http://gallery.technet.microsoft.com/site/search?f%5B0%5D.Type=RootCategory&f%5B0%5D.Value=App-V&f%5B1%5D.Type=SubCategory&f%5B1%5D.Value=PackageAccelerators

• You can create your own and distribute

Primary Device• Factored in the Deployment

Type decision.• Has no technical meaning, it

just meant to represent the computer the user most uses.

• Can be administrator set.• Devices can have multiple

primary users• User can have multiple

primary devices

App-V and Terminal Server• Case where user centric delivery is not the best

choice• However you can still leverage it.• Users will share one cache.

• Must use the App-V Client for RDS.

Considerations for VDI• App-V Shared Cache is your friend• Reduces storage• Reduces IO

• Deploy as you would any other application• Availability is instant, no streaming• However, update process is more complicated

Demo – User Centric App Delivery and Desktop Virtualization

Bonus – SCEP 2012 – Simple Security• SCEP now part of SCCM 2012, not a separate add-on• Very simple deployment• Will remove most AV products and replace with

SCEP• Reports status through SCCM.

Bonus – Mobile Device Management• SCCM integrates with Exchange for mobile device

management

Bonus – Third Party Hardware• Microsoft does not broadly support 3rd party

hardware• VDI – Citrix XenDesktop• Broad device support• Optimized WAN Experience• Dedicated Clients

• RDP – Many Choices• Lots of client software apps for many devices