Moving Physical server to Virtual, what to check?

What does this server do or its function, that was kinda left out...?- Is it just a file server- SQL Server- Print ServerOnce its converted over and functioning live and all NIC settings are identical to your current phys. you shouldnt have to do anything more than shut down the current phys. server and then decom. after a couple weeks of knowing the virtual is working solid!*** Have it boot up the first time with no NIC at all present, so it doesnt try to come online with the settings from your phys. server in production or you may have a ip conflict or could ingest a new setting into your dns record ( been there done that )Its always interesting when doing this, cause you find out shares you didnt know existed or services running certain functions you had no idea about exist doing something... or something that is no longer needed...

Additionally with the NIC, I would copy the original MAC address and use that as a manually entered MAC address for the new virtual machine's primary NIC. Less chance of things like license servers or hardware-locked software licensing breaking in the move that way. Keep the old physical machine around for a few weeks to make sure everything is stable with the new virtualized server.
Eventually though, you'll probably want to migrate your data and services to new, freshly configured VMs. One of the downsides with any P2V move is you're also carrying along an old version of your OS with it's old data/registry, some of who's settings were originally for the physical hardware. Migration to a "natively installed on virtual hardware" server brings benefits.
If your server you're migrating has multiple roles, you may want to divide those...

Similar Messages

Moving Physical Cluster into Virtual Cluster

Hello All...........I have a Physical SQL Cluster 1 cluster1.domain.com (Node A and
Node B) using SAN A. Physical SQL Cluster contains
three-3 instances.
I have built a Hyper-V Failover Cluster and upon it I have also built a Guest/Virtual SQL Cluster 2
cluster2.domain.com (Node A and Node B) using SAN B.
Now, I want to move the instance/databases from Physical SQL Cluster 1 cluster1.domain.com to Guest/Virtual SQL Cluster 2 cluster2.domain.com. Is this supported?
Or do I have to add the Virtual Nodes (NodeC and
NodeD) to cluster1.domain.com and then failover the
instances/database to new virtual nodes and then remove the Physical Nodes (NodeA and
NodeB).
Also, confused as to how would I manage the Storage as old Physical SQL Cluster
cluster1.domain.com uses SAN A and I have new Virtual SQL Cluster
cluster2.domain.com on SAN B. Would I be requiring to change the instances/databases location as well?
Any help on this would be appreciated.

Hello,
There is a good bit of different things going on here so I'll try and make it short.
Normally, it wouldn't be a problem to add in new nodes (virtual) to the current physical, install SQL Server, and eventually evict the physical nodes in order to migrate. However, you're using a different SAN for the storage. You could *still* do this, but
you'd need to have SAN replication on the backend between the two and set it up very much like a 2008/R2 geo-cluster.
The *easier* way, depending on clients, would be to either log-ship or mirror the databases to the new instances. When you have time to cutover, fail the mirrors to the new cluster and then remove mirroring. The clients would need to either be aliased or
re-pointed. It could be done less cleanly by using a cname change for the old to the new but I'd stay away from that.
-Sean
The views, opinions, and posts do not reflect those of my company and are solely my own. No warranty, service, or results are expressed or implied.

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"

Physical Server Clustered Migration to Virtual Machine

Dear All,
We got an request from SQL server running on physical server migrate to virtual machine.
Please advice me the procedure and checklist for this migration request.
Thanks.

