COM component registration problem

[batul]

we have an application for which installer has been created using
installshield. this appilcation is installed for all user of that PC. it is
done by setting ALLUSERS property to 2 in installer. this application
consists of COM server exe, which is used by main application. Once this
application is installed by administrator on any PC it works perfectly fine
for that user but if any other user tries to execute an application for first
time, OS does some configuration for that user and PC restarts. different
behaviour has been observed on XP & vista.
Operating system XP
Operating system does configuration for each group(users group defined by
OS) once, when application is executed by user of that group for first time.
after that any user of a group for which configuration has been done can
sucessfully execute an application.
Operating system Vista
OS does configuration for each user of that Pc and do not retain this
information(i.e. is any other user access an application it configure for
this user and previous user setting has been destroyed) so at any time only
one user can successfully execute an application. it is been observed that
there is some problem related with COM server registration as if COM server
EXE has been executed before executing application no problem occurs who so
ever execute an application.

 

[Paul Montgumdrop]

we have an application for which installer has been created using
installshield. this appilcation is installed for all user of that PC. it is
done by setting ALLUSERS property to 2 in installer. this application
consists of COM server exe, which is used by main application. Once this
application is installed by administrator on any PC it works perfectly fine
for that user but if any other user tries to execute an application for first
time, OS does some configuration for that user and PC restarts. different
behaviour has been observed on XP & vista.
Operating system XP
Operating system does configuration for each group(users group defined by
OS) once, when application is executed by user of that group for first time.
after that any user of a group for which configuration has been done can
sucessfully execute an application.
Operating system Vista
OS does configuration for each user of that Pc and do not retain this
information(i.e. is any other user access an application it configure for
this user and previous user setting has been destroyed) so at any time only
one user can successfully execute an application. it is been observed that
there is some problem related with COM server registration as if COM server
EXE has been executed before executing application no problem occurs who so
ever execute an application.

Have you looked at this link about ALLUSERS?

http://msdn.microsoft.com/en-us/library/aa367559(VS.85).aspx

Are you running the installshield installation package exe using the Run
as Administrator setting on the exe when UAC is enabled?

About the COM registration, it seems that UAC can interfere with this
according to the link.

<http://chrisbensen.blogspot.com/2007/02/com-registration-under-microsoft.html>

It's also talking about using the hidden built-in Administrator account,
yes, that same built-in Administrator account on XP.

<http://www.computerperformance.co.u...nefits_of_Vistas_Hidden_Administrator_Account>

You should read the information in the link, like read the section about
the benefits of using the Administrator account, which is the account is
a admin account that has full admin rights all the time and UAC can
still be enabled.

As opposed to using your default out of the box user/admin account on
Vista that does not have full rights, because of the two access tokens
being used on the user/admin account, with the default being the
Standard user token. And that's why you must run something with Run As
Administrator to can access to the Admin Full rights token and escalate
privileges, not so with the built-in Administrator account.

<http://technet.microsoft.com/en-us/library/cc709691.aspx>