Arquivo da categoria ‘System Center’

Fala galera !

Como todos notaram, algumas máquinas com o Windows 7 32 bits instalado apresentaram problemas com o Security Update KB2823324 que trouxe algumas alterações para correção de itens no system kernel-mode driver, porém, aparentemente essas correções conflitaram com os softwares Guardiões utilizados pelos Bancos (GBPlugin – G-Buster Browser Defense) – Fato ainda não comprovado.

É importante frisar que máquinas sem o plugin não apresentaram os erros, então, existem fortes indicações de este ser o causador dos problemas.

A Microsoft disponibilizou a Correção para o problema no link:

http://www.microsoft.com/brasil/resolucao/

Não formate seu computador, siga os passos do site para a resolução.

Caso você não tenha aplicado o KB ainda e tenha certeza que o GBPlugin esteja instalado na sua máquina, não instale o KB mencionado.

Se você não fizer o uso do cadeado eletrônico, não haverá problemas na instalação do KB.

Um abraço a todos,

Rodrigo Lopes
Absolut IT Soluções em Suporte e Tecnologia | Microsoft Partner
MCT | MCSE | MCITP | Enterprise, Server, Lync and Virtualization Administrator, MCSA, MCTS | Active Directory, MCTS | Windows Server 2008 Virtualization, MCDST

Olá pessoal !

Conforme comentei no último post, consegui passar na 70-246 e assim fechar o MCSE em Private Cloud, com a honra de ter mais um Charter Member.

Hoje estou trazendo para vcs algumas dicas para realizar o exame 70-247, e no próximo post trago mais uma série de dicas para a prova 70-246.

Então vamos ao que interessa !

A grade oficial informa que os seguintes itens são cobrados:

Design and Deploy System Center (19%)
Configure System Center Infrastructure (21%)
Configure the Fabric (27%)
Configure System Center Integration (16%)
Configure and Deploy Virtual Machines and Services (17%)
Dentro desses temas, as questões abordaram:
– MPIO / SAN;

– VMM Network;

– Storage Classification;

– Console do VMM 2012 ( Bom fazer as demos do produto e brincar bastante com ele, visto que as questões são interativas);

– Role Services do IIS;

– APP Controler / User roles /  Environment Swap Upgrade;

– VMM Hardware Profile;

– VMM APP Profile;

– SQL Service Template / Notification Services;

– Configurar Memoria em Hardware Profile;

– APP-V e Sequencer;

– AD-CS – Certificados, como importar;

– Adicionar Wsus  à Infra do VMM ;

– SCOM Management Packs – Windows Server MP, SQL Monitoring MP, VMM MP e IIS7 MP;

– SCOM caiu questão sobre as portas 5723, 5724 – Root management server e Gateway;

– Sharepoint Foundation – Web Parts;

– Service Manager, User Roles, Connectors;

– Baremetal Deployment, DNS e DHCP;

– PowerShell commands – New-SCUserRole / Set-SCUserRole

Cairam algumas questões do tipo Drag and Drop para mostrar a sequência das tarefas a serem executadas dentro do VMM e do SCOM, além de Wsus.

Usei bastante os materiais e exercícios do MVA, V-labs de System Center 2012 e o Blog do meu amigo Cleber Marques:

https://msmvps.com/blogs/clebermarques/archive/2012/04/23/dicas-para-os-exames-70-246-e-70-247-sobre-nuvem-privada.aspx

https://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032501040&culture=en-us

http://www.microsoftvirtualacademy.com/tracks/configuring-and-deploying-microsoft-s-private-cloud

http://www.system-center.fr/?p=2942

Espero ter ajudado galera e quero receber notícias de vcs !

Um super abraço e bons estudos!!!

Rodrigo Lopes
Absolut IT Soluções em Suporte e Tecnologia | Microsoft Cloud Partner
MCT | MCSA | MCSE: Private Cloud | MCITP | Enterprise, Server, Lync and Virtualization Administrator, MCTS| Active Directory, MCTS | Windows Server 2008 Virtualization, MCDST

A Microsoft disponibilizou a alguns meses uma nova série de Certificações – MCSA e MCSE focados em Infra, Desktop e Private Cloud.

Vou abordar aqui o MCSE em Private Cloud.

