On which physical server do I register my ALERT HANDLER in SP2010/SP2013?

I wrote an alert handler to customize alerts.
The way to register mentions to basically add the .dll in the GAC and then to launch an STSADM comand to modify the alert template XML. However it does not mention the case in which you have multiple Front End servers or multiple Back End servers.
My solution is a generic solution for any customer and I must do a generic installer and I was wondering on which server(s) I should run my installers.
Thanks

RubiconCSL wrote:
Not too sure yet - it may come down to the first omne's that can actually take an order!  Talk Talk look cheap, but I don't know what they are like.  BT do look a LOT more expensive; but maybe one gets what one pays for?  So, nothing certain yet, as no-one wants my business
Well the BT Care Team can only help you with placing an order with BT, not any other Service Provider, that is something you would have to sort out yourself.
There are some useful help pages here, for BT Broadband customers only, on my personal website.
BT Broadband customers - help with broadband, WiFi, networking, e-mail and phones.

Similar Messages

  • 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

  • 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"

  • Multiple SAP system on single physical server.

    Hello Experts.
    We are in process of implementaing SAP solution withLandscpe having systems ECC 6.0, SolMan 4.0, BI. We are planning to have 3 Sytem landscape for all.
    Now but currently we are having only one Physical server
    Is it possible to Install 6 SAP system on single server?(DEV and QAS for ECC, Solman, BI respectively). The server is having sufficient hardware for 6 system as per sap standered. Planne OS is RHEL and DB MaxDB. Initially we are having 16 GB RAM extendable.
    Will SAP support such kind of landscape?

    Hi Nikhil
    Just my two cents:
    Never put non-prod/prod systems on the same server, how would you test os patches, what if system wide components cause problems, what if - for example - you want to upgrade your database on the dev system, but you need a new library, which is not compatible to the version needed by the prod system.
    Your single linux box will not be big enough to hold all these systems, trust me. And x86_64 hw is sooo cheap ))
    Regards, Michael

  • ADS+Terminal Services on a Single Physical Server running Windows Server 2008 R2

    We have a Dual Processor Server (2 x Intel Xeon E5-2620v2 + 32GB RAM) running on Windows Server 2008 R2. This has ADS configured. We now wish to add a VDI Setup with NComputing Zero-Clients. We have to run Terminal Services with User RDS CAL + User
    CAL for all VDI Clients.
    Please confirm if we can have both the ADS & Terminal Services running on the same physical server ? Are there known issues or crashes due to this ? Or should both these run on two different servers ? Customer does not want to invest in one more server
    & OS. Hence, we have to run both the services on a single physical server. Customer has just upgraded his server to a Dual Processor with 32GB RAM to accommodate both the services.
    Please advice, if we can run both the ADS & TS on the same server. What is the best practice for this Solution ?
    Thanks & Regards,
    VR
    ([email protected])

    Hi,
    After referring your comment I can say that, you can able to use ADS and Terminal service on same physical server with server 2008 R2. But installing a terminal server on an Active Directory domain controller is not recommended. I suggest that it’s not a good
    practice to manage the environment in that way. If possible, then try to run on two different machines for better result and to avoid any problem. Allowing users to run programs on a domain controller could create security risks and performance issues.
    If the Terminal Server role service is installed on a domain controller, the security settings of the domain controller will need to be adjusted to allow user’s remote access to the server. This remote access is controlled by the "Allow log on through Terminal
    Services" user rights assignment, which can be configured by using the Group Policy Management Console (GPMC).
    You can refer below link for more information.
    1.  Installing RD Session Host on a Domain Controller
    2.  Best practices for setting up Remote Desktop Licensing (Terminal Server Licensing) across Active Directory Domains/Forests or Workgroup
    Hope it helps!
    Regards.

  • How to migrate Sun One directory server to a new physical server install

    need help
    We have to move our existing installation of sun on directory server 5.2 to a new physical server.
    We have a new physical server with a new host name. I am trying to find an easiest way to take a snapshot of our existing server and put it on a new installation
    So will installing sun one directory server , its shows me two choices either to create a new instance or copy configuration from a existing server
    What do i choose and which is the fastest route to replicate my old server
    Thanks a bunch in advance
    Sganb

    Hi,
    I'm glad you're still using the old, glorious Sun One Directory Server 5.2, because it brings me back a lot of memories... But are you seriously talking of the 'plain' version, with no patches/hot fixes on top? If that's the case, you're using of a software that has been developed in 2004 and released in Jan 2005! Just for you to be aware, in the last *8* (eight) years a considerable number (in the magnitude of 10^3) of bugs, security problems and performance issues has been identified and fixed...
    However, to provide a better answer to your question, it would be important to understand the 'big picture' in terms of scenario and requirements:
    1) Is this a critical 24x7 service for which you need to perform an on-line migration or you have a 'maintenance window' during which the service may be switched off?
    2) Is the old server member of replication environment? If yes, how many masters/slaves do you have already? Shall the new server be part of this topology? What role shall it have?
    3) Would it be possible to make the the old server able to communicate with the new server?
    4) How big is the database that you've got to migrate? Do you have any requirement in terms of caches?
    5) Do you take backups on a regularly basis and have in place working (*tested*) backup/restore procedures?
    6) Is the new server conserving or changing the O.S. and architecture? [SPARC->SPARC, x86->x86, SPARC->x86, Solaris -> ? , 32 .vs. 64-bit? ]
    7) What are the steps you did to 'install' the software on the new server?
    Thanks,
    Marco
    P.S.: I don't wanna sound 'scaring' with all these questions, neither this should be intended as an 'hidden advertising' for Oracle Professional/Consulting Services, but the only way to not put in jeopardy your data is being aware of the risks, having the control of what's going on and ... possibly have a 'B' plan ;-)
    P.S.S.: My last suggestion is to consider a migration to a later release AS SOON AS POSSIBLE; the latest is ODSEE 11.1.1.7, which is available here:
    http://www.oracle.com/technetwork/middleware/downloads/oid-11g-161194.html
    and seems to work pretty well ;-)

  • Improve VM IOPs performance vs. physical server

    Hi there,
    Need some advice on VM configuration and improving IOPs - were testing out VM IOPs performance on our EMC SAN vs. physical server attached to the same SAN testing for migration.
    Server setup - we have a 4-Way 32-Core (X7550CPU) HP DL580  from 3 years ago running physical OS connected to the above SAN and also a VM (8vCPU) hosted on  latest 3-Way HP DL580 60-Core (E4870 v2) with ESXi 5.1 both servers are using 8Gb FC connect to SAN.
    We've setup an IOmeter test on both physical and VM (test disk is RDM physcal mode) with 100GB test file on a RAID10 drive, based on the tests - the physical server can produce almost 10000IOPs while the VM can only produce 4800IOPs on a 4KB 100% read; 100% random test profile with 4 workers and 32 outstanding queues configuration.
    Can anyone advise how I can improve the performance IOPs on the VM or is this expected given that its a VM its likely to produce less IOPs and is the percentage difference between the physical/VM consistent or expected.We've even tried increasing the VM vCPU from 8-16 but the results don't seem to change much.
    Many thanks

    Are you using identical or similar multipathing configurations on both tests?
    Which virtual SCSI controller are you using on the VM?

  • Create ISO of Windows Server 2012 R2 Physical Server - NOT VM

    I have a windows server 2012 R2 installed on a physical server. I have windows patches and other firmware upgrades on it. I would like to create a gold image in the form of ISO, so that i can use this ISO and build my other servers. I have read many many
    blogs but none of them have clear steps. I know there are tons of ways to do this for VM, but this is for a physical machine. I have used sysprep, completely messed up my server, i am used there is no warning or anything listed on technet for using this software.
    If anyone has able to do this successfully please let me know. Please don't send me instructions for VM, this is not a VM, it is a physical server. Thanks in advance.

    Okay, it's been a while since I worked with MDT and my memory was bad.  The best thing to do is to download MDT (https://www.microsoft.com/en-us/download/details.aspx?id=40796
    for the 2013 version) and its documentation.  One of the documents is a Quick Start Guide.  It gives you step-by-step instructions on how to do what you are asking.  It doesn't make sense to replicate all that content in a forum when there is
    already a published document.
    Then, if you have problems with performing the tasks, come back to this forum and ask specific questions about the issues you are encountering.
    Note, the documentation assumes working with Windows 8.1, but it also says it supports it for Windows Server. 
    . : | : . : | : . tim
    Thanks Tim. I started working on it, i do have few questions:
    i) Why do i need 3 machines as per the document "Quick Start Guide for Lite Touch Installation.docx"? I am not quite following here, can i just do it on 2 servers, 1 which will capture the image and server 2 will be used to build using captured image.
    ii) I was able to get till Step 41. (page 17 from doc 'Quick Start Guide for Lite Touch Installation.docx'), i do see the ISO created, but it is only 300 MB? My original ISO was 4 gb. I don't think i can just copy the 300 MB iso and build another machine, i
    am lost here, any advice is appreciated.
    Thanks

  • Should the Weblogic machines be created on each physical server?

    Hi,
    In order to have a cluster configuration, should the Weblogic machines be created on all physical servers involved in the cluster?
    Thank and Regards.

    If I well understand, there should be one machine per physical sever. Correct?
    YesWhen creating a machine, what should be the Listen Address and the Listen Port?
    It shud refer to IP and port of your remote serverShould the IP address be explicitly the IP address of the physical server on which the machine is created or the hostname of the physical server (for instance localhost)?
    Hostname/IP addressWhat id the machine is created in one server, but it s meant for a remote physical server?
    You create machine in Weblogic Server Console running on say Physical Server 1, you need to specify IP & Port of remote server which will be running the actual service.Should the Listen Port be the port on which the Node Manager listens or not?
    No, it shud be different.Refer: - http://middlewaremagic.com/weblogic/?p=971
    - Akshay

  • SQL Physical Server vs Hyper-V or VM

    We had Brent Ozar evaluate our SQL Environment about a year ago , one of the recommendations was to moved from Virtual to a Physical Server but there were no further explanations as to the PROs and CONs of Physical vs Virtual.
    This is an SQL server for Dynamics GP  ERP system and they also recommented to go from 8GB of ram to 128GB ram
    Any comments appreciated.

    Hi Elant,
    Regarding the Pros and Cons of Physical vs Virtual, they’re briefly described in the below link.
    SQL Server Physical Vs Virtual Environment
    As for the recommendation of moving your SQL server from Virtual to Physical, toughly to say, it is on purpose to improve the performance. A dedicated physical server is all yours, namely critical resources(CPU and IO, which is sensitively related to performance)
    will not be used by anything other than the SQL server task. Without outside interruption, SQL server will run smoother. As you mentioned you had Brent Ozar evaluate your SQL Environment, so this should be based on his understanding of your scenario. See below
    link’s from Brent Ozar’s site.
    Reasons Why You Shouldn’t Virtualize SQL Server
    With regards to memory gaining from 8GB to 128GB, since SQL Server uses memory to cache data and avoid additional trips to disk, it can improve performance obviously. You’ll get the added benefit of additional memory to cache query plans, perform bigger joins
    and sorts in memory, and may even see a reduction in CPU and disk utilization to boot. SQL Server 2008 R2 Standard Edition maxes out at 64GB  as well as SQL Server 2012 Standard Edition does while SQL Server 2014 standard Edition maxes out at 128GB. Generally
    speaking, the more memory you gain, the more performance is improved. See the link from Brent Ozar’s site also.
    How to Prove Your SQL Server Needs More Memory
    If you have any question, feel free to let me know.
    Best Regards,
    Eric Zhang

  • Controlling which CUCM server communicate over a SIP trunk

    We have 3 CUCM servers, two sub and one pub at two different physical locations.
    There are two SIP trunk servers (non Cisco), we wish to have the CUCM at the same physical location to communicate with the SIP trunk device at its location, instead of going over the WAN to communicate with the other one.
    Communications are initiated from the CUCM side through a route pattern that points to a RL/RG that contains the SIP trunk.
    The SIP trunk uses a DP that uses a CUCM group that only contains the local CUCM server.
    Can this be setup to reliably control which CUCM server talks to the SIP trunk server at its location?
    Do we need to configure something differently?

    Hi,
    If the CUCM's are located in different physical location then the communication should be over the IP-WAN and if it is about different CUCM Cluster then we can use H323 ICT Trunk between CUCM server for communication which is again WANLink.
    Still not clear with your query, However as you want to control the Gwy/Trunks using the Route Pattern. You can create two separate route pattern for internal & external.
    Wherein in Internal Route Pattern you can specify the ICT/SipTrunk/GWY which is connected within the cluster under Route List/RouteGroup to route the call.
    And for External Route Pattern specify the Gwy/SipTrunk which connects you to the outside world.
    Regards,
    Venkatesh

  • Migrate DPM to another Physical Server

    I have one DPM server on Windows 2008 R2 SP1 and SCDPM 2012 SP1 running on it. This server has OS related issue and giving BSOD frequently, Have logged call with Microsoft but it hasn't fixed yet. 
    I am planning to move this server to another physical server with Fresh OS and new DPM setup. This server having 400 Datasources and 37 TB storage pool on it.
    The biggest fear we have of Tape data information. We write tapes on every month with tape retention of 5 years. There's no any certificate or encryption is on DPM server side. The encryption we have is on tape library side provided by HP. 
    I just want to confirm that if I move DPM all configuration with storage pool to new server. Will be able to restore data on new DPM server from tapes which we wrote last year?
    In simple words just want to confirm that tape information will be loosed?

    Hi,
    Yes, as long as you do a true hardware migration keeping the same DPM Server name and restore the DPMDB, then the rebuilt server will be able to read the tapes and restore data back to original location.  
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
    This posting is provided "AS IS" with no warranties, and confers no rights.

  • WL Instance versus Physical Server

              I was under the impression that each instance of a WebLogic server in a cluster ran on its own physical
              server. But now I've been told that you can have a cluster of WebLogic servers running on a
              single physical machine!
              Is this advisable? Is it a common configuration?
              To me, this seems to defeat the purpose of clustering.
              Dave
              

    Yes, cluster load-balancing and failover will work for virtual 2 or n tiered architecture. Physical
              tiering is irrelevant here for these software-based clustering behaviors. What physical tiering is
              relevent for, though, is hardware robustness.
              Gene Chuang
              Join Kiko.com!
              "Ganaraja V Bhat" <[email protected]> wrote in message news:[email protected]...
              > We have 2 instances runing on the same box , but while going through the doc Planning for
              Clustering , i
              > see that lot of emphasis is given on the Physical aspect , rather than the logical .But in our
              case
              > everything is on one box , now will the ckustering work at all the levels (servlet/JSP,EJB)
              >
              > Thanks
              > Neeraj
              >
              > Gene Chuang wrote:
              >
              > > Is your web and app the same server instance, or two instances running on the same box? If the
              > > former, then load-balance will definitely not occur. If the latter, then I believe it will.
              > >
              > > --
              > > Gene Chuang
              > > Join Kiko.com!
              > > "Ganaraja V Bhat" <[email protected]> wrote in message news:[email protected]...
              > > > Hello,
              > > > To make things more clear i am giving the details of the arch being used,
              > > > we have 3 GS140 machines(8 CPU) .In each machine we r installing
              > > > Webserver/LDAP/Weblogic , so that they behave in the cluster mode.
              > > > Will this arch facilitate the fail-over and load balancing at webserver/application layer
              > > >
              > > > ang wrote:
              > > >
              > > > > We could implementing all instances in a single physical server. That requires more high
              power
              > > server in order to achive the similar performance as the mulit-physical server configuration.
              It
              > > would be ok for load balance. But not for fail-over. There is no redunanncy for physcial
              server in
              > > this configuration. A single system crash will lose all services to clients.
              > > > >
              > > > > Ganaraja V Bhat <[email protected]> wrote:
              > > > > >David ,
              > > > > > i am also searching for the right answer as in my project we r using cluster wherein all
              the
              > > machines
              > > > > >have webserver/appserve/ldap i am not convinced with this as i got hold of a whitepaper
              which
              > > clearly says
              > > > > >that we need to have diferent physical layer.........but .....needs more clarifications .
              > > > > >
              > > > > >Looking for the comments from u all
              > > > > >
              > > > > >Neeraj
              > > > > >
              > > > > >David Mrozek wrote:
              > > > > >
              > > > > >> I was under the impression that each instance of a WebLogic server in a cluster ran on
              its
              > > own physical
              > > > > >> server. But now I've been told that you can have a cluster of WebLogic servers running
              on a
              > > > > >> single physical machine!
              > > > > >> Is this advisable? Is it a common configuration?
              > > > > >> To me, this seems to defeat the purpose of clustering.
              > > > > >> Dave
              > > > > >
              > > >
              >
              

  • 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

  • More webdispatchers on one "physical" server serving more WAS

    Hi we have two different web AS which we both need to access from the
    outside(HTTPS port 443). Normally you would just install two web dispatchers on two
    different servers.
    However it would of course be preferable if you could install the two
    web dispatchers on one physical server.
    I have seen a document by Jochen Rundholz where it's mentioned that
    this is the recommended way to do it. Infortunately I have not been
    able to find any more documentaion on how.
    Do any of you have any more documentation on how to configure this?
    Best regards
    Flemming Grand

    Hi Flemming
    Hi,
    We can install multiple web dispatcher on one host (with different SIDs)
    Note: until release 7.20 (same kernel/web dispatcher also in 7.02) you need 1 wd per message server. It is also possible to cascade them. see note:
    https://service.sap.com/sap/support/notes/740234
    the mandatory rule is ONE webdispatcher per ONE message server until 7.02/7.20 (exception: dual stack setup with Java addin, which is not not recommended anymore by SAP except for Solution Manager
    If you have only one ip:port for the internet, but several web dispacthers, becasue you have several system with several central systems/ message server, then you have to cascade the Webdispatcher. One Web Dspatcher collects all others WDs for the internet IP:port.
    Virtual IP adresses is IMHO more relevant for high availability and/or ACC adaptive computing controlling if you want to move Systems to different physical hosts.
    Also please check the following link:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/events/webinars-nw-rig/sap%20web%20dispatcher%206.40%20-%20webinar%20powerpoint.pdf
    I hope the info in this helps you.
    Regards
    Chen

Maybe you are looking for