Windows NT ActiveX is installed but runs only for Administrator

[Scott]

We have recently replaced a Terminal Server. After installing Terminal
Services we installed Adobe Flash Player and a QuickBooks ActiveX control.
Both work if a user with local Administrator rights logs into the local
machine. Both work if "Administrator" logs into the domain. Neither works
if anyone else logs in to the domain - even other Domain Admins. Console vs.
terminal session makes no difference. The domain controller has not been
changed, so any domain Group Policies that were in affect for the old Term.
Server are still in affect for the new one.

We know it has to be permissions/security - but we've tried everything we
can think of. We've added "Domain Users" to the local Administrators group
and we've added "Domain Users" to the Registry permissions for the QuickBooks
ActiveX control, among other things. Can anyone suggest something else to
try?

The Terminal Server is a Windows 2003 R2 Standard x64 Edition with all
updates.

 

[Vera Noest [MVP]]

Do the users get any error message?
Check if this helps:

123869 - Message: "An ActiveX control on this page is not safe" or
QuickBooks Centers are blank
http://www.quickbooks.com/support/faqs/qbw2002/premier/123869.html

If that doesn't fix it, check this FAQ from
http://ts.veranoest.net/ts_faq_applications.htm#install_runonce

Q: My application runs only for the Administrator who installed the
application, but not for normal users or other accounts with
Administrator rights

A: Some applications create HKEY_CURRENT_USER registry settings the
first time a user runs the program, rather than during
installation.

The way to avoid this problem is to run the application for the
first time from the Administrator account, immediately after
installation, and WHILE THE SERVER IS STILL IN INSTALL MODE.

If you do so, the registry key and ini-file creation is monitored
by the server and put into the shadow area of the registry. All
users then receive the registry entries and a personal copy of the
ini file in their windows folder, when they run the application for
the first time.

What you can do now to solve the problem is:

1. make sure no other user is logged onto the server
2. put the server into install mode (change user /install)
3. run the application under an administrative account THAT HAS
NEVER RUN THE APPLICATION BEFORE (create a new one if needed)
4. exit the application
5. put the server back into execute mode (change user /execute)
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?U2NvdHQ=?= <Scott@discussions.microsoft.com> wrote on 24
aug 2007 in microsoft.public.windows.terminal_services:

> We have recently replaced a Terminal Server. After installing
> Terminal Services we installed Adobe Flash Player and a
> QuickBooks ActiveX control. Both work if a user with local
> Administrator rights logs into the local machine. Both work if
> "Administrator" logs into the domain. Neither works if anyone
> else logs in to the domain - even other Domain Admins. Console
> vs. terminal session makes no difference. The domain controller
> has not been changed, so any domain Group Policies that were in
> affect for the old Term. Server are still in affect for the new
> one.
>
> We know it has to be permissions/security - but we've tried
> everything we can think of. We've added "Domain Users" to the
> local Administrators group and we've added "Domain Users" to the
> Registry permissions for the QuickBooks ActiveX control, among
> other things. Can anyone suggest something else to try?
>
> The Terminal Server is a Windows 2003 R2 Standard x64 Edition
> with all updates.