mcse Confesso que fiquei super animado com a volta do MCSE focado agora em Cloud, que tem como foco profissionais com os titulos MCITP: Server Admin, MCITP: Enterprise Admin que já concedem o titulo de MCSA: Microsoft Certified Solution Associate, pré-req para a nova Certificação que estou abordando.

Como já possuo todos os títulos necessários, baixei os Mocs Digitais 10751AB: Beta: Configuring and Deploying a Private Cloud with System Center 2012 (5 Days) e 10750AB: Beta: Monitoring and Operating a Private Cloud with System Center 2012 (5 Days) e comecei os estudos a mais ou menos 30 dias.

Prestei na última sexta-feira o exame 70-247 – Configuring and Deploying a Private Cloud with System Center 2012 e em breve postarei aqui para vocês as dicas para se preparar para os 2 exames.

Na próxima segunda irei prestar a 70-246 – Monitoring and Operating a Private Cloud with System Center 2012, portanto esse será um fim de semana focado nos estudos.

O desafio maior é que tratam-se de produtos novos, uma gama enorme de recursos oferecidos com um controle fantástico, desde o usuário que irá operar o sistema até a aplicação, que roda com um Banco de Dados por tráz, tudo isso monitorado fim a fim pelas ferramentas da suíte do System Center.

Os exames necessários para você que pretende tirar o MCSE em Private Cloud são:

MCSA em Windows Server 2008:

image

Em breve posto para vocês todas as dicas e materiais de apoio necessários para vencer esses super desafios que são as Certificações da Microsoft!

Sucesso a todos,

Rodrigo Lopes
Absolut IT Soluções em Suporte e Tecnologia | Microsoft Partner
MCT | MCITP | Enterprise, Server, Lync and Virtualization Administrator, MCSA, MCTS | Active Directory, MCTS | Windows Server 2008 Virtualization, MCDST
IM: rodrigollopes@live.com

Download Microsoft Private Cloud Evaluation Software

A Microsoft liberou para o download o Kit de Avaliação para Nuvem Privada com System Center 2012.

O Pacote inclui toda a suite do System Center 2012 e opcionalmente o download do SP1 do Windows Server 2008R2:

System Center 2012

  • System Center 2012 Unified Installer is a utility designed to perform new, clean installations of System Center 2012 for testing and evaluation purposes only. If you want to upgrade from an existing System Center installation or choose set up options such as high availability or multi-server component installs, please refer instead to the System Center 2012 component installation guides located on the Microsoft Private Cloud Evaluation Resource Page.
    User’s Guide >>
  • System Center 2012 App Controller provides a common self-service experience across private and public clouds that can help you empower application owners to easily build, configure, deploy, and manage new services.
    System Requirements >>
  • System Center 2012 Configuration Manager provides comprehensive configuration management for the Microsoft platform that can help you empower users with the devices and applications they need to be productive while maintaining corporate compliance and control.
    System Requirements >>
  • System Center 2012 Data Protection Manager provides unified data protection for Windows servers and clients that can help you deliver scalable, manageable, and cost-effective protection and restore scenarios from disk, tape, and off premise.
    System Requirements >>
  • System Center 2012 Endpoint Protection, built on System Center Configuration Manager, provides industry-leading threat detection of malware and exploits as part of a unified infrastructure for managing client security and compliance that can help you simplify and improve endpoint protection.
    System Requirements >>
  • System Center 2012 Operations Manager provides deep application diagnostics and infrastructure monitoring that can help you ensure the predictable performance and availability of vital applications and offers a comprehensive view of your datacenter, private cloud, and public clouds.
    System Requirements >>
  • System Center 2012 Orchestrator provides orchestration, integration, and automation of IT processes through the creation of runbooks that can help you to define and standardize best practices and improve operational efficiency.
    System Requirements >>
  • System Center 2012 Service Manager provides flexible self-service experiences and standardized datacenter processes that can help you integrate people, workflows, and knowledge across enterprise infrastructure and applications.
    System Requirements >>
  • System Center 2012 Virtual Machine Manager provides virtual machine management and services deployment with support for multi-hypervisor environments that can help you deliver a flexible and cost effective private cloud environment.
    System Requirements >>

