Teradici released a new  PCoIP zero client and host card firmware and the PCoIP Management Console. The following releases are now available for download on the Teradici support site (techsupport.teradici.com):

• Firmware 3.5.0 for PCoIP Zero Clients and PCoIP Host Cards.
• PCoIP Management Console 1.7.0

Firmware 3.5.0 update includes key feature enhancements including:

• USB2.0 with VMware View sessions
• Imprivata OneSign® Virtual Desktop Access via proximity cards with VMware View
• IEEE 802.1x network security
• IPv6 support. 

With this release, Teradici continues to innovate PCoIP zero client technology and accelerate the adoption

Highlights of VMware Workstation 8.0.1 functionality include:

• Graphics performance and compatibility enhancements.
• Improvements in creating and using shared virtual machines and remote virtual machines.
• Ubuntu 11.10 is officially supported as a guest operating system.
• Disk and memory management issues have been addressed.
• Many customer-reported issues have been resolved.

VMware Workstation 8.0.1 is a free update for all VMware Workstation 8 users.

Resolved Issues

The following sections list the resolved issues in VMware Workstation 8.0.1.

• Windows 7 guest installation failed after powering on the virtual machine with the error A required CD/DVD drive device driver is missing. If you have a driver floppy disk,
CD, DVD, or USB flash drive, please insert it now.
• VMware Tools failed with the message VMware Tools unrecoverable error.
• VMware Tools failed to start in Fedora 15 guests.
• An Ubuntu 11.10 guest crashed with a signal 11 error if you installed or upgraded VMware Tools.
• On hosts with Nvidia GeForce and Quadro video cards, some of the clouds in the Unigine Heaven Benchmark application were drawn solid black.
• Easy Install did not properly function on Ubuntu 11.10.
• If remote virtual machines were open, you could not shut down the Windows hosts.
• When transitioning from Full Screen mode to Exclusive mode, the Full Screen toolbar sometimes failed to hide.
• Host memory reservation restrictions on Windows hosts are more relaxed in VMware Workstation 8.0.1 than in previous versions of VMware Workstation.
• CD/DVD mount Linux.iso failed while installing VMware Tools in Ubuntu 11.10 guests.
• The AltGr key was not working in an Ubuntu guest in Unity mode when the host and guest keyboards were both set to a layout that contained the AltGr key.

To check the status of the Multipath Policy you can run the following PowerCLI script:

Per host:

Get-VMhost ESXHOST | Get-ScsiLun -LunType disk

Per Cluster:

Get-Cluster CLUSTERNAME| Get-VMHost | Get-ScsiLun -LunType disk

To change the Multipath Policy you can run the following command:

Per Host:

Get-VMHost ESXHOST | Get-ScsiLun -CanonicalName "naa.6005*" | Set-ScsiLun -MultipathPolicy "roundrobin"

Per Cluster:
get-cluster “Cluster Name” | Get-VMHost | Get-ScsiLun -LunType disk | Where-Object {$_.MultipathPolicy -ne “RoundRobin”} | Set-ScsiLun -MultipathPolicy “RoundRobin”

Special thanks to: VMPROS

The View desktops we’ve got setup are using linked clones and persistent disks which map to the D:\ in the users sessions. Of course this means the users profile is loaded to the D:\ instead of C:\ in the virtual desktops. My issue is, when a new users comes from our old environment into the test view setup, their Outlook is trying to find their OST file on the C:\ (c:\document and settings\…etc). The users data has been loaded to the D:\ though. The only way I’ve found to get around this is going into the Contol Panel in the users session, deleting their Outlook profile,

Solution:

Microsoft saves information about profile under HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\Outlook

So, within regedit, I right-clicked on HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\Outlook then chose Export. For Save as Type, I changed the value to "Text Files (*.txt)". I then opened the text file I created with Notepad. You can’t just search for "Outlook.ost", since there are null, i.e. 00, characters stored between each character. They show up in an ASCII representation as dots. E.g. Outlook.ost would be O.u.t.l.o.o.k…o.s.t.

Since the "Outlook.ost" could be broken across multiple lines, I decided just to search for o.s.t. I found the following in the text file I had created.

Value 31

  Name:            001f6610

  Type:            REG_BINARY

  Data:           

00000000   43 00 3a 00 5c 00 44 00 – 6f 00 63 00 75 00 6d 00  C.:.\.D.o.c.u.m.

00000010   65 00 6e 00 74 00 73 00 – 20 00 61 00 6e 00 64 00  e.n.t.s. .a.n.d.

00000020   20 00 53 00 65 00 74 00 – 74 00 69 00 6e 00 67 00   .S.e.t.t.i.n.g.

00000030   73 00 5c 00 4a 00 69 00 – 6d 00 5c 00 4c 00 6f 00  s.\.J.i.m.\.L.o.

