Plain Virtualization

Was doing a Proof of Concept for Horizon View at one customer with a partner.  The infrastructure was setup and network trunked on the uplinks. We started out deploying all the components leveraging on customer's Active Directory, DHCP server and as well as Database. All was well and setup but two things was encountered: Every Desktop pools will always have some desktops not getting IP address. Horizon View client receive connection error after choosing a desktop or while using a desktop. Spend a bit of time troubleshooting by the partner.  Things like using a Windows DHCP instead of Linux (customer's was linux DHCP) and putting Horizon View Connection Server in the same subnet as the Desktops. I took over to see what have gone wrong since my partner has already done so many work.  Did some tests with my colleague, Wei Chiang who is strong in networking.  We managed to isolate the issue and even set static IP on those Desktops that does not have IP howeve...

Recently many new channels has articles on the code leak and you can see the official announcement here .  VMware has also release ahead of patch cycle as well documented here . Many users asked about the concerns they have.  First and foremost, won't open source be also a concern if we were to use it as well? Every organization would have in place certain regulation and policy in their infrastructure be it hardening, patches to be up to date and firewalls, etc.  If these are been follow up and maintain compliance, is there much of a concern really? One article from Michael White, a VCDX makes really good sense and encourage you to have a read. This single file from ESX code dating to 2004 was leaked and I wonder who much vulnerabilities that wasn't discovered from VMware regular patches till now 8 years later.  If any of the environment are still vulnerable due to this leak this will be disastrous and it can only see how back dated the servers are not keep ...