Windows Server 2008 R2 SP1 (optional download)

  • Windows Server 2008 R2 SP1 is designed to help you increase control, availability, and flexibility of your datacenter and desktop infrastructure while helping reduce costs.

Download no link:

http://technet.microsoft.com/pt-br/evalcenter/hh505660

Abraços e bons estudos!

Rodrigo Lopes
Absolut IT Soluções em Suporte e Tecnologia | Microsoft Partner
MCT | MCITP | Enterprise, Server and Virtualization Administrator, MCSA, MCTS | Active Directory, MCTS | Windows Server 2008 Virtualization, MCDST
IM: rodrigollopes@live.com

System Center Virtual Machine Manager 2012

A Microsoft divulgou o lançamento do System Center 2012, que será no dia 18 de Maio à partir das 8hs:

http://www.microsoft.com/pt-br/server-cloud/events/systemcenter.aspx?WT.mc_id=MSCOM_BR_HP_Banner01_systemcenter_VueLev

Inscreva-se agora para o evento online

Para que você possa se preparar para a nova suite de produtos, destaco aqui o SCVMM2012.

Segue abaixo o link para download da versão Trial do produto em VHD:

System Center 2012 – Virtual Machine Manager – Evaluation (VHD)

http://www.microsoft.com/en-us/download/details.aspx?id=10712

Overview

System Center 2012 – Virtual Machine Manager delivers industry leading fabric management, virtual machine management and services deployment in private cloud environments. System Center 2012 – Virtual Machine Manager offers key new features that include hypervisor creation and management, network management, storage management, private cloud creation, self-service usage and service creation. It features deep investments in server application virtualization, service design and service modeling all of which can be used to efficiently offer an on-premises private cloud.

System requirements

Supported operating systems: Windows 7 Enterprise, Windows 7 Professional, Windows 7 Ultimate, Windows Server 2008 R2, Windows Server 2008 R2 Datacenter, Windows Server 2008 R2 Enterprise

    • Windows Server 2008 R2 (full installation) Standard, Enterprise, Datacenter x64
    • Windows 7 Professional, Enterprise, Ultimate x32, x64
    • Windows Remote Management (WinRM) 2.0
    • Windows PowerShell 2.0
    • Microsoft .NET Framework 3.5 Service Pack 1 (SP1)
    • Windows Automated Installation Kit (AIK) for Windows 7
    • SQL Server 2008 or SQL Server 2008 R2 Standard, Enterprise, and Datacenter
    • Windows Deployment Services (WDS) – (Version on Windows Server 2008 R2)
    • Windows Software Update Services (WSUS) 3.0 SP2 64bit

Segue também um excelente post do Leandro Carvalho, MVP de Virtual Machine sobre a instalação passo a passo do VMM2012 no link:

http://social.technet.microsoft.com/wiki/contents/articles/novidades-pr-233-requisitos-e-instala-231-227-o-do-system-center-virtual-machine-manager-2012-pt-br.aspx

Em breve vou postar as telas de instação do produto no meu Lab.

Um abraço e até o próximo Post!

Rodrigo Lopes
MCT | MCITP | Enterprise, Server, Lync and Virtualization Administrator, MCSA, MCTS | Active Directory, MCTS | Windows Server 2008 Virtualization, MCDST
Absolut IT Tecnologia em Suporte
www.absolutit.com.br
IM: rodrigo_llopes@live.com

Boa tarde galera,

Escolhi um tema show para iniciar o ano e as contribuições à Comunidade Microsoft.

Trouxe para vocês materiais que ajudarão bastante no exame 70-659 – Windows 2008 R2 Server Virtualization.

Abaixo temos o conteúdo atualizado do E-Book de Virtualização Microsoft – Understanding Microsoft Virtualization R2 Solutions  e o treinamento Gratuito 6333: Exploring Microsoft Virtualization Technologies:

http://www.microsoft.com/learning/en/us/training/virtualization.aspx

https://www.microsoftelearning.com/eLearning/offerDetail.aspx?offerPriceId=228501

Collection 6333: Exploring Microsoft Virtualization Technologies

Visão Geral

This collection of two 2-hour online clinics and an 1-hour online clinic provides IT Professionals experienced in Windows 2000 Server or Windows Server 2003 with the knowledge and skills to implement and manage virtualization technologies.