00000040   63 00 61 00 6c 00 20 00 – 53 00 65 00 74 00 74 00  c.a.l. .S.e.t.t.

00000050   69 00 6e 00 67 00 73 00 – 5c 00 41 00 70 00 70 00  i.n.g.s.\.A.p.p.

00000060   6c 00 69 00 63 00 61 00 – 74 00 69 00 6f 00 6e 00  l.i.c.a.t.i.o.n.

00000070   20 00 44 00 61 00 74 00 – 61 00 5c 00 4d 00 69 00   .D.a.t.a.\.M.i.

00000080   63 00 72 00 6f 00 73 00 – 6f 00 66 00 74 00 5c 00  c.r.o.s.o.f.t.\.

00000090   4f 00 75 00 74 00 6c 00 – 6f 00 6f 00 6b 00 5c 00  O.u.t.l.o.o.k.\.

000000a0   6f 00 75 00 74 00 6c 00 – 6f 00 6f 00 6b 00 2e 00  o.u.t.l.o.o.k…

000000b0   6f 00 73 00 74 00 00 00 -                          o.s.t…

I could also have searched in the .reg file I created when I exported the registry information from the other computer. But, again, you can’t just search for "Outlook.ost" in the .reg file you created, either, since the information in it is the hexadecimal representation of the binary data in the registry keys. You would need to convert a string, such as "ost" to hexadecimal form. You can do that at String – ASCII, HEX, Binary Converter. In the String field, I put in ost. The converter showed me the equivalent hex value is 6F 73 74. Note: the converter shows decimal/ASCII, binary, and hex values. Make sure you use the correct one. Also note that the hexadecimal representation of "OST" is not the same as "ost". Since the error message I received referred to Outlook.ost, I converted "ost" to hexadecimal. Again, it may be better to limit the length of the string to reduce the chance it will be broken across multiple lines in the file.

Once you have the hexadecimal equivalent of the ASCII string, you still can’t just search for it, i.e. a search for 6F7374 wouldn’t work. The hexadecimal numbers are stored in the .reg file with commas and the null character, 00, between them. I.e., I would need to search for 6f,00,73,00,74 instead.

In the .reg file found it among the following lines:

"001f6610"=hex:43,00,3a,00,5c,00,44,00,6f,00,63,00,75,00,6d,00,65,00,6e,00,74,\

  00,73,00,20,00,61,00,6e,00,64,00,20,00,53,00,65,00,74,00,74,00,69,00,6e,00,\

  67,00,73,00,5c,00,4a,00,69,00,6d,00,5c,00,4c,00,6f,00,63,00,61,00,6c,00,20,\

  00,53,00,65,00,74,00,74,00,69,00,6e,00,67,00,73,00,5c,00,41,00,70,00,70,00,\

  6c,00,69,00,63,00,61,00,74,00,69,00,6f,00,6e,00,20,00,44,00,61,00,74,00,61,\

  00,5c,00,4d,00,69,00,63,00,72,00,6f,00,73,00,6f,00,66,00,74,00,5c,00,4f,00,\

  75,00,74,00,6c,00,6f,00,6f,00,6b,00,5c,00,6f,00,75,00,74,00,6c,00,6f,00,6f,\

  00,6b,00,2e,00,6f,00,73,00,74,00,00,00

I noticed it was associated with a "001f6610" entry. When I had searched the text file, I had also seen Outlook.ost associated with "Name: 001f6610".

You can delete the following registry key with group policy preferences to disable using Offline Folders after disabling Use Cached Mode in Group Policy:

HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\Outlook\13dbb0c8aa05101a9bb000aa002fc45a\001f6610

VMware View makes it easy to extend to your users the opportunity to work where you want and on the device they choose. Today, we are excited to make this even easier with the release three new or updated mobile clients:

• VMware View Client for iPad 1.2 (Photo below showing new presentation mode!*)

• VMware View Client for Android Tablets

• VMware View Client for Cius

Let’s talk about the new clients…

VMware View Client for iPad 1.2
Building on the earlier View Client for iPad we released in March, VMware View Client for iPad 1.2 makes it easier, faster and better than ever to connect to your View desktop.

Optimized for VMware View 5
With support for VMware View 5, you can get better performance with reduced bandwidth options as well as more resilient connections to your desktop than previous versions.

Move Back and Forth between Windows Desktop and iOS Apps
Now with support for background multitasking, you can jump from your Windows desktop to another iPad app and then right back into the Windows desktop to where you left off!

Simpler to Connect with Embedded RSA Soft Token
If you need to use an RSA key to authenticate to connect to your View Desktop, just activate the RSA soft token built into the View Client for iPad and you just need to enter your RSA PIN when you connect to your View desktop.

