Using Windows XP Mode when migrating to Windows 7
As you know, virtualization can be different.
Microsoft has identified the following types of virtualization:
1. Datacenter virtualization.
The solution in this area is the Windows Server 2008 R2 Hyper-V or Hyper-V Windows Server 2008 R2 server role.
2. Client virtualization.
Solutions in this area are Remote Desktop Services in Windows Server 2008 R2, Microsoft Virtual Desktop Infrastructure, Microsoft Enterprise Desktop Virtualization, Microsoft Application Virtualization, Windows Virtual PS, and finally Windows XP Mode.
3. Cloud virtualization.
Why would I? And the fact that some solutions are undeservedly forgotten, concentrating all their attention on server virtualization and VDI, well, maybe RDS.
What, for example, to do if the company has changed the corporate standard and now the standard is not Windows XP, but Windows 7? At the same time, programmers did not have time to rewrite their software, which is “sharpened” under the outdated operating systems.
Of course, you can buy a server farm, implement VDI, and distribute virtual machines to users — a matter of money. And if they are not so many?
')
One solution is to use Windows XP Mode, which allows, using a local virtual machine running Windows XP with specific software installed, to publish to Windows 7 this application as if it were not installed in a virtual machine.
In this case, the sequence of actions is as follows - we save user data, reinstall Windows 7, turn on Windows XP Mode, install the software in the running virtual machine and publish it outside. Long? And then
And if such machines are 100 or 200, or 1000? You can let go of the mustache and beard :)
Well, simplify - you have installed Microsoft System Center Configuration Manager with Microsoft Deployment Toolkit. These tools are intended for managing workstations and servers, especially highlighting the Operating System Deployment module, which allows centralized spilling of the OS to new workstations, or reinstalling the OS on stations that are already running. Recently, the sharing of these products allows you to fully automate the process of migrating an enterprise to a new Windows 7 operating system.
And for those companies that have purchased Software Assurance, there is another additional bonus - a new product from Microsoft - P2V Migration for Software Assurance (based on Sysinternals Disk2VHD). During automated migration to Windows 7, it allows you to create a virtual machine from an existing one running Windows XP or later, launch it in Windows XP Mode and publish installed applications and Internet Explorer in Windows 7 (using RemoteApp and Virtual PC mechanisms).
Naturally, the use of publishing applications in XP Mode is a temporary solution, because more system resources are being spent, and not all operating systems are supported, but at least there is a time buffer that allows you to either rewrite the software or buy new versions that support Windows 7 .
The beta version of P2V Migration for Software Assurance is available at https://connect.microsoft.com/site14/Downloads/DownloadDetails.aspx?DownloadID=30989 .
Naturally, there are some restrictions:
- such migration is possible if you have 32-bit OS Windows XP SP3, Windows Vista Business, Windows Vista Enterprise SP1 or SP2, Windows 7;
- the license of the installed OS is not OEM;
- hard drives must be less than or equal to 127 GB.
In addition, if during the installation of P2V Migration there was no access to the Internet, then the following software should be downloaded and copied to the / Tools installation folder:
- Disk2VHD.exe . Sysinternals tool for performing P2V hard disk conversion
- KB961742-v3.exe . Update for Windows XP with SP3 to support RemoteApp
- Windows6.0-KB961741-x86.msu . Update for Windows Vista SP1 to support RemoteApp
- Windows6.1-KB958559-x64.msu . 64-bit Windows Virtual PC for Windows 7
- Windows6.1-KB958559-x86.msu . 32-bit Windows Virtual PC for Windows 7
- Windows6.1-KB977206-x64.msu . 64-bit update for Windows Virtual PC
- Windows6.1-KB977206-x86.msu . 32-bit update for Windows Virtual PC
Let's wait for the release
Microsoft has identified the following types of virtualization:
1. Datacenter virtualization.
The solution in this area is the Windows Server 2008 R2 Hyper-V or Hyper-V Windows Server 2008 R2 server role.
2. Client virtualization.
Solutions in this area are Remote Desktop Services in Windows Server 2008 R2, Microsoft Virtual Desktop Infrastructure, Microsoft Enterprise Desktop Virtualization, Microsoft Application Virtualization, Windows Virtual PS, and finally Windows XP Mode.
3. Cloud virtualization.
Why would I? And the fact that some solutions are undeservedly forgotten, concentrating all their attention on server virtualization and VDI, well, maybe RDS.
What, for example, to do if the company has changed the corporate standard and now the standard is not Windows XP, but Windows 7? At the same time, programmers did not have time to rewrite their software, which is “sharpened” under the outdated operating systems.
Of course, you can buy a server farm, implement VDI, and distribute virtual machines to users — a matter of money. And if they are not so many?
')
One solution is to use Windows XP Mode, which allows, using a local virtual machine running Windows XP with specific software installed, to publish to Windows 7 this application as if it were not installed in a virtual machine.
In this case, the sequence of actions is as follows - we save user data, reinstall Windows 7, turn on Windows XP Mode, install the software in the running virtual machine and publish it outside. Long? And then
And if such machines are 100 or 200, or 1000? You can let go of the mustache and beard :)
Well, simplify - you have installed Microsoft System Center Configuration Manager with Microsoft Deployment Toolkit. These tools are intended for managing workstations and servers, especially highlighting the Operating System Deployment module, which allows centralized spilling of the OS to new workstations, or reinstalling the OS on stations that are already running. Recently, the sharing of these products allows you to fully automate the process of migrating an enterprise to a new Windows 7 operating system.
And for those companies that have purchased Software Assurance, there is another additional bonus - a new product from Microsoft - P2V Migration for Software Assurance (based on Sysinternals Disk2VHD). During automated migration to Windows 7, it allows you to create a virtual machine from an existing one running Windows XP or later, launch it in Windows XP Mode and publish installed applications and Internet Explorer in Windows 7 (using RemoteApp and Virtual PC mechanisms).
Naturally, the use of publishing applications in XP Mode is a temporary solution, because more system resources are being spent, and not all operating systems are supported, but at least there is a time buffer that allows you to either rewrite the software or buy new versions that support Windows 7 .
The beta version of P2V Migration for Software Assurance is available at https://connect.microsoft.com/site14/Downloads/DownloadDetails.aspx?DownloadID=30989 .
Naturally, there are some restrictions:
- such migration is possible if you have 32-bit OS Windows XP SP3, Windows Vista Business, Windows Vista Enterprise SP1 or SP2, Windows 7;
- the license of the installed OS is not OEM;
- hard drives must be less than or equal to 127 GB.
In addition, if during the installation of P2V Migration there was no access to the Internet, then the following software should be downloaded and copied to the / Tools installation folder:
- Disk2VHD.exe . Sysinternals tool for performing P2V hard disk conversion
- KB961742-v3.exe . Update for Windows XP with SP3 to support RemoteApp
- Windows6.0-KB961741-x86.msu . Update for Windows Vista SP1 to support RemoteApp
- Windows6.1-KB958559-x64.msu . 64-bit Windows Virtual PC for Windows 7
- Windows6.1-KB958559-x86.msu . 32-bit Windows Virtual PC for Windows 7
- Windows6.1-KB977206-x64.msu . 64-bit update for Windows Virtual PC
- Windows6.1-KB977206-x86.msu . 32-bit update for Windows Virtual PC
Let's wait for the release
Source: https://habr.com/ru/post/103956/
All Articles