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.
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
Steps to configure the vCenter Server to generate SNMP traps: A.In the Home page of vSphere Client B.Select vCenter Server Settings C.Select SNMP configuration D.Enable one of the SNMP receivers E. Provide the details for : Receiver URL : Provide the host name of the Management Server (target SNMP server / monitoring tool) which will be connected to the VMware vCenter Server. (VMware vCenter Server sends the SNMP traps to this Management Server) Configure port 162 as the SNMP port. Community String: Provide community string (default string is "public") SNMP versions v1/v2/v3 are supported That is all that is needed for the configuration. Now you need to configure alarm for generating SNMP traps in the vCenter server. When ever there is a change in the environment ( host state change, VM state change ,etc) the trigger will be generated and send an alert to the monitoring server. Configure the Alarms After you have setup the external SNMP server, v
In our previous posts , we saw the option to deploy the VCH using CLI utility, vSphere client etc. In this post, we see an option to automate the VCH deployment using vRealize Automation ( vRA) Background: The current automated world requires the seamless and fastest deployment of its infrastructure. VMware vSphere Integrated Containers gives developers an essential tool for streamlining the process of building and running containerized applications in production. The deployment of VCH is done through various methods as we see in our previous posts. But in this post, we are going to see how to automate the VCH deployment and the first VCH in few mouse clicks. By using the service catalog in vRealize Automation to provision Virtual Container Hosts on-demand as a ticketless offer, you can make your developers self-sufficient. The vRealize Automation 7.4 and later versions support provisioning and management of Virtual Container Hosts(VCH) for running vSphere Integrated Containe