Deploying UCA 5.0 client with privilege authority

[rlafata]

We plan on deploying UCA client 5.0 from 4.1.25.  Most of our users do not have admin rights to their PC.  We would like to use our privilege authority software.  When we tried to use this in the past it locked up Outlook 2007.  Has anyone used this software when rolling out UCA 5.0?  If so what files need admin rights to run the upgrade?

Thanks for any assistance!

[akuhn]

I'm not familiar with that brand of roll-out software, but when I do something like that, I create a Group Policy Object and assign it to the computer object rather than the user object.  Therefore, user rights are no longer an issue because the installation occurs before the user logs into the PC.

You can look at some of my posts on how I deployed UCA 4x doing just that. 

Is this a possibility in your organization?

[rlafata]

Well we pushed out UCA 5.0 and all users are asked to upgrade the collaboration client.  They installed it but everytime they exit out of UCA and reopen it asks them again to upgrade colloboarion client?   We have version 1.2.4.0 of AWC but the server is trying to load 5.0 of AWC???   Anybody run into this issue?

[akuhn]

I'm going to guess that your AWC should be upgraded to match your new UCA server.  They are two peas-in-a-pod.

[martyn]

Apart from you AWC being quite old and needing to be upgraded to MCA, I know there was a bug with one version of UCA 5 that caused the loop of the AWC client to occur. An update fixed the issue.

[dozer]

The AWC needs to be upgraded to MCA.  The error stating there is a newer client download is a bug because even if you turn off the MCA feature for the UCA feature profile, you will still get that error because your UCA is configured with a collaboration server.  The client installs with the collaboration server enabled regardless of your feature profile.  The latest release of 4.0.0.25 still has this bug.  I just went through this with a new install and Mitel. 

For installers out there, if you install UCA and you have MCA, do NOT install the MCA blade on the same server as UCA unless you plan on getting it running.  If the blade is installed, UCA still tries to run the collaboration server regardless of features.  Also, if UCA and MCA are on the same server, I would suggest that your DN of MAS is the FQDN of MCA.  Example:

MAS - collab.domain.com - Locally resolved
MCA - collab.domain.com - Externally and internally resolved and points to internal LAN IP
UCA - uca.domain.com - Externally and internally resolved and points to internal LAN IP
UCA - always build via FQDN and never IP

Once this is done, and users browse to collab.domain.com, they will automatically be routed to collab.domain.com/portal.  You can still access collab.domain.com/server-manager internally.