deploying Viewmail for Outlook on terminal servers

[kdotten36]

We have 10 terminal servers in a farm that users logon to.  They are Windows 2008 Server R2.  We're using Viewmail 9.0.0.2 which I understand is compatible with terminal servers.

Is there an easy way to deploy this on each server without forcing the users to fill out the configuration information?  I installed it on a test server and everyone who logged in was prompted upon launching Outlook to fill out all information.

Ideally, what I'd like is to create a Group Policy to automatically fill out all fields except for password obviously, so they can just enter that on first logon.

If that's not possible, I'd rather the prompt to configure Viewmail be disabled by default so I can deploy it in groups at planned times and just walk them through the configuration steps.

Anyone experienced with this?

Thanks.

[Jonathan Schulenberg · Accepted solution]

You'll want to configure AdminConfig.xml prior to running the installer so that the Unity Connection server information gets pre-populated. As for user-specific credentials you can avoid this by using the Single Sign-On (poorly named, do not confuse with a real SSO product/feature) feature introduced in Viewmail 8.6(5) onward. This should negate the configuration dialog if memory serves. I would try it on your own workstation first and then reproduce on WTS.

Correction: I just tried this on my Win7 VM to validate the guidance I provided. When I specified a element in the XML file I still got the ViewMail Wizard; however, all of the values had been pre-populated for me, I just needed to click Next, Next, Finish. My VM was not domain-joined though so the experience may differ slightly if the user is logged into the domain as the Release Notes state they should be.

Please remember to rate helpful responses and identify helpful or correct answers.

[kdotten36]

Thanks so much, the adminconfig.xml takes significant edge off the blow.  We're unable to use the single sign-on since our hardware platform (7835-H3) is apparently the only one not supported in CUC8.6 and up, which is disappointing for servers less than 2 years old.

[Jonathan Schulenberg]

Are you sure it's an 7835-H3 (i.e. HP)? I believe that the 7835-H3 servers never shipped as that was when the HP/Cisco relationship was having difficulties due to the UCS launch. Is it perhaps a 7835-I3 (i.e. IBM)?  If it is, then you are in fact supported as a Platform Overlay 2 server as long as you bump the RAM to 6GB.

6-GB (two 2-GB dual in-line memory module [DIMM]) PC3-10600 1333-MHz, fully buffered DDR-3 registered DIMM (RDIMM). The RAM (as shipped) needs some enhancement. Only 4-GB RAM is shipped with the server. Connection 8.6.1 and later require 6-GB RAM, therefore, add 2-GB RAM to the server (MEM-7835-I3-2GB=).

With that said, do not buy any more MCS servers, under any circumstances.

Please remember to rate helpful responses and identify helpful or correct answers.

[kdotten36]

Yes, it's an HP unfortunately.  It's not Cisco branded or anything.  It's what was recommended by our vendor.

[jonwoloshyn]

Jonathan. When you say "poorly named, do not confuse with a real SSO product", do you mean to say that OpenAM or some other SSO solution doesn't need to be set up? I was always under the impression that you didn't need OpenAM for VMO SSO (going back to CUC 8.6 when SAML was not supported), but I have a customer that is having some VMO issues and TAC is saying it is because OpenAM or ADFS isn't setup.