vSphere Client will not give you same funtionality as vCenter Server.
So if you try to connect to host directly with vSphere Client and try to convert VM to Template you will not get that option to convert to template.
Instead you can try vCenter Converter.
Hi Alan,
No, you can't do that. I mean, the changes will be lost when the sync starts. Here are some internals of how it works: Every conversion consists of data cloning and reconfiguration. Reconfiguration is needed to enable the VM to boot. Synchronization keeps track of modified data on the source and transfers only them. However, reconfig has made changes to the disk, too and this can create inconsistency. To work around this, a snaphot of the VM is made right before reconfig and the VM is reverted to that snapshot right before the sync starts.
Regards,
Plamen
Ciao,
Nel primo caso puoi aggiornare a ESXi 5 se hai il supporto ancora attivo.
Puoi utilizzare anche la licenza vSphere 5 che avanza. In questo caso puoi anche gestirlo dallo stesso vCenter.
Ciao
Francesco
--
www.thevitualway.it
Here is the correct answer to my problem: VMWare Workstation 9 does not support iSCSI booting. It requires "PXE chainloading", where PXE loads to a gPXE (or iPXE) image gives VMWare PXE the ability to bootstrap an iSCSI target. Here are some valuable pages I found on the subject, though none show my specific "PXE boot CentOS from Debian iSCSI in VMWare Workstation 9"... guess I may be the one to write that tutorial up!
PXE Booting Ubuntu from an iSCSI drive
http://www.heath-bar.com/blog/?p=184
Setting up PXE chainloading
pxechaining - Etherboot/gPXE Wiki
Using iSCSI On Debian Squeeze (Initiator And Target)
http://www.howtoforge.com/using-iscsi-on-debian-squeeze-initiator-and-target
Puoi configurare il mittente accedendo a "Home > Administration > vCenter Server Settings", qui seleziona l'opzione "Mail" e modifica il campo "Sender".
Ciao
--
Rocco Sicilia
You are brilliant! I'd kiss you if you were right in front of me!
Ok, so I managed to uninstall Avast and reinstall VMware Player. Now, however, when I try to open my ISO I get an "Error while powering on: Transport (VMDB) error -44: Message.
The following error occured when starting VMWare Player.
W32AuthConnectionLaunch: Reply error "Process creation failed".
I'll go over the link you posted to see if I can find anything there.
EsattoEsatta atto io ho impostato proprio li la mail corretta ma essendo la vcenter all'interno di un dominio locale le mail escono con root@dominio.local anche se impostata la mail corretta.
That worked. Many thanks!
Any idea? Thanks.
Ok, I right-clicked and ran as system administrator. I think that has solved my issue. 
*Keeping fingers crossed*
Someone knows? Thanks.
Qui hanno il tuo stesso problema: http://communities.vmware.com/thread/345352?start=0&tstart=0
Il dominio che utilizzi nel Sender deve essere risolvibile dal server SMTP a cui ti appoggi e viene inoltre suggerito di utilizzare il FQDN per il server SMTP.
--
Rocco Sicilia
Are you sure you need reservations (i.e. you are overcommitting resources)?
Unless you already did, take a look at http://www.yellow-bricks.com/vmware-high-availability-deepdiv/ which explains the different admission control settings.
André
It seems the RAID controller in your system is not a real hardware RAID controller, but a software (fake) RAID controller, which requires drivers in the OS to operate. ESXi only supports hardware RAID controllers which transparently present the physical disks as a logical volume to the OS.
André
I was running a Linux Mint 15 virtual machine in WorkStation 9.0.2 on a Win7X64 host.
The vm has the tools installed with file drag/drop enabled.
I was going to transfer an ssh key file by dragging it from the linux file manager to Windows Explorer.
This is a simple text file and not very big.
What happened is this:
1) The file icon moved with the mouse to the edge of the virtual machine.
2) Then the move stopped with the icon half remaining on the vm
3) Now WorkStation 9 is totally unresponsive, nothing I do seems to affect it in any way.
4) After a minute or two the laptop fan comes on whirring like mad
5) Taskmanager shows the vmware.exe process running at 12% CPU (never changing)
Total memory usage stays put at about 4.2 GB out of the 8 GB RAM available.
Now I can do absolutely nothing in WS9 to stop this, seems like the only way out is to use TaskManager and kill vmware.exe, but that will probably corrupt my virtual machine...
What the heck is causing this and how can I get out of it???
EDIT:
After about 10 minutes the vm (which uses bridged networking) caused my main machine to completely lose network access too!
So I had no choice but to use Windows task manager and kill the process. 
Network now back again so I can post this edit, plus fan back to normal speed.
I think that this is exactly what NAT does. The host just acts as a router with Network Address Translation from the guest onwards out to the network the host is connected to.
If you want a network connection to the guest that will not do this and will not be lost if the host cannot get a network connection (i.e. to a WiFi router) then I think your only option is host only networking.
This isolates the connection between host and guest from all other connections but it stays put no matter what.
On the downside: The guest will not have Internet access.
I have used this a lot when I did not want to use bridged networking since it would clutter up the router (especially at customers) and my only need was to be able to communicate host-guest.
openSUSE 13.1 (Factory) VM - VMware tools install with kernel 3.9.4 perfectly. Just grab the devel files.
I've been doing some pretty solid labs using Workstation. Fusion is catching up with the network editor. I created this post to show how to running a nested vCenter Server inside of ESXi inside of Fusion. It's a start to some of the more complex scenerios.
I have a VMXF file, but I can no longer load my VM when I add in the code you mentioned. I know this wasn't an issue for the others that I gave the code to.