Hi mailatdinesh,
If you want to run SQL Server in a virtual machine (VM), here are some of the essential tips for virtualizing SQL Server.
1. To support bare metal virtualization platforms, you need to make sure that the host uses a 64-bit x64 processor; In addition, for a resource-intensive workload like SQL Server, it's vital that the host processor supports Second Level Address Translation.
2. SQL Server can automatically take advantage of multiple CPUs if they're present. If you're migrating from a physical SQL Server implementation to a virtualized SQL Server implementation, you can use the number of CPUs in the physical implementation as
a guide for the number of virtual CPUs that you'll configure in the SQL Server VM.
3. In order for SQL Server to take advantage of dynamic memory, I recommend you to use the Enterprise edition of SQL Server 2008 or later or using the Datacenter edition of SQL Server 2008 R2 or SQL Server 2008.
For more information , see:
http://sqlmag.com/sql-server/sql-server-virtualization-tips
When you migrate one instance from one server to another, as other post, you can use backup and restore, the sp_detach_db and sp_attach_db stored procedures, or
the Import and Export Data Wizard to copy objects and data between SQL Server databases, you also need to transfer logins and passwords between instances of SQL Server, move jobs, alerts and operators. For more information, you can refer to the following
article,
http://support.microsoft.com/kb/314546
There is also similar issue about moving SQL Server to VM, you can refer to the following post.
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/43085f0f-4526-4994-be95-530aecb5dd7c/moving-sql-server-to-vm
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Convert Physical DPM Management server to Virtual

Hi,
I am looking to convert my existing DPM 2012 R2 physical management server to a virtual server.
The current setup is a physical server with locally attached storage and a secondary DPM server in another site (which is already virtual). Both DPM servers were recently upgraded to DPM 2012 R2 and are running Windows 2012.
I would like to use the same hardware but run DPM as a virtual server and attach the physical disks in Hyper-v as pass-through disk. I don't have enough hardware to do a side by side migration (which would be much easier)
My plan is as follows.
backup DPM database
rebuild physical DPM server as hyper-v server
create new DPM virtual server with same name, ip etc.
install dpm and restore db from backup
attach old DPM physical storage drives to virtual DPM server
I am fairly happy at doing the rebuild and database restore as I have done this before, but I don't know if I can attach the existing DPM drives from the storage pool and retain the data.
I have a secondary server so would not lose the backup data, but it would be a lot easier if i could keep the data on the storage pool
Does anyone know if this will work or have any other suggestions?
thanks
sg

Hi SG,
Your plan will work. You will be able to use the existing drives as long as you bring them into the VM, restore the DPM DB and run
DpmSync. DPMSync will synchronize the DPM database with the replicas in the storage pool. Old link but still applies:
http://technet.microsoft.com/en-us/library/bb808877.aspx
Another thought...why not do a P2V on the DPM server vs. re-install? The only thing you will need to do/could run into issues with is bringing the disks into DPM once it is virtual.
My Blog | www.buchatech.com | www.systemcenterportal.com
If you found this post helpful, please give it a "Helpful" vote. If it answered your question, remember to mark it as an "Answer". This posting is provided "AS IS" with no warranties and confers no rights! Always test ANY suggestion
in a test environment before implementing!

CCX 8.5 HA virtual+physical server over WAN

Hello for everyone.
There is such task to deploy CCX 8.5 HA cluster - make one node on virtual maschine and second node on the physical server over WAN (wow! :).
So there some question. Anybody already does this deployment model? Will there any trouble in admistration and working in such way?
Will this configuration supported by Cisco?
Tried to find it out on cisco.com and google.com, but no success. So i think, if Cisco supports deployment on hardware, and on virtual so there no problem. But by hardware+virtual, there's a question.
So, any help and thoughts on this will be kindly appreciated!

Yes it's supported as long as they are equivelent hardware. In other words you can't use the 300 OVA on one side and an MCS-7825 on the other. You would need to use a MCS-7845. Personally I wouldn't recommend this. At some point MCS hardware will fall off the compatibility matrix forcing the customer to move to UCS at that time. CCX is rather finicy when it comes to backup/restore of a node in the HA cluster. That's a task I would avoid if you can.

What is Informatica OEM Powercenter ETL Server for Physical Server

Hi expert
What is Informatica OEM Powercenter ETL Server for Physical Server. And For which OEM is stands for.
Thanks in advance
Regards
Frnds

