If you create a workflow in vRO and then add it as an item in Service Broker to the catalog, then the workflows inputs will be mapped into the form. Relevant data will be sent to the correct input in...
See more...
If you create a workflow in vRO and then add it as an item in Service Broker to the catalog, then the workflows inputs will be mapped into the form. Relevant data will be sent to the correct input in vRO when the workflow is executed. Have you tried to do this at all?
Hey there, Assuming that the Owner is the same as the Requester (which it normally is), create a workflow in vRO, as follows Workflow Name: Show Properties Single input, called inputProperties ...
See more...
Hey there, Assuming that the Owner is the same as the Requester (which it normally is), create a workflow in vRO, as follows Workflow Name: Show Properties Single input, called inputProperties of type Properties Add a script object to the canvas and set the inputProperties workflow input as an input to the script object. Use the following code to show the properties as well as the requestors name: for each (var inputProp in inputProperties) { for each (var key in inputProp.keys) { System.log("Name: " + key + " = " + inputProp.get(key)); } } System.log("Username: " + System.getContext().getParameter("__metadata_userName")); System.log("EventTopicId: " + System.getContext().getParameter("__metadata_eventTopicId")); From there, you can adapt and modify to suit your needs and use case.
Hi Mark, I have done this a few times now, and as long as you follow the upgrade guide you will be fine. The guide is located at the following link: http://www.vmware.com/pdf/vsphere...
See more...
Hi Mark, I have done this a few times now, and as long as you follow the upgrade guide you will be fine. The guide is located at the following link: http://www.vmware.com/pdf/vsphere4/r40/vsp_40_upgrade_guide.pdf As for your question regarding managing a mixture of ESX host versions, considerations will be installing a license server to ensure that your ESX35 hosts remain licensed (ESX4 uses license codes, the license server itself is deprecated). I would also keep your ESX35 and ESX4 hosts in seperate clusters. Out of curiosity, any reason that you are not upgrading the ESX35 hosts to vSphere? If you found this helpful, please consider awarding some points
I know the article is for esx 3.5 but it might be worth having a look at VMware KB Article: 1005566 If you found this helpful, please consider awarding some points
I am presuming you only have the 'flat' vmdk file, not the smaller vmdk descriptor which explains why you cannot see it in the VI Client (the descriptor file is what you actually see when browsin...
See more...
I am presuming you only have the 'flat' vmdk file, not the smaller vmdk descriptor which explains why you cannot see it in the VI Client (the descriptor file is what you actually see when browsing for a VMDK file, not the actual flat file / data file) once you have imported it. If the file has come from Vmware Server or Workstation it should still have a descriptor file with it - without it you are stuck. If you dont have both files, I am not sure that you can convert it using Vmware convertor - you would have to try that one for yourself as per the previous advice. You could try recreating the VMDK descriptor for the flat file. There is a VMware KB on how to do this: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1002511 If you found this helpful, please consider awarding some points
Place the CD in the drive on your laptop/desktop where you have the VI Client installed. Edit the settings for the VM and make sure the CDROM drive is configured for client connect. Power ...
See more...
Place the CD in the drive on your laptop/desktop where you have the VI Client installed. Edit the settings for the VM and make sure the CDROM drive is configured for client connect. Power on the VM, press the ESC key at the boot screen to get it to wait. You can then select to connect the local CDROM drive to the VM (see the attached screenshot). Once connected, you can then selected CDROM as the bootdevice from theboot list in the VM and you should be good to go. In the PIC, drives D and E are two local cdrom drives on my desktop. If you found this helpful, please consider awarding some points
SuryaVMware is absolutely spot on with his suggestion. I went through the same scenario on the 3750's a few months back myself. If you found this helpful, please consider awarding point...
See more...
SuryaVMware is absolutely spot on with his suggestion. I went through the same scenario on the 3750's a few months back myself. If you found this helpful, please consider awarding points
Connect directly to the host and re-add the storage, dont do it through Virtual CEnter and you should be fine. This has been documented as a bit of a 'feature' before. If you found this...
See more...
Connect directly to the host and re-add the storage, dont do it through Virtual CEnter and you should be fine. This has been documented as a bit of a 'feature' before. If you found this helpful, please consider awarding points
The actual sysprep files dont need to change, you can use the same on the VC server. For the customisation spec, you could have one for spanish, one for english, or you could create a sysp...
See more...
The actual sysprep files dont need to change, you can use the same on the VC server. For the customisation spec, you could have one for spanish, one for english, or you could create a sysprep file that adds support for both languages and import that in to the customisation spec wizard. If you found this helpful, please consider awarding points
If the guest account was disabled before you P2V'd it then it is still disabled now. You should enable it on the physical PC, ensure local security policies allow you to login and then re P2V i...
See more...
If the guest account was disabled before you P2V'd it then it is still disabled now. You should enable it on the physical PC, ensure local security policies allow you to login and then re P2V it. or, at your own risk, you could try using this utility to reset the password and enable the account Offline NT Editor If you found this helpful, please consider awarding points
I would have another look at vReplicator - I have used as well as others in the Xtravirt team and certainly with the latest release we have had good results. You dont need to worry about a...
See more...
I would have another look at vReplicator - I have used as well as others in the Xtravirt team and certainly with the latest release we have had good results. You dont need to worry about a static MAC for licensing unless you really want to, it makes no difference to VC licensing. When the IP address changes you should be ok. If you found this helpful, please consider awarding points
Sorry Chris, I have no idea what I was on earlier when I answered this! Taken from the Convertor 4 manual - you have to download a previous version (eg Enterprise 3.x) to get the ColdC...
See more...
Sorry Chris, I have no idea what I was on earlier when I answered this! Taken from the Convertor 4 manual - you have to download a previous version (eg Enterprise 3.x) to get the ColdClone CD Prepare for Cold Cloning Because VMware vCenter Converter Standalone 4.0 does not support cold cloning, you must use an earlier Converter edition boot CD. The features supported on the boot CD depend on the product version you choose. VMware Converter 3.0.x Enterprise edition is not a free software product. Procedure 1 To obtain a boot CD, go to the VMware Download Web site and download Converter 3.0.x Enterprise installation. 2 Extract the boot CD .iso file from the installation package. 3 Burn the boot CD .iso on a CD. Apologies for misleading you. If you go here -> Right to the bottom, select VMware vCenter Converter 3.0.3 (Standalone Enterprise Edition) and you can download from there. Hope that clears it all up for you If you found this helpful, please consider awarding points
Hi, Have you consolted this KB Article? Memory values returned during Registry inventory collection on Windows may occasionally be incorrect or unreliable. To resolve this, use...
See more...
Hi, Have you consolted this KB Article? Memory values returned during Registry inventory collection on Windows may occasionally be incorrect or unreliable. To resolve this, use the WMI collection method instead. If you found this helpful, please consider awarding points
Point your web browser at the IP address of your ESXi host. On the webpage that loads there should be a link to the VI Client. Download and install that for a decent management GUI ...
See more...
Point your web browser at the IP address of your ESXi host. On the webpage that loads there should be a link to the VI Client. Download and install that for a decent management GUI If you found this helpful, please consider awarding points
It could be an issue with the version of converter you are using. From the 3.0.3 release notes, in the issues section: New Task fails for remote Windows source machine when you navigate ba...
See more...
It could be an issue with the version of converter you are using. From the 3.0.3 release notes, in the issues section: New Task fails for remote Windows source machine when you navigate back and forth in the Conversion wizard When all of the following circumstances exist, the physical source machine does not reboot: You are remote hot cloning a Windows NT4 or Windows 2000 source machine The agent is installed on the source machine, but the system has not yet been rebooted You change the source selection and change back to the original source before you click Finish in the Conversion wizard In this scenario, the task fails with a snapshot failure error message. The reboot is necessary to start the snapshot service on the remote source machine so that Converter can take the snapshot of the machine. You could try using the converter 4.0 standalone version and see if you can reproduce the fault. If you found this helpful, please consider awarding pointsIt
The release notes for Converter 4 state that ESXi 3.5 is a supported target so in future you will just be able to select ESX for the destination and you will be fine. In this instance, you...
See more...
The release notes for Converter 4 state that ESXi 3.5 is a supported target so in future you will just be able to select ESX for the destination and you will be fine. In this instance, you can select the VMware Workstation or other VMware Virtual Machine opton and store the P2V'd machine on a Windows share. You can then use converter again later on, to convert the VM in to an ESX format. The user guide for the product says this is possible and supported. If you found this helpful, please consider awarding points
Assuming you have configured some LUNs on your storage itself you will need to ensure that the HBA Fibre Worldwide ID's on the ESX host (you can see them listed against the fibre HBA under stora...
See more...
Assuming you have configured some LUNs on your storage itself you will need to ensure that the HBA Fibre Worldwide ID's on the ESX host (you can see them listed against the fibre HBA under storage adaptors, WWID) are configured on the fibre switch for access (read and write). In the VI Client connected to your ESX host, select the Storage Adaptors tab and highlight the Fibre HBA. Right click it and select Rescan. If you have configured the SAN and Fibre Switch properly, then the LUNs will now be listed under the Fibre HBA. Go to storage and select add storage. Follow the wizard through to add the LUNs and format as VMFS. Do this for each ESX host you want to see the LUNS on. If you found this helpful, please consider awarding points