Support for iOS 5 and Apple AirPlay
That right… VMware View Client for iPad 1.2 works well with iOS 5 and takes advantage of Apple AirPlay and an available AppleTV to use your big screen TV as a display for your View desktop. While some people might think that Apple TV is just for fun, it can now blur the lines between work and play and represents the best the post-PC era has to offer.

Work Smarter with Presentation Mode *
Use an external monitor or AirPlay in iOS 5 and the iPad display turns into a trackpad / keyboard while the external screen shows your View desktop!

Speaks Your Language
The latest VMware View client is now available in English, French, German, Japanese, Simplified Chinese, and Korean. When working multi-byte Asian languages, the new local input mode enables you to type in full lines of complete multi-byte words and then send them to your View desktop.

The new VMware View Client for iPad is available in the Apple App Store today! Check it out!

For those of you who follow this blog and use Android based tablets. Today we are happy to release our production Android clients for Android Tablets and the Cisco Cius. After all it is about supporting the tablet you choose.

VMware View Client for Android Tablets and the Cisco Cius
Whether you are using a Samsung Galaxy Tab 8.9 or 10.1, an LG/T-mobile G-Slate, a Motorola Xoom or any of the other newly available Honeycomb-based Android tablets or the Cisco Cius, you can get the most of your View desktop on the Android tablet you choose.

Optimized for VMware View 5
The VMware View Client for Android Tablets is the first Android client to support the PCoIP display protocol for best performance with VMware View 4.6 and View 5 users. With support for VMware View 5, you can get better performance with reduced bandwidth options as well as more resilient connections to your View desktop.

Move Back and Forth between Windows Desktop and Android Apps
Leveraging the power of Android multitasking, you can jump from your Windows desktop to another Android app and then right back into the Windows desktop to where you left off!

Speaks Your Language
The latest VMware View Client for Android is available in English, French, German, Japanese, Simplified Chinese, and Korean. When working multi-byte Asian languages, local input mode enables you to type in full lines of complete multi-byte words and then send them to your View desktop.

The new VMware View Client for Android Tablets is available in the Android Marketplace and the VMware View Client for Cius will soon be available in Cisco’s AppHQ. Check them out today!

To download just click on the picture .

Blindly deploying entirely the same Windows desktop image that was used for the physical desktops is not the smartest thing to do. Running Windows in a VDI environment requires a decent amount of optimizing. This optimizing is nothing new. Quest has been optimizing SBC environments for over ten years now and many of things that we learned there (the hard way) apply equally to VDI environments.

Quest created a piece of software that contains our entire ‘optimizing knowledge’ called the Quest vWorkspace Desktop Optimizer and it is Free!

Although optimized for Quest vWorkspace environments, the Quest vWorkspace Desktop Optimizer will work just as well in Citrix XenDesktop or VMware View environments. You can download the Quest vWorkspace Desktop Optimizer HERE. Read HERE important information on how to use the Quest vWorkspace Desktop Optimizer.

You can make machine based selections for turning off services and functions that may not be required when the operating system is running in a VDI environment such as hibernation, system restore, and background defrag, as well as adjusting some user based settings such as visual effects, font smoothing and off-screen composition for Internet Explorer.

The beta of this tool is available from http://www.autoitscript.com/files/tools/VDIOptimizer.zip but please remember The tool is provided "AS IS" with no warranties, confers no rights, and is not supported by the authors or Microsoft Corporation.

Source: Optimizing Windows 7 images for use in VDI

Testing shows the effectiveness of vSphere 5 to add compute power by scaling up Exchange Server VMs, in increments, from 2 to 12 virtual CPUs. This allowed the total number of very heavy Exchange users to increase from 2,000 to 12,000 while sendmail latency remained well within the range of acceptable user responsiveness. Processor utilization remained low, at about 15% of the total host processing capacity for 12,000 very heavy Exchange users.

Testing also shows that scaling out to eight Exchange Server VMs supports a workload of up to 16,000 very heavy users, with the load consuming only 32% of the ESXi host processing capacity.

Additional tests were undertaken to show the performance improvements of vMotion and Storage vMotion in vSphere 5. vMotion migration time for a 4-vCPU Exchange mailbox server VM showed a 34% reduction in vSphere 5 over vSphere 4.1. Storage vMotion migration time for a 350GB database VMDK showed an 11% reduction in vSphere 5 over vSphere 4.1.

For the full paper, see Microsoft Exchange Server 2010 Performance on vSphere 5.

This release of VMware Workstation adds the following new features and support.

• Installation Changes and Enhanced Keyboards
• Virtual Hardware Improvements
• New User Interface
• What Happened to Teams?
• Shared Virtual Machines and AutoStart
• Remote Connections
• Upload to vSphere
• Documentation Changes