It looks like it is the name Oracle has given to the Informatica Powercenter product delivered with OBIA 7.9.5:
http://www.oracle.com/technology/software/products/ias/htdocs/101320bi.html
OEM should stand for the Original Equipment Manufacture distribution model Oracle is employing to bundle the Informatica developed product.

OES - moving Physical installtion to Virtusl possible?

I'm think of VMWare EXSI
is it possible to move a Physical installtion of OES to Virtual ?
I've done this for Windows using Vmware converter but can't find options for
Linux / OES

Originally Posted by Brian
I get a message saying that conversion of Live computers with GPT disks are
NOT supported!
is that because of NSS?
"kjhurni" <[email protected]> wrote in message
news:[email protected]..
>
> Brian;2218232 Wrote:
>> I'm think of VMWare EXSI
>>
>> is it possible to move a Physical installtion of OES to Virtual ?
>>
>> I've done this for Windows using Vmware converter but can't find
>> options for
>> Linux / OES
>
> You can sorta-kinda do it for SLES. To be honest, you MAY find it
> "easier" to install OES11 in the VM and do an ID transfer from the
> physical machine. At least that's what I'd do.
>
>
> --
> The opinions expressed are my own.
> Check out my OES2 Guides:
> Installing OES2 SP2:
> Important Notice
> Upgrading to OES2 with ID Transfer:
> Important Notice
> GroupWise Migration with OES2 ID Transfer:
> Important Notice
> ------------------------------------------------------------------------
> kjhurni's Profile: View Profile: kjhurni - Novell Forums
> View this thread: OES - moving Physical installtion to Virtusl possible?
>
The one time I've done any conversion with any OES/SLES, I've had to power down the VM and do the conversion. I don't think Vmware supports live P2V with Linux like they do MS Windows.
But that was a while ago with the "free" Vsphere 4.x, not an actual ESXi with Vcenter or anything.

Exchange server as VM vs Physical Server

Hello All,
which one will be better to implement. Exchange server as a VM or as a physical server for the users below 500 and 3 mail boxes

My organization recently went through a big push to virtualize everything. Our mailbox servers each support around 5,000 mailboxes (DAG members) though our concurrency is only about 50%.
We found a LOT of CPU contention on the Hub Transport and CAS servers until we allocated a lot of dedicated CPUs to each machine and until we provided more RAM to the mailbox servers. We were originally were 48GB of RAM, but pushed that up to 64GB.
All of our sizing was calculated using the Microsoft sizing guidance and we were quite liberal in defining expected I/O and loads by our users. We wanted room to grow.
This ill-fated exercise in to visualization proved to management what I had been saying for years. Not everything virtualizes well. (I resisted the urge to do a little victory dance on the conference room table.)
We are now in the process of moving everything back to physical servers and direct attached storage.
Now, for a 500 user mailbox server, it will probably work okay. However, IMHO, it would still be *cheaper* to go with physical / DAS servers.
Why? Calculate how much that SAN storage you are using for virtualized Exchange costs. Our SAN storage costs are about $2/GB. Our DAS storage costs are closer to $0.40 per GB. If you are only giving your users a few GB of mailbox
storage, then the costs may be negligible.
There are some nifty/cool things you can do with virtualized Exchange when it comes to backups and changes. But, be wary of what vendors tell you. For example, if a vendor tells you "you can snapshot your Exchange server before you apply a service
pack, then revert to the snapshot if you have a problem" has neglected to take in to consideration that when some changes to Exchange, such as a SP being applied, also stamp version specific data in to the Active Directory.
Jim McBee - MVP, MCT, MCSE Using Exchange since the v4.0 beta in 1995 - Blog http://mostlyexchange.blogspot.com

Essbase 64 bit on Windows 2003 Server: Windows Virtual cache/ Paging File ?

