My problem is caused by having some RDM LUNs sync'd besides the one used by my test VM. It works fine with just the one LUN being replicated.
I'll work on this...
EDIT - yes, I needed a VM in the protection group that had access to all of the LUNs in the consistency group. I was being careful, and tried it with a test VM, which did not work - but it works fine with the "real" VM.
I think I can say that this is working now - for a test failover. Next we have to try a "real" datacenter migration.
So, did some defrags and another sdelete, when trying vmkfstools -K it does this:
/vmfs/volumes/4ee2394e-69bbfe1d-ccd5-1cc1de6ce910/HD-SQL-02 # vmkfstools -K ./SQL-02_1.vmdk
Hole Punching: 2% done.Could not punch hole in disk './SQL-02_1.vmdk': Function not implemented
Which i have no luck looking up. using vmkfstools to clone the disk to another volume also does not shrink the disk, stays the same size.
Converter will shrink it, leaving me with a 19 GB thick disk that i just clone to thin, that's what i did with the last VM also.
Dear MKGUY,
if i run this command vmware-toolbox-cmd timesync status then it shows Disabled.
if i want to synchronize linux guest vm with esx host then i have to check the "Synchronize guest time with host" checkbox, is it correct???
Please help me with the same.
regards
Mr VMware
Are the VMware tools installed on the VM level, or is it at the player level - that is, it is common to all VM on a given host?
When VMware Player is initially installed it's done so without VMware Tools installed. Typically when you install a Guest OS in a Virtual Machine and you choose to install VMware Tools, or during an Easy Install, if the appropriate VMware Tools ISO Image hasn't been downloaded from VMware then it's downloaded and installed on the Host. As an example you install VMware tools in a Windows Guest then VMware Played downloads an executable from VMware's Server and when this file is executed in the background the windows.iso file and the windows.iso.sif file are extracted to the working directory of VMware Player. The windows.iso file gets attached to the VM's CD/DVD and then VMware Tools gets installed in the Windows Guest. The installation on the Host and the installation on the Guest are two separate processes. The install of VMware Tools in any given VM is not hooked to any other VM as each VM (other then linked clones) are totally separate and apart from each other and by default have no bearing on any other VM as far as it's install goes. Obviousy if you have limited RAM and are running multiple VM's the it can have a performance impact on each other however creating a new VM and installing an OS in that VM has no bearing on existing VM's provided you didn't add an existing virtual hard disk from an existing VM! 
As for the second part of your answer you probably right... the message is:
Bad Image (error code c000007b)
The Application or DLL \??\c:\windows\system32\DGI32.dll is not a valid windows iamge. Please check this against your installtion diskette.
Well, have you done as the error message suggests?
Hi All ,
I have a Vcenter Setup and having one ESXi host . When i am trying to clone a VM residing in the ESXi via Powercli , its giving error not able to find storage datastore1 . Below is the command i gave from vCenter .
Powercli > New-VM -name clone1 -Datastore datastore1 -VM <sourcevm name> -VMHost <ESXI name>
New- New-VM Unable to get objects by name: server <ESXI name> not connected .
New-VM : New-VM Could not find StorageResource w
ith name 'datastore1'.
But I was able to do the cloning from Vsphere GUI .
Note : Datastore1 is local storage in ESXi host .
Regards
Deb
Does the View connection server modify RDP when it's brokered through the connection server? I had a user (off shore) say that they're getting better performance from RDPing (8) directly instead of using the view client.
Thank you!
Thanks for your answer
hello,
i cannot introduce my license key, please check out this video to see my problem
many other people have the same probleme
thanks for your help 
Xunty, what do you mean ? This is not a guide, here I just descrebed my issue. What had worked for you ?
Hi ,
I ran all the commands after connecting to Vcentre .
But PowerCLI C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI> $default
:globalviserver returning nothing .
Thread moved to the PowerCLI COmmunity.
It looks as if you are not connected to the vCenter.
Can you check what is in
$global:defaultviserver
If that is empty, do a
Connect-VIServer -Server vcenterserver
Sorry, that should be
$global:defaultviserver
A picture is worth a 1000 words . This is typical of what I am use to seeing. Could possibly be a firmware bug that is just a small timing issue. The mouse input in a soft client vs. a hardware zero client is very different so seeing different behavior is not surprising. This also is not specific to a 3D GPU backed desktop or a 2D based desktop.
I can get mine dialed back in by adjusting my zero client settings. From the login dialog of the zero client go to Options, User Settings, Mouse. Set the speed to the second lowest option. You will loose some range of motion but the mouse pointer will stay in sync with the window drag / on the title bar.
The lowest setting was two slow for me and the 3rd setting still left some delay.
WP
Welcome to the Community - I have moved this to a more appropriate forums-
Its returning the expected value for VCenter server.
the first time password enters becomes the MASTER password. There is no UI to set it explicitly.
Also for multisite, the SSO local users/configuration will be lost if the proper replication steps are not followed:
Regards
Girish
Hi, thanks for the reply. I only run in bridged mode so they have been like that since build. I do however use locations though as I have multiple places without DHCP. I'm therefore stuck with that.
I've tested the same build on an alternative virtualisation package and it works immediately. Given that I was running trial versions of Fusion and the 'Other' and one works then unfortunately I've moved to go the other way for now.
Anybody??
Alright, I need a quick sanity check.
After going through the steps in KB 2034833, I've managed to update all of my SSL certs for everything else without issue. There were no errors in generating the requests, the certs themselves, and the actual process replacing them on the SSO, inventory service, vCenter Server, web client, log browser, and orchestrator.
When I get to Update Manager, I've used the automation tool as well as the manual process. The correct certs are in the SSL directory, and there were not apparent errors when updating using both methods. Yet, after restarting the service, I can open my vSphere client and still get warnings about the certificate from my update manager server. Looking at the certificate, it appears to be a fresh SSL cert generated when the services were restarted.
I've searched high and low for any indication that there's a bug. I can't seem to find a lot of data regarding this particular issue, save for 1 communities posting that was never answered. Right now this is my only snag. We have local risk requirements that state I have to change these certs to valid CA signed ones. I would hate for us to have to uninstall update manager just because we can't get cleared for compliance.
Anyone have any insight? Suffice it to say I've followed the KB where you use the utility / update the host DNS so that you can connect to a vCenter on a different VM, as well as the automation tool. The certs are valid and I made sure they have the right flags.