I beleive you are referring to SE sparse disks, this gets invoked when you choose to reclaim space from Horizon View(only).
Following blog provides some commandline option to create this directly on the host but is not supported yet
http://www.virtuallyghetto.com/2012/09/how-to-create-se-sparse-space-efficient.html
It's working fine for me - I used the link for the blueprint on this page: http://mylearn.vmware.com/mgrReg/plan.cfm?plan=30483&ui=www_cert
Hi Scott,
Seems something is wrong with my login then. I am getting the attached error when i click on blueprint link. Could you please confirm that the version there is still 1.1 or has it changed.
Thanks - AG
Joe5 wrote:
It seems like I need a way to determine the change log size. Is there a way to determine the change log size?
Your snapshot size will be a temporary file with the same size as the VM memory + a temporary file of ALL writes done to the virtual machine during the snapshot time. You could think of the original disk being in read-only mode and a "delta file" will catch all new writes instead.
Since every VM and every application is different there is no way to tell this in advance, but you could to do a simple experiment like monitor, with perhaps Performance Monitor if using Windows, how much writing is done in for example one hour in the night time where the backup is likely to take place.
gianlucab wrote:
Esxi need to use a vmkernel as dedicated nic so doesn't permit to tag other vlan ad use the 'same nic 'for other treffic in other vscwitch' ?
There are no requirement to have a dedicated nic for anything actually. You could run Management, vMotion, iSCSI, NFS and VM traffic all over a single physical NIC port.
However, since this would make many important functions dependable of the network usage rate of the others this is most often seen as a bad practice.
A common way to set up the vSwitch0 is:
Attach two "vmnics" = physical nic ports, use default NIC teaming Port ID, make no link aggregation at physical switch.
VMK0 - management - vmnic0 active, vmnicX standby
VMK0 - vMotion (other IP range!) - vmnic0 standby, vmnicX active
If possible use a separate and isolated VLAN for the vMotion network, and if already having a management network put the VMK management interface on that management VLAN as well.
Was spending a lot of time on it before I found this post. Thanks!
If you search for the buildnumber you usually get a hit on the releasenotes for that version.
// Linjo
Where did you found that document? Please provide a link since that is plain wrong.
Horizon Workspace 1.0 does not support XenApp Applications.
// Linjo
The following KB article correlates build numbers to ESX(i) versions:
Correlating vCenter Server and ESXi/ESX host build numbers to update levels (1014508)
thanks so much!
I can now verify that this is working perfectly - and much faster than it was last week. An entire recovery (not test plan) of 3 VMs and 4 LUNs is only taking around 3 minutes, and then < 1 minute to "reprotect".
for the sake of having all th einformation in one place:
Here are the versionn I'm using:
IBM v7000 Version 6.4.1.2 (build 75.0.1211301000)
vCenter 5.1
SRM 5.1.0-941848 on Windows 2008 R2 64 bit (2vCPU 8GB RAM)
SRM advanced settings
I have set the Advanced Settings option:
storage.Commandtimeout to 1800 (def 300)
storageProvider.hostRescanRepeatCnt to 2 (def 1)
storageProvider.hostRescanTimeoutSec 600 (def 300)
SRA v2.1.0.121224
non-preconfigured environment
Pre-Configured Env. not set
Test MDisk Group ID set
SpaceEfficient Mode = true
I hope this is of value to someone
Discussion moved from Virtual Lounge to VMware ESXi 5.
Hello VMGurus,
I am using following link to get vm information and it's working
http://communities.vmware.com/message/2100780#2100780
the only problem is I am not getting the guest OS edition and version, using this script I am getting OS which I've selected during the creation of VM.
is there any way that we can incorporate wmi caption in this script and get exact OS edition and version like in wmi caption?
thanks in advance for your help.
Regards,
Samir.
WoodyZ,
The question was regarding the principle of boot from USB technique ...as eventually another VM is loaded.
How does it enable watching the files in the broken VM
Anyway - I still feel it wa a VM ware issue but I have decided to drop that
Thanks a LOT for your help 
With
Get-WmiObject Win32_OperatingSystem -Computer $vm.Name
you can get the class with the OS info.
Which properties do you want to include ?
hi LucD,
thanks for your prompt reply, I want to include Operating system caption, sp and architecture
I've tried following
$VMInfo.OS = (Get-WmiObject -computername $vm -class Win32_OperatingSystem).Caption but it's not working.
I don't know how to use this, if you can help I would be very thank ful to you.
Thanks,
Samir
OK, we'll take a look at it. Unfortunately, due to a large number of official holidays at the beginning of May (Labour Day, Easter, etc.) there vill be very low activity from vCO team (if any at all) till May 7th.
I'll file a PR to track this issue.
I just started to do some testing on our test upgraded 9.1.5 system. We customise the email Message templates quite a lot and they no longer seem to be working the same in 9.1.5.
Attached are some screenshots showing where it is no longer displaying correctly, along with a copy of the html template file.
Note, I know it’s bad practice to put the Style section in the Body, rather than then Head, but this seemed to be the only way of getting this to work in 9.1.2. All of the message templates for the emails sent out from the rest of the application I put the Style in the Head and it worked OK; it’s just the templates used on this “Email” window from within a call I had to make the change on and put it in the Body. I’ve tried putting the Style back into the Head on these templates as well on the test 9.1.5 system and it displays the same (i.e. without any of the styles applied)
Any idea’s if we can still do this kind of styling on these message templates in 9.1.5?
Thanks, Ian
Hi,
I'd review the "fixes" list and see if any relate/could potentially relate to your current environment
If not hold off for a couple of wks just in case there is any "emergency" hotfixes published over the next couple of wks.