rpmello
Enthusiast
Enthusiast

Change Domain Drop-down Default?

Since upgrading to View 4.0, I've encountered a new issue I hadn't really seen before. The value in the domain drop-down selection when logging into the View Portal is now defaulting to our root domain instead of our production domain. Is there any way to change the default back to our production domain, or simply remove the root domain altogether since it's not used for authentication?

Thanks

0 Kudos
3 Replies
mgmn
Enthusiast
Enthusiast

There is a registry string value that you can specify that will set the default domain:

HKCU\Software\VMware, Inc.\VMware VDM\Client\MRDomain

Note it is a Current User value, you could specify this in the HKU\.default section to have it apply to all users.

You can also force the selection of a certain domain in the scripting section of the View client ADM files. Either through editing your group policy or use a local machine policy to set this.

I also think there may be a way to specify this in the command line setup when installing View Client, I thought I seen that around somewhere but I can't remember right now.

Hopefully this helps.

-Matt

0 Kudos
rpmello
Enthusiast
Enthusiast

That would definitely help for users inside my domain, but how about users that don't login to my domain and are using VDI to access domain resources? That's my biggest segment of users and I don't have access to their PCs to make those changes.

0 Kudos
mgmn
Enthusiast
Enthusiast

I solved this problem by repackaging the View Client installer and

including the MRDomain key as part of my repackaged setup, which I have

made available to our users.

If you have ThinApp you could also use that to virtualize the View

client and hold your needed settings.

Some of these blog postings may be helpful:

http://oztek.blogspot.com/2009/07/vmware-view-client-silent-installation.html

http://communities.vmware.com/thread/240986

http://www.thatsmyview.net/2009/04/17/silent-install-without-reboot/

http://myvirtualcloud.net/?p=770

Outside of distributing a repacked installer or thinapp I'm not sure

what other methods you could employ to ensure the user has the correct

settings. Someone else may have some other ideas.