Installation Changes and Enhanced Keyboards

The hardware requirements to install this version of Workstation have changed. Workstation now requires a relatively modern 64-bit CPU. See Installation Requirements for details.

The keyboard filter driver is no longer installed by default. When the driver is not installed, the enhanced keyboard functionality is unavailable and you must press Ctrl-Alt-Ins instead of Ctrl-Alt-Del to send a Ctrl-Alt-Del keystroke to the guest. To use the enhanced keyboard functionality, you must perform a custom installation and select the component. If you select the component, you must reboot whenever you install or uninstall Workstation.

Virtual Hardware Improvements

This version of Workstation includes many hardware improvements. To try new hardware features, you must upgrade the hardware version of your virtual machine or create a new virtual machine that uses the latest virtual hardware version.

• The display technology has been changed to provide a better experience for Unity users and users who have multiple monitors. These changes also allow you to add a projector to your laptop without restarting your virtual machine.
• Virtual machines can now support up to 64GB of memory. The host system should have more than 64GB of memory to use this feature.
• An HD Audio device is available for Windows Vista, Windows 7, Windows 2008, and Windows 2008 R2 guests. The HD Audio device is compatible with the RealTek ALC888 7.1 Channel High Definition Audio Codec.
• USB 3.0 support is available for Linux guests running kernel version 2.6.35 or later (Ubuntu 10.10) through a new virtual xHCI USB controller. To enable this feature, add the following line to the .vmx file: usb_xhci.present = “true”. Do not enable this feature for Windows guests. Because Windows does not currently have a generic xHCI driver, this feature will not work in Windows.
• Bluetooth devices on the host can now be shared with Windows guests. With the latest hardware version, Bluetooth devices that are paired to the host system radio are available to Windows guests and can be paired from within the guest. You should not pair Bluetooth audio devices, such as headphones, or Bluetooth input devices, such as keyboards and mice, to a guest.
• You can now enable Virtual VT-X/EPT or AMD-V/RVI in the processor settings interface. With this feature, applications running in a guest can take advantage of these virtualization technologies. You can also run 64-bit guest operating systems inside of vSphere running inside Workstation.

New User Interface

The Workstation user interface has been updated to include new menus, toolbars, and an improved preferences screen.

• The favorites sidebar has been replaced with a virtual machine library. Instead of identifying every virtual machine created in Workstation as a favorite, the library is a comprehensive list of all of the virtual machines that Workstation users create, open, or access.
• A new folder summary page helps you to better manage a group of related virtual machines. Live thumbnails make it easy to see what is happening in running virtual machines.
• The full screen toolbar has been updated so that you can do more without having to leave full screen mode. Quick switch mode is no longer needed.

What Happened to Teams?

Although at first it might appear that the teams feature has been removed, you can add team attributes to any virtual machine in this version of Workstation.

• The team structure has been converted to a simple folder of virtual machines.
• A new advanced settings dialog box has been added for network adapters to let you throttle the bandwidth of incoming and outgoing transmissions and simulate packet loss.
• You can perform power operations on several virtual machines at the same time by selecting virtual machines on the folder tab and pressing the power button on the toolbar. If all of the virtual machines in a folder are in the same power state, you can select the folder to perform a power operation on all of the virtual machines in the folder.
• You use a global Workstation preference to configure the delay between powering on virtual machines.
• To implement LAN segments, you can use traditional VMnets or put all of the virtual machines that you want to communicate on the same custom VMnet.

Shared Virtual Machines and AutoStart

You can share virtual machines with remote users in this version of Workstation. A shared virtual machine can be accessed remotely by other instances of Workstation. Workstation moves virtual machines to the shared virtual machines folder, where the VMware Host Agent service manages them. The VMware Host Agent service is used by other VMware products, including VMware Server and vSphere, and provides additional capabilities required by professional users. An extensive permissions interface lets you control the users who can access and use shared virtual machines.

You can use the new AutoStart feature to configure shared virtual machines to start with the host system. You can also configure AutoStart for shared virtual machines on remote hosts running Workstation and ESX 4.x and later.

Remote Connections

In this version of Workstation, you are no longer constrained to working only with virtual machines that your computer has enough power to run. You can use the new Connect to Server feature to connect to remote hosts running Workstation, ESX 4.x and later, and VMware vCenter Server. After connecting to a remote host, all of the virtual machines that you have permission to access are displayed in the virtual machine library.

Upload to ESX/ESXi and vCenter Server

VMware OVF Tool is now integrated with Workstation so that you can upload a virtual machine from Workstation to a remote server running ESX, ESXi, or vCenter Server. After connecting to a remote server, you drag the virtual machine from the local My Computer section of the virtual machine library to the remote server. A wizard walks you through the process.

