locked
Installing Windows Server 2012 Essentials R2 - Hyper-V role

    Question

  • Hello,

    Downloaded the preview of WE2012E R2 but not sure or found anywhere with information on how to install it in Hyper-V mode.

    Can you please help with this?

    Best Regards,

    Abby_Doc


    • Edited by Abby_Doc Tuesday, July 09, 2013 8:50 AM
    Tuesday, July 09, 2013 8:49 AM

Answers

  • Hi, Abby_Doc

    This tool is for partners to prepare a configuration that allows end user to go through a simple wizard to set up Essentials as a Hyper-v host and a configured Essentials VM guest.

    This is only applies to Windows Server 2012 R2 Essentials edition.

    Below is some sample steps you can try:

    How to prepare virtualized deployment

    First of all, your hardware must support virtualization and it must be turned on.

     

    Secondly, you need to prepare a customized image that contains the images for Windows Server Essentials Host and Windows Server Essentials Guest. To do this, perform the following steps:

    1. Prepare Virtual Machine media.
    2. Prepare the virtual machine Host:

    Prepare Virtual Machine media:

    1. Start the installation media you get from Microsoft and put in on your technical computer.
      1. If you are having an ISO file, mount it in File Explorer
      2. If you’re using a DVD, put it on your DVD drive.
    2. Assume the mounted drive or your DVD drive is E:\
    3. Copy all content under E:\ to C:\essentials-image\. You can use different folder.
    4. Create two other folder C:\essentials-mount\ and C:\scripts\. You can use different folder.
    5. Mount the install.wim using DISM to C:\essentials-mount

    dism /Mount-Wim /WimFile:C:\essentials-image\sources\install.wim /index:1 /MountDir:C:\essentials-mount

    1. Customize the image using DISM. The later sections provides guidance on how to customize the essentials image, such as add branding, by changing registry keys, and placing additional files. Depending on your needs, you can selectively apply these settings offline using DISM. If you’re just evaluate how to make a virtualized deployment, you can skip this step.
    2. Add additional language packs using DISM. The step follows Windows Server standard approach listed in TechNet.
    3. Commit the changes to the image.
    4. dism /unmount-Wim /MountDir:C:\essentials-mount /commit
    5. Now, you have a customized Windows Server 2012 R2 Essentials wim file. Depending on your needs, you can either seal it to an installation ISO file or convert it to a VHD.
      1. To Seal it to an ISO file, download Windows ADK, and run the following script
      2. cd C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64
      3.                       oscdimg.exe -u1 -bC:\essentials-image\boot\etfsboot.com C:\essentials-image C:\OEMEssentials.isoTo convert it to a VHDX, perform step a) and download Convert-WindowsImage to C:\scripts and run the following
      4. powershell -c "Set-ExecutionPolicy Unrestricted; C:\scripts\Convert-WindowsImage.ps1 -VHDFormat vhdx -sizebytes 127GB –sourcepath C:\OEMEssentials.iso- -vhdpath C:\OEMEssentials.vhdx

    Up to here, you got a customized image in format of ISO or VHDX for your VM guest that contains Windows Server Essentials features, such as Remote Web Access, Dashboard, etc. You can test the image by installing it in a hyper-v machine. Next step is to prepare the Virtual Machine

    Preparing the virtual machine Host:

    1.  
    2. Start the installation ISO file you get from Microsoft and put in on your technical computer.
    3. Mount the ISO file to technical computer. Assume the mounted drive is E:\
    4. Copy all content under E:\ to C:\essentials-host-image\. You can use different folder.
    5. Create another folder C:\essentials-host-mount\. You can use different folder.
    6. Mount the install.wim using DISM to C:\essentials-mount

    dism /Mount-Wim /WimFile:C:\essentials-host-image\sources\install.wim /index:1 /MountDir:C:\essentials-host-mount

    1. Remove Windows Server Essentials roles and features you want installed by default. Optionally you can remove other roles, see Remove roles. Run the following:

    dism /Image:C:\essentials-host-mount /disable-feature:"wss-product-package"

    1.  
    2. Enable Hyper-V,  hyper-v management PowerShell  and Hyper-V Management RSAT Tools. Run the following script
    3. dism /Image: C:\essentials-host-mount   /enable-feature:Microsoft-Hyper-V /All
    4. dism /Image: C:\essentials-host-mount   /enable-feature:Microsoft-Hyper-V-Management-Clients /All

    10.  dism /Image: C:\essentials-host-mount   /enable-feature:Microsoft-Hyper-V-Management-PowerShell /All

    1. Set registry key to not pop up server manager. Run the following script:

    11.  reg load HKLM\test C:\essentials-host-mount\windows\system32\config\software

    12.  reg add "HKLM\test\Microsoft\ServerManager" /v DoNotOpenServerManagerAtLogon /t REG_DWORD /d 1 /f

    1. Set registry key to specify the deployment settings. Run the following script:

    13.  reg add "HKLM\test\Microsoft\Windows Server\Setup\OEM" /v DeployAsVM /t REG_SZ /d C:\DeployAsVM\ICConfig.xml /f

    14.  reg unload HKLM\test

    Key

    Value

    Path

    HKLM\Software\Microsoft\Windows Server\Setup\OEM

    Name

    deployasvm

    Type

    REG_SZ or REG_EXPEND_SZ

    Value

    <path to settings file, which can contain environment variables and/or be relative to the %SYSTEMROOT% (i.e., %WINDIR%)>

     

    10.  Create the setting files following the Sample called C:\ICConfig.xml and copy it to C:\ essentials-host-mount\DeployAsVM. Run the following script:

    16.  md C:\ essentials-host-mount\DeployAsVM

    17.  copy C:\ICConfig.xml C:\essentials-host-mount\DeployAsVM\ICConfig.xml

    11.  Integrate the WS2012 R2 Essentials virtual guest image (*.vhdx or *.iso) into the Hyper-V host image. Run the following script

    18.  copy C:\OEMEssentials.vhdx  C:\essentials-host-mount\DeployAsVM\OEMEssentials.vhdx

    10.  Add additional language packs using DISM. The step follows Windows Server standard approach listed in TechNet. Note the set of languages on guest image and host image should be the same.

    11.  Commit the changes to the image.

          dism /unmount-Wim /MountDir:C:\essentials-host-mount /commit

    12.  Now, you have a customized Windows Server 2012 R2 Essentials wim file for the Host. To Seal it to an ISO file, run the following script

    1.      cd C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64

    20.           oscdimg -m -o -u2 -udfver102 -bootdata:2#p0,e,bc:\essentials-host-image\boot\etfsboot.com#pEF,e,bc:\ essentials-host-image\boot\efisys.bin C:\essentials-host-image C:\OEMEssentialsHost.iso

    Remove roles

    The Windows Server Essentials edition installs the following dependent roles by default. You can safely remove them from the Host.

     

    It’s required that you remove Essentials role from server host. If you want to remove Essentials role offline, the package name is “wss-product-package”

     

    [X] Essentials

    ServerEssentialsRole         

    [X] File and Storage Services

    FileAndStorage-Services

        [X] File and iSCSI Services

     File-Services

            [X] File Server

    FS-FileServer

            [X] BranchCache for Network Files

    FS-BranchCache

            [X] DFS Namespaces

    FS-DFS-Namespace

     [X] Web Server (IIS)   

    Web-Server

        [X] Web Server                                                      

    Web-WebServer

            [X] Common HTTP Features                                      

    Web-Common-Http

                [X] Default Document                                     

    Web-Default-Doc

                [X] Directory Browsing                                  

    Web-Dir-Browsing

                [X] HTTP Errors                                          

    Web-Http-Errors

                [X] Static Content                                    

    Web-Static-Content

            [X] Health and Diagnostics                     

    Web-Health

                [X] HTTP Logging                                         

    Web-Http-Logging

                [X] Tracing                                              

    Web-Http-Tracing

            [X] Performance                                              

    Web-Performance

                [X] Static Content Compression                       

    Web-Stat-Compression

            [X] Security                                                     

    Web-Security

                [X] Request Filtering                      

    Web-Filtering                

                [X] Basic Authentication                   

    Web-Basic-Auth               

                [X] Windows Authentication                              

    Web-Windows-Auth

            [X] Application Development                                        

    Web-App-Dev

                [X] .NET Extensibility 4.5                 

    Web-Net-Ext45                

                [X] ASP.NET 4.5                            

    Web-Asp-Net45                

                [X] ISAPI Extensions                                      

    Web-ISAPI-Ext 

                [X] ISAPI Filters                          

    Web-ISAPI-Filter             

                [X] Server Side Includes                                     

    Web-Includes

        [X] Management Tools                                              

    Web-Mgmt-Tools

            [X] IIS Management Console                                   

    Web-Mgmt-Console

        [X] ASP.NET 4.5                                          

    NET-Framework-45-ASPNET

            [X] HTTP Activation                            

    NET-WCF-HTTP-Activation       

    [X] BranchCache                                        

    BranchCache                  

    [X] Group Policy Management                            

     GPMC                         

    [X] Remote Server Administration Tools                                           

    RSAT

        [X] Role Administration Tools                      

    RSAT-Role-Tools               

            [X] File Services Tools                        

    RSAT-File-Services           

                [X] DFS Management Tools                              

    RSAT-DFS-Mgmt-Con 

            [X] Remote Access Management Tools                           

    RSAT-RemoteAccess

                [X] Remote Access module for Windows PowerShell

    RSAT-RemoteAccess-PowerShell  

     [X] Windows Process Activation Service                                            

    WAS

        [X] Process Model                                               

    WAS-Process-Model

        [X] Configuration APIs                              

    WAS-Config-APIs              

    [X] Windows Server Backup                              

    Windows-Server-Backup        

     

     

     

    Sample of configuration file

    Virtual Machine sample file: ICConfig.xml

    <?xml version="1.0" encoding="utf-8"?>

    <DeploymentSettings

      xmlns:xsd="http://www.w3.org/2001/XMLSchema"

      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

      xmlns="http://schemas.microsoft.com/WindowsServer/Essentials/2013/01/ServerDeployment/Virtualization”>

     <InstallationMedia>C:\DeployAsVM\OEMEssentials.vhdx </InstallationMedia>

    <VMBaseDirectory> %SYSTEMROOT%\vms </ VMBaseDirectory>

    <VMProcessorCount>4</ VMProcessorCount>

    < VMMemorySizeMB>4096</ VMMemorySizeMB>

    < VMSystemDiskSizeGB>127</ VMSystemDiskSizeGB>

    < VMDataDiskSizeGB>999</ VMeDataDiskSizeGB>

    <AllowDeployOnHost>true</AllowDeployOnHost>

    </DeploymentSettings>

     

    Note

    All paths can contains environment variables and/or be relative to the %SYSTEMROOT% (i.e., %WINDIR%).

     

    Setting

    Description

    InstallationMedia

    [A2] This configuration on the Hyper-V host specifies the path to the image that will be used for the virtual guest instance of WS2012 R2 Essentials.

    It can be in .iso format or .vhdx format.

     

    AllowDeployOnHost

    AllowDeployOnHost “true” enables WS2012 R2 Essentials to be installed either as a physical installation or as a virtual instance (using itself as a stripped-down Hyper-V host). AllowDeployOnHost “false” blocks the physical install option and forces a virtual deployment.

    VMBaseDirectory

    (Optional) Specify where the VM file is located

    VMProcessorCount

    (Optional) Specify the number of logical processor cores assigned to the VM

    VMMemorySizeMB

    (Optional) Specify the size of memory size allocated to the VM. By default it will use the 80% of available Memory for VM.

    VMSystemDiskSizeGB

    (Optional) Specify the size of system drive. By default it is 127GB.

    VMDataDiskSizeGB

    (Optional) Specify the size of the data drive. By default it will use the available space of the hard disk. Your total size of hard drives shouldn’t not exceed the physical capacity of the disk.

     

    Best Practices

    • Make sure your hardware has virtualization capability turned on.
    • After installation Essentials VM is not activated by default. Please guide your customer to activate the image using the product key you provided.
    • If you ship multi-language image to your customer, please make sure you have same set of languages available for VM Host and VM guest. The language for the guest VM will be the same as the VM Host.
    • If you want to prepare a factory reset DVD for your end user, make sure you include the installation media for VM and the necessary settings in the DVD image. If the image size exceeds to a size of DVD9, consider using multiple DVDs for your image.
    • It’s highly recommended that your use .vhdx instead of .iso for your installation media. This provides your end user with faster deployment.
    • This deployment type is only applicable when you ship Windows Server 2012 R2 Essentials.

    You have now created a customized image in ISO or VHDX format to be used as the virtual instance of Windows Server 2012 R2 Essentials with full Essentials functionality including the Dashboard, client backup, remote access etc.


    Thursday, July 11, 2013 3:19 AM

All replies

  • They are hinting about some magic wizard in this blog post,

    "This can be set up manually by the administrator or, depending on your OEM configuration, a simple wizard will guide you through the process of setting up the guest VM during the installation process of the server."

    but it seems the steps document is WIP, http://blogs.technet.com/b/sbs/archive/2013/07/01/windows-server-2012-r2-essentials-preview-and-windows-server-essentials-experience-server-role-now-available.aspx

    i will reply back after some experiments unless someone else knows the steps already.

    Thanks.


    KailashC

    Tuesday, July 09, 2013 10:40 AM
  • Ok. it works like this
    install Essentials on bare metal box and then install the Hyper V role (through server manager>Roles & features tab)
    once Hyper-v role is installed you can create one VM and install again another copy of essentials on it

    no other SKU are supported as Guest OS on Essentials with HYper v

    btw, that wizard thing seems to be meant for OEM customization only

    Thanks.


    KailashC


    • Edited by KailashC Tuesday, July 09, 2013 11:29 AM wizd
    Tuesday, July 09, 2013 11:16 AM
  • Hi Kailasah,

    Thanks for the input but that's not how its suppose to work from my understanding. I have searched and read every document I can find and the wizard is suppose to set it up for you with having to go into the server manager and set it up manually. That is the value to the SMB market place.

    I am surprised of the lack of input from the Microsoft WE2012E R2 team on this forum to help guide us.

    Thanks,

    Abby_Doc

    Tuesday, July 09, 2013 11:20 AM
  • Hi, Abby_Doc

    This tool is for partners to prepare a configuration that allows end user to go through a simple wizard to set up Essentials as a Hyper-v host and a configured Essentials VM guest.

    This is only applies to Windows Server 2012 R2 Essentials edition.

    Below is some sample steps you can try:

    How to prepare virtualized deployment

    First of all, your hardware must support virtualization and it must be turned on.

     

    Secondly, you need to prepare a customized image that contains the images for Windows Server Essentials Host and Windows Server Essentials Guest. To do this, perform the following steps:

    1. Prepare Virtual Machine media.
    2. Prepare the virtual machine Host:

    Prepare Virtual Machine media:

    1. Start the installation media you get from Microsoft and put in on your technical computer.
      1. If you are having an ISO file, mount it in File Explorer
      2. If you’re using a DVD, put it on your DVD drive.
    2. Assume the mounted drive or your DVD drive is E:\
    3. Copy all content under E:\ to C:\essentials-image\. You can use different folder.
    4. Create two other folder C:\essentials-mount\ and C:\scripts\. You can use different folder.
    5. Mount the install.wim using DISM to C:\essentials-mount

    dism /Mount-Wim /WimFile:C:\essentials-image\sources\install.wim /index:1 /MountDir:C:\essentials-mount

    1. Customize the image using DISM. The later sections provides guidance on how to customize the essentials image, such as add branding, by changing registry keys, and placing additional files. Depending on your needs, you can selectively apply these settings offline using DISM. If you’re just evaluate how to make a virtualized deployment, you can skip this step.
    2. Add additional language packs using DISM. The step follows Windows Server standard approach listed in TechNet.
    3. Commit the changes to the image.
    4. dism /unmount-Wim /MountDir:C:\essentials-mount /commit
    5. Now, you have a customized Windows Server 2012 R2 Essentials wim file. Depending on your needs, you can either seal it to an installation ISO file or convert it to a VHD.
      1. To Seal it to an ISO file, download Windows ADK, and run the following script
      2. cd C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64
      3.                       oscdimg.exe -u1 -bC:\essentials-image\boot\etfsboot.com C:\essentials-image C:\OEMEssentials.isoTo convert it to a VHDX, perform step a) and download Convert-WindowsImage to C:\scripts and run the following
      4. powershell -c "Set-ExecutionPolicy Unrestricted; C:\scripts\Convert-WindowsImage.ps1 -VHDFormat vhdx -sizebytes 127GB –sourcepath C:\OEMEssentials.iso- -vhdpath C:\OEMEssentials.vhdx

    Up to here, you got a customized image in format of ISO or VHDX for your VM guest that contains Windows Server Essentials features, such as Remote Web Access, Dashboard, etc. You can test the image by installing it in a hyper-v machine. Next step is to prepare the Virtual Machine

    Preparing the virtual machine Host:

    1.  
    2. Start the installation ISO file you get from Microsoft and put in on your technical computer.
    3. Mount the ISO file to technical computer. Assume the mounted drive is E:\
    4. Copy all content under E:\ to C:\essentials-host-image\. You can use different folder.
    5. Create another folder C:\essentials-host-mount\. You can use different folder.
    6. Mount the install.wim using DISM to C:\essentials-mount

    dism /Mount-Wim /WimFile:C:\essentials-host-image\sources\install.wim /index:1 /MountDir:C:\essentials-host-mount

    1. Remove Windows Server Essentials roles and features you want installed by default. Optionally you can remove other roles, see Remove roles. Run the following:

    dism /Image:C:\essentials-host-mount /disable-feature:"wss-product-package"

    1.  
    2. Enable Hyper-V,  hyper-v management PowerShell  and Hyper-V Management RSAT Tools. Run the following script
    3. dism /Image: C:\essentials-host-mount   /enable-feature:Microsoft-Hyper-V /All
    4. dism /Image: C:\essentials-host-mount   /enable-feature:Microsoft-Hyper-V-Management-Clients /All

    10.  dism /Image: C:\essentials-host-mount   /enable-feature:Microsoft-Hyper-V-Management-PowerShell /All

    1. Set registry key to not pop up server manager. Run the following script:

    11.  reg load HKLM\test C:\essentials-host-mount\windows\system32\config\software

    12.  reg add "HKLM\test\Microsoft\ServerManager" /v DoNotOpenServerManagerAtLogon /t REG_DWORD /d 1 /f

    1. Set registry key to specify the deployment settings. Run the following script:

    13.  reg add "HKLM\test\Microsoft\Windows Server\Setup\OEM" /v DeployAsVM /t REG_SZ /d C:\DeployAsVM\ICConfig.xml /f

    14.  reg unload HKLM\test

    Key

    Value

    Path

    HKLM\Software\Microsoft\Windows Server\Setup\OEM

    Name

    deployasvm

    Type

    REG_SZ or REG_EXPEND_SZ

    Value

    <path to settings file, which can contain environment variables and/or be relative to the %SYSTEMROOT% (i.e., %WINDIR%)>

     

    10.  Create the setting files following the Sample called C:\ICConfig.xml and copy it to C:\ essentials-host-mount\DeployAsVM. Run the following script:

    16.  md C:\ essentials-host-mount\DeployAsVM

    17.  copy C:\ICConfig.xml C:\essentials-host-mount\DeployAsVM\ICConfig.xml

    11.  Integrate the WS2012 R2 Essentials virtual guest image (*.vhdx or *.iso) into the Hyper-V host image. Run the following script

    18.  copy C:\OEMEssentials.vhdx  C:\essentials-host-mount\DeployAsVM\OEMEssentials.vhdx

    10.  Add additional language packs using DISM. The step follows Windows Server standard approach listed in TechNet. Note the set of languages on guest image and host image should be the same.

    11.  Commit the changes to the image.

          dism /unmount-Wim /MountDir:C:\essentials-host-mount /commit

    12.  Now, you have a customized Windows Server 2012 R2 Essentials wim file for the Host. To Seal it to an ISO file, run the following script

    1.      cd C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64

    20.           oscdimg -m -o -u2 -udfver102 -bootdata:2#p0,e,bc:\essentials-host-image\boot\etfsboot.com#pEF,e,bc:\ essentials-host-image\boot\efisys.bin C:\essentials-host-image C:\OEMEssentialsHost.iso

    Remove roles

    The Windows Server Essentials edition installs the following dependent roles by default. You can safely remove them from the Host.

     

    It’s required that you remove Essentials role from server host. If you want to remove Essentials role offline, the package name is “wss-product-package”

     

    [X] Essentials

    ServerEssentialsRole         

    [X] File and Storage Services

    FileAndStorage-Services

        [X] File and iSCSI Services

     File-Services

            [X] File Server

    FS-FileServer

            [X] BranchCache for Network Files

    FS-BranchCache

            [X] DFS Namespaces

    FS-DFS-Namespace

     [X] Web Server (IIS)   

    Web-Server

        [X] Web Server                                                      

    Web-WebServer

            [X] Common HTTP Features                                      

    Web-Common-Http

                [X] Default Document                                     

    Web-Default-Doc

                [X] Directory Browsing                                  

    Web-Dir-Browsing

                [X] HTTP Errors                                          

    Web-Http-Errors

                [X] Static Content                                    

    Web-Static-Content

            [X] Health and Diagnostics                     

    Web-Health

                [X] HTTP Logging                                         

    Web-Http-Logging

                [X] Tracing                                              

    Web-Http-Tracing

            [X] Performance                                              

    Web-Performance

                [X] Static Content Compression                       

    Web-Stat-Compression

            [X] Security                                                     

    Web-Security

                [X] Request Filtering                      

    Web-Filtering                

                [X] Basic Authentication                   

    Web-Basic-Auth               

                [X] Windows Authentication                              

    Web-Windows-Auth

            [X] Application Development                                        

    Web-App-Dev

                [X] .NET Extensibility 4.5                 

    Web-Net-Ext45                

                [X] ASP.NET 4.5                            

    Web-Asp-Net45                

                [X] ISAPI Extensions                                      

    Web-ISAPI-Ext 

                [X] ISAPI Filters                          

    Web-ISAPI-Filter             

                [X] Server Side Includes                                     

    Web-Includes

        [X] Management Tools                                              

    Web-Mgmt-Tools

            [X] IIS Management Console                                   

    Web-Mgmt-Console

        [X] ASP.NET 4.5                                          

    NET-Framework-45-ASPNET

            [X] HTTP Activation                            

    NET-WCF-HTTP-Activation       

    [X] BranchCache                                        

    BranchCache                  

    [X] Group Policy Management                            

     GPMC                         

    [X] Remote Server Administration Tools                                           

    RSAT

        [X] Role Administration Tools                      

    RSAT-Role-Tools               

            [X] File Services Tools                        

    RSAT-File-Services           

                [X] DFS Management Tools                              

    RSAT-DFS-Mgmt-Con 

            [X] Remote Access Management Tools                           

    RSAT-RemoteAccess

                [X] Remote Access module for Windows PowerShell

    RSAT-RemoteAccess-PowerShell  

     [X] Windows Process Activation Service                                            

    WAS

        [X] Process Model                                               

    WAS-Process-Model

        [X] Configuration APIs                              

    WAS-Config-APIs              

    [X] Windows Server Backup                              

    Windows-Server-Backup        

     

     

     

    Sample of configuration file

    Virtual Machine sample file: ICConfig.xml

    <?xml version="1.0" encoding="utf-8"?>

    <DeploymentSettings

      xmlns:xsd="http://www.w3.org/2001/XMLSchema"

      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

      xmlns="http://schemas.microsoft.com/WindowsServer/Essentials/2013/01/ServerDeployment/Virtualization”>

     <InstallationMedia>C:\DeployAsVM\OEMEssentials.vhdx </InstallationMedia>

    <VMBaseDirectory> %SYSTEMROOT%\vms </ VMBaseDirectory>

    <VMProcessorCount>4</ VMProcessorCount>

    < VMMemorySizeMB>4096</ VMMemorySizeMB>

    < VMSystemDiskSizeGB>127</ VMSystemDiskSizeGB>

    < VMDataDiskSizeGB>999</ VMeDataDiskSizeGB>

    <AllowDeployOnHost>true</AllowDeployOnHost>

    </DeploymentSettings>

     

    Note

    All paths can contains environment variables and/or be relative to the %SYSTEMROOT% (i.e., %WINDIR%).

     

    Setting

    Description

    InstallationMedia

    [A2] This configuration on the Hyper-V host specifies the path to the image that will be used for the virtual guest instance of WS2012 R2 Essentials.

    It can be in .iso format or .vhdx format.

     

    AllowDeployOnHost

    AllowDeployOnHost “true” enables WS2012 R2 Essentials to be installed either as a physical installation or as a virtual instance (using itself as a stripped-down Hyper-V host). AllowDeployOnHost “false” blocks the physical install option and forces a virtual deployment.

    VMBaseDirectory

    (Optional) Specify where the VM file is located

    VMProcessorCount

    (Optional) Specify the number of logical processor cores assigned to the VM

    VMMemorySizeMB

    (Optional) Specify the size of memory size allocated to the VM. By default it will use the 80% of available Memory for VM.

    VMSystemDiskSizeGB

    (Optional) Specify the size of system drive. By default it is 127GB.

    VMDataDiskSizeGB

    (Optional) Specify the size of the data drive. By default it will use the available space of the hard disk. Your total size of hard drives shouldn’t not exceed the physical capacity of the disk.

     

    Best Practices

    • Make sure your hardware has virtualization capability turned on.
    • After installation Essentials VM is not activated by default. Please guide your customer to activate the image using the product key you provided.
    • If you ship multi-language image to your customer, please make sure you have same set of languages available for VM Host and VM guest. The language for the guest VM will be the same as the VM Host.
    • If you want to prepare a factory reset DVD for your end user, make sure you include the installation media for VM and the necessary settings in the DVD image. If the image size exceeds to a size of DVD9, consider using multiple DVDs for your image.
    • It’s highly recommended that your use .vhdx instead of .iso for your installation media. This provides your end user with faster deployment.
    • This deployment type is only applicable when you ship Windows Server 2012 R2 Essentials.

    You have now created a customized image in ISO or VHDX format to be used as the virtual instance of Windows Server 2012 R2 Essentials with full Essentials functionality including the Dashboard, client backup, remote access etc.


    Thursday, July 11, 2013 3:19 AM
  • Hello Yunlong,

    Thanks for the reply. That's the information I wanted.

    So this feature of WS2012E R2 as VM will only be configurable by OEM partners such as us?

    I will test this and give feedback on how it went in a few days.

    Best Regards,

    Abby_Doc

    Thursday, July 11, 2013 5:12 AM
  • Correct. This targets same audience as ADK/OPK does, which is indeed part of ADK.

    Let me know how it goes. Feel free to contact me by mikech@microsoft.com.

    Thursday, July 11, 2013 8:03 AM
  • ok, will be in touch if needed once we start testing. Thanks for your help. :)

    Thursday, July 11, 2013 9:30 AM
  • Thank you Yunlong,

    your manual is exactly what I was looking for. Unfortunately, I get error 0xc0000135 when I use DISM to remove the Essentials role. I searched the web for the original document "How to prepare virtualized deployment" with no result. Could you please post the original manual or more information about setup hyper-v with 2012 R2 Essentials?

    BTW: I believe, it's impossible to install a Hyper-V host with 2012 R2 Essentials without adjustment of the iso, because when I installed it by using the RTM iso from TechNet, the assistant to configurate Essentials, which is including domain settings, starts every time after login, even when I added Hyper-V role and removed Essentials role by Powershell.

    And as i posted on another thread, I got no option to join a existing domain but ist needed to migrate 2012 Essentials to 2012 R2 Essentials.

    Tuesday, September 17, 2013 10:02 PM
  • Hi Simon,

    The original documents can be found here.

    The link to Deploy as VM part: http://technet.microsoft.com/en-us/library/dn293253.aspx

    Tuesday, September 17, 2013 10:40 PM
  • Hi Abby_Doc,

    thank you, unfortunately I get the same error as before while preparing the image for the Hyper-V host.

    Wednesday, September 18, 2013 6:11 AM
  • Hi Simon,

    Which OS and ADK Version are you using to prepare the image?

    Wednesday, September 18, 2013 6:31 AM
  • I'm using Windows 8 Enterprise x64 with ADK 8.1 installed.
    • Edited by SimonL1986 Wednesday, September 18, 2013 8:23 AM OS
    Wednesday, September 18, 2013 8:22 AM
  • I had a similar issue while testing the deployment.

    The ADK 8.1 is not compatible with Windows 8 or Windows 2012

    You need to be using Windows 8.1 in conjunction with ADK 8.1

    or better still Windows Server 2012 Essentials R2 and ADK 8.1


    • Edited by Abby_Doc Wednesday, September 18, 2013 8:38 AM
    Wednesday, September 18, 2013 8:38 AM
  • Thank you, I understand. Luckily, 8.1 Enterprise RTM was available on TechNet yesterday.

    I will test it and then we will know more.

    Wednesday, September 18, 2013 8:56 AM
  • Ok that's great.

    Just to let you know that with the help of the Microsoft Engineers in this thread I have been testing and had this working for over 2 months now.

    Sometimes there might be some issues with some of the scripts but I think they are all working with the NEW deployment doc.

    Wednesday, September 18, 2013 9:01 AM
  • Thanks again - it works!

    I used the fresh installation of 2012 R2 Essentials on my new microserver together with ADK 8.1 and I was able to remove the Essentials role from the host image.

    Now I've got the next Problem - I don't know how to fill the ICConfig.xml.

    Wednesday, September 18, 2013 12:46 PM
  • Which part of the ICConfig.xml are you not sure about how to fill?

    Wednesday, September 18, 2013 3:50 PM
  • I don't want to config the "virtual" data partition automatically and I also want to save it on a separate "physical" Partition.
    Wednesday, September 18, 2013 6:35 PM
  • Ok, I got it - setup runs fine but I don't understand why the Essentials configuration manager wants to setup domain on the host system.

    But the biggest Problem is, that I'm not able to join a existing domain to migrate 2012 Essentials to 2012 R2 Essentials.

    Wednesday, September 18, 2013 9:28 PM