Hi all Requireent If you have to install the VMware Horizon View Agent outside a VM (or a phyiscal PC) not managed in vCenter you have to use the following command: Soution in VMware Agent VMware-viewagent-Y.Y.Y0-xxxxxx.exe /v”VDM_VC_MANAGED_AGENT=0″ If you then create a manual desktop pool in the VMware Horizon View Admin you will see the desktop listed in “Other” sources. Hope this helps other out there in the jungle 🙂

Dear all As you know, Microsoft has changed their licensing model to a core-license model regarding Microsoft Server 2016. HPE has a really nice calculator to help you and understand, what you have to license. Check out the link: Calculator Link http://h17007.www1.hpe.com/us/en/enterprise/servers/licensing/#.WVURket97mF Regards vm-up – Team

Dar all Last week I had following Task: „Find on all our system, where the Domain Admin is used“. And there is a simple answer: http://www.cjwdev.com/Software/ServiceCredMan/Info.html Hope this helps other out there. This utility is very helpful. Regards

Dear all Issue Today a customer called and told me, that he had some issues with access to vCenter from certain networks. After some research we found a wrong (old) default gateway enty in the vCenter. As it was VCSA 6.0 we had no VAMI at this time. So we used the console, but the menu for changing the gateway did not shown up. Access through shell and fireing up the vami in console with:

1

/opt/vmware/share/vami/vami_config_net

gave us a lot of errors. Solution Solution was to change the gatewy with the following line

Hi all Short info: In the Veeam documentation I found a PowerShell script, that helps you to enable BitLooker on all your Veeam jobs. Very helpful if you have more than only 5 jobs 🙂 Script (also in the Script Section)

Dear VMware User Today a customer called me and showed me following error (Veeam & VMware logs): Error A general system error occurred: Failed to write header to “/var/log/vmware/journal/1487689997.1: Error while writing to file. There is no space left on the device Reservation destination directory Solution Solution was to move the logs away from the scratch partition (in our case a 4 GB SD card) to a persistent scratch location (i.e. a VMware datastore) More information on the VMware KB site: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2003322