Use of FIDO in the Payments and Identity Landscape: FIDO Paris Seminar.pptx
Deploying An Optimized Desktop - XP to 7 With P2V
1.
2. Before we start….some good reference content
• Your Building aLiteTouch Bootable USB Image Questions Answered!
• Your Adding Office 2010 to MDT 2010 Environment Questions
Answered!
• Improving Your Image: Sector-Based, File-Based, and Sysprep -
What Makes the Most Sense?
• Part1:TermsandWindowsToolsPrimer
• Part2:TheProsandCons.
• Part3:Deploy-timeBuildAutomationandRecommendations
• NEW -Manually Performing P2V Migration for Software Assurance
http://windowsteamblog.com/windows/b/springboard/
3. The Myth
There Is No Way to Upgrade a Windows XP
Computer to Windows 7
4. Channel Web Network (CRN) did this in February 2009
http://www.crn.com/software/214502800
WAIT A SECOND!!!
5. So how do people move from Windows
XP to Windows 7 then?
6. If You Still Use Any Of These…It’s Time To Update!
6
Sector Based Imaging
7. Options
1 -Windows XP-to-
Windows Vista-to-
Windows7 using
setup.exe
2- Manual migration and
install from DVD
3- Drive Cloning based on
a Reference Windows 7
Install
4- Automated migration
with applications and
drivers
8. But I Use One Of These Other Leading Brands…
Desktop Environment Type / Image and
Build Type
Traditional Thick Sector-
Based Images with Limited
Install-time Customization
File-based Images with
Build Automation for User
and Hardware
Customization
Thick File-based Images
used like Traditional Sector-
Based Images with Limited
Install-Time Customization
Thick local client environment with user
and region-specific applications, local
user state and variance in hardware
No Yes No
Completely homogeneous environment
for all users (no local user state, one
language, draconian hardware
standardization) – either physical or
hosted
Yes No Yes
Thin client hardware environment with
main user desktop environment hosted
in the datacenter
Yes Yes Yes
Datacenter-hosted user-specific
desktop environments No Yes No
OEM Computer Manufacturing Process Yes No Yes
Any Combination of the Environment
Types Listed in This Column No Yes No
9. The Magic of The PiXiE Stick
My boss has XP. She needs
Windows 7 before she lands.
I have 10 machines I want
to pilot Windows 7 on.
I want to enable my remote
workers to migrate to Windows 7
without sending in their laptops.
10. Here’s The Best Part….
MDT 2010
Windows
Deployment
Server
(WDS)
12. P2V Migration for SA Customers
P2V Migration will convert a user’s existing
Windows XP environment to a virtual hard disk
then automates the delivery of an updated and
personalized Windows 7 operating system
containing a virtual machine with the user’s
previous Windows environment, applications and
Web browser.
14. The Deployment Project…
Testing Process
Infrastructure
Remediation
Image
Engineering
Application
Management
MigrationOffice
Deployment
Security
Deployment
Operations
Readiness
Project
Process and
Team Guidance
Business Case
for Deployment
Do I need to invest in test
hardware, personnel,
and infrastructure?
Do I replace all of my
users’ hardware?
Do I need to build and maintain
an image for each hardware class?
Are my applications
going to work?
Do my techs need to manually
migrate everyone’s files at
their desk or in the lab?
Office, too? Does that
mean more testing
and images?
How do I think about
policies, data, and security now?
Do my users need to send their
hardware to IT or be without
their PCs for a day?
How is this going to impact
users and the helpdesk?
15. …It Depends
• Windows architecture and deployment tools change for a
reason
• Test?
• Hardware?
• Image management?
• User data migration?
• Hardware specs and application requirements pretty
static for
3+ years
• Security updates are easier to integrate into the project
16. …What it Means
• Refresh existing hardware- don’t wait for hardware
replacement
• Make the process fast and not disruptive for users
• Test wisely, but don’t expect things to break as often as
before
• That means fewer helpdesk calls than with previous
OS deployments
18. Windows Application Compatibility Tools
Application Compatibility Toolkit
Asset Inventory Service
Microsoft Assessment
and Planning
System Center Family
Application Compatibility Toolkit
Windows Compatibility Center
Compatible Applications List
Application Quality Cookbook
Application Verifier
Application Compatibility Toolkit
Application Virtualization
Application Quality Cookbook
Virtual Legacy Windows OS
(MED-V, XP Mode)
Test &
Mitigate
AnalyzeCollect
19. Application Compatibility Toolkit (ACT) 5.6
Provides tools to inventory applications, hardware, and
devices in the production environment
Synchronizes collected inventory with current
application and hardware compatibility data from
Microsoft
Includes tools to test and repair individual applications
Version 5.6 has x64 support for inventory, compatibility
fixing, and standard user account issue detection
26. Windows Server 2008 R2 + KMS = Office
2010, Windows XP, Vista and 7 Activation
• What it provides:
• Better license management
• Visibility of activations
• Consistent activation approach for Windows and Office
• NOT monitored by Microsoft
• What it requires:
• Plan for your activation method
• KeyManagementService (KMS)
• Multiple ActivationKey(MAK)
28. How Do They Work?
...add your ingredients, create a build, and install
Microsoft Deployment Toolkit 2010 or
System Center Configuration Manager 2007
Operating
Systems
Applications
Drivers
30. Improving the Deployment Core
MigrationDeliveryImaging
Deployment Image Servicing
and Management
Add/Remove Drivers and
Packages
WIM and VHD Image
Management
User State Migration Tool
Hard-link Migration
Offline File Gather
Improved user file detection
Windows Deployment Services
Multicast
Multiple Stream Transfer
Dynamic Driver Provisioning
Solutions to Prepare and Deploy
So How Does This Help You?
Saves time building
and updating images
These are big files – we
can now transfer them
quickly
Reduce the number of
deployment servers
Migrate gigabytes of user
state in minutes, not hours
More installs per day
Minimized end user
disruption
Keep your existing
hardware
=
33. Results
Pros and Cons of Each Method
Method XP-to-Vista-to-
Windows7 using
setup.exe
Manual migration and install
from DVD
Drive Cloning based on a
Reference Windows 7
Install
Automated migration with
applications and drivers
Pros • Applications migrate
• If you can find the
media, it’s an easy
user experience
• Easy to figure out
• You know what you’re
getting
• Makes you look busy to
your boss
• Easy to duplicate hard
drive
• Fast installation via file
copy or apply
• Seems to work
• Everyone is doing it,
even OEMs
• Speed
• One build works for all
hardware
• Data moves in the
process
• You know which apps
are installed
Cons • OMG, where do I
start?
• Applications break
• Hardware breaks
• Sloooooowwww
• Makes IT guys feel
dirty attempting it
• Slooooowwww
• Clicking “next” fatigue
• Lots of images to
manage
• User data migration
can take hours
• Building it can be tricky
for the first time
• Apps need to be
packaged
• Drivers need to be
added/managed
34. So there is a double-standard for the word
“upgrade” between IT pros and consumers?
WAIT!!!