I have users on non-trusted domains that are setup in such a way that we cannot simply push the software install package to their computers for the Contributor web client components. I have instructed the users to obtain local admin rights on their machines, temporarily, and to access Cognos Connection and then drill into one of the Contributor apps, forcing the download and install of the client components. This works well.
The problem is that when local admin rights are removed from the user, they continue to get an error message that suggests the client components are trying to write to the registry to run the client components. Any suggestions? Are users need to update their budgets and their local IT does not want to leave admin rights on their machines...
Windows 2003 server
Cognos 8.4.1
Windows XP client
Hey Jeff,
What are the errors that are experienced? What's the version of IE that the end user's are using?
I haven't seen any issues like what you've described. In fact, in most cases the install approach you've identified usually works and continues to work. The install is being performed into the user's local profile and not C:\program files\cognos\etc etc?
It might be prudent to fire up process monitor (http://technet.microsoft.com/en-us/sysinternals/bb896645) and take a look at the registry / file system activity (you can configure a filter on the contributor.exe).
Let me know
Most of our users are on IE8 and Windows XP, although a few users are on IE7 and/or Windows Vista (seems to be causing another issue with getting cognosrcp installed, but I don't want to mix threads...).
Do you happen to have a screenshot of the errors encountered?