http://www.windowsitpro.com/authors/author/author/5076555/rsscomment/5076555en-USSun, 27 May 2012 06:01:32 GMTSun, 27 May 2012 06:01:32 GMThttp://www.windowsitpro.com/article/services/vmware-at-your-service-#commentsAnchorMon, 24 Jan 2005 01:47:03 GMT
I could not get MS Virtual PC to work with the -singlepc -pc TerminalServerVM -launch but it does work with the -startvm switch. I suppose because this will install the vmc into the system account. "C:\Program Files\Microsoft Virtual PC\virtual pc.exe" -startvm "q:\vm\TerminalServerVM.vmc"]]>ROBERTMon, 24 Jan 2005 01:47:03 GMThttp://www.windowsitpro.com/article/services/vmware-at-your-service-#commentsAnchorhttp://www.windowsitpro.com/article/clustering/a-vmware-clustering-recipe#commentsAnchorSat, 23 Oct 2004 12:47:19 GMT
I am having the same problem like Duarte. I followed you article step by step. When I was ready to install MSCS the application prompt me that I do not have any shared SCSI disk. Do you have any quick answer. I’m running VMWARE 3.2 on W2K. ]]>NIKHILSat, 23 Oct 2004 12:47:19 GMThttp://www.windowsitpro.com/article/clustering/a-vmware-clustering-recipe#commentsAnchorhttp://www.windowsitpro.com/article/clustering/a-vmware-clustering-recipe#commentsAnchorSat, 23 Oct 2004 12:47:19 GMT
I am having the same problem like Duarte. I followed you article step by step. When I was ready to install MSCS the application prompt me that I do not have any shared SCSI disk. Do you have any quick answer. I’m running VMWARE 3.2 on W2K. ]]>NIKHILSat, 23 Oct 2004 12:47:19 GMThttp://www.windowsitpro.com/article/clustering/a-vmware-clustering-recipe#commentsAnchorhttp://www.windowsitpro.com/article/services/vmware-at-your-service-#commentsAnchorTue, 21 Sep 2004 07:40:50 GMT
I am new to this and using MS Virtual PC. Nothing I try seems to work. Also ... what should be in the "ServiceName"\ImagePath\ string ? is this the same as the Parameters\Application\string ? Thanks]]>WILLIAMTue, 21 Sep 2004 07:40:50 GMThttp://www.windowsitpro.com/article/services/vmware-at-your-service-#commentsAnchorhttp://www.windowsitpro.com/article/clustering/a-vmware-clustering-recipe#commentsAnchorFri, 10 Sep 2004 17:38:32 GMT
I also receive the same results of Aric Cecil and David Chapman. Any data created on one node cannot be viewed on the other node after failing over. It is as if there are two seperate disks, any input would be appreciated.]]>ARTHURFri, 10 Sep 2004 17:38:32 GMThttp://www.windowsitpro.com/article/clustering/a-vmware-clustering-recipe#commentsAnchorhttp://www.windowsitpro.com/article/services/vmware-at-your-service-#commentsAnchorWed, 14 Jul 2004 20:02:58 GMT
For those of you using Microsoft Virtual PC instead of VMWare, you can also do this by changing the Application Line to read "C:\Program Files\Microsoft Virtual PC\virtual pc.exe -singlepc -pc DC2K3 -launch" WITHOUT the quotes. where DC2K3 is the name of the virtual PC. ]]>BRYANWed, 14 Jul 2004 20:02:58 GMThttp://www.windowsitpro.com/article/services/vmware-at-your-service-#commentsAnchorhttp://www.windowsitpro.com/article/services/vmware-at-your-service-#commentsAnchorWed, 14 Jul 2004 19:24:22 GMT
What exactly is the -x for that is listed in the command "c:\program files\vmware\vmware workstation\vmware.exe" -x "e:\ms\w2k1w2k1.vmx"]]>BRYANWed, 14 Jul 2004 19:24:22 GMThttp://www.windowsitpro.com/article/services/vmware-at-your-service-#commentsAnchorhttp://www.windowsitpro.com/article/services/vmware-at-your-service-#commentsAnchorWed, 14 Jul 2004 10:26:59 GMT
If you have more than one virtual machine, you can add them all into the command line in the registry. If one machine depends on another (such as an Exchange server depending on a DC), you could create two services with one dependant on another and maybe a timer to slow the second from starting until the first was totally up.]]>dulawWed, 14 Jul 2004 10:26:59 GMThttp://www.windowsitpro.com/article/services/vmware-at-your-service-#commentsAnchorhttp://www.windowsitpro.com/article/services/vmware-at-your-service-#commentsAnchorTue, 06 Jul 2004 20:26:22 GMT
Anyone has a good tip to handle the shutdown of the services so that the VM session shuts down properly. I considered a shutdown script but I have yet to try one.]]>Rob Norman Tue, 06 Jul 2004 20:26:22 GMThttp://www.windowsitpro.com/article/services/vmware-at-your-service-#commentsAnchorhttp://www.windowsitpro.com/article/services/vmware-at-your-service-#commentsAnchorWed, 30 Jun 2004 15:06:31 GMT
This is a great trick. We use a similiar method and install the AutoExNT service, another resource kit utility which allows you to run an autoexec.bat file as the local system account without logging in under a user session. You can then use the same command-lines Chris uses to run your VMWare machines without having to install them as services.]]>Sean Powell Wed, 30 Jun 2004 15:06:31 GMThttp://www.windowsitpro.com/article/services/vmware-at-your-service-#commentsAnchorhttp://www.windowsitpro.com/article/services/vmware-at-your-service-#commentsAnchorTue, 01 Jun 2004 00:50:57 GMT
Finally! Chris, you can not believe how long i have been looking (hopeing) on how to run my VM’s as service and do exactly what you say => running a DC in VM and have the host logon to it. Great article, thanks! Tom Ps. A while back i had a hard time finding how to turn of the PC beep sound for a VMware session. I’d just like to pass on to everyone there is a ’mks.nobeep = "TRUE"’ feature you can add to your vm’s .vmx file.]]>Tom Decaluwe Tue, 01 Jun 2004 00:50:57 GMThttp://www.windowsitpro.com/article/services/vmware-at-your-service-#commentsAnchorhttp://www.windowsitpro.com/article/clustering/a-vmware-clustering-recipe#commentsAnchorFri, 07 May 2004 09:15:25 GMT
I too get the same results as Aric Cecil. Its as if the nodes have their own version of the shared disks. Here are the additions to my VM that made clustering possible for me on VM WS 4.5.: scsi0.sharedBus = "virtual" disk.locking = "false" scsi0.present = "TRUE" scsi0:0.mode = "persistent" scsi0:1.present = "TRUE" scsi0:1.fileName = "C:\VMWareGuestOS\ClusterQuorum\QuorumDisk.vmdk"]]>David Chapman Fri, 07 May 2004 09:15:25 GMThttp://www.windowsitpro.com/article/clustering/a-vmware-clustering-recipe#commentsAnchorhttp://www.windowsitpro.com/article/clustering/a-vmware-clustering-recipe#commentsAnchorThu, 15 Jan 2004 11:19:53 GMT
I’m astounded by the depth of the problem and the solution in Chris Wolf’s "A VMware Clustering Recipe" (February 2003, http://www.winnetmag.com, InstantDoc ID 37599). I’ve been trying to set up virtual machines (VMs) and had given up until I came across this article. Great job by the author, and thanks to the magazine for publishing such an in-depth and technical piece. I would love to see more of these kinds of articles.]]>Senthil Prabakaran Thu, 15 Jan 2004 11:19:53 GMThttp://www.windowsitpro.com/article/clustering/a-vmware-clustering-recipe#commentsAnchorhttp://www.windowsitpro.com/article/clustering/a-vmware-clustering-recipe#commentsAnchorThu, 15 Jan 2004 11:18:32 GMT
Chris Wolf’s article "A VMware Clustering Recipe" (February 2003, http://www.win netmag.com, InstantDoc ID 37599) was excellent. At my company, we use VMware GSX servers and VMware workstations to model new infrastructure, support Microsoft .NET development, and provide systems for quality assurance testing and sales demos. The author’s "recipe" might be missing an ingredient, however. Chris recommends simply copying the contents of the first virtual machine (VM—VM1) to create the second (VM2). This approach will certainly work, but our testing has shown that it typically results in Windows SID problems because both servers are essentially identical copies of each other. Changing the system name and IP address doesn’t change the underlying SID. However, an ingredient is easily available that will fix this problem. After you’ve completed the initial VM1 configuration, run Microsoft’s Sysprep utility (available at http://www.microsoft.com/windows2000/downloads/tools/sysprep/default.asp) to remove the unique identifying characteristics of the system. Next, make a backup of the Windows 2000 configuration that you used Sysprep on, and use it as the foundation for all future Win2K Server­based VM work. Then, copy the configuration into the directory for VM2 to create the second VM. Finally, after you power on both VM1 and VM2 machines, Windows will generate unique SIDs for each system. Note that Windows will prompt you to name each system and provide network configuration details during the first boot after using Sysprep—just as if you had purchased "real" servers with the OS preinstalled by the manufacturer. This extra step should prevent potential SID problems.]]>Mark F. Ewert Thu, 15 Jan 2004 11:18:32 GMThttp://www.windowsitpro.com/article/clustering/a-vmware-clustering-recipe#commentsAnchorhttp://www.windowsitpro.com/article/migration/migrating-legacy-applications-with-microsoft-virtual-server#commentsAnchorWed, 03 Dec 2003 06:35:33 GMT
Love the article. Very informative. Now we need a comparion to VMWare both desktop and server versions. I current use VMWare in production environments.]]>JayWed, 03 Dec 2003 06:35:33 GMThttp://www.windowsitpro.com/article/migration/migrating-legacy-applications-with-microsoft-virtual-server#commentsAnchorhttp://www.windowsitpro.com/article/clustering/a-vmware-clustering-recipe#commentsAnchorThu, 06 Nov 2003 05:53:33 GMT
I am keen to understand Clusering so I tried this on vmware 3 and vmware 4 but couldn’t get the Virtual Machine to create the cluster. The disks were present in Disk Manager as basic disks formatted NTFS and visible from both Virtual Machines but the Cluster Wizard failed saying that it couldn’t find any suitable disks. Any ideas please]]>joeThu, 06 Nov 2003 05:53:33 GMThttp://www.windowsitpro.com/article/clustering/a-vmware-clustering-recipe#commentsAnchorhttp://www.windowsitpro.com/article/clustering/a-vmware-clustering-recipe#commentsAnchorTue, 01 Jul 2003 03:44:51 GMT
I followed you article step by step. When I was ready to install MSCS the application prompt me that I do not have any shared SCSI disk. Do you have any quick answer. I’m running VMWARE 3.2 on W2K.]]>Duarte Matos Tue, 01 Jul 2003 03:44:51 GMThttp://www.windowsitpro.com/article/clustering/a-vmware-clustering-recipe#commentsAnchorhttp://www.windowsitpro.com/article/clustering/a-vmware-clustering-recipe#commentsAnchorWed, 19 Mar 2003 08:48:48 GMT
After setting up my VMware cluster using the steps outlined in Chris Wolf’s artice I failed over the cluster to the other node. Before I failed over the cluster to the other node I created several documents on the "Data" drive. Once I failed it to the other node the data wasn’t on the Data drive. If I failed it back to the original node the data was there. Any ideas? Thank you!]]>Aric Cecil Wed, 19 Mar 2003 08:48:48 GMThttp://www.windowsitpro.com/article/clustering/a-vmware-clustering-recipe#commentsAnchorhttp://www.windowsitpro.com/article/clustering/a-vmware-clustering-recipe#commentsAnchorTue, 25 Feb 2003 12:26:30 GMT
Hi, just read your article and had one remark. When you add scsi0.sharedbus=virtual and disk.locking="false" to the configuration file for both nodes then you can use persistent drives and it is possible to power off the nodes without loosing the drives.]]>Rob van Es Tue, 25 Feb 2003 12:26:30 GMThttp://www.windowsitpro.com/article/clustering/a-vmware-clustering-recipe#commentsAnchorhttp://www.windowsitpro.com/article/clustering/a-vmware-clustering-recipe#commentsAnchorFri, 21 Feb 2003 09:55:12 GMT
Hi! I follow you article step by step. When I was ready to install MSCS the application prompt me that I do not have any shared SCSI disk. Do you have any quick answer. I’m running VMWARE 3.2 on Windows XP. Kind regards ]]>Mikael Johansson Fri, 21 Feb 2003 09:55:12 GMThttp://www.windowsitpro.com/article/clustering/a-vmware-clustering-recipe#commentsAnchor