Topics covered in the clinic within the collection include:•Introduction to Microsoft System Center Virtual Machine Manager 2008

•Overview of Microsoft Application Virtualization •Overview of Terminal Services in Windows Server 2008 •Overview of Hyper-V

Student Prerequisites:

•Experience in planning, implementing, and supporting Windows Server–based networks, operating systems and platform infrastructure. This may include experience in Windows 2000 Server, Windows Server 2003, and Windows Server 2008. •Knowledge of server virtualization and Hyper-V.

Em breve divulgarei em novo post a campanha da Microsoft Learning Rewards sobre vouchers para a prova 70-659.

Um abraço e bons estudos !

Rodrigo Lopes
Absolut IT Soluções em Suporte e Tecnologia | Microsoft Partner
MCT | MCITP | Enterprise, Server and Virtualization Administrator, MCSA, MCTS | Active Directory, MCTS | Windows Server 2008 Virtualization, MCDST
IM: rodrigollopes@live.com

 

Olá pessoal,
 
Foi publicado no Technet uma matéria sobre o P2V bem completa. Ela cobre desde a tomada de decisão inicial até os pré-req para que sua migração seja bem sucedida através do System Center Virtual Machine Manager 2008 e 2008 R2.
 
Contudo são necessários alguns cuidados com as limitações da tecnologia em relação as portas USB, pois existem alguns softwares que rodam nos servidores que necessitam de dispositivos hardlock e por enquanto isso não é suportado no Hyper-v.
 
Existem 2 tipos de conversão P2V:
 
Online – A máquina é convertida para o estado Virtual a quente, ou seja, seu sistema continua operando normalmente enquanto a conversão é realizade e no final do processo, o VMM2008 desliga a fisica e mantem a Virtual rodando.
 
Offline – A máquina fisica é desligada durante o processo, pois o Windows inicia no modo WPE (Windows Preinstallation Environment) e o VMM clona o volume o transformando em um .vhd.  No final do processo, o VMM reinicia o computador de origem no Sistema original e você realiza o start do Sistema Virtual.
 
Vantagens – O modo P2V Offline pode se mostrar mais confiável em algumas situações garantindo assim a consistência dos dados.
 
Segue a matéria:
 
 

P2V: Converting Physical Computers to Virtual Machines in VMM

Updated: July 15, 2010

Applies To: Virtual Machine Manager 2008, Virtual Machine Manager 2008 R2

Microsoft System Center Virtual Machine Manager (VMM) allows you to convert existing physical computers into virtual machines through a process known as physical-to-virtual (P2V) conversion. VMM simplifies P2V by providing a task-based wizard to automate much of the conversion process. Since the P2V process is completely scriptable, you can initiate large-scale P2V conversions through the Windows PowerShell command line.

noteNote
VMM performs P2V conversions on a best-effort basis. We cannot guarantee that all possible combinations of physical hardware can be converted to a virtual machine.

Diagram of the possible P2V and V2V paths.

Which Physical Computers Can I Convert?

The requirements for physical source computers depend on whether you are performing an online or offline P2V.

Online vs. Offline Conversions

The following table lists some of the differences between the online and offline P2V conversions.

 

Category Online P2V Offline P2V

Source computer availability

The source computer continues to perform normal operations during the conversion.

The source computer is taken offline during the conversion.

Process

VMM creates a copy of local NTFS volumes and data of VSS-aware applications. VMM leverages the Volume Shadow Copy Service (VSS) to ensure that data is backed up consistently while the server continues to service user requests. VMM uses this read-only snapshot to create a VHD.

The source computer restarts into the Windows Preinstallation Environment (Windows PE), and then VMM clones the volume to a VHD. Finally, VMM restarts the source computer into the original operating system.

Compatibility

Online P2V is the default for the operating systems on most physical computers.

Offline P2V is the only option for Windows 2000 Server conversion, the only method to reliably migrate FAT volumes, and the recommended method for converting domain controllers.

Advantages

Source computer is available throughout the conversion.

Offline P2V can be the most reliable way to ensure data consistency and is the only option in certain situations (see above).

noteNote
With both online and offline P2V, VMM temporarily installs an agent on the physical source computer to be converted.