Documentation Changes

This version of Workstation includes several important documentation changes.

(NEW) Getting Started with VMware Workstation
Describes how to install and upgrade Workstation, create a typical virtual machine, and perform common virtual machine operations.

Using VMware Workstation
(previously VMware Workstation User’s Guide)
Describes how to create typical, custom, and shared virtual machines, add virtual devices, configure network connections, connect to remote servers and use remote virtual machines, upload virtual machines to remote servers, and perform all virtual machine operations.

Getting Started with VMware Player
(previously VMware Player Getting Started Guide)
Now contains complete information on installing and using Player.

Online help
Has been redesigned to provide context-sensitive help and information on performing common tasks. For complete information on using Workstation and Player, see the guides.

(NEW) Installing and Configuring VMware Tools
Contains comprehensive information on installing, upgrading, and configuring VMware Tools.

Top of Page

Installation Requirements

When you install Workstation, the installer performs checks to make sure the host system has a processor that meets the following requirements. You cannot install Workstation if the host system does not meet these requirements.

• 64-bit x86 CPU
• LAHF/SAHF support in long mode

You can use CPU-Z or a similar utility to determine if the host system CPU is 64-bit capable. CPU-Z shows EM64T (Intel) or AMD64 (AMD) if the processor is 64-bit capable.

If you plan to install a 64-bit guest operating system in a virtual machine, the host system must have one of the following processors. Workstation will not allow you to install a 64-bit guest operating system if the host system does not have one of these processors.

• AMD CPU that has segment-limit support in long mode.
• Intel CPU that has VT-x support. VT-x support must be enabled in the host system BIOS. The BIOS settings that must be enabled for VT-x support vary depending on the system vendor. See VMware KB article 1003944 for information on how to determine if VT-x support is enabled.

Top of Page

Known Issues

The known issues are grouped as follows:

• Remote Connection and Remote Virtual Machine Issues
• Role and Permission Issues
• Shared Virtual Machine Issues
• Display and Input Issues
• Folder and Team Conversion Issues
• Device Issues
• Physical Machine Virtualization Issues

Remote Connection and Remote Virtual Machine Issues

• When Workstation is installed on a Linux host, VMware Workstation Server writes the core file to /usr/bin instead of to /var/core or /var/log/vmware.
• You cannot use Workstation to create a remote virtual machine on an ESX or ESXi 4.1 host if the virtual machine name contains non-ASCII characters.
• When you upload a virtual machine to a remote server (VM > Manage > Upload), Workstation modifies the MAC address and PCI slot number of the virtual Ethernet device in the newly created remote virtual machine. Network errors can occur in the remote virtual machine if the network settings in the guest operating system require the original network hardware configuration.
  Workaround: Change the network settings in the guest operating system in the remote virtual machine to match the new network hardware configuration.
• VMware Workstation Server occasionally crashes on a 32-bit Red Hat Enterprise Linux 6.x host.

Role and Permission Issues

• On a Windows host, if you edit a permission, assign the Administrator role, and then immediately click Remove to delete the permission, the original permission still exists when you reopen the Permissions dialog box.

Shared Virtual Machine Issues

• On Windows hosts, if a shared virtual machine has a floppy drive that is configured to connect at power on, and a remote user powers on the virtual machine, a dialog box appears on the host system asking whether to connect the device every time the virtual machine powers on. If you click Yes to close the dialog box on the host system after the virtual machine is completely up and running on the host system, Workstation crashes on the host system.
• On a 32 or 64-bit Windows 7, 64-bit Windows 2008 R2, or 32-bit Windows XP Professional SP3 host, if you uninstall Workstation, preserve the configuration, and then reinstall Workstation to a different path, the Shared VMs item is unavailable in the virtual machine library.
• On a Windows host, if you create a virtual machine with a name that contains non-ASCII characters in the New Virtual Machine wizard, you cannot share the virtual machine with the Move the virtual machine option if the destination path is other than the system operating system location. The sharing process stops with the error message Failed to move VM to destination path.
  Workaround: If you want to share the virtual machine, you must use only ASCII characters in the virtual machine name when you create the virtual machine in the New Virtual Machine wizard.

Display and Input Issues

• On an Ubuntu 11.04 host, the virtual machine icon does not appear on the system tray when you set the Show tray icon setting (Edit > Preferences > Workspace) to Always or When a virtual machine is powered on.
  Workaround: Whitelist vmware-tray as an application that can show system tray icons in Ubuntu 11.04. Alternatively, enable Notification Area (Systray) for all applications, for example:
  gsettings set com.canonical.Unity.Panel systray-whitelist "['all']"
  After you run the command, log out and log back in. The command can take several minutes to take effect.
