Virtual Machines

This is something that has bugged me for a long time. When you use RDP (Terminal Services) to connect to your VMWare host console, seemingly at random, the cursor will move significantly slower on particular VMWare guest systems. For me, the problem usually occurred on Windows XP and Windows 2008 guest systems.

Just a quick heads up that might keep you from diving into the shallow end of the pool.

One of my customers that are running Notification Server on ESX, ran into this scenario recently:

Recently, VMware released their Update Manager to handle patch management of ESX servers.

For those of you who haven't implemented it, here's a setup of reasonably robust scripts to do the patching via the Deployment console.

As we prepare for a new deployment of Deployment Solution 6.9, IT personnel may encounter difficulties using WinPE 2.x in conjunction with VMWare network drivers. In addition, as more and more users try to virtualize their environments, Microsoft Vista users might find themselves without networking in VMWare Virtual Machines.

There is little known work-around for this issue: make the virtual machine load up the Intel e1000 network driver. Forcing this change will make virtual machines think they have an e1000 network driver and load up the network. This also prepares Virtual Machines to run automation jobs in a pre-boot environment using this driver instead of the VMWare drivers.

Nel caso di una nuova installazione di Deployment Solution 6.9, il personale tecnico IT può incontrare delle difficoltà nell'uso di WinPE 2.x in abbinamento con i driver di rete di VMWare. In aggiunta come ulteriore considerazione, sempre più utenti provano a virtualizzare gli ambienti di lavoro, e con Microsoft Vista possono incontrare delle difficoltà non avendo la possibilità di usare connessioni di rete con le Virtual Machine di VMWare.

Il supporto e sviluppo personale sono adesso principalmente eseguiti con l'uso di piattaforme virtuali per ambienti di test.