Requirements on the Source Machine

To perform a P2V conversion, your source computer:

  • Must have at least 512 MB of RAM.
  • Cannot have any volumes larger than 2040 GB.
  • Must have an Advanced Configuration and Power Interface (ACPI) BIOS – Vista WinPE will not install on a non-ACPI BIOS.
  • Must be accessible by VMM and by the host computer.
  • Cannot be in a perimeter network. A perimeter network, which is also known as a screened subnet, is a collection of devices and subnets placed between an intranet and the Internet to help protect the intranet from unauthorized Internet users. The source computer for a P2V conversion can be in any other network topology in which the VMM server can connect to the source machine to temporarily install an agent and can make Windows Management Instrumentation (WMI) calls to the source computer.
ImportantImportant
Before you convert a VMware virtual machine to a Hyper-V or Virtual Server virtual machine, you must uninstall VMware Tools on the guest operating system of the virtual machine.

The following table lists the Windows operating systems for which P2V conversions are supported in VMM 2008 and in VMM 2008 R2.

noteNote
Support for Windows 2000 Server and Windows XP SP2 ended on July 13, 2010. After this date, integration services for these operating systems will not be updated and support will not be available for any issues arising from using these operating systems in virtual machines. For more information about the end of support, see Support for Windows 2000 and Windows XP Service Pack 2 (SP2) Ends on July 13, 2010 (http://go.microsoft.com/fwlink/?LinkID=196755).

Supported Operating Systems for P2V Conversions in VMM 2008 and VMM 2008 R2

Operating System VMM 2008 VMM 2008 R2

Windows XP Professional with Service Pack 3 (SP3)

Yes

Yes

Windows XP 64-Bit Edition SP3

Yes

Yes

Windows Server 2003 Standard Edition (32-bit x86)

Yes (Requires SP1 or later.)

Yes (Requires SP2 or later.)

Windows Server 2003 Enterprise Edition (32-bit x86)

Yes (Requires SP1 or later.)

Yes (Requires SP2 or later.)

Windows Server 2003 Datacenter Edition (32-bit x86)

Yes (Requires SP1 or later.)

Yes (Requires SP2 or later.)

Windows Server 2003 x64 Standard Edition

Yes (Requires SP1 or later.)

Yes (Requires SP2 or later.)

Windows Server 2003 Enterprise x64 Edition

Yes (Requires SP1 or later.)

Yes (Requires SP2 or later.)

Windows Server 2003 Datacenter x64 Edition

Yes (Requires SP1 or later.)

Yes (Requires SP2 or later.)

Windows Server 2003 Web Edition

Yes

Yes

Windows Small Business Server 2003

Yes

Yes

Windows Vista with Service Pack 1 (SP1)

Yes

Yes

64-bit edition of Windows Vista with Service Pack 1 (SP1)

Yes

Yes

Windows Server 2008 Standard 32-Bit

Yes

Yes

Windows Server 2008 Enterprise 32-Bit

Yes

Yes

Windows Server 2008 Datacenter 32-Bit

Yes

Yes

64-bit edition of Windows Server 2008 Standard

Yes

Yes

64-bit edition of Windows Server 2008 Enterprise

Yes

Yes

64-bit edition of Windows Server 2008 Datacenter

Yes

Yes

Windows Web Server 2008

Yes

Yes

Windows 7

No

Yes

64-bit edition of Windows 7

No

Yes

64-bit edition of Windows Server 2008 R2 Standard

No

Yes

64-bit edition of Windows Server 2008 R2 Enterprise

No

Yes

64-bit edition of Windows Server 2008 R2 Datacenter

No

Yes

Windows Web Server 2008 R2

No

Yes

The following restrictions apply to P2V operation system support:

  • VMM does not support P2V conversion for computers with Itanium architecture–based operating systems.
  • VMM does not support P2V on source computers running Windows NT Server 4.0. However, you can use the Microsoft Virtual Server 2005 Migration Toolkit (VSMT) or third-party solutions for converting computers running Windows NT Server 4.0.
  • VMM 2008 R2 does not support converting a physical computer running Windows Server 2003 SP1 to a virtual machine that is managed by Hyper-V. Hyper-V does not support Integration Components on computers running Windows Server 2003 SP1. As a result, there is no mouse control when you use Remote Desktop Protocol (RDP) to connect to the virtual machine. To avoid this issue, update the operating system to Windows Server 2003 SP2 before you convert the physical computer. As an alternative, you can convert the computer by using VMM 2008 and then deploy the virtual machine in VMM 2008 R2.

Requirements for the Destination Host Server

In VMM, a host is a physical computer on which you can deploy one or more virtual machines. To run P2V, you need a host on which to place the image of the source computer.

Requirements for the host server include:

  • The destination host during a P2V conversion can be running Windows Server 2008 with Hyper-V, Windows Server 2008 R2 with Hyper-V, or Virtual Server R2 SP1 (or later).
  • The destination host cannot be in a perimeter network.
  • As in any virtual machine creation or migration, the destination host for a P2V conversion must have sufficient memory for the virtual machine in addition to memory reserved for the host operating system. By default, the amount of memory reserved for the host operating system is 256 MB in VMM 2008 or 512 MB in VMM 2008 R2. If the host does not have enough memory for the virtual machine in addition to the memory reserved for the host, you will get a placement error in the Convert Physical Server Wizard.

Deciding Which Computers to Convert

To successfully perform P2V, you must be able to identify appropriate physical workloads for consolidation into the virtualized environment. This section will help you identify which computers are good candidates for conversion.

Identifying Virtualization Candidates

If you have deployed Microsoft System Center Operations Manager 2007, VMM can help you identify the right physical servers for consolidation based on direct analysis of the performance counters of the target machine or historical performance data stored in the Operations Manager database.

The Virtualization Candidates report helps you identify underutilized computers by displaying average values for a set of commonly requested performance counters for CPU, memory, disk usage, hardware configurations, including processor speed, number of processors, and total RAM. To use the Virtualization Candidates report, you must deploy the System Center VMM 2008 Management Pack. For more information about reporting, see Configuring Reporting for VMM.

Prioritizing Virtualization Candidates

When identifying the best candidates for P2V conversion, consider converting these types of computers, in order of preference:

  1. Non business-critical underutilized computers. By starting with the least utilized computers that are not business critical, you can learn the P2V process with relatively low risk. Web servers may make good candidates.
  2. Computers with outdated or unsupported hardware that needs to be replaced.
  3. Computers with low utilization that are hosting less critical in-house applications.
  4. Computers with higher utilization that are hosting less critical applications.
  5. The remaining underutilized computers.
  6. In general, business-critical applications, such as e-mail servers and databases that are highly utilized, should only be virtualized to the Hyper-V platform in the Windows Server 2008 (64-bit) operating system.

How to Perform a P2V Conversion

During a P2V conversion, disk images of the hard disks on the source computer are packaged into virtual hard disks (.vhd files), and then prepared to ensure that the operating system will operate in the virtualized environment on the destination host.

Before You Begin

The following list includes tasks that you should perform before starting the P2V conversion:

  • The first phase of a P2V conversion is to survey the hardware configuration of the source computer and make sure the patch cache contains all necessary drivers and system files to support the drives emulated by the target virtualization software. If any drivers are missing, you will get specific error messages indicating where to get the necessary drivers.
    noteNote
    You can use the Add-Patch cmdlet to manually download available patches to VMM.

  • Bad sectors on disk cannot be transferred during a P2V conversion. To avoid data loss, run a disk maintenance tool, such as Chkdsk, on the source computer to detect and correct any file system errors.
  • To help minimize the time required for the imaging phase, perform a disk defragmentation on the source computer’s hard drives. Also, ensure that you have a fast network connection between the source computer and the host.
  • Use dynamic Virtual Hard Disks (VHD) to conserve disk space on the destination host. For example, if you convert 5 GB of data on a 40 GB hard drive, VMM will create a dynamically expanding 40 GB VHD that occupies approximately 5 GB of disk space and can expand up to 40 GB. The actual size depends on fragmentation of the original volume plus some VHD format overhead.
    noteNote
    It is not possible to shrink the size of a disk.

  • For online P2V only: Make sure that all critical applications running on the source computer have VSS-aware writers or that they are stopped.
  • For offline P2V only: Be prepared to supply NIC and mass storage drivers that are compatible with Windows Vista. VMM will evaluate the source physical computer and compare it with the drivers included in Windows PE 2.0 and provide instructions on adding drivers on the source computer.

Convert Physical Server Wizard

  • You can use the Convert Physical Server Wizard to create a new virtual machine from a physical source computer. For more information, see P2V: How to Perform a Conversion.
    noteNote
    You can provide the IPv4 or IPv6 address instead of machine names in the Convert Physical Server Wizard or from the command line.

  • After the P2V is complete, remove any unnecessary vendor-specific hardware utilities and drivers from the virtual machine.
noteNote
The Convert Physical Server Wizard invokes the New-P2V cmdlet. Some conversion options are only available from the command line.

Performing P2V from the Command Line

You can perform a P2V conversion from Windows PowerShell by using the New-P2V cmdlet. To get a base script that you can customize, run the Convert Virtual Machine Wizard from the VMM Administrator Console and click the View Script button.

For more information about using the New-P2V cmdlet type Get-Help New-P2V in the Windows PowerShell – Virtual Machine Manager command shell.

The P2V Process

The P2V conversion process captures an image of the source disk and modifies the operating system and drivers to make them compatible with the Hyper-V or Virtual Server emulated hardware. Online and offline P2V conversions use two distinct processes:

Online Conversion

Online conversion does not require a restart of the source computer. VMM uses the Volume Shadow Copy Service (VSS) to create an image of the source machine that is consistent on the application level and then creates an analogous virtual machine. The online conversion process consists of five steps:

  1. Installing the agent on the source computer
  2. Retrieving hardware configuration
  3. Imaging
  4. Fixing up
  5. Creating the virtual machine

Diagram of the P2V online conversion process.

  1. Virtual Machine Manager installs the P2V agent on the source computer to gather the hardware and software configuration. After the conversion is complete, the agent is removed.
    ImportantImportant
    The VMM agent Windows Installer creates a firewall exception for remote administration (RemoteAdmin service) and Secure Sockets Layer (SSL) port. These exceptions are removed when the VMM agent is removed at the end of the P2V process. The HTTPS port default is TCP 443.

  2. VMM gathers the source computer’s hardware and software configuration, as follows:
    1. The VMM agent gathers information about hardware, software, services, hotfixes, and the disk layout (file system, volume type). The VMM agent exports this information to the VMM database as a machine configuration file in XML format.
    2. VMM determines whether the source machine can be virtualized. VMM confirms that the operating system is supported and that the physical configuration can be made compatible with the destination virtualization software. VMM verifies that the required files are present in the patch cache and downloads any missing patches to the Patch Import directory on the VMM server.
  3. Imaging phase:
    1. A Volume Shadow Copy Service (VSS) image is captured for each selected volume that is consistent on the application level. If a dynamic destination VHD format is selected, this process captures data only, not empty space.
    2. Data is streamed directly from the source computer to the VMM host using Background Intelligent Transfer Service (BITS).
    3. Each physical volume becomes a separate virtual hard disk.
  4. Fix-Up phase. VMM prepares the operating system and the virtual hard disks for virtual machine creation.
  5. Create Virtual Machine phase:
    1. VMM creates the virtual machine.
    2. VMM attaches virtual hard disks, network adapters, CD-ROM, and memory.

Offline Conversion

Offline P2V is the most reliable way to ensure data consistency because it creates an exact copy of the source computer while it is not in use. Also, offline P2V is the only option for converting Windows 2000 Server, domain controllers, and non-NTFS volumes. Unlike online conversions, the user must provide any missing drivers if Windows PE does not support the source computer. The offline conversion consists of four steps:

  1. Agent installation. Virtual Machine Manager installs the VMM agent on the source computer.
  2. The VMM agent installs a Windows PE image on the source computer, modifies the boot record, and restarts in Windows PE instead of the base operating system.
  3. VMM begins streaming physical disks. There are no snapshots in this process.
  4. The remainder of the process is similar to the Fix-Up phase and Create Virtual Machine Phase in an online P2V.

[]’s

Rodrigo L. Lopes
Absolut IT Soluções em Suporte e Tecnologia
www.absolutit.com.br
MCT | MCITP | Virtualization Administrator 2008 R2