• On a Fedora 15 host, powering on a virtual machine that has DirectX 9 accelerated graphics enabled might fail with the error "Unable to change virtual machine power state: Cannot find a valid peer process to connect to."
  Workaround: Deselect the Accelerate 3D graphics setting (VM > Settings > Hardware > Display) to disable DirectX 9 accelerated graphics in the virtual machine.
• When you enter Unity mode in an Ubuntu 11.04 guest, application menus do not appear for applications that were opened before entering Unity mode. Application menus do appear for applications that are opened from the Unity launch menu after entering Unity mode.
  Workaround: Disable the APPMENU (Global menu) in the Ubuntu 11.04 guest. See the Ubuntu documentation for more information.
• After you upload a Windows XP virtual machine from the local host to a remote server, you cannot autofit the guest in full screen mode. This problem occurs because VRAM is reduced to 4 MB when the virtual machine is uploaded to the remote server.

Folder and Team Conversion Issues

• When you select a newly created folder in the Workstation library, the toolbar power option button is dimmed and you cannot perform batch power operations on the virtual machines in the folder.
  Workaround: If you select a virtual machine in the folder, move the selection off the virtual machine (for example, click anywhere on the folder tab), and then select the folder in the library again, the toolbar power option button becomes available.

Device Issues

• On Windows hosts, Player crashes if you click Connect or Disconnect in the Removable Devices menu before the console appears.
• An Ubuntu 11.04 host might crash when you try to connect a USB device to a running virtual machine from the status bar icon’s context menu. This problem typically occurs after Workstation is freshly installed, the host is rebooted, and the first time the device is connected to the virtual machine.

Physical Machine Virtualization Issues

• When simple file sharing or UAC is enabled on the physical machine, the Virtualize a Physical Machine wizard returns an "incorrect user credentials" error instead of an error message that indicates simple file sharing or UAC must be disabled before virtualizing the physical machine. See the online help or Using VMware Workstation for information on preparing a physical machine for virtualization.
• You cannot use the Virtualize a Physical Machine wizard if the Workstation installation path contains non-ASCII characters.

For Windows or Linux and install on your workstation.

2. Download the Upgrade Package for 4.0 to 4.1

3. Power off your VM’s and put the host into maintenance mode

4. From the vSphere CLI prompt

vihostupdate.pl –server hostname or IP -i –b d:\downloads\upgrade-from-ESXi4.0-to-4.1.0-0.0.260247-release.zip -B ESXi410-GA

Check out the Video

VMware Party Rock Parody

And off Course the New features in View 5:

PCoIP WAN performance optimization – Improvements on PCoIP protocol performance in low-bandwidth WAN environments. Users who connect to their desktops over an external WAN have enhanced desktop experience.

PCoIP Build-to-Lossless – PCoIP now provides the ability to turn off Build-to-Lossless. This is the feature that puts PCoIP in parity with ICA when the discussion is around bandwidth consumption. Build-to-Lossless is ON by default and included in the PCoIP protocol within VMware View. I have prepared another post specifically to discuss this feature along with other important changes to the display protocol.

VMware Client Side Caching – VMware View Client (Windows Only) now implements a client side image caching to store portions of the display that were previously transmitted. Image caching reduces the amount of data that is retransmitted and improve user experience. This cache can be managed and it’s size can be modified. I have prepared an article specifically to address this feature.

Support for 3D graphics on vSphere 5.0 – This feature provides View desktops with vGPU graphics enablement available on vSphere 5.0 platforms (hardware version 8). View users can take advantage of desktop graphics enhancements provided by AERO (such as peek, shake, and Flip 3D) and the 3D capabilities of Windows Office 2010 (such as picture editing, slide transitions and animations, presentation-to-video conversion, video embedding, editing, and 3D rotations). Include here: Support for DirectX9 and OpenGL 2.1

View Persona Management – The View Persona Management feature manages user profiles in a secure and centralized environment. (User profiles include user data and settings, application data and settings, and Windows registry settings configured by user applications.) View Persona Management allows IT organizations to simplify and automate the capture and management of a user’s persona while providing a rich user experience. View Persona Management offers the following benefits:

• Provides a user profile that is independent of the virtual desktop. When a user logs into any desktop, the same profile appears.
• Lets you configure and manage personas entirely within View. You do not have to configure Windows roaming profiles.
• Expands functionality and improves performance compared to Windows roaming profiles.
• Minimizes login impact by downloading only the files that Windows requires, such as user registry files. Other files are copied to the local desktop when the user or an application opens them from the local profile folder.
• Copies recent changes in the local profile to a remote profile repository at configurable intervals, typically once every few minutes.

