Activate Virtual Machines on OEM Server 2012 R2 Standard

As allowed under my license I can run my OEM Server 2012 R2 as a Hyper V Host and run 2 production Server 2012 R2 VMs.
So how do I activate these VMs? What am I missing?
I tried using the OEM key of the server/host. Failed.
I tried using the AVMA key. Failed.
Shouldn't be this hard.
One of the machines I want to activate is a Server Core. I can see posts around the place saying use the OEM and if it fails call Microsoft activation. But I can find none of the options or information how to complete the phone activation via sconfig or
command line options.
Really should not be this hard at all. Someone should be fired and this process fixed.

Hi,
Did you talk about Windows Server 2012r2 with hyper-v role or Hyper-v Server 2012r2? 
Activating a VM is the same as activating a physical machine. When the VM asks to be activated, you would use the same product key as you used to activate your physical host. If this is an OEM licensed server, your OEM should have provided you with the proper
key.
Please refer to:
http://social.technet.microsoft.com/Forums/en-US/7cbd9aab-2c95-4bc1-b0a1-5a24a0945ebf/activate-the-virtual-machine
http://www.petri.com/automatic-virtual-machine-activation-avma-windows-server-2012-r2-hyper-v.htm
Regards.
Vivian Wang

Similar Messages

  • Cannot start virtual machine on Windows Server 2012

    Hello,
    I have a weird problem and have been unable to find a solution to it after two days of searching. I have Windows Server 2012 host on IBM x3500M2 machine. I set up a hyper-v platform (added the role, configured the storage and network) and created two virtual
    machines. Now when I try to start either one of these VMs, using the Hyper-V manager, it throws this error:
    "machine name" could not initialize
    Could not initialize machine remoting system. Error: Element not found. (0x80070490).
    Could not find a usable certificate. Error: Element not found. (0x80070490)
    In the event log there is a similar error with the event IDs: 3040, 12460, 12500.
    I tried clearing up the certificate from vmm/personal folder to recreate it again but to no avail. I found few articles regarding a similar problem on Windows Server 2008R2 but from what I can see this problem mainly occurs with SCVMM...

    Hi,
    Please restart your server or restart VMMS service to check the result.
    In addition, I searched the internet and found that someone with the same issue has solved it by removing a
    certificate from my Trusted Root Certificate Authorities container. The certificate is a self-signed cert generated by Remote Desktop Gateway service.
    Hope it helps.
    Regards,
    Yan Li
    Cataleya Li
    TechNet Community Support

  • Trying to install a setup on a 64 bit machine with Windows server 2012 R2 which writes to registry FAILES

    My msi is a 32 bit setup.
    When I install it on a 32 bit machine with Windows XP it works fine .
    I tried to install it on a 64 bit machine with windows server 2008 and it succeeds
    While running my setup on a 64 bit machine with Windows server 2012 R2 it failes and I get the folloawing message:
    "Registry object reference not set to an instance of an object"
    Then the setup exits and leaves the app partially installed
    I tried searching for known problems over the net, but found nothing
    I will be happy to get some advice
    Thanks
    Liora

    Sounds like you are trying to update a registry object that is not there.
    Is this your own msi, or is it from a third party application?  If third party, check with them to see if they support it on 2012 or if they have a known workaround.
    If it is your own msi, sounds like it is time to debug it.
    .:|:.:|:. tim

  • V2P Virtual Machine to physical Server migration on IBM x3650 M4 and switch from BIOS to UEFI Boot environment

    Hi there,
    just wanted to share my experience with a manual P2V Migration. The VM became to ressource hungry and it was decided to move it off an ESX 5 Cluster to a dedicated physical Machine.
    V2P Virtual Machine to physical Server IBM x3650 M4 and switch from BIOS to UEFI Boot environment
    Task:
    V2P Migrate a VMware virtual machine to a IBM x3650 M4 with a ServeRAID 5110e RAID Controller or any other LSI RAID Controller without 3rd Party tools.
    This should also work with other RAID Controllers or Servers but be sure to pick the right drivers then.
    Extra Task:
    The VM's boot environment/virtual BIOS is BIOS, not UEFI (as per default VMware Setting). The physical Server is running in UEFI mode.
    The Challenge:
    After restore the Server won't boot or get into a BSOD (7B), because the RAID drivers are missing.
    After restore the VM won't boot because the boot environment has changed from BIOS to UEFI
    Preparations:
    An existing physical Server of the same type and with the same RAID controller and same OS would be nice for troubleshooting and checking the registry.
    An existing DHCP server will make networking things easier.
    Connect the new physical server x3650 M4 to power and network
        create a virtual drive that has at least the size of the existing VM plus the size of the full backup (.vhd). Should be about twice the size of the original vmdk.
    Get a USB Flash stick (I used a 8GB modell so no problem with larger sticks)
    Download and extract LSI MegaRAID Driver on that USB media (I used 6.705.05.00-MR_Windows_Driver directly from LSI website)
    Download and extract INTEL Network Adapter Driver on that USB media (I used 12.11.97.0 of e1r62x64.inf from 19.5 driver release from 2014.09.26 directly from LSI website)
    Step by Step:
    if you have an other physical Server of the same type and same Controller and same OS:
    1.    open regedit and export everything related to SCSIAdapter and megasas2 to .reg files or skip this step and use my files below
        some of this (sub)keys may not be accesible - you will then first take ownership and/or modify permissions to read them
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318}
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\VEN_1000&DEV_005B&SUBSYS_04121014&REV_05
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\megasas2
        this one is more complicated:
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase (only relevant are those devices where the service name is megasas2 - export the whole subkey and get the filtering done with tools like notepad++)
        Make a copy of the following files/folders:
        c:\programdata\LSI\
        c:\windows\inf\megasas2.INF
        c:\windows\inf\megasas2.PNF
        c:\windows\system32\drivers\megasas2.SYS
    on the existing VM:
    1.    create a full backup (image) with the built-in Windows Backup Utility and save it in an accessible network location (you will need this one, if anything goes wrong or you want to come back to this point.
        Alternatively you could create a VMware snapshot.
    2.    import the .reg files you created earlier or import my files below.
        Attention: This will make the VM unbootable!
        But it is required to prepare the VM for the new RAID controller when it will be restored on the physical server.
        Do NOT reboot now as this will make the VM unbootable!
    4.    Copy the LSI folder and the megasas2.INF/PNF/SYS files to the appropriate destination folders on the VM.
    3.    again create a full backup (image) with the built-in Windows Backup Utility and save it in an other accessible network location but not where you safed the first backup.
        This will be the "golden" backup if you want, where the RAID controller is prepares. We will rebuild the new machine with this second backup.
    4.    Optional: you could use the Backuputility now to restore the Systemstate of the first backup and reboot or restore the VMware snapshot.
        This will undo the changes we made to the VM.
    on the new physical server:
    1.    boot the physical server from Windows Server 2008 R2 SP1 DVD
    2.    when it is ready to install, press shift+F10 to get command prompt and do not click to install Server 2008
    3.    check driveletter of the USB stick with diskpart list vol (was C: at my Server, so don't wonder about that letter)
    3.    load drivers for ServeRAID SAS controller (this is mandatory to see the volume in diskpart)
        drvload c:\srv_2008_x64\megasas2.inf
    4.    load drivers for INTEL I350 Gigabit NIC's (you will need this to access the backup that is on the network)
        drvload c:\PRO1000\NDIS62\e1r62x64.inf
    5.    wpeinit (will start network. wait ~15 sec to let it start and get IP address)
        check if you have IP connectivity an address with ipconfig, if not, use an other NIC driver and repeat steps 4+5
    6.    create the EFI and BCD
        diskpart
        list disk
        select disk x (where x is the number of the disk to convert)
        clean
        convert gpt
        create partition EFI size=128
        format fs=fat32 quick label=EFI
        assign letter=i or any other free drive letter
        create partition MSR size=128
    6.1    Copy EFI bootloader to EFI partition
        i: (where i is the letter of your EFI partition)
        mkdir EFI\Boot
        mkdir EFI\Microsoft\Boot
        copy x:\Windows\Boot\EFI\bootmgfw.efi i:\EFI\Microsoft\Boot (where x ist the default letter of the current Windows PE environment)
        copy x:\Windows\Boot\EFI\bootmgfw.efi i:\EFI\Boot\bootx64.efi (note that the file will be renamed to bootx64.efi)
    7.    create the new partitions
        diskpart
        create partition primary size=100000 (edit the size to your needs. this will later become the system drive of your server)
        format fs=ntfs quick label=Windows
        assign letter=Y or any other free drive letter
        create partition primary size=990000 (this will temporarily store your backup and we need it for the restore process)
        format fs=ntfs quick label=Backup
        assign letter=B or any other free drive letter
        exit
    8.    map network drive and copy the backup .vhd  to the local disk
        net use L: \\networklocation\where\you\saved\the\backup (enter the credentials when asked)
            copy the .vhd file that contains the OS of your VM to the local Backup Partition B. The relevant vhd file is usually the largest file in that fileset.
            Note that the names are very similarly - be sure to get the correct file!
        copy "L:\WindowsImageBackup\VMNAME\Backup 2015-02-03 123456\00e767c6-xxxx-xxxx-xxxxxxxxxxxx.vhd" B:\
            give it time, this is slow and will take some minutes/hours and you will not see any progress! Look at the disk-LED's to see if anything is still happening
    9.    mount the .vhd and copy it's contents to the new system partition
            Note that you can only mount a locally stored .vhd. You cannot mount a .vhd in a network location.
        diskpart
        select vdisk file=B:\00e767c6-xxxx-xxxx-xxxxxxxxxxxx.vhd
        attach vdisk
        select vol 5 (where 5 is the number of the mounted vdisk)
        assign letter=Z or any other free drive letter
        exit
    10. Restore the files from the image
        z: (where z is the letter of your mounted .vhd)
        xcopy * Y:\ /e /c /h /k /o /b /q /y (where Y: is the letter of your new partition with the label "Windows")
            several "Access denied" messages appear, ignore them. Those are SystemVolumeInformation folders.
    11.    Create Boot Configuration Data (BCD)
        bootrec /RebuildBcd
            this will try to repair the missing BCD on the second of the two small partitions we created earlier in and should normally work, otherwise you'll have to create BCD manually (search google for that procedure)
            Note that it may find more than one Windows installation and ask which sould be added to the boot list. Be sure to select only the one that is in the correct Volume (Y:\)
        that's it - exit the DOS command box and close the "Install Windows" Window, after a prompt it will reboot.
        Select "Start Windows Normally", if Windows Error Recovery appears.    
    12. Preparing Windows
        When Windows boots for the first time, DO NOT reboot if you are asked, it won't come back at this stage!
        Install Intel chipset drivers for the Server (I used "intc_dd_inteldp_9.4.0.1026_windows_32-64.exe" from IBM website)
        Open Device Manager, uninstall the "RAID-Controller" with the exclamation mark. You cannot install the correct driver for this Device at this point, it will bring you the error: "Cannot create a stable subkey under a volatile
    parent key"
        Once again, DO NOT reboot!
        In Device Manager select Action>Add Legacy Hardware
        click Next
        select Hardware manually
        select Storage Controller as Type
        LSI should be listed, select "LSI MegaRAID SAS 9281-8E"
        click Next, ignore the error "Code 10" Message.
        Click Done.
        Rightclick the LSI MegaRAID SAS 9281-8E device with the exclamation mark in Device Manager
        select Update driver
        select Browse my computer for driver software
        select let me pick from a list of device drivers on my computer
        select "Have Disk"
        browse to the folder where the extracted RAID driver 6.705.05.00-MR_Windows_Driver is located (e.g. USB Flash stick E:\6.705.05.00-MR_Windows_Driver\srv_2008_x64)
        then unselect "Show Compatible Hardware"
        on the right side, scroll up and select "IBM ServeRAID M5110e SAS/SSATA Controller"
        ignore the Update Driver Warning and click Yes
        click Next, ignore the error "Code 10" Message.
        ignore the exclamation mark on "IBM ServeRAID M5110e SAS/SSATA Controller" in Device Manager but be sure that there is only this controller and no other RAID-Controller or LSI SAS Controller listed under "Other Devices"
    or "Storage Controllers"
        NOW you are safe to reboot
        After reboot you will find two "IBM ServeRAID M5110e SAS/SSATA Controller" in Device Manager
        Rightclick and uninstall the one with the exclamation mark. Do not tick the checkbox to remove the driver as well!
    You're done!! (hopefully)

    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase]
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C31115D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C38015D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C41115D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C48015D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C51115D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C58015D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C61115D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C68015D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C71115D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C78015D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C81115D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C88015D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C91115D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C98015D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_D20219E5]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_D20319E5]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0071&SUBSYS_00721137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00011BD4]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00721137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00731137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_008F1137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B01137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B11137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B61137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B71137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00C21137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00C31137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_03B11014]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_040015D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_040D1014]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_10541000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_11771734]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_14581002]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_1F201462]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_30351054]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_350C8086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_350D8086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_822910F1]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_843B1043]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_84711043]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92211000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92401000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92408086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92411000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92418086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92421000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92431000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92441000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92A01000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92A11000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0078&SUBSYS_92501000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0078&SUBSYS_92511000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0078&SUBSYS_92701000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_00011BAA]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_00021BD4]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_00791137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_02001AE3]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_03B21014]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_03B31014]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_03C71014]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_070015D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_11761734]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_11B31734]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_30361054]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_350B8086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_84731043]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_84801043]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_8985152D]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92551000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92561000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92568086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92601000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92608086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92611000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92618086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92621000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92631000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92641000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92648086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92671000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92678086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92681000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92688086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92751000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92758086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92761000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92768086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92771000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92801000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92808086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92811000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92821000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92828086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92841000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92881000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92891000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92901000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92908086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_D20819E5]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_D20919E5]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0409&SUBSYS_10091000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10011000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10018086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10021000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10031000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10038086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10041000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10081000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10088086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_100C1000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_100D1000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10811734]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10a31734]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_20041000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_20051000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_30161054]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_34908086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35008086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35018086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35048086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35078086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_82871033]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0413&SUBSYS_10051000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"

  • What licence do I need to install server 2012 R2 standard on a single i-7 cpu machine?

    What licence do I need to install server 2012 R2 standard on a single i-7 cpu (multi-core)  machine?
    Is a 2 processors licence OK?
    Thanks.

    Yes, you are all covered.

  • VMM is unable to perform this operation without a connection to a Virtual Machine Manager management server.

    Hi,
    I'm running SCOM and VMM integration. For the most part everything is working. However I get lots of alerts generated in regards to my scvmm server.
    This is a the guide I used:
    https://technet.microsoft.com/en-ca/library/hh882396.aspx
    SCOM + VMM 2012r2 Ur4
    One of the Errors(which appears to be root issue):
    The PowerShell script failed with below
    exception
    System.Management.Automation.CmdletInvocationException: VMM is
    unable to perform this operation without a connection to a Virtual Machine
    Manager management server. (Error ID: 1615)
    Use the Get-VMMServer cmdlet
    or the -VMMServer parameter to connect to a Virtual Machine Manager management
    server. For more information, type at the command prompt: Get-Help Get-VMMServer
    -detailed.At line:109 char:12
    + $vmm = Get-SCVMMServer $VMMServer -Credential
    $cred;
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    at
    System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object
    input, Hashtable errorResults, Boolean enumerate)
    at
    System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean
    ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[]
    pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext
    funcContext)
    at
    System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame
    frame)
    at
    System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame
    frame)
    at
    System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame
    frame)
    Script Name:
    GetStorageSubsystemPerfScript
    One or more workflows were affected by
    this.
    Workflow name:
    Microsoft.SystemCenter.Advisor.StorageSubsystem.Performance.PerfCollection
    Instance
    name: SCVMM01.Domain.com
    Instance ID:
    {B5175EAC-D64D-2553-D567-F19B5C864BBD}
    Management group: OMGRP82

    Can you connect from powershell? get-vmmserver <VMMServerComputerName>
    If this doesn't work it's likely that your VMM server doesn't work. Check Application log to see if there are errors related to VMM service.
    You can also collect traces as described
    here and attach them to this thread.
    Are you using a domain administrator account?  (this is the default allowed after SCVMM is installed - until other users are added).
    also try restarting VMM server or VMM services once.
    this occur if the SQL database owner is indicated as NULL.  Try adding the SQL SA account as db owner.
    refer this once -
    https://social.technet.microsoft.com/Forums/en-US/a4199cb2-ccbf-4bb0-96c1-7a640143f81b/error-id-1615-vmm-is-unable-to-perform-this-operation?forum=virtualmachingmgrhyperv
    Thanks, S K Agrawal

  • Using NIC Teaming and a virtual switch for Windows Server 2012 host networking and Hyper-V.

    Using NIC Teaming and a virtual switch for Windows Server 2012 host networking!
    http://www.youtube.com/watch?v=8mOuoIWzmdE
    Hi thanks for reading. Now I may well have my terminology incorrect here so I will try to explain  as best I can and apologies from the start.
    It’s a bit of both Hyper-v and Server 2012R2. 
    I am setting up a lab with Server 2012 R2. I have several physical network cards that I have teamed called “HostSwitchTeam” from those I have made several Virtual Network Adaptors such as below
    examples.
    New-VMSwitch "MgmtSwitch" -MinimumBandwidthMode weight -NetAdaptername "HostSwitchTeam" -AllowManagement $false
    Add-VMNetworkAdapter -ManagementOS -Name "Vswitch" -SwitchName "MgmtSwitch"
    Add-VMNetworkAdapter -ManagementOS -Name "Cluster" -SwitchName "MgmtSwitch"
    When I install Hyper-V and it comes to adding a virtual switch during installation it only shows the individual physical network cards and the
    HostSwitchTeam for selection.  When installed it shows the Microsoft Network Multiplexor Driver as the only option. 
    Is this correct or how does one use the Vswitch made above and incorporate into the Hyper-V so a weight can be put against it.
    Still trying to get my head around Vswitches,VMNetworkadapters etc so somewhat confused as to the way forward at this time so I may have missed the plot altogether!
    Any help would be much appreciated.
    Paul
    Paul Edwards

    Hi P.J.E,
    >>I have teams so a bit confused as to the adapter bindings and if the teams need to be added or just the vEthernet Nics?.
    Nic 1,2 
    HostVMSwitchTeam
    Nic 3,4,5
             HostMgmtSwitchTeam
    >>The adapter Binding settings are:
    HostMgmtSwitchTeam
    V-Curric
    Nic 3
    Nic 4
    Nic 5
    V-Livemigration
    HostVMSwitch
    Nic 1
    Nic 2
    V-iSCSI
    V-HeartBeat
    Based on my understanding of the description , "HostMgmtSwitchTeam and
    HostVMSwitch " are teamed NIC .
    You can think of them as two physical NICs (do not use NIC 1,2,3,4,5 any more , there are just two NICs "HostMgmtSwitchTeam and
    HostVMSwitch").
    V-Curric,
    V-Livemigration , V-iSCSI ,
    V-HeartBeat are just VNICs of host  (you can change their name then check if the virtual switch name will be changed )
    Best Regards
    Elton Ji
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Server 2012 RS Standard Planning

    It's been a while since I've planned a new server strategy.  There are so many options and looking for some guidance on best practices.  (no Laughing please) Currently we have 1win2000 Global catalog, active directory server, 1 Server 2003
    file/ accounting host server and 1 server 2008 r2 hyper-v enabled running 2 vms for remote offsite users.  We have about 34 users over 30 client desktops (win7-win8)  All server systems are running solid, but would like to
    start consolidating.
    Moving forward, I'm not interested in trying to figure out how to get active directory from my win200 server, over to a new server 2012.  I'm ok with starting from scratch.
    Required Roles:
    File server
    SQL Server for SAGE Accpac database (about 20gb accounting databse)
    3-6 Remote offsite users (RDS? or Hyper-v?)
    What I'd like to buy is 1 physical Lenovo server with 2 Xeon 6core CPU's, 24gb ram, 2tb storage.
    Is it wrong for me to want the above mentioned roles to run on 1 server?
    Should I do it on 1 server with server vms in hyper v?
    If I could, I'd install server 2012R2 Standard as a New Domain global cat/active directory server.
    I'd then install file server role and SQL server for the accounting DBs.  My thoughts for the 3-6  offsite remote users would be to run virtualized win7 machines.  Does this setup sound feasible in the way I've outlined it?  I usually
    read people objecting to having all these roles on 1 server instance, but we are pretty small (less than 40 users) and feel 1 server could easily handle this load.
    Robert

    Hi
     Further clarify:-)
    If you plan to buy 1 physcial server you can create this topology;
    - Install Server 2012 r2 Standard on your physcial envorenment
    - Also install hyper-v role (Windows Server 2012 r2 standard Support vm with licenced)
    - Install first vm and configure as an DC.
    - Install second Vm and install SQL server on this.
    As you say you have 3 Physcial server thats great...
    - Install Windows Server 2012 r2 on each 3 physcial server
    - Also install Hyper-v role on this 3 server 2012 r2 standard (also you can create totally 6 Vm wth licence on server 2012 standard with hyper-v)
    - Install PDC on a vm,then install another vm and add as an Additional DOmain Controller (for Redundacy AD DS,DNS)
    - Install 2 vm server and configure a SQL cluster
    - install file server another vm
    - install RDS server on another vm
    Is this appropriate?

  • What will I do with the SQL Server (2012/2014) (Standard/Enterprise) Licenses?

    What will I do with the SQL Server (2012/2014) (Standard/Enterprise) Licenses?
    Are these the same as software product keys, or just some pieces of paper the company needs to have on hand?
    In which case, when we install SQL Server 2014, (and when looked for videos) - there is only 1 product key value to be put in, is there some other screen in the setup to input the License bought ( in our case will be Core licenses).
    So in addition to the Core Licenses do will a Product key be needed? Would product key from an msdn work, as it is the licenses that we will buy to indicate that we bought to run the software on server X?
    Thanks for any indications.

    1. What will I do with the SQL Server (2012/2014) (Standard/Enterprise) Licenses?
    Are these the same as software product keys, or just some pieces of paper the company needs to have on hand?
    2. In which case, when we install SQL Server 2014, (and when looked for videos) - there is only 1 product key value to be put in, is there some other screen in the setup to input the License bought ( in our case will be Core licenses).
    3. So in addition to the Core Licenses do will a Product key be needed? Would product key from an msdn work, as it is the licenses that we will buy to indicate that we bought to run the software on server X?
    Thanks for any indications.
    I will answer your question point wise
    1. Keeping license key is good idea it helps you during audit and you have proof that you are using a valid Microsoft License. Plus in scenario of disaster where whole box gets damanged you might need to install SQL Server again in that case during
    reinstallation on setup page where you need to enter key you might need need it. If you are missing your paper then you are in trouble.
    2. Only on product key page license key is required and it is not required anywhere else during installation. Unless you enter valid product key installation will not proceed further.
    3 License makes you a valid owner of Microsoft product with restrictions on how much hardware resource you can use how much max connections you can make etc. Key lets you install it on Windows machine making sure that you are using valid Microsoft product.
    This was just a general idea please speak to your licensing specialist for more details. This is technical forum and we generally ask user to speak to licensing expert for such queries.
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
    My TechNet Wiki Articles

  • Windows Server Essentials error occurred while configuring on Windows Server 2012 R2 Standard

     am attempting to install the Windows Server Essentials on a new domain controller in a new domain and forest.   I go to add roles and features and select essentials.  The config wizard says it is Updating and Preparing the Server and
    That is all the information that you need to provide. Your server is being prepared for use and may restart more than once. This may take up to 30 minutes.
    It goes to 3% and the encounters an error saying An error occurred while configuring Windows Server Essentials. Please try again.  I don't seem to find anything in the log to indicate why it fails.

    Hi boe_d,
    Based on your description, did you mean that this error was occurred in process of installing the Windows Server
    Essentials Experience Role on Windows Server 2012 R2 Standard? If I misunderstand, please don’t hesitate to let me know.
    If it is, have you re-tried the role installation? Please check if still go to 3% and then get the same error
    message.
    In addition, please add
    ServerAdmin$ account to the Logon as a service Group Policy, and then monitor the result. For more details, please refer to the following article.
    You may be unable to run post-deployment configuration wizard after you install the Windows Server Essentials
    Experience role
    http://blogs.technet.com/b/sbs/archive/2013/12/04/you-may-be-unable-to-run-post-deployment-configuration-wizard-after-you-install-the-windows-server-essentials-experience-role.aspx
    If this issue still exists, please navigate to: %windir%\Logs\CBS folder and check the CBS log file if you
    can find any error that depend on the Essentials Experience Role setup time.
    Hope this helps.
    Best regards,
    Justin Gu

  • Attempted to perform an unauthorized operation error while installing SQL Server 2008 R2 Enterprise edition on Windows Server 2012 R2 standard VM server

    I've been trying fresh installation of SQL Server 2008 R2 enterprise on Windows Server 2012 R2 standard VM server several times for two weeks, but always get the error "Attempted to perform an unauthorized operation". At first, I attempted
    to install all features, but failed several times. So I decided to try install just Database Engine service, and still fail at the SqlBrowserConfigAction_Install_ConfigNonRC_Cpu32, with the error "Attempted to perform an unauthorized operation".
    I remote login to server with my admin domain account. This account is in server local Administrators group. I
    1. Right-click on setup.exe file | properties | Compatibility tab | select compatibility to Windows 8.Then click OK.
    2. Right-click on setup.exe file | Run as Administrator, to start the Installation Center.
    I have the document of my installation steps and zip file of the installation logs, if you need to take a look.
    Appreciate for any help!
    ntth

    Hi ntth,
    "Attempted to perform an unauthorized operation"
    The above error is always related to the Windows account SID mapping. I recommend you login into Windows using another Windows account which has administrative privileges and run SQL Server setup using that Windows account.
    Besides, please note that we need to apply SQL Server 2008 R2 Service Pack 2 or a later update when installing SQL Server Windows Server 2012 R2. For more information, please review this
    KB article.
    Thanks,
    Lydia Zhang
    If you have any feedback on our support, please click
    here.
    Lydia Zhang
    TechNet Community Support

  • Cannot install Windows Server 2012 R2 Standard on a Supermicro X9SRA

    I have bought the Windows Server 2012 R2 Standard OEI and it will not install on the brand new Supermicro X9SRA motherboard. I have tried to install the previous version (Windows Server 2012 Standard) and it installs fine with no problems. 
    I need to install R2 in order to use the Essentials role. I have also tried to install the trial version of 2012 R2. which I downloaded from the microsoft website and got the same result. The installation goes into a loop. The circle bellow the Windows logo
    goes on forever and nothing happens. I can not even get to choose the language. The loop happens as the disk starts.
    Can anyone please help?

    Does SuperMicro support the installation of Windows Server onto that MB?  I do not find any reference to X9SRA at
    www.windowsservercatalog.com, which is where hardware vendor post the systems on which they will support the various versions of the Windows Server operating system.  I see lots of SuperMicro solutions,
    but none of them appear to list the X9SRA MB.  You need to contact SuperMicro to determine if they support it.
    . : | : . : | : . tim

  • Migrating Small Business Server 2008 to Server 2012 R2 Standard

    Hi All,
    We are going to migrate SBS 2008 to Server 2012 R2 Standard for one of our customer.
    We cannot find a  proper guide to do the migration. Any idea for this process.
    We already migrated email to Office 365. We are going to migrate Active Directory and Shared data to new Server 2012 R2 Standard.
    Thanks,
    MKH

    Hi,
    Thanks for your posting.
    There is a similar thread has been discussed:
    Migrating from SBS 2008 to Windows Server 2012 R2 (NOT Essentials and with NO Exchange)
    http://social.technet.microsoft.com/Forums/en-US/1276d2d3-a8f2-4786-82f3-4308a2affb11/migrating-from-sbs-2008-to-windows-server-2012-r2-not-essentials-and-with-no-exchange?forum=smallbusinessserver
    Regards.
    Vivian Wang

  • [Forum FAQ] How to install and configure Windows Server Essentials Experience role on Windows Server 2012 R2 Standard via PowerShell locally and remotely

    As we all know,
    the Windows Server Essentials Experience role is available in Windows Server 2012 R2 Standard and Windows Server 2012 R2 Datacenter. We can add the Windows Server
    Essentials Experience role in Server Manager or via Windows PowerShell.
    In this article, we introduce the steps to install and configure Windows
    Server Essentials Experience role on Windows Server 2012 R2 Standard via PowerShell locally and remotely. For better analyze, we divide this article into two parts.
    Before installing the Windows Server Essentials Experience Role, please use
    Get-WindowsFeature
    PowerShell cmdlet to ensure the Windows Server Essentials Experience (ServerEssentialsRole) is available. (Figure 1)
    Figure 1.
    Part 1: Install Windows Server Essentials Experience role locally
    Add Windows Server Essentials Experience role
    Run Windows PowerShell as administrator, then type
    Add-WindowsFeature ServerEssentialsRole cmdlet to install Windows Server Essentials Experience role. (Figure 2)
    Figure 2.
    Note: It is necessary to configure Windows Server Essentials Experience (Post-deployment Configuration). Otherwise, you will encounter following issue when opening Dashboard.
    (Figure 3)
    Figure 3.
      2. Configure Windows Server Essentials Experience role
    (1)  In an existing domain environment
    Firstly, please join the Windows Server 2012 R2 Standard computer to the existing domain through the path:
    Control Panel\System\Change Settings\”Change…”\Member of. (Figure 4)
    Figure 4.
    After that, please install Windows Server Essentials Experience role as original description. After installation completed, please use the following command to configure Windows
    Server Essentials:
    Start-WssConfigurationService –Credential <Your Credential>
    Note: The type of
    Your Credential should be as: Domain-Name\Domain-User-Account.
    You must be a member of the Enterprise Admin group and Domain Admin group in Active Directory when using the command above to configure Windows Server Essentials. (Figure 5)
    Figure 5.
    Next, you can type the password for the domain account. (Figure 6)
    Figure 6.
    After setting the credential, please type “Y” to continue to configure Windows Server Essentials. (Figure 7)
    Figure 7.
    By the way, you can use
    Get-WssConfigurationStatus
    PowerShell cmdlet to
    get the status of the configuration of Windows Server Essentials. Specify the
    ShowProgress parameter to view a progress indicator. (Figure 8)
    Figure 8.
    (2) In a non-domain environment
    Open PowerShell (Run as Administrator) on the Windows Server 2012 R2 Standard and type following PowerShell cmdlets: (Figure 9)
    Start-WssConfigurationService -CompanyName "xxx" -DNSName "xxx" -NetBiosName "xxx" -ComputerName "xxx” –NewAdminCredential $cred
    Figure 9.
    After you type the commands above and click Enter, you can create a new administrator credential. (Figure 10)
    After creating the new administrator credential, please type “Y” to continue to configure Windows Server Essentials. (Figure 11)
    After a reboot, all the configurations will be completed and you can open the Windows Server Essentials Dashboard without any errors. (Figure 12)
    Figure 12.
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    Part 2: Install and configure Windows Server Essentials Experience role remotely
    In an existing domain environment
    In an existing domain environment, please use following command to provide credential and then add Server Essentials Role: (Figure 13)
    Add-WindowsFeature -Name ServerEssentialsRole
    -ComputerName xxx -Credential DomainName\DomainAccount
    Figure 13.
    After you enter the credential, it will start install Windows Server Essentials role on your computer. (Figure 14)
    Figure 14.
    After the installation completes, it will return the result as below:
    Figure 15.
    Next, please use the
    Enter-PSSession
    cmdlet and provide the correct credential to start an interactive session with a remote computer. You can use the commands below:
    Enter-PSSession –ComputerName
    xxx –Credential DomainName\DomainAccount (Figure 16)
    Figure 16.
    Then, please configure Server Essentials Role via
    Add-WssConfigurationService cmdlet and it also needs to provide correct credential. (Figure 17)
    Figure 17.
    After your credential is accepted, it will update and prepare your server. (Figure 18)
    Figure 18.
    After that, please type “Y” to continue to configure Windows Server Essentials. (Figure 19)
    Figure 19.
    2. In a non-domain environment
    In my test environment, I set up two computers running Windows Server 2012 R2 Standard and use Server1 as a target computer. The IP addresses for the two computers are as
    below:
    Sevrer1: 192.168.1.54
    Server2: 192.168.1.53
    Run
    Enable-PSRemoting –Force on Server1. (Figure 20)
    Figure 20.
    Since there is no existing domain, it is necessary to add the target computer (Server1) to a TrustedHosts list (maintained by WinRM) on Server 2. We can use following command
    to
    add the TrustedHosts entry:
    Set-Item WSMan:\localhost\Client\TrustedHosts IP-Address
    (Figure 21)
    Figure 21.
    Next, we can use
    Enter-PSSession
    cmdlet and provide the correct credential to start an interactive session with the remote computer. (Figure 22)
    Figure 22.
    After that, you can install Windows Server Essentials Experience Role remotely via Add-WindowsFeature ServerEssentialsRole cmdlet. (Figure 23)
    Figure 23.
    From figure 24, we can see that the installation is completed.
    Figure 24.
    Then you can use
    Start-WssConfigurationService cmdlet to configure Essentials Role and follow the steps in the first part (configure Windows Server Essentials Experience in a non-domain environment) as the steps would be the same.
    The figure below shows the status of Windows Server Essentials.
    Figure
    25.
    Finally, we have successfully configured Windows Server Essentials on Server1. (Figure 26)
    Figure 26.
    More information:
    [Forum
    FAQ] Introduce Windows Powershell Remoting
    Windows Server Essentials Setup Cmdlets
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

  • Can't upgrade Windows Server 2008 R2 Enterprise to Windows Server 2012 R2 Standard

    Even though the "Windows Server Installation and Upgrade" TechNet article (DN627667) claims that I can upgrade Windows Server 2008 R2 SP1 to Windows Server 2012 R2 Standard, it seems I can't. I get an error message saying "Windows 2008
    R2 Enterprise cannot be upgraded to Windows Server 2012 R2 Standard (Server Core Installation). You can choose to install a new copy of Windows..." What might be causing this issue? Thanks for any input! :)

    Hi,
    Firstly, for retail versions, Windows Server 2008 R2 Enterprise with SP1 can be upgraded to Windows Server 2012 R2 Standard/Datacenter.
    I assume you are running Windows Server 2008 R2 retail version, right?
    In addition, it seems that in earlier version than Windows Server 2012,
    once you install the server in Core or with GUI mode, you could not switch to the other. The only option was to rebuild the server from scratch.
    Did you install Windows Server 2008 R2 in GUI? If yes, I recommend you to upgrade it to Windows Server 2012 R2 in GUI
    mode to see if the issue persists. If it succeed and you want to run in server core, you can just remove the graphical shell and convert your Windows Server 2012 R2 to Server Core.
    Best regards,
    Susie
    Thanks for replying Susie. The 2008 R2 software is the one provided by Microsoft for Action Pack subscribers, so I'm assuming it's not retail. That's another thing, I think I should be installing the GUI as my 2008 has a GUI, not just the server core. For some
    reason I missed that and clicked on the server core only install!

Maybe you are looking for

  • Free disk space

    When I select my HDD in finder and select Get Info it reports that I have 150GB of free disk space, however when I run disk utility it reports that there is only 55GB of free disk space.  What is going on?  Where is that 95GB discrepancy being used? 

  • Accrual in Incentive and commission management

    Hi, We have a scenario where we need to pay certain royalty to our customer based on sales generated from using their premises... now we are exploring two options...rebate functionality in SD and incentive and commission ..my question is with rebate

  • Importing images from ipod into iPhoto

    I installed the iPhoto 9.2 update as part of the OSX10.7.2 and am now when I try import my pictures that are stored on my iPod Touch only my Mac shows up. The iPod used to show so I could import the images stored on it, but now that option doesn't ex

  • Transporting message(T100) in all languages

    Hi All... I created one message in already existing message class, for example message no: 390. I further translated message in German and French using translation function in message class only. Note: Original language of the message class is EN onl

  • Unix command to turn OFF Software Update

    I've browsed through the networksetup -help and the systemsetup -help files and can't find anything that would allow me to send a unix command that would turn automatic software update off? Anyone got any thoughts?