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.

Also see » Configure and customize SharePoint Workspace 2010

In the VMRC Plus Console Manager click on Media > Load Floppy Disk Image.

Navigate to the C:\Program Files\Microsoft Virtual Server\Virtual Machine Additions folder and select the "SCSI Shunt Driver.vfd" driver.

If you want, you can do the same by right-clicking on the VM's name in the main VMRC Plus window, then selecting Settings.

Now navigate to the C:\Program Files\Microsoft Virtual Server\Virtual Machine Additions folder and select the "SCSI Shunt Driver.vfd" driver.

Click Ok.

4. Back in the installation window, click on Browse.

5. Navigate to the virtual floppy drive's root folder, then expand the Vista subfolder.

Note: For other operating systems select the right subfolder.

Press Ok.

6. After a few seconds the driver's name will appear on the list. Click Next.

7. The driver will load.

8. In the "Where do you want to install Windows", if you're installing the server on a regular IDE hard disk, click to select the first disk, usually Disk 0, and click Next.

9. If you must, you can also click Drive Options and manually create a partition on the destination hard disk.

10. Continue the installation as usual, and when it's done the server will automatically reboot.

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T Last month I got a call from a customer who was pulling their hair out over a networking issue. They had just deployed VMware Tanzu Kubernetes Grid on their vSphere with Tanzu environment, everything looked good in the dashboards, all pods were running, but their applications inside the pods could not reach external databases running on traditional VMs in the same datacenter. The frustrating part was that some pods could reach external services perfectly fine, while others would just timeout. There was no clear pattern. Let me tell you how we figured this out and fixed it. The Initial Problem Here is what the customer setup looked like: vSphere 8.0 with Tanzu enabled NSX-T 4.1.2 for networking Three Tanzu Kubernetes clusters running different microservices applications External PostgreSQL database running on traditional VMs (non-Kubernetes) External API services running on another se...

Troubleshooting vSAN Storage Policy Migration Failures in VMware Cloud Foundation 9.0

Recently I had a customer who migrated their VMware infrastructure from vSphere 7.0 to VMware Cloud Foundation 9.0. After the migration, they wanted to update their vSAN storage policies to take advantage of the new vSAN ESA (Express Storage Architecture) features. However, when they tried to change the storage policy for their production VMs, the operation kept failing with a cryptic error message. The error they were getting was: "Cannot complete operation due to insufficient resources to satisfy current storage policy." This was strange because they had plenty of disk space available. The vSAN cluster was only at 45% capacity, and all the hosts were healthy. Let me walk through how we troubleshooted and fixed this issue. Understanding the Problem First, let's understand what was happening in their environment: They had a 6-node vSAN cluster running VCF 9.0 vSAN was configured with the new ESA architecture They were trying to migrate VMs fro...

Unlocking VMware Cloud Foundation 9.0: A Strategic Blueprint for Enterprise Transformation

The evolution of VMware under Broadcom represents not disruption, but clarification—a focused vision toward unified private cloud excellence. As organizations navigate this transformation, the opportunity has never been greater to build truly modern, efficient, and powerful infrastructure with VMware Cloud Foundation. After architecting VMware solutions across diverse enterprise environments, I've observed a pattern: organizations that embrace VMware Cloud Foundation (VCF) strategically—rather than viewing the transition as a burden—emerge with significantly more capable, cost-effective, and future-ready infrastructure. This post shares a practical framework for successfully modernizing your VMware environment, maximizing your investment, and positioning your organization for the AI-driven, cloud-native future. Understanding the VMware Cloud Foundation Vision Let's start with clarity about what Broadcom and VMware are building: VMware Cloud Foundati...

My IT Blog

Search This Blog