Client certificate checking for Windows Clients – You can configure remote Windows clients to require certificate verification. Users without valid certificates are denied access to View Connection Server. Alternatively, you can use a Warn But Allow mode that supports self-signed server certificates and lets users connect to View Connection Server with certificates that have expired or are not yet valid. You can also set a No Security mode that lets users connect without certificate checking.

Support for vSphere 5.0 and hardware v8 – Remote View desktops can be hardware v8 virtual machines. Hardware v8 is not supported for desktops that run in local mode.

VMware ESXi 5.0 (Build 469512)

VMware vCenter 5.0 (Build 456005)

VMware Data Recovery 2.0 (Build 433157)

vSphere Storage Appliance 1.0

VMware vShield Zones for vSphere 5 (Build 216288)

We use the Wyse P20 zero client.

Step 1 was to config the VMware View Desktop Pool Multiple Monitor Support

Ensure your desktop pool is configured to support 2 monitors.

Sign into the VMware View Administrator go to Inventory go to Pools. Select your Pool  Click the Edit button. Go to the Pool Settings Tab under Remote Desktop Protocol change the max number of monitors to 2.

Step 2. Choosing Multi-monitor in VMware View Client

In the VMware View client you must enable multiple monitor support. However, when we used the Zero client (Wyse P20) to connect to your virtual desktop pool the Display option isn’t even present. So what you need to do is access the VMware View Client on a desktop PC or Laptop, sign in as the user that needs multiple monitor support, select the desktop pool and set the display to Multimonitor.  Login and wait till the desktop is fully loaded and then logoff. Then when the user signs in on the Zero client (Wyse P20) Multiple Monitor support will be engaged because you set it previously..

• Virtual machine enhancements
• Improved SSD handling and optimization
• Command-line enhancements
• VMware® ESXi™ firewall
• vSphere Image Builder
• vSphere Auto Deploy server
• vSphere Host Profiles
• VMware vCenter™ Update Manager

• What’s New in VMware vSphere 5.0: Platform
• What’s New in VMware vSphere 5.0: Storage
• What’s New in VMware vSphere 5.0: Performance
• What’s New in VMware vSphere 5.0: Networking
• What’s New in VMware vSphere 5.0: Availability
• vSphere 5.0 Licensing, Pricing and Packaging Whitepaper

VMware View Bootcamp Series

Design Considerations Guidelines for VMware View – Overview

• Speaker – John Dodge, Sr. Manager PSO Services, VMware
• Overview of the technical considerations to keep in mind while you’re designing a View environment

Watch the Video

Storage Deep Dive – Considerations and Best Practices

• Speaker – Jim Yanik, Sr. Systems Engineer, VMware
• How to design your storage infrastructure to fit your environment
• Sizing and workload considerations

Watch the Video

Network Considerations and Best Practices

• Speaker – Shannon McFarland; Consulting Engineer for Data Center technologies and Enterprise IPv6 design on Cisco’s Consulting Engineering team in the Office of the CTO, Cisco
• Network requirements for LAN and WAN
• Bandwidth requirements deep dive
• Security considerations – Security Server, AV, Encryption, Authentication

Watch the Video

Optimizing the Base Image for VMware View

• Speaker – Todd Dayton, Staff Product Manager, Desktop Product Management, VMware
• How to build and tune your desktop image
• User and workload considerations
• OS specific tips (XP, Win7)

Watch the Video

Delivering Applications

• Speaker – Heath Doer, Sr Systems Engineer, VMware
• Packaging and updates (applink and appsync)
• Best practices-storage, image management and application deployment
• Application migration, application conflict and compatibility

Watch the Video

PCoIP Implementation Overview and PCoIP Tuning Best Practices

• Speaker – Chuck Hirstius, PSO, WW Advanced Services, VMware
• How to optimize PCoIP for different types of workloads
• How to optimize for LAN, mobile and remote users
• Bandwidth requirements

Watch the Video

Automating View 4.5 with Powershell

• Speaker – Tom Elliot, Sr. MTS, Enterprise Desktop, VMware
• Introduction to View PowerCLI
• Setting up an environment and basic tasks
• Creating your own scripts
• Integrating with vSphere

Watch the Video

Leveraging Security Server for PCoIP

• Speaker – Mark Benson, View Architect, Enterprise Desktop, VMware
• Introduction to Security Server

Watch the Video

VMware View’s Reference Architecture

• Speaker – Mac Binesh, Sr. Technical Marketing Manager, Enterprise Desktop, VMware
• Review of RA for stateless desktops
• Description of test environment, equipment and lab results

Watch the Video

Download the Compliance Checker HERE

Reboot and then setup continues
 
 
 

Edit Package.ini

