No matter how sophisticated the technology is , It still takes people !
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.
First, we will install the AD LDS Instance: 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 N
DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997. Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy. Remember that old test server that you built two years ago that caught fire before it could be used? Probably not. DNS still remembers it though. There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening. Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying. What happened?" This post should help us figure out when the first issue will happen and completely avoid the second. We'll go through how scavenging is setup then I'll give you my best practices. Scavenging s
Virtual Container Host Deployment using the "vic-machine" Utility - VMware Integrated Containers In our previous posts , we saw the steps to deploy VIC appliance and deploying the VCH from vSphere client. In this post, we will see the steps to deploy the VCH using the "vic-machine" CLI Utility Refernce: https://github.com/rdjagadeesh/vic_homelab/ Once we deploy the vSphere Integrated Containers (VIC) appliance, access the VIC appliance IP from the browser and we land on the below page. From this page, we can download the vSphere Integrated Containers Engine bundle from the appliance and unpack it on the workstation/laptop/ jump host where we connect to our vSphere environment. Unpack the downloaded bundle The bundle included the following contents and utilities The VIC bundle includes the vic-machine CLI utility. We use "vic-machine" to deploy and manage virtual container hosts (VCHs) at the command line. Procedure: