I was recently doing an upgrade from Vcentre 4.1 to 5.5 and the Vcentre install kept failling with the following error: Error 1935 An error occurred during the installation of assembly component HRESULT: 0x80070422
To resolve it all you have to do is to make sure the Windows Modules Installer service is enabled and started.
If it happens after this again check the HRESULT number it will have changed.
This method below will guide in using VMware pass-through to connect a Physical tape device to a Virtual Machine.
1. Install Backup Exec on the Virtual Machine that you would like to be the Media Server, run updates then restart server. Do this until Backup Exec is completely up to date.
2. Shutdown the Virtual Machine
3. Go to your Vmware Manager and edit the particular Virtual Machine that runs Backup Exec.
4. Click on Add – Hardware and select SCSI Device
5. Make sure the correct Tape device is selected
6. The Finish page will be displayed
7. Restart the Host server then start the Virtual Machine.
8. Go to Device Manager on the specific Virtual Machine and check if the Tape Device is listed.
10. Open Backup Exec. Go to Devices – Right click the server and select “Configure Tape Devices”
10. Select install Tape Device drivers. Leave defaults in place and keep clicking next. A Popup will appear asking if you would like to install unsigned drivers. Select install anyway.
11. Wizard will complete. Restart the Virtual Machine.
Now you will be able to run backups on the Virtual Machine as if it was a physical device.
When trying to install Vpshere you come across the following error message: Admission check failed for memory resource.
99% of the time it will be that you don’t have the required memory. ESXI 5 requires a minimum of 2GB Ram.
So you’ve opened up the required ports 80 and 443 to connect remotely to your ESXI 5 Server with your Vsphere client and you can get to the ESXI Management Interface but when trying to open a Console session to one of your Virtual Machines you get the following error message:
The MKS in the error message stands for Mouse, Keyboard and Screen.
After a bit of research I have found that ports 902 and 903 TCP also needs to be opened to the ESXI 5 host for Console session to be reached. So make sure your Natting rules and Firewall reflect this.