Add the following line under:
[VMware View Client.exe]
Source=%ProgramFilesDir%\VMware\VMware View\Client\bin\wswc.exe
;Change ReadOnlyData to bin\Package.ro.tvr to build with old versions(4.6.0 or earlier) of tools
ReadOnlyData=Package.ro.tvr
WorkingDirectory=%ProgramFilesDir%\VMware\VMware View\Client\bin\
ObjectTypes=VMware_VDM_Client;VMware_VDM_Client.1
Shortcuts=%Desktop%;%Programs%\VMware;%AppData%\Microsoft\Internet Explorer\Quick Launch

Commandline=%ProgramFilesDir%\VMware\VMware View\Client\bin\wswc –serverurl viewdemo.wardvissers.nl

Open Project Folder:
Remove the following Folders

%AppData%
%Common Desktop%
%Common Programs%
%Desktop%
%drive_C%
%Local AppData%
%Personal%
%Profile%
%Program Files Common%
%SystemRoot%

Then Click on Build

You can read the release notes Here.

Downloads:
Wyse P20 Firmware

Management software for P20

Wyse P20 WDM package

The executable "chemiekaarten 2011.exe" links to a primairy datacontainer "Chemiekaarten.dat". Deze wordt niet gevonden in package.ini

Delete the following rule Shortcut= after [chemiekaarten 2011.exe] at package.ini  and add the follow ing ReadOnlyData=bin\Package.ro.tvr.

Thanks to my college Edwin

What’s New

Support for Windows 7 SP1

Security Fixes

Other Resolved Issues

• In Workstation 7.1, the default main memory VA cache size (mainMem.vaCacheSize) for 32-bit Windows guests was reduced to accommodate 3D emulation memory requirements. However, the reduced value resulted in performance loss. For 7.1.4, the default main memory VA cache size has been be increased to 1000 MB and performance is improved.

• Because Workstation failed to identify more than 10 USB host controllers in newer Windows guests, some USB devices did not appear in the Removable Devices menu. Now Workstation shows all USB devices in the Removable Devices menu as long as they are connected to the first identified 16 USB controllers.

• When using the Capture Movie option, the captured video stopped playing around the 1GB mark if the video file exceeded 1GB. Now you can capture and play video files that are greater than 1GB. 

• On Windows host systems that have more than 4GB of memory, Workstation sometimes crashed during cryptographic operations, for example, when performing disk encryption.

• VMware Tools upgrade could be started by a non-administrator user from the VMware Tools Control Panel in a Windows guest. In this release, only administrator users can start VMware Tools upgrade from the VMware Tools Control Panel. To prevent non-administrator users from starting VMware Tools upgrade from a guest by using other applications, set isolation.tools.autoinstall.disable to TRUE in the virtual machine configuration (.vmx) file.

• When a virtual machine running on a Windows host was used to access an Omron Industrial CP1L Programmable Logic Controller, Workstation generated an unrecoverable error.

• When using NAT virtual networking on Windows hosts, the traceroute command did not work when used within virtual machines.

• Workstation crashed with an access violation when a user tried to open the sidebar after closing all tabs in Quick Switch mode. 

• The VMware Tools HGFS provider DLL caused a deadlock when making calls to the WNetAddConnection2 function from an application such as eEye Rentina in a Windows guest operating system.

• There was no option to disable guest time sync when a host resumes. Now you can set time.synchronize.resume.host to FALSE in the virtual machine configuration (.vmx) file to disable guest time sync when a host resumes. See VMware Knowledge Base Article 1189 for other time sync options.

• Setting a hidden attribute on a file in a shared folder from a Windows guest on a Linux host failed with an error. This problem caused applications such as SVN checkout to fail when checking out to shared folders on Linux hosts from Windows guests

VMware vCenter XVP Manager and Converter provides basic virtualization management capabilities for non-vSphere hypervisor platforms towards enabling centralized visibility and control across heterogeneous virtual infrastructures. It also simplifies and enables easy migrations of virtual machines from non-vSphere virtualization platforms to VMware vSphere.

Features

• Management of the following Microsoft Hyper-V platforms:
  • Microsoft Hyper-V Server 2008
  • Microsoft Windows Server 2008 (64-bit) with Hyper-V role enabled
  • Microsoft Hyper-V Server 2008 R2
  • Microsoft Windows Server 2008 R2 with Hyper-V role enabled
• Familiar vCenter Server graphical user interface for navigating through and managing non-vSphere inventory
• Ease of virtual machine migrations from non-vSphere hosts to vSphere inventory
• Compatible with VMware vCenter Server 4.0 & 4.1
• Scalable up to management of 50 non-vSphere hosts

For more detailed information refer to the vCenter XVP Manager and Converter Technology Preview Release Notes and Installation Guide (included in zip file download).

VIDEO’s

Installation

Host Operations

Convert HyperV VMs to vSphere

Guest VM Operations inside HyperV

Download: HERE