Yes thanks for your advice i download 2.1 today and try to upgrade this version to 2.1 .
In features we are using thin app infect all modules but i deploy this a fewer days ago so configuration is still remaining for web applications , mobile applications
after that i want to deploy the VMWARE Mirrage also so onward
If you want the Virtual Machine to connect to the Internet then set its Network Adapter to either NAT or Bridged in the Virtual Machine's Settings! 
Hi,
Sadly, I don't think it's possible to control the step or page visibility dynamically at this point (v6.0.1). I have tried to do this also and the only elements whose visibility can be controlled are individual fields. Even with those, I encountered some limitations with some actions working perfectly in vCO itself but not having any effect when the workflow was imported in to vCAC as an ASD item.
Michael
Just installed Yosetime on my iMac and now I am having problems running the Windows 8.1 program in my fusion virtual machine.
Everything was OK before installing the new Mac operating sytem.
Any suggestions please?
Ron.
You have 512GiB (binary) SSD, that is 512 * 1.073.741.824 bytes
Out of this, you see 512GB (decimal) capacity, that is 512 * 1.000.000.000 bytes
This is ~7% factory-set overprovisioning.
That is apparently not enough in case you do not have TRIM (as in HW/raid1). Write-amplification factor is very high for just 7% OP (about 6-7). It means, for every MB you want to write (from system), 6-7MB are written. It could shorten your SSD-life signifficantly. But write amplification factor drops to 3 (which is quite acceptable compromise) at about 27% OP (page 11 of the above mentioned pdf).
So it is advisable to add 20% "user-level" overprovisioning. The way to achieve this with raid is that you pick SSDs (in WebBios, or Megaraid Storage Manager, or StorCLI/MegaCLI), but you do not use its whole capacity for raid-array, but just about 80%. Beware: SSD must be in "factory-reset" state (never used, nothing written); if not, you have to re-set it first. That remaining 20% will be left as "unused", and controller will use it for wear-leveling, garbage collection, etc.
After that, when raid-array is constructed (with only ~80% of SSD capacity) you create partition/s (using all the capacity array is reporting), and format it. How much real space remains depends on filesystem you use (block/subblock size, metadata, etc).
I did log in, but still wasn't able to download it! thank's for the link, finally started downloading 
JarryG wrote:
You have 512GiB (binary) SSD, that is 512 * 1.073.741.824 bytes
Out of this, you see 512GB (decimal) capacity, that is 512 * 1.000.000.000 bytes
This is ~7% factory-set overprovisioning.
That is apparently not enough in case you do not have TRIM (as in HW/raid1). Write-amplification factor is very high for just 7% OP (about 6-7). It means, for every MB you want to write (from system), 6-7MB are written. It could shorten your SSD-life signifficantly. But write amplification factor drops to 3 (which is quite acceptable compromise) at about 27% OP (page 11 of the above mentioned pdf).
So it is advisable to add 20% "user-level" overprovisioning. The way to achieve this with raid is that you pick SSDs (in WebBios, or Megaraid Storage Manager, or StorCLI/MegaCLI), but you do not use its whole capacity for raid-array, but just about 80%. Beware: SSD must be in "factory-reset" state (never used, nothing written); if not, you have to re-set it first. That remaining 20% will be left as "unused", and controller will use it for wear-leveling, garbage collection, etc.
After that, when raid-array is constructed (with only ~80% of SSD capacity) you create partition/s (using all the capacity array is reporting), and format it. How much real space remains depends on filesystem you use (block/subblock size, metadata, etc).
Thanks for the reply.
Sorry to be ultra pedantic about this but I want to make sure I do this correctly!
Lets say I start with 512GB SSD drive. Its a brand new drive with no data on it. So I connect it to RAID card and go into WebBIOS. Now I start configuring drive in WebBIOS as a SINGLE drive in RAID0. So when I add the drive do I add it with 409GB (512GB x 20% OP)? Therefore I will have a 409GB drive listed on the RAID card?
Assuming the above is correct: Now in ESXi I create a new datastore and add the 409GB SSD drive as storage. Do I need to keep 20% of the 409GB datastore free as well??
VmWare reports "Lost access to volume due to connectivity issues" and it does not recover from it. Problem occurs after random periods of time. Sometimes after few hours, sometimes after few days. Only solution is to hard reset the system. What could be the probelm?
System info:
Supermicro X9DR3-F
2 x Intel Xeon CPU E5-2680 v2 @ 2.8Ghz
64GB RAM
VmWare ESXi 5.5.0., 1331820
3ware-sas-9750-8i RAID controller, RAID 10 with 4 x 3TB RAID Edition disks
Best regards,
Goran Vrabec
"...Do I need to keep 20% of the 409GB datastore free as well??..."
No. It is enough to have 1x 20% (you saved in WebBios), not twice. Apart from that, I do not see any reason to have single drive in raid0 (if it is possible at all). Instead of that, you can configure it as single JBOD. That way you omit all those raid-array metadata...
ronniebootwest wrote: Everything was OK before installing the new Mac operating sytem.
If everything was fine before then why'd you upgrade!? (Rhetorical question, no need to answer!)
Any suggestions please?
Have you tried uninstalling/reinstalling VMware Fusion?
Some of the other threads on the same issue suggest try reinstalling OS X.
`sdelete -z` will zero out the space on your Windows guest's volumes by creating a (hidden) file called SDELTEMP on the destination volume and filling it with zeros until the volume runs out of space. Thus, it is functionally equivalent to `dd if=/dev/zero of=/zerofile; rm /zerofile` commonly used on Linux platforms for this purpose. You only should do this on guests where either a brief out-of-space condition is not an issue to the running application set or where you can schedule a downtime for the process. As the amount of zero data written may be quite large, it might be difficult to exactly predict when sdelete's zero file is going to create disk space shortage to impact applications.
As the `sdelete -z` run is going to inflate the thin virtual disk to its maximum configured size, you need to make sure the VMFS datastore the disk resides on does indeed have enough space to accommodate the inflated virtual disk. You also should delete all snapshots you have created for the virtual guest in question beforehand. Last but not least, do take the additional I/O strain on your disk array into account - `sdelete` does not allow for I/O throttling and will write out zeros in large blocks as fast as it can.
After I update to Mac OS X Yosemite, I failed to open VMware Fusion 5, it shows
I tried to uninstall the VMware, restart the Mac, and install the VMware again, but still this problem.
I searched in Google and found another article discussing about this before, the solution is as below:
I can not find the below applications in my Mac, so can not uninstall. Anyone has my issue after upgrade to Yosemite?
----------------------------------
Looking further back in the support information bundle's history gave me a big clue. It seems that some driver on your system is triggering the problem by consuming all of the available "character device major numbers" (a small number used to identify a driver/device). I can't immediately identify the culprit driver, but the possibilities include:
We have quite a few users with VirtualBox alongside Fusion, so I doubt that VirtualBox is the cause, or I'd expect to have seen more widespread reports of this problem, unless it's being exacerbated by some other environmental factor.
It's also possible (although less likely) that it is a problem with one of the drivers built in to Mac OS, or it might even be one of the other drivers in VMware Fusion, but – again – in either of those cases I'd expect to have encountered more reports of the problem unless it's triggered by some other factor on your system.
Could you try temporarily uninstalling either the SNS iSCSI initiator or Viscosity VPN and see if that helps?
Cheers,
--
Darius
Fusion 5 - Could not open /dev/vmmon: No such file or directory.
-------------------------------------------------------
VMware Fusion 5 is not supported on OS X 10.10 Yosemite! At the present time VMware Fusion 7 is the only officially supported release on OS X 10.10 Yosemite!
JarryG wrote:
"...Do I need to keep 20% of the 409GB datastore free as well??..."
No. It is enough to have 1x 20% (you saved in WebBios), not twice. Apart from that, I do not see any reason to have single drive in raid0 (if it is possible at all). Instead of that, you can configure it as single JBOD. That way you omit all those raid-array metadata...
Ok, I will reserve 20% then for OP. Thats very helpful.
The only reason I have the RAID card is for the caching since ESXi doesn't do this. So can I setup this card in JBOD mode AND use the cache to improve the performance in ESXi?
You can setup a single disk on the M5015 in RAIDo as I have done it when testing with my two SSD drives. If theres a better way to do this in JBOD (with caching) then I would like to hear about it please
Is it necessary to keep any free space in an ESXi datastore? If so how much?
>>> Can it be a certification issue ?
It could be a communication issue. I found some older discussions where issues with the same error message were solved by rebooting the ESXi host. If this is currently not an option for you, maybe restarting the management agents on the host will already help. Just a guess, but maybe worth a try!?.
I moved the discussion, because I think you may get more feedback for this issue in this community. If you want me to move the discussion back to the original place, please let me know.
André
Please check whether the add-ons are properly loaded, i.e. not blocked by e.g. the A/V or the browser. See vSphere 5.5 Documentation Center for more information.
André
at this time, Persona management does not support RDS apps or desktops.
cheers
peterB
Thanks, Woody. I uninstalled the VMware Fusion 5 and installed the 7 to solve this problem. The only one problem is that I bought the license key for 5, and now I can not use it for 7.
I have the same issue. the solutions for me was temporary disable the McAfee HIPS (firewall). with this process the VMware Workstation was 10 able to create the failing registry Keys.
Hi there,
I am having a problem with a two host ESXi 5.1 cluster that seems to be becoming more frequent. The hosts are hanging up (purple screen) and having to be rebooted. Debugging is available when the hosts hang and they can be rebooted from the debugging tools menu. I have attached the purple screen error from one of the affected hosts as well as some excerpts from the vmkernel log.
I won't go too much into the specifics of the setup as I could spend all day listing the most minute details. However I can answer any questions about those specifics if relevant.
Thanks in advance.
