Troubleshooting Slow Virtual Machines
Friends:
I am struggling with very slow virtual machines.
I have Windows Server 2012 installed on a Dell T620. It has two Intel Xeon E5-2650 2.00GHz chips (20M Cache, 8.0GT/s QPI, Turbo) and 64 G of 1600 MHz RDIMMS. It is set up with two RAID arrays (RAID 1 for OS with two 300G 10k SAS drives; RAID
5 for server stuff with four 600G 10k SAS drives) running on a PERC H710 Adapter RAID Controller (512MB NV Cache).
There are two virtual servers running on the box. One is the domain controller and the other hosts a SQL-based practice management program. The "physical server" hosts HyperV etc.
There are 5 or 6 virtual workstations, each running Win8.1E with one virtual CPU and dynamic RAM allocations of up to 8192MB.
HyperV has two virtual switches ("RDS Virtual" and "Intel I350 Gigabit Network Connection - Virtual Switch"). (I don't actually know why it is set up that way.)
I wonder whether anyone can help me trouble-shoot my poor performance?
Hi MicahS,
" There are 5 or 6 virtual workstations, each running Win8.1E with one virtual CPU and dynamic RAM allocations of up to 8192MB. "
First , I would suggest you to try to allocate more host CPU resources to these VMs .
To narrow it down , you can use performance monitor to check specific host resource .
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.
Similar Messages
-
Java virtual machine very slow: why?
Since I have upgraded Tiger to Leopard, the startup of the Java virtual machine is unbelievably slow: for example, just executing java -version for the first time requires almost one minute. This happens only the first time the JVM is started: after that, everything seems to work properly. Any idea of what is the problem? Thank you.
I don't have this problem at all.
Which version of Unix are you using? And which version of Java are you using on the Unix computer? How old is your Computer? -
Slow down speed for testing purpose between virtual machine in hosted in Hyper-v
Hello All,
I have searched and could not find thread related to this .
There is a scenario to test: the network speed between virtual machine [client and server ] must be really slow to check the application behavior on connecting to server.
Please advise . thanks in advanceHi
Thanks for the reply . I am using
Virtual machine manager console .
right click on the virtual machine, i see network adaptar in Hardware Configuration and there no option to choose speed in any of the option.
Please guide me if i am wrong -
Cant create replica and Hyper V virtual machine management service slow shutting down
Hi,
I cant create replica and Hyper V, I go through the process and all looks good it even starts to create the hard disk but it stops at 4096K and the wizard just keeps going.
The management console is also slow or wont load virtual machines - stuck on loading virtual machines
The Hyper V virtual machine management service slow shutting down over 30 minutes on re boot of Hyper V core 2012 R2
Any ideas ?Hi Sir,
I assume that you have a standalone hyper-v server 2012R2 and you are using hyper-v manager to manage the hyper-v host .
Which system you are using to manage hyper-v host , win8 or win8.1 or other ?
Have you created VMs on the HOST ?
I would suggest you to create vhd or someother operation on hyper-v host directly to check the result .
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Virtual Machines extemely slow to load on brand new server.
We're about to put our first virtualized Windows 2012 Hyper-V server on a small business site. Everything went fine with the installation, but I've noticed that when loading up the virtual machines, the process takes hours... For example, I created a new
virtual machine with 4GBs of RAM, and installed Windows 7 64-bit edition from an ISO file... It took about two hours. I deleted this virtual machine and tried to create another Windows 7 64-bit virtual machine, this time using the actual DVD and it was just
as slow.. EVEN with all other VMs shut down... I have another test copy of Hyper-V for Windows 8 at home that I use for learning, so I tried installing the same Windows 7 64-bit ISO on this workstation and it installed in twenty minutes. And this is just a
workstation.
The server is a HP Proliant ML350 server with 24GBs RAM. If anything I would have expected the server to install the Windows 64-bit VM in twenty minutes, NOT the workstation !! On the face of it the only differences between the two systems is:
a) The server has two 500GB SAS drives, which are mirrored. There is no mirroring on the Windows 8 workstation.
b) The server had drive is partitioned in to a C: drive (for the host O/S) and a D: drive (for the virtual machines). There is only one partition on the Windows 8 workstation, which holds the operating system and the virtual machines.
Below is a graphic I drew up which I hope helps you visualise the hard drive setup.
This is a small site, so they wont pay for additional hard drives. Is there something about the way I have the disks set up that could cause the virtual machines to load slowly? Would it be better NOT to have two partitions on the host?
Thanks in advance for any advice offered.It looks like you are trying to use 100% of your disk space. Are the VHDs fixed size or dynamic? How much free space is there on the host partition? If the host partition is 80% full and you are using fixed VHDs, the system could be thrashing
itself trying to find free space, and that free space can get highly fragmented meaning no large blocks for storing. Generally a disk is considered 'full' when it is at about 80% utilization. If you are using fixed VHDs, you have 80% utilization
even before you take into consideration what the host needs.
Partitions don't change performance characteristics. You still have the same number of read/write heads sharing the processing of the same amount of data. That's why multiple disks can improve performance - multiple read/write heads going against
multiple data blocks. So what you are describing has nothing to do with partitions versus no partitions.
Have you run any other IO load tests to see if there is a hardware problem with the RAID controller? That is not unheard of. What you are seeing is completely atypical for your environment. That's why I am wondering about hardware issues.
.:|:.:|:. tim -
Internet Explorer 11 slow response on Windows 7 x64 virtual machine
I have a number of virtual machines running Windows 7 64bit on my network.
They are set up on a server running VMWare ESXi 5.1.0. Their users access them from Windows 7 desktops via Remote Desktop.
The overall performance of the Virtual Machines is fine, except when browsing the web using Internet explorer 11. (Firefox and Chrome are better, but not by much).
The user experiences uneven scrolling (looks like low FPS), delayed responses to input, new tabs take 1~2 seconds to open and closing the browser sometimes takes a few seconds after you click the 'X'. Firefox also experiences the uneven scrolling and delay
in opening new tabs, Chrome just has the uneven scrolling.
None of these issues occur when viewing the virtual machine through the VMware vSphere console.
This is a fresh install of both the operating system and browsers (installed on 2013-11-22). Everything is up-to-date and all browsers still have their default settings.
Running browser benchmark tests like Peacekeeper (http://peacekeeper.futuremark.com/) shows a notable difference in performance between browsers running natively on a desktop, through the vSphere console and through RDP.
Does anyone know what could be causing this and/or how it could be remedied?Hi,
To speed up RDP connection, please select High Color (16 bit) under Colors, and under Experience tab, select Modem (56 Kbps).
To make IE fast, safe and stable, please attempt to run this fixit below:
http://support.microsoft.com/mats/ie_performance_and_safety
Also, you can use UI responsiveness tool to dig into what is happening in F12 developer tool in IE11.
Thanks!
Andy Altmann
TechNet Community Support -
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" -
Install R12 on a Virtual Machine hosted on Windows Vista
I wanted to install Oracle EBS R12.1.1 on Windows Vista Home Premium 64-bit but used to get .\jre\nt\1.6.0\bin\java error. Hussein Sawwan
helped and said that this is not certified. He adviced me to create a VMWare Server. Following is my experience. I hope it is helpful. Any
suggestions, additions are more than welcome. Thanks to all who helpmed me especially Hussein Sawwan, Helios, Gareth Roberts.
I used to get .\jre\nt\1.6.0\bin\java error after the installation would zoom through 33%. That was because my staging area was not correct. The staging area should be just next to c:\ or whatever be the root directory (or drive). No space or special characters in folder name. My current structure is as follows:
c:\r12stage. Under r12stage I have following folders and subfolders
oraAppDB -- 49 Disks
oraApps -- 11 Disks
oraAS -- 3 Disks (This comes from the Rapid Install Tools)
oraDB -- 5 Disks
startCD -- 1 Disk plus other folders. Just copy startcd from the unzipped download and paste to r12stage area.
I then created a virtual machine using VMWare Server (free download but need to register to get the serial number). Because I installed
vmware server on Vista Home Premium 64 bit Host OS, I have to boot my machine by pressing F8 and then select Disable Digital Signature
Enformcement. Thanks to Gareth Roberts for this tip. Create a vm and install Windows 2003 by selecting the .img file (first cd) by selecting Use ISO image and then path of the windows 2003 cd 1 (zipped file). start the virtual machine, that will install windows 2003 and then ask for location of 2nd cd. On the host machine, where the second win 2003 zip file resides, unzip the second zip file and name the folder as cd2. share this folder to the __vmware_user__ and from the virtual machine, map network drive to \\hostmachinename\cd2. Select this as the location of cd2 and complete the installation. Install MKS Toolkit from http://cygwin.com/ and visual c++ from Microsoft website. for information on this please refer to the following URL. Thanks to Muhammad Habib
http://mhabib.wordpress.com/2007/03/14/installing-oracle-applications-e-bussiness-11i-on-windows-xp/
After installation is done and Windows Update is run, share the r12stage directory on the host machine to the vmuser and launch rapidwiz.cmd from the command prompt and follow the instruction. For internet connection from the VM use Ethernet as NAT.
If the installation errors halfway through, clean up your VM by following instructions in document id 292424.1 in MetaLink. If you dont have access to Metalink then I summarize the steps briefly over here.
Launch the Registry Editor.
Navigate to the HKEY_LOCAL_MACHINE\Software key.
Select the Apache Group subkey and delete it.
Select the Oracle subkey and delete it.
Navigate to the HKEY_LOCAL_MACHINE\System\Current Control Set\Services.
Carefully select and delete each service beginning with Oracle. For example, delete "Oracle Apache Server PROD_<nodename>".
When you are finished, exit the Registry Editor.
Navigate to the Environment Variables editing screen according to your system setup. For example, right-click My Computer and select
Properties. From the Advanced tab, click the Environment Variables button.
Select the following system variables if created during the failed installation, and delete them: DISCO_JRE, DISCO_VBROKER, JSERV,
VBROKER_JAVAVM, VBROKER_TAG, WV_GATEWAY.
Select the Path variable, but do not delete it. Carefully edit it and remove any component with "Oracle" in the name, or that otherwise
references the failed install. For example, delete "E:\11.5.10\test\visora\8.0.6\bin;".
Save and exit System Properties.
Open a command window and navigate to the C:\Program Files\ directory. Delete the Oracle subdirectory.
If your Oracle Inventory directory was not C:\Program Files\Oracle\Inventory and was therefore not deleted in the previous step, locate it
and delete it.
Restart your machine
It is now safe to remove the Oracle filesystem that was partially installed during the failed installation. Go to the base install directory,
or top-level directory under which you installed either the Database Server (DATA, DB) or the Applications Tier Server (APPL, ORA, COMN)
directories, or both. Note that you may choose to rename a directory before you delete it. This allows you to use the same directory name and start a new installation even before you finish the delete filesystem operation. For example, if you placed your filesystem in a "test" directory under
"E:\11.5.10":
C:\> E:
E:\> cd 11.5.10
E:\> rename test oldtest
E:\> del /s /q oldtest
In another window:
C:\> cd <stage install directory>
Q:\> rapidwiz.cmd
After cleaning up if you still get error like RW-50004: Error Code received when running external process. Check log file for
details. Running database Install driver for VIS instance, after 13% complte step 1 of 5 then I suggest that you re-create the machine and follow the above steps again. Including installing win 2003, mks tool kit , vc++, etc. It will be a success.
Starting concurrent manager takes up enormous memory and slows down everything, so if you dont need it then dont ever start it. APPS password is apps and sysadmin user is sysadmin.
Good luck.
Mahesh AcharyaI had Vista 64-bit machine, installed Ubuntu in VMWare. Installed Oracle apps on 32-bit Ubuntu under VMware and was able to access Oracle apps. But, it is very very slow. It hangs sometimes and takes 15-20mins to display Ubuntu screens. Am I missing something here. I have a 4GB RAM and VMWare can not use all the 4GB. It may be using 2GB of 4GB. Am I missing something?
-
Can not see a sbRIO in MAX running on a virtual machine
I am trying to connect a sbRIO-9606 to a Windows 7 virtual machine (VMWare) running on a MacPro. I can open a CMD prompt and ping the sbRIO but when I run MAX, it does not appear in Remote Systems.
The virtual NIC is bridged to the pyhsical one (on the MAC)
Does anyone have experience doing this, or know why I cannot see the sbRIO?Hi jaketc,
I've had similar issues at times depending on how my host and guest operating sytems network interfaces are configured. It sounds like your settings are correct (bridged), but it is difficult to guarantee. The first step I usually take is disable any network interfaces (on the host and guest OS) that are not critical to connecting to the remote target.
A more generic answer is to walk through the troubleshooting steps in this document, but it won't cover the virtualized OS considerations of your setup:
Why Does My CompactRIO Controller or Single-Board RIO Not Show Up in Measurement & Automation Explor...
Because you can ping the target, it sounds like the Single-Board RIO already has an IP address, you know what it is, and ethernet communication can be established. When I've been in that situation in the past, I've been able to manually add the RIO target to MAX. To find a system that is already configured with an IP address, simply right-click on Remote Systems and select Create New. Enter the appropriate configuration information in the dialog box, and MAX will manually place that system in the Remote Systems listing and all tasks will function properly.
Cheers,
Spex
National Instruments
To the pessimist, the glass is half empty; to the optimist, the glass is half full; to the engineer, the glass is twice as big as it needs to be... -
Office 2013 Installation stuck on Windows 8.1 ESXi virtual machine
When I try to install Office 2013 32 Bit - on a Windows 8.1 64 Bit Virtual Machine that is hosted on ESXi Host server .....it stucked installing it for hours and hours without finishing ....... I tried to install locally on a mounted ISO image with the same
result !!
It happens on many machines not a specific one !
Does any one know what can be a reason for that ?!
Hossam Wael Elmosallamy (IT Support Engineer-ECC Solutions) MCSE - CCNA [email protected] Mobile:(011)-49464671 www.eccsolutions.net "Experience Reliability"Hi,
At which specific percentage will the setup hang? Vuk is right above, but it's really hard to say what's the cause of your case.
Please first take a look at this KB article and see if it is helpful for you:
Microsoft Office 2013 or Office 365 hangs during setup
I would suggest you go and check the setup log files to troubleshoot the issue, which is the best way to narrow down the issue I think.
Regards,
Ethan Hua
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs. -
Problems PXE booting Gen 2 Virtual Machines after Upgrading to Windows Server 2012 R2
My Current Setup:
I have two virtual machines set up with Hyper V on my Windows Server 2012 Server.
VM1: Configured to boot from an ISO file and runs Clonezilla server.
VM2: Configured to PXE boot using a legacy network adapter, and with a passthrough 250Gb hard disk.
These two VMs are connected to an external Virtual Switch, which allows physical machines to PXE boot to the Clonezilla server.
For the past few months I have been using this setup for two purposes:
1. To clone physical machines to the Clonezilla virtual server (as a backup).
2. To restore those image to the second VM if I find that need to get access to the files on the original image..
This has worked perfectly, except for the fact that the speed of the legacy network adapter on the second VM (which is required to PXE boot) is very slow. But I know this is because of the limitations in how the legacy adapter works...
Now my problem:
I found out that Gen 2 VMs allow you to PXE boot without having use a legacy network adapter, allowing me to image back to the VM faster. So I upgraded the Server to Server 2012 R2 . I then created the same two virtual machines on the R2 server. I can still
PXE boot the Gen 1 VM to the Clonezilla Server but I cannot get the Gen 2 VMs to PXE boot properly. They get an IP address from the Clonezilla Server but then just stop with the following screen. (note: I have disabled the Secure Boot).
Are Gen 2 VMs unable to pull down images from anything other than a WDS Server?Hi J,
>>Unfortunately WDS is not a solution for us as it is dependent on the PC being part of a domain
If you would like to make the client not join to the domain, please check the box before “Do not join the client to a domain after an installation.” In addition, make sure not to set the client to the domain in the unattend file and do not prestage
the computer in AD. "
It is quoted from following thread :
https://social.technet.microsoft.com/Forums/windowsserver/en-US/1026c3a9-0a10-4a58-a48f-5391659a96c8/wds-set-unattend-file-for-workgroup?forum=winserversetup
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Hi everyone,
I have 2x physical servers running Hyper-V 2012 R2. Each hosts several virtual machines. The VHDs of the VMs are stored on several dedicated physical disks to have a performance boost. For exampe if VM A has two VHDs attached I made sure that the VHDs are
on different physical disks to have them not slow-down each other in case of intensive disk accesses.
So far so good. I was looking forward to the replication-feature. The idea is to have the two physical servers have their primary running VMs being replicated to the other physical server and vice-versa. I was hoping to have the chance to choose for each
individual VM where the replicated VHD will be stored. But instead I can only see the one location/path which is configured in Hyper-V Manager when I activate the replication-feature on the server.
Is there by any chance a way how to select the storage location for each VHD/VM if using the replication-feature of Hyper-V 2012 R2?
Thanks in advance.
Cheers,
SebastianSecondly, you could replicate different VMs to different storage locations to perform some of the disk balancing you are trying to perform. Lastly, you could copy the vhd file to a different location
before starting the VM.
.:|:.:|:. tim
Hi Tim,
thanks for the reply. Sorry, but I had some other tasks to take care of, so I wasn't paying enough attention to this thread.
The part I quoted from your reply sounds exactly like the action I'd like to perform, but as you pointed out before this should not be possible.
How can I perform the action (replicating each VM to a storage location) as you mentioned secondly? To sum it up again:
2x physical machines carrying severel HDDs
8+ VMs spread to run on the 2x servers
when setting up replication I can only set the storage-location from server A on B and vice versa B on A
Thanks again for your reply.
Cheers,
Sebastian -
When is Apple going to fix the problem with slow Time Machine backups with Mavericks?
I have been with Apple tech support and they got my Time Machine working by doing a spotlight re-indexing and a safe boot. This worked for about three days and I am back to very slow backups. It is impossible for Time Machine to back up every hour when it takes six hours to do the back up. I don't want to take hours to re-index with spotlight all the time. I think taking six hours to do an incremental backup is a bit much. I see that there are many people that have this trouble and it all started with an upgrade to Mavericks. The question is when is Apple going to fix this problem of slow backups with Time Machine for Mavericks. I have wasted more time than I care to. I am think of going back to Windows. I need good solid backups of my machine and Apple has taken it away with the new Mavericks. Oh, I am using the UBS 3.0 connection so the drive should not be the problem. Also this has occurred in about the last five months, so I am not sure this problem was in the original Marvericks.
Allen Thanks for your reply. All I can say is several months ago Time Machine quit working in a reasonable manner. Right now I have a Time Machine backup that has been running all night and still has three hours to go to backup 6 GB of data. I am using a OWC 1.5 TB drive connected directly to my MacBook with a USB 3.0 connection. In the resent past I have added Dropbox, GoogleDrive and a MAMP server on which I am using a program called Learning With Text from Sourceforge. There have been a lot of questions on the forum about people having very slow Time Machine back ups, so it appears to be a general problem. I should also state I am getting this very slow backup after doing the Spotlight re-indexing and the Safe Restart procedure that was told to me by apple support. I have a 750 GB drive in my MacBook Pro which I am constantly trying to keep at a 5% level of free space. This might be a problem also. However, I am working on a lot of things and like to have a lot of things on my drive. Also the heavily loaded drive has not be a problem in the past. This slow backup business started about three months ago, so something has happen in a very short time period. Now it seems even the procedure that Apple support gave me is not working. Currently I am in China and it is difficult to interact with Apple support to solve this problem, but because I am in China having my computer backed up is critical. I have run the EtreCheck and am attaching the results below. I would appreciate any suggestions. If necessary I will clear out more of my hard drive if that appears to be a solution. The Time Machine drive was recently reformed so I only have a few backups on it. I also don't run the Time Machine all the time as I don't want multi-hour backups running all the time. I run it every few days.
Here is the info from EtreCheck:
Hardware Information:
MacBook Pro (15-inch, Mid 2012)
MacBook Pro - model: MacBookPro9,1
1 2.6 GHz Intel Core i7 CPU: 4 cores
8 GB RAM
Video Information:
Intel HD Graphics 4000 - VRAM: 1024 MB
NVIDIA GeForce GT 650M - VRAM: 1024 MB
System Software:
OS X 10.9.2 (13C1021) - Uptime: 0 days 10:18:59
Disk Information:
APPLE HDD HTS727575A9E362 disk0 : (750.16 GB)
EFI (disk0s1) <not mounted>: 209.7 MB
Macintosh HD (disk0s2) / [Startup]: 749.3 GB (54.06 GB free)
Recovery HD (disk0s3) <not mounted>: 650 MB
HL-DT-ST DVDRW GS31N
USB Information:
VIA Labs, Inc. USB3.0 Hub
OWC Elite Pro mini C 1.5 TB
EFI (disk1s1) <not mounted>: 209.7 MB
NewMBP-TimeMachine-1.1 (disk1s2) /Volumes/NewMBP-TimeMachine-1.1: 1.5 TB (691.6 GB free)
Apple Inc. FaceTime HD Camera (Built-in)
Apple Inc. BRCM20702 Hub
Apple Inc. Bluetooth USB Host Controller
Apple Computer, Inc. IR Receiver
Apple Inc. Apple Internal Keyboard / Trackpad
Logitech USB Receiver
Thunderbolt Information:
Apple Inc. thunderbolt_bus
Gatekeeper:
Mac App Store and identified developers
Kernel Extensions:
[not loaded] com.LaCie.ScsiType00 (1.2.2) Support
[not loaded] com.lacie.driver.LaCie_RemoteComms (1.0.1) Support
[not loaded] com.oxsemi.driver.OxsemiDeviceType00 (1.28.0) Support
[not loaded] com.roxio.BluRaySupport (1.1.6) Support
[not loaded] com.roxio.TDIXController (2.0) Support
[not loaded] com.seagate.driver.PowSecDriverCore (5.0.1) Support
[not loaded] com.seagate.driver.PowSecLeafDriver_10_4 (5.0.1) Support
[not loaded] com.seagate.driver.PowSecLeafDriver_10_5 (5.0.1) Support
[not loaded] com.seagate.driver.SeagateDriveIcons (5.0.1) Support
[kext loaded] com.symantec.kext.SymAPComm (11.2.2f3) Support
[not loaded] com.symantec.kext.confidentialData (1.4f5) Support
[not loaded] com.symantec.kext.filesecurity (1.4.3f19) Support
[kext loaded] com.symantec.kext.fw (1.0.3f5) Support
[kext loaded] com.symantec.kext.internetSecurity (1.3.2f5) Support
[kext loaded] com.symantec.kext.ips (1.3.1f7) Support
[kext loaded] com.symantec.kext.pf (4.2.1f7) Support
[not loaded] com.wacom.driver.HIDTablet (5.0.1) Support
Startup Items:
cma: Path: /Library/StartupItems/cma
MySQLCOM: Path: /Library/StartupItems/MySQLCOM
ParallelsDesktopTransporter: Path: /Library/StartupItems/ParallelsDesktopTransporter
ParallelsTransporter: Path: /Library/StartupItems/ParallelsTransporter
Tablet: Path: /Library/StartupItems/Tablet
Launch Daemons:
[loaded] com.adobe.fpsaud.plist Support
[loaded] com.adobe.versioncueCS4.plist Support
[loaded] com.barebones.authd.plist Support
[not loaded] com.barebones.textwrangler.plist Support
[loaded] com.bombich.ccc.plist Support
[loaded] com.mcafee.virusscan.eupdate.plist Support
[running] com.micromat.TechToolProDaemon.plist Support
[loaded] com.oracle.java.Helper-Tool.plist Support
[loaded] com.oracle.java.JavaUpdateHelper.plist Support
[loaded] com.prosofteng.DriveGenius.locum.plist Support
[running] com.symantec.avscandaemon.plist Support
[running] com.symantec.deepsight-extractor.plist Support
[running] com.symantec.diskMountNotify.plist Support
[loaded] com.symantec.MissedTasks.plist Support
[loaded] com.symantec.navapd.plist Support
[running] com.symantec.navapdaemonsl.plist Support
[loaded] com.symantec.Sched501-1.plist Support
[loaded] com.symantec.Sched501-2.plist Support
[loaded] com.symantec.Sched503-3.plist Support
[loaded] com.symantec.Sched503-4.plist Support
[running] com.symantec.sharedsettings.plist Support
[running] com.symantec.symdaemon.plist Support
[running] com.symantec.symSchedDaemon.plist Support
[loaded] org.macosforge.xquartz.privileged_startx.plist Support
Launch Agents:
[loaded] com.adobe.CS4ServiceManager.plist Support
[running] com.lacie.safemanager.daemon.plist Support
[running] com.micromat.TechToolProAgent.plist Support
[loaded] com.oracle.java.Java-Updater.plist Support
[running] com.seagate.SeagateStorageGauge.plist Support
[failed] com.sogou.SogouServices.plist Support
[running] com.symantec.uiagent.application.plist Support
[running] net.culater.SIMBL.Agent.plist Support
[loaded] org.macosforge.xquartz.startx.plist Support
User Launch Agents:
[loaded] com.adobe.ARM.[...].plist Support
[loaded] com.adobe.ARM.[...].plist Support
[loaded] com.google.keystone.agent.plist Support
[running] com.wondershare.mobilegodaemon.plist Support
User Login Items:
GeekTool
SIMBL Agent
QQ
Safari
Calendar
Google Drive
Dropbox
Day One
Dictionary
SymSecondaryLaunch
Internet Plug-ins:
Flip4Mac WMV Plugin: Version: 2.2.1.11 Support
FlashPlayer-10.6: Version: 13.0.0.182 - SDK 10.6 Support
iPhotoPhotocast: Version: 7.0
Flash Player: Version: 13.0.0.182 - SDK 10.6 Outdated! Update
AdobePDFViewer: Version: 9.5.5 Support
Default Browser: Version: 537 - SDK 10.9
QuickTime Plugin: Version: 7.7.3
OfficeLiveBrowserPlugin: Version: 12.3.6 Support
RealPlayer Plugin: Version: (null) Support
Silverlight: Version: 4.0.51204.0 Support
JavaAppletPlugin: Version: Java 7 Update 55 Check version
Safari Extensions:
Video Converter: Version: 4.0.0
AllMyTube: Version: 4.1.0.0
Open in Internet Explorer: Version: 1.0
Audio Plug-ins:
BluetoothAudioPlugIn: Version: 1.0 - SDK 10.9
AirPlay: Version: 2.0 - SDK 10.9
AppleAVBAudio: Version: 203.2 - SDK 10.9
iSightAudio: Version: 7.7.3 - SDK 10.9
iTunes Plug-ins:
Quartz Composer Visualizer: Version: 1.4 - SDK 10.9
User Internet Plug-ins:
QQMail: Version: 1.0.2.0 - SDK 10.7 Support
txftn: Version: 1.0.0.6 Support
3rd Party Preference Panes:
Adobe Version Cue CS4 Support
Flash Player Support
GeekTool Support
Growl Support
Java Support
MacFUSE Support
MenuMeters Support
MySQL Support
Norton\nQuickMenu Support
Paragon NTFS for Mac ® OS X Support
Pen Tablet Support
Perian Support
TechTool Protection Support
Time Machine:
Skip System Files: NO
Mobile backups: OFF
Auto backup: YES
Volumes being backed up:
Macintosh HD: Disk size: 697.84 GB Disk used: 647.49 GB
Destinations:
NewMBP-TimeMachine-1.1 [Local] (Last used)
Total size: 1
Total number of backups: 11
Oldest backup: 2014-03-18 15:09:46 +0000
Last backup: 2014-04-29 23:24:28 +0000
Size of backup disk: Too small
Backup size 1 < (Disk used 647.49 GB X 3)
Time Machine details may not be accurate.
All volumes being backed up may not be listed.
Top Processes by CPU:
47% SymAVScanDaemon
7% Finder
7% WindowServer
2% mds
1% NortonAutoProtect
Top Processes by Memory:
385 MB NortonAutoProtect
262 MB mds_stores
180 MB Safari
139 MB WindowServer
115 MB Finder
Virtual Memory Information:
1.15 GB Free RAM
2.87 GB Active RAM
1.83 GB Inactive RAM
1.05 GB Wired RAM
1.02 GB Page-ins
380 MB Page-outs
I hope you can see something that can be fixed. -
Problem installing SCE 2010 on a virtual machine
I'm having issues while installing SCE on a clean Hyper-V virtual machine running Windows 2008 R2.
I've tried several options:
- all-in-one from scratch, no SQL or serverroles/features installed -> error 1603
- seperate SQL and SCE Management Server -> Management server installation fails, error 1603
Different variations including and excluding reporting and VM Management with the same results.
I then went and tried to install tbe Management server on a physical box -> success!
However, I can't use this box for SCE and need to virtualize the whole thing.
I'll dig through the SCE setup log files to see where it goes wrong.
In the mean time, any ideas/suggestions anyone?
/edit
Below a snippet of the setup log. This is the part just before I get 'Return value 3':
MSI (s) (68:88) [15:42:11:574]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIDD55.tmp, Entrypoint: AddPrivilegesToActionsAccount
AddPrivilegesToActionsAccount: Custom action data property value. *****\administrator
AddPrivilegeToAccount: Giving privilege to account. *****\administrator
AddPrivilegeToAccount: Account does not have privilege. SeServiceLogonRight
MSI (s) (68:14) [15:42:11:637]: Executing op: ActionStart(Name=_SetHealthServiceACL.80B659D9_F758_4E7D_B4FA_E53FC737DCC9,,)
AddPrivilegeToAccount: Successfully granted privilege right to account. SeServiceLogonRight
MSI (s) (68:14) [15:42:11:639]: Executing op: CustomActionSchedule(Action=_SetHealthServiceACL.80B659D9_F758_4E7D_B4FA_E53FC737DCC9,ActionType=3073,Source=BinaryData,Target=SetHealthServiceACL,)
MSI (s) (68:F8) [15:42:11:642]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIDD95.tmp, Entrypoint: SetHealthServiceACL
MSI (s) (68:14) [15:42:11:734]: Executing op: ActionStart(Name=_ChangeMOMHealthServiceRecoverySettings.80B659D9_F758_4E7D_B4FA_E53FC737DCC9,,)
MSI (s) (68:14) [15:42:11:736]: Executing op: CustomActionSchedule(Action=_ChangeMOMHealthServiceRecoverySettings.80B659D9_F758_4E7D_B4FA_E53FC737DCC9,ActionType=3073,Source=BinaryData,Target=ChangeMOMHealthServiceRecoverySettings,)
MSI (s) (68:04) [15:42:11:739]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIDDF3.tmp, Entrypoint: ChangeMOMHealthServiceRecoverySettings
MSI (s) (68:14) [15:42:11:755]: Executing op: ActionStart(Name=_RegisterMU.80B659D9_F758_4E7D_B4FA_E53FC737DCC9,,)
MSI (s) (68:14) [15:42:11:756]: Executing op: CustomActionSchedule(Action=_RegisterMU.80B659D9_F758_4E7D_B4FA_E53FC737DCC9,ActionType=1025,Source=BinaryData,Target=RegisterMU,CustomActionData=C:\Program Files\System Center Essentials\MUAuth.cab 3)
MSI (s) (68:A0) [15:42:11:757]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIDE04.tmp, Entrypoint: RegisterMU
RegisterMU: Custom action data property value. C:\Program Files\System Center Essentials\MUAuth.cab 3
RegisterMU: AddService failed. Error Code: 0x80070005.
CustomAction _RegisterMU.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (68:14) [15:42:12:017]: User policy value 'DisableRollback' is 0
MSI (s) (68:14) [15:42:12:017]: Machine policy value 'DisableRollback' is 0
Action ended 15:42:12: InstallFinalize. Return value 3.Hi Guys,
I am having the exact same issue. I have verified all prerequisites and can find absolutely nothing I am doing wrong with regards to what is prescribed in the guides. I am also trying to install SCE 2010 on a Hyper-V guest on Windows Server 2008 64Bit. I
tried several times and troubleshooted my way through all the blogs. This is what I have done:
Re-imaged the server (twice),
Verified NetBios and FQDN is similar,
Opened all required ports first and also disabled firewall eventualy,
Using Domain Admin account,
Removed ISS and reinstalled(SCE still complaing IIS needs configuration),
Removed ISS again and let SCE setup fix prerequistes (SCE still complaining IIS needs configuration),
Also below please find my exact log... The sucess of my SCE 2010 installation is VERY KEY for us, but I believe for the product team as well. We are busy building an Enteorise Management Architecture in a hosted/multi-tennant environment and at this moment
our POC is a showstopper :(.
operty(S): RuntimeUseWorkstationGC = 1
Property(S): ShouldManageMemory = true
Property(S): MOM_DB_IS_LOCAL = 1
Property(S): AGENTSERVERCOMPATIBLE = 1
Property(S): IsValidMgmtGroup = 1
Property(S): WINDOWS_LANGUAGE_ID = ENS
Property(S): DNS_COMPUTERNAME = PSGKSTSCE.psgkst.co.za
Property(S): AD_COMPUTERNAME = PSGKSTSCE.psgkst.co.za
Property(S): NETBIOS_DOMAINNAME = PSGKST
Property(S): ENABLE_ERROR_REPORTING = 0
Property(S): USE_SETTINGS_FROM_AD = 0
Property(S): SDK_ACCOUNT_FOR_DB = SYSTEM
Property(S): SDK_DOMAIN_FOR_DB = NT AUTHORITY
Property(S): ACTIONSDOMAIN_FOR_DB = PSGKST
Property(S): ACTIONSUSER_FOR_DB = Service-SCE
Property(S): ROOT_MANAGEMENT_SERVER_DNS = PSGKSTSCE.psgkst.co.za
Property(S): ROOT_MANAGEMENT_SERVER_AD = PSGKSTSCE.psgkst.co.za
Property(S): CONFIG_ACCOUNT_FOR_DB = SYSTEM
Property(S): CONFIG_DOMAIN_FOR_DB = NT AUTHORITY
Property(S): SOURCEDIR = D:\Setup\AMD64\Server\
Property(S): SourcedirProduct = {EA43D2A4-0926-445A-A220-6FF0CA34AA09}
Property(S): MANAGEMENT_GROUP_ID = ac80d722-cdb5-acaa-a3e3-c5b2e1ca4717
Property(S): ROOT_MANAGEMENT_SERVER_PORT_ID = C51B7833-DA54-1653-D8FD-1A738EF8DED5
Property(S): ProductToBeRegistered = 1
MSI (s) (24:C8) [10:55:13:979]: Note: 1: 1708
MSI (s) (24:C8) [10:55:13:980]: Product: System Center Essentials 2010 -- Installation operation failed.
MSI (s) (24:C8) [10:55:13:981]: Windows Installer installed the product. Product Name: System Center Essentials 2010. Product Version: 7.0.2432.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.
MSI (s) (24:C8) [10:55:13:987]: Deferring clean up of packages/files, if any exist
MSI (s) (24:C8) [10:55:13:987]: MainEngineThread is returning 1603
MSI (s) (24:2C) [10:55:13:988]: No System Restore sequence number for this installation.
=== Logging stopped: 2010/05/12 10:55:13 ===
MSI (s) (24:2C) [10:55:13:989]: User policy value 'DisableRollback' is 0
MSI (s) (24:2C) [10:55:13:989]: Machine policy value 'DisableRollback' is 0
MSI (s) (24:2C) [10:55:13:989]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (24:2C) [10:55:13:989]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (24:2C) [10:55:13:989]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (24:2C) [10:55:13:990]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (24:2C) [10:55:13:990]: Restoring environment variables
MSI (s) (24:2C) [10:55:13:991]: Destroying RemoteAPI object.
MSI (s) (24:10) [10:55:13:991]: Custom Action Manager thread ending.
MSI (c) (98:48) [10:55:13:993]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (98:48) [10:55:13:994]: MainEngineThread is returning 1603
=== Verbose logging stopped: 2010/05/12 10:55:13 === -
Microphone is not working on Windows 10 Tech Prev installed on a Virtual Machine
Microphone is not working on Windows 10 Tech Prev installed on a Virtual Machine.
What are the recommended troubleshooting procedure?
Thanks,
sistecHi,
Audio redirection might not be configured correctly for the virtual machine, I recommend you refer to the audio\sound\usb redirection guide for the type of your virtual machine.
Hyper-V virtual machine
http://blogs.windows.com/bloggingwindows/2013/12/05/overview-client-hyper-v-enhanced-session-mode-in-windows-8-1/
Windows Virtual PC
https://technet.microsoft.com/en-in/library/ee449432(v=ws.10).aspx
If the settings are set correctly, then please check the driver for the
Microphone, update the driver, it also might be a driver compatibility issue with Windows Technical Preview.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Maybe you are looking for
-
Hi, Based on the release notes of WSDP 2.0, Service Resigry has been removed. I was wondering, how can we use this functionality from now on? Where do can we get Service Registry API for registring and querying services. This is moves somewhere else?
-
Pavilion dv6 6169sl does not restart after installing video driver
Hi, I reinstalled windows 7 (64 bit) on my Pavilion dv6 6169sl.Then, I downloaded the video driver from the hp website and, when I restart the pc in order to complete the installation, it doesn't start, but the system stops showing the windows logo.C
-
What is the Infinity option 2 usege limit?
hello all. what is the Infinity option 2 usage limit? is it 100gb or 300gb? a month. cos its been 5 days now I'm getting very bad speed, 2 mb down and .8mb up after 6 pm till 2am. this is absolutely rubbish paying £24.99 a month for this **bleep**!!
-
Proper use of location in metadata
I'm building my library of images now with LR and want to get started on the right foot. I store on CD. In Metadata "Location" I have entered the CD volume name as a way of identifying where the images are stored. But now I am wondering if the Metada
-
Table display from RFC web servcice
Hi, I am calling a RFC web service from my WD for Java app.I am able to get the export param in one of the UI elements.But I am not able to display the TABLES parameter in the WD table. I have tested the web service from the WS explorer and it works