Hi,
the speed of our nightly calculations seems to differ from day to day between 1 and 2 hours
I am wondering, what the correct setting for the windows paging file is ?
We use Windows 2003 64 Bit Server with 16 GB RAM
We run 1 Essbase application with 80 GB pag files with 4 GB Data Cache Setting and 1 GB Indexcache Setting in EAS console - on that server is actually nothing else running in production mode (just a few essbase-test application, usually offline)
what is the recommended setting on the windows level in the windows system properties for memory usage ?
We have:
Memory Usage: Adjust for best performance of "Programs" ;
Virtual Memory/Paging file on C-Drive: Custom Size, initial Size: 10 GB, maximum size 16 GB
when system was handed over from Oracle, we had 4 GB virtual memory - however in essbase manual, you read that the recommended value should be 3-5 times the physicial ram -
for me, the cache-bevahiour is strange anyway: if I watch taskmanager, I see in the middle of our 1 hour calculation the memory usage of Esssvr.exe Service using 7 GB of RAM, then the 16 GB RAM are used up at some point (paging file is 9 GB )- then suddenly nearly all the RAM get's cleared and ESSSVR.exe memory consumption goes down to 0 and from 0 increasing again-
looks to me, as all the cache for essbase get's deleted in the miiddle of the calculation, because RAM used up for paging files ?
Can anybody explain or give a clear directions, what to check ?
our application operates normally (no abnormal termination, no generation of *.xcp files)
(Essbase is installed on the 500 GB D-Drive)

Hi John,
thanks for the helpful link - the long discussion reminded me again, that pure cores and cache is not all, what makes up a good essbase application -
I will test with calcparallel 6 (in comparison to 4) on our 64bit environment - just to see if I can achieve a 10, 20 or 30% improvement...
In addition, I must admit, that 50% of our 1-2 hour calculation is calculated in serial/ not parallel... so I expect an additional 5 to 10 min improvement, not more.
Thank you for now

Two SAP production systems in a single physical server

Dear All,
Is SAP support installing two SAP production systems like SAP ECC 6.0 of one customer and ECC 6.0 with a different SID and instance no. for another customer in a single physical server? Would like to know from the experts is this possible? If yes , what are the things to take care of this design if any?
Thanks
Hany

Hi ,
check below blog
You can check the following blog https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/5124. [original link is broken]
It helps you to understand different logon pages for portal
Koti Reddy

Moving SAP server to a new domain

