1 reply to this topic

[fish]

Hi,
One of the clients we supply uses Windows TSE to provide web-based access to our software.  

Part of the installation runs an app that must access a database, which means that MDAC and DCOM must be installed on the system already.  This only needs to be done once per machine.

We solve this by using merge modules, and running the app after a reboot (using the RunOnce registry key in HKLM).  

However, despite the fact that this is done in HKLM, every user sees the app first time they log on.  We don't want this.  We want the administrator to log on, and let the app complete, and then no-one else has to worry about it.

We think this could be because TSE is maintaining a virtual machine for each user.  Is there any way to fix this?

Many thanks

John

[P_Sinclair]

Only the administrator can write and delete in HKLM, which means that runonce will not remove itself at Login if anyone other than an administrator logs in. So essentially, your entry in runonce will run for every user, Every time they login(not just once) until the admin logs in. Once the admin logs in, runonce will succesfully delete itself and no one will see your app launching at login.

the best solution would be to write the runonce entry into the current users section of the registry rather than HKLM. Then only the administrator would get the install launching on login rather than everyone being bothered everytime they login until the admin logs in.

Hope this helps.