May
16

VMware EUC KB articles for the Week of May 14th, 2012

VMware ThinApp

· A ThinApp which includes the .NET Framework generates the message: Event ID: 1101 “.NET Runtime Optimization Service (clr_optimization_version) – 1>Failed to compile:” (2018794)

· Running a ThinApp application fails with the error: License problem: Unable to validate your license (2019985)

VMware View

· Unable to install VMware View Composer 2.7 with Oracle ODBC connectio

· Persona Management fails when Novell Secure Login is installed

· Attempting to view persistent disks fails with the error: java.lang.IllegalArgumentException

Apr
09

#VDI Tip 68: Use Overridable Administrator Defaults for PCoIP Session Variables

Why is there two different settings for PCoIP Session Variables and which should I use?

Overridable Administrator Defaults contains settings that specify PCoIP session variable default values, which can be overridden by an administrator. These settings write registry key values to HKLM\Software\Policies\Teradici\PCoIP\pcoip_admin_defaults.

Not Overridable Administrator Settings contains the same settings as the Overridable Administrator Defaults folder, but these settings cannot be overridden by an administrator. These settings write registry key values to HKLM\Software\Policies\Teradici\PCoIP\pcoip_admin.

Local machine settings are held in the registry keys in HKLM\Software\Teradici. If the same registry key is present under both HKLM\Software\Teradici and HKLM\Software\Policies\Teradici, the group policy setting in HKLM\Software\Policies\Teradici overrides the local machine value.

I prefer setting the PCoIP Session variables as “Overridable”. You are using these settings per pool basis via GPO to give the best overall experience for your users. This will allow you to cater to most of your users but allow for some flexibility for the odd use case that tend to crop up. If you start implementing a hundred and one PCoIP GPO’s you will have more to maintain during upgrades and more to troubleshoot.
The flexibility comes in the form of using different settings on your zero client and soft clients. Zero clients are easy to make different settings but the software client can be changed with a text file. VMware KB -> http://kb.vmware.com/kb/2015292 has the full steps to create the text file. The below steps are from the KB article.

1. Create a file called pcoip_client_settings.txt using a text editor such as notepad.exe.
Settings in this file only take effect on the client.
2. Save the file to C:\Documents and Settings\\Local Settings\Application Data\Teradici
where is the login user ID.
3. Enter they key/value pair for the session variable that you want to override.
Enter one key/value pair per line, seperating the key, ‘=’ character, and value with spaces.
For example: pcoip.device_bandwidth_floor = 1000

Mar
08

#VDI Tip 65 – Repeat After Me – Tools and then the Agent

Anytime you upgrade the VMware tools on your VDI image you need to reinstall the View agent again. The tools can replace the VGA driver and end up causing blurriness, disconnects or no connection at all. I found a nice table at the Teradici website and in a VMware KB that you can reference.

 

Windows XP

Windows Vista

Windows 7

View 3.1.3 build 252693

VMware SVGA II
Version: 11.6.0.35
Dated: 4/21/2010
VMware SVGA 3D
Version: 17.14.1.42
Dated: 4/21/2010

Not Supported

View 4.0.2 build 294291

VMware SVGA II
Version: 11.6.35
Dated: 4/21/2010
 

Not Supported

View 4.5.0 build 293049

VMware SVGA II
Version: 11.6.37
Dated: 7/16/2010
VMware SVGA II
Version: 11.6.37
Dated: 7/16/2010
VMware SVGA 3D
Version: 7.14.1.49
Dated: 7/16/2010

View 4.6.0 build 366101

VMware SVGA II
Version: 11.6.0.37
Dated: 7/16/2010
VMware SVGA II
Version: 11.6.0.37
Dated: 7/16/2010
VMware SVGA 3D
Version: 7.14.1.49
Dated: 7/16/2010
View 5.0 build 481677 VMware SVGA II
Version 11.7.5.0
Date: 7/12/2011
VMware SVGAII
Version: 11.7.5.0
Dated: 7/12/2011
VMware SVGA 3D
Version 7.14.1.1061
Date: 7/29/2011

VMware KB: The PCoIP server log reports the error: Error attaching to SVGADevTap, error 4000

Mar
07

VDI-IOmark – VDI Storage Benchmarking For People With A Schedule

Translating Max IOPS into how many users you can fit onto a storage array(s) can be a pretty complicated question to ask of someone. Workloads are random between users, different blocks sizes are hitting the storage, AV is getting in the way and the list goes on and on. 20 IOPS per user is big joke in the VDI space. While 20 IOPS may represent the average, the deviation from that number can be astonishing. I encourage you watch Applied Math for VDI Design: A Statistical Approach to Designing VDI Environments. The session was presented at BriFourm last year and now is free. If you watch the video, you will see and understand what you need to be planning for.

VDI-IOmark from Evaluator Group is a tool that can tests your storage subsystem with realistic workloads. IOmeter can only give you simulated IO and not all the crazy behaviors of actual workload. VDI-IOmark uses workload replay from previous work captured from VMware RAWC implementation(View Planner). VDI-IOmark has 64 unique replays. The workloads range from 5 IOPS -20 IOPS on average but have peaks over 100. Microsoft Office(Excel, Powerpoint and Outlook), Internet Explorer, 7zip and Windows Media Player were all used to creat the replay. Boot and steady were also included in the replay. The tests are not dependent on your server platform, switching fabric or storage protocol so that’s a big thumbs up but it doesn need to run on .

The great thing about VDI-IO mark it that requires less the time to configure than building out a full environment. This is great if want to repurpose some old storage and test it our prior too or if you’re a consultant, you can do apple to apple comparisons between different vendors. Also since is each replay file contains 8 workloads test you can test your storage subsystem will less server hardware, you don’t need all the RAM it would normally take in a traditional LoginVSI or View Planner test. It’s always hard to get more money for test gear but people always want to know what the expensive box can do in the datacenter.
[Read more...]

Feb
11

VMware ADAM Database – Backup & Connect

Working with the ADAM database in VMware View is kind of like going to the dentist. You never want to go there, your reasons for going are usally related to pain, but your glad when it’s all said and done. This post will form the ground work for a series of tips & articles over the next couple of weeks. The article references all locations in terms of Windows 2008. If you’re running Windows 2003, god bless you.
Step 1 – Always Get a Current Backup
In the VMware View Administrator console you get create an on-demand backup Under View Configuration -> Servers.
Once the backup is complete, go to the server you ran the backup on and move the .LDF and .SVI file to a “safe location”.

The backup location is: C:\ProgramData\VMware\VDM\backups
.LDF = ADAM database
.SVI = View Composer Database

Step 2 – Connecting to the ADAM database

To connect to the View ADAM database:
1. Log in to one of the View Connection Servers.
2. Click Start > Administrative Tools > ADSI Edit.
3. In the console window, right-click ADSI Edit and click Connect to.
4. In the Name field type: View ADAM Database
5. Select Select or type a Distinguished Name or Naming Context.
6. In the field below, type dc=vdi,dc=vmware,dc=int
7. Select Select or type a domain or server.
8. In the field below, type localhost
9. Click OK.
10. Click View ADAM Database [localhost] to expand.
11. Click DC=vdi,dc=vmware,dc=int to expand