No matter how sophisticated the technology is , It still takes people !
Subscribe to this blog
Follow by Email
Installing the Virtual SCSI Controller Driver for Virtual Server 2005 on Windows Server 2008
You can install the virtual SCSI controller driver during the installation of the guest operating system by performing the following steps:
Description and screenshots where made while installing Windows Server 2008 on Virtual Server 2005 R2 SP1, however the same instructions apply to the installation of Windows Vista. For Windows 2000/2003/XP you will need to press the F6 key during the text phase of the installation process, then press “S” to specify additional drivers, and then provide the driver floppy image.
1. Begin the installation by inserting the appropriate Windows Server 2008 installation media into your DVD drive.
2. Continue with the installation process, until you reach the point where you’re prompted for the location of the system partition. Click on the Load Driver link.
3. Now you need to load the driver files as a virtual floppy image. The image’s name is “SCSI Shunt Driver.vfd”, and it is located in the C:\Program Files\Microsoft Virtual Server\Virtual Machine Additions folder. You can mount it by using VMRC Plus (read my “Manage Virtual Server Machines with VMRC Plus“, or from the Virtual Server administrative website. For this example I’ve used VMRC Plus.
1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next. The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance. 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click Next to display the App…
What is an Inventory? An Inventory is the process of mounting media in the drive and reading the media label, which is then displayed in the Devices view. If this is the first time that Backup Exec ™ has encountered this media, the media label is also added to the Media view. Note: Each time new tape is introduced in the tape drive or robotic library, it must be inventoried so that the Backup Exec database gets updated with the new tape Information. To Inventory a Tape/Robotic Library: 1. Insert the tape 2. Click the Devices tab 3. Select the correct tape drive/robotic library slot 4. Right-click on the tape drive/robotic library slot and select Inventory (Figure 1) Figure 1
The inventory will complete and should display the correct tape name. What is a Catalog? When cataloging a tape, Backup Exec reads the header information from the tape and stores it in a file on the hard drive. The information contained in the catalog includes, but is not limited to: Tape number/label/name (something to identi…
This post is related to the issue what we faced today when we replaced the SSL certificates in our setup. When I launched the web-client and access the update manager tab, I get the message "interface
com.vmware.vim.binding.integrity.VcIntegrity is not visible from class
I started off by
restarting the VMWare vSphere Update Manager Service for the affected vCSA: 1. Log into vCenter
using the firstname.lastname@example.org account. 2. Home - System
Configuration - Services - Restart
This did not resolve
my issue... And we tried restarting all the services by SSH/Console into the
affected server and run the following commands: service-control
--start --all Still no luck. Make sure the certs are applied and it gets reflected in the config file. ( verify if the thumbprint matches) root@homelab71 [
/usr/lib/vmware-updatemgr/bin ]# pwd/usr/lib/vmware-updatemgr/bin root@homelab71 [
/usr/lib/vmware-updatemgr/bin ]# ./updatemgr-util config -g | less