Tag: w2k8

You may always here from people in the industry that IPv6 "breaks things/stops things working" and that the recommendation is to disable it. If you where to speak to Microsoft or attend their seminars, you will always hear them say DON'T disable IPv6. So who is correct!! The link below gives you an insight into IPv6. I've extracted an example Q and A from the list. IPv6 for Microsoft Windows http://technet.microsoft.com/en-us/network/cc987595.aspx Q. What are Microsoft’s recommendations about disabling IPv6? A. It is unfortunate that some organizations disable IPv6 on their computers running Windows 7, Windows Vista, Windows Server 2008 R2, or Windows Server 2008, where it is installed and enabled by default. Many disable IPv6-based on the assumption that they are not running any applications or services that use it. Others might disable it because of…

When it comes to the virutalisation , there are considerations for performance. There are options which are enabled by default which makes sense for laptops and even desktops. A VM, however, may not benefit and in fact may see performance loss. One such feature is TCP Chimney offload. TCP Chimney offload is designed to free up CPU utilization and increase network throughput by moving TCP processing tasks to hardware. This frees up the server’s CPU for other tasks. This makes sense if consider the available processors, ram and types of tasks running. Chances are a VM is only performing a certain task and might even be network bound when considering how many VM’s are running on the host. If your VM has access to fast processors and enough RAM, you…

I've had a number of emails recently asking about why when accessing a Windows 2008 R2 server using the VM console the display and mouse are very sluggish. Well the answer to this is because by default a Standard VGA Graphics Adapter is installed (figure 1) when you have your video RAM set yo 8MB in your virtual machine properties. (figure1) To change this you will need to upgrade the display adapter by using the driver in C:Program FilesCommon FilesVMwareDriverswddm_video this will install the new WDDM device driver. After the upgrade and a reboot your system should be fully responsive. Look in device manager (figure2) and check to make sure this change has occured. (figure2)