Hi,
We need to move a set of SAP servers (windows) running in one network/domain to another network/domain. No other change is planned, the systems are going to remain as is.
I would like to know
- What might be involved in achieving this (I tried searching SDN and OSS, but wasn't successful)
- What precautions I should take (I do not plan any backup etc as the SAP servers themselves are not to be touched)
Thanks,

Hi
We did the same.. moving the servers from one datacenter to other [which mean different domain, hostname, IP, DNS]
It is very easy for UNIX servers compared to Windows.. You do not need to reinstall.
The impacted components are:
- DB: For Oracle, change listene.ora, sqlnet.ora, init.ora, init.sap, passwd file
- CI & DI: system profiles
- Printers: change in mass from SPAD
- Interfaces: All interfaces at the receiving end need to change the server details..
- Any ABAP programs which is storing files in appl servers hard coding the server name
- In system profiles, check for any parameter which is hard coded to hostname like helppath
And many more..
For JAVA system, you need change the hostname via offline config tool.
SAP only stores hostname, so you need to identify all the locations where hostname is hard coded during installation/configuration.
Also you need to check performance on new servers..
Let me know if you need any more information..
Regards
Madhu

Business connector server on Virtual Server

Hi,
Currently our 4.6 release Business Connector servers running on Windows NT Operating system. We would like to upgrade them to BC release 4.7 on Windows 2000 operating system on Virtual servers.
Are there any known issues/disadvantages if we install Business connector servers on Virtual Server rather than a Physical server?
These virtual servers will be in the same domain as that of SAP systems. Host names of the upgraded Virtual servers will be same as the current production BC hosts.
Thanks,
Srini

Technical Data
These functions are:
Changed, new, deleted
For Release
   Software Component
·        Component: SAP Business Connector (external)
·        Release: 4.7
Assignment to Application Component
BC-MID-BUS (SAP Business Connector)
Country Setting
Valid for all countries
Use
The following information provides you with an overview of the new features in SAP BC Release 4.7: It also tells you about incompatible changes that you need to know about before performing an upgrade.
SAP BC 4.7 is based on Integration Server 4.6 from webMethods. However, the SAP BC elements in Integration Server 4.6 have been redeveloped (see below for details).
Features
Additional Functions in SAP BC Developer
As well as SAP BC Administrator GUI, you can now use SAP BC Developer to perform typical development tasks. You do not need administrator authorizations in SAP BC Developer to do this. For example, with SAP BC 4.7 you can use SAP Lookup to generate elements for the Developer. This enables you to gather information about function modules, structures (tables), BAPIs and IDocs in an SAP system, and then generate outbound maps or records for these objects directly.
SAP BC Developer contains a new menu, SAP, which contains the following functions:
·        Look up a function module and generate an outbound map
·        Look up a structure definition and generate a record.
·        Lookup a business object.
·        Look up an IDoc and creating a Record.
·        Browser for Function Maps.
In addition, the Developer now also supports the following actions:
·        Generate an SAP inbound map if you want an SAP system to run a service in SAP BC.
·        Generate an SAP outbound map to execute a function module in an SAP system.
·        Generate a record based on an SAP ABAP Dictionary structure.
·        Generate a record based on an SAP IDoc.
SAP BC Developer now also supports a proxy bypass list. This means that you no longer need to define whether a connection runs through a proxy; instead, the bypass list performs this task.
New Public Services on SAP BC Server
pub.string:gzip
Compresses the specified input string and generates a check total (optional). For measurements or for statistical purposes, the lengths of the zipped and unzipped strings are provided as output.
·        pub.string:ungzip
Decompresses a specified input string, which was compressed with pub.string:gzip, and verifies the check total (optional).
·        pub.string:numericParse
Analyzes a number in accordance with a given number pattern.
·        pub.math:randomLong
Generates a pseudo random number and sends its string representation in a pipeline variable. You can use this number as a universal identifier with an acceptable level of security, as long as it is used in non-distributed scenarios and for a small number of variables.
·        pub.file:head
Shows the start of a given file.
·        pub.file:tail
Shows the end of a given file.
·        pub.flow:sleep
Puts the current service into sleep mode for the specified period (in seconds).
Restructuring of the WmPartners Package
The WmPartners package in SAP BC Server has been completely restructured and now offers the following enhancements:
·        Improved status information in the messages displayed in the Transaction Store and the Audit Log. This solves a range of problems, such as incorrect status information being displayed by IDocs.
·        Improved search and sort options for transactions in the file system of the Message Store. In the Transactions menu, SAP BC Administrator GUI offers you a new option, Message Store Query Settings, which enables you to select and delete transactions. In Release 4.7, the Message Store can also be displayed on separate pages, which makes it easier to edit large numbers of transactions.
·        Improved search and sort options for Routing Rules. In the Routing Rules menu, SAP BC Administrator GUI offers you a new option, Routing Rule Filter Settings, which enables you to restrict the number of routing rules that are displayed, and to sort the display. The filter accepts all combinations of characters, and the placeholders '*' (string of characters) and '?' (one character). This makes it easier to sort and search for routing rules, especially if you need to process a large number of communication partners and message types.
·        Forwarding the "Confirm Event" tRFC (triggered by an SAP system) to the next receiver (for the following transports: B2B Service, ALE (R/3 IDoc), and XML (only if another SAP BC is the receiver)) and triggering "Confirm Event" from an external client. Both of these cases can be significant if the final receiver is an SAP system. In this case, "Confirm Event" removes the transaction ID from the ARFCRSTATE table, which can improve system performance significantly when a large number of tRFCs are being processed.
Support for Distributed Statistic Records (DSRs)
SAP BC has supported the generation of DSRs since Release 4.7 DSRs enable you to monitor the performance of each SAP system and its components. In this way, you can check how much system load is produced by each individual component, and how many resources are being used. This enables you to identify "performance leaks" and optimize system performance.
The DSR support integrated in SAP BC also allows you to measure the total retention period of a process in SAP BC. To evaluate the DSRs, you require additional SAP software, including specific versions of the SAP Solution Manager, and the RFC Library. The exact requirements are still being defined.
The details will be published in SAP Note 620418. You can find a link to this SAP Note on the SAP BC download page at http://service.sap.com/sbc-download.
SAP BC Server Core Enhancements
·        Reverse Invoke
The reverse invoke protocol has been enhanced and now allows you to forward more information, such as IP addresses.
If, for example, an application fails because a connection is broken, and other working connections exist, the connection is checked using a ping.
From now on, the internal server can open or reopen a defined number of connections, if necessary.
A document is generated for any exceptions on the internal server.
·        Email Listener
New Features in the Email Listener
¡        Reprocessing of invalid mails for IMAP Server
¡        Processed mails selected as "unread" if they have not been deleted.
You can also specify whether mails with exceptions are deleted or not.
·        Update Manager
The Update Manager manages fixes and patches for the upgrade of an SAP BC Server. Previously , the Update Manager allowed a fix to set other fixes as obsolete, using the updateVoidList field in the update.cnf file of the fix. An obsolete fix is not shown in classpath, but up to now the Update Manager has not been able to give a fix in classpath priority ahead of this other fix. The Update Manager has now been enhanced to support these fix priorities: The update.cnf file in the fix now contains an updatePrecedeList field.
Incompatible Changes
SAP BC Delivery Without JVM
The Windows Version of SAP BC 4.7 is no longer delivered with a Java Virtual Machine (JVM). The SAP BC 4.7 Installation Guide describes the JVMs that are supported.
See also
For more information, see the documentation on the SAP Business Connector, under
·        http://service.sap.com/connectors (SAP Business Connector ® SAP Business Connector in Detail ® Documentation).

Exchange Server 2013 Hyper-V vs Physical Server & SMB3.0 vs SAN

Looking for advise on installing Exchange Server 2013 in a virtual (Hyper-V) environment or dedicated physical server installation. Also, when setting up the data storage, what's the best practices for using SMB3.0 vs direct storage SAN. We're
leaning to shared storage using SMB3.0 rather the SAN (very costly) and can use a dedicated 2012 Server with 4TB of storage (RAID 10) with (shares).
Thank you,
William

Have you tried Storage Calculator? search it on TechNet site an input the values .. If you want me to give your the specs then I'd ask
Total Send/Receive Capability / Mailbox / Day
Average Message Size (KB)
Mailbox Size Limit (MB)
Personal Archive Mailbox Size Limit (MB
If you already have an existing Exchange 2010/2007 then you can also calculate the above input.
Let me know ..
Where Technology Meets Talent

Find whether OS on which Oracle DB is deployed is a VM or Physical server

Hello,
Is there a way via SQL or any built in utility could provide me the information that the OS on which my Oracle DB is deployed is a VM or a Physical Server?
Ta.

You can query the OS:
[root@vm601 ~]# dmidecode | grep -i virtual
    Version: VirtualBox
    Product Name: VirtualBox
    Family: Virtual Machine
    Product Name: VirtualBox
[root@vm601 ~]# virt-what
virtualbox
[root@vm601 ~]# lspci | grep -i VGA
00:02.0 VGA compatible controller: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter

Moving Physical server to Virtual, what to check?

Similar Messages

Maybe you are looking for