Microsoft has released new patch for Windows Server 2008 R2 SP1 and Windows 7 SP1, on the March 13th 2018. I some cases this patch will VM's running these OS, loss there VMXNET3 nic, at get a new one, using DHCP. VMware has published a Blog about the problem, and in this blog there is a referance […]
I have been looking for this for at long time and there are some script on, VMware forums and other places, that can do this, but I was satisfied with them, since they did not give me all the information i needed. So began to peace some of them tougher to a new one, And this […]
VMware has announced that the next number version (not update) will be the last version to have a Window vCenter version, vSphere Web Client (Adobe Flash) and support for old Linux style /O drivers. vCenter on Windows VMware introduced the vCenter Server Appliance (vCSA) back in version 5.0. I did not use vCSA version 5.0 and 5.1 at […]
You can now sign up for the Public Beta of the Veeam Agent for Microsoft Windows 2.0. System requirements Hardware CPU: x86-64 processor architecture. Memory: 2 GB RAM. Disk Space: 150 MB for product installation. Network: 1 Mbps or faster. High latency and reasonably unstable WAN links are supported. System firmware: BIOS or UEFI. Drive encryption: […]
I had a customer with a problem where he could not upgrade VMware Tools on a danish localized Windows Server 2008 R2. The solution was to change it to US localized and choose to copy the setting to: “Welcome screen and system accounts” and “New user accounts”. And after upgrading/installing VMware Tools change it back […]
I had a customer call me, that after they updated there ESXi hosts with patches from VMware and afterwards upgraded VMware tools on a Windows 2008 R2 server, the machine lost it's default gateway Trying to configuring it again, just resulted in the default gateway field being blank after enabling it. There where more then one […]
I have had a number of Customer experiencing that when there Virtual Windows Machines reboots or are booted, they may come up with an APIPA address (169.254.x.x) this is due to a problem with Cisco switches. But here is a solution that is described in a VMware KB: KB1028373 Share This: