Windows NT Windows 2003 TS - Software Constantly re-installing

  • Thread starter Thread starter LeighP
  • Start date Start date
L

LeighP

We have a client - remote with own IT (i.e. have never seen this setup
personally).
They're running Windows Server 2003 Standard Edition Terminal Services.

The server has Office 2003 Standard Edition installed on it.

We have an Access 2003 Runtime application recently installed on it.
This same runtime application has successfully installed on many hundreds of
PCs and indeed several TS servers perfectly well.
It's an Access 2003 Runtime wrapped in an Installshield expression package
(uses an MSI).

On this one instance - every attempt to launch the application file (an
Access mde) sees the whole install of the package fire up and attempt to run
again.
It has been fully removed - and then installed again clean. But the
behaviour persists.
Every launch of either the MDE file (or even the MSAcess.exe itself!) merely
relaunches the whole package installer.

This behaviour occurs for Admin as well as limited users.


Any thoughts would be most welcome indeed! :-S

Many thanks.
 
Hi Leigh,

I assume that this means that KB 911682 didn't solve the problem?
Nothing in the EventLog?
It sounds like the Access Runtime package was deployed with a
Software Installation GPO and published or assigned to all users.
That doesn't work on a TS.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"LeighP" <LeighNews@NotThisBitDatabaseDevelopment.co.uk> wrote on
16 aug 2007 in microsoft.public.windows.terminal_services:

> We have a client - remote with own IT (i.e. have never seen this
> setup personally).
> They're running Windows Server 2003 Standard Edition Terminal
> Services.
>
> The server has Office 2003 Standard Edition installed on it.
>
> We have an Access 2003 Runtime application recently installed on
> it. This same runtime application has successfully installed on
> many hundreds of PCs and indeed several TS servers perfectly
> well. It's an Access 2003 Runtime wrapped in an Installshield
> expression package (uses an MSI).
>
> On this one instance - every attempt to launch the application
> file (an Access mde) sees the whole install of the package fire
> up and attempt to run again.
> It has been fully removed - and then installed again clean. But
> the behaviour persists.
> Every launch of either the MDE file (or even the MSAcess.exe
> itself!) merely relaunches the whole package installer.
>
> This behaviour occurs for Admin as well as limited users.
>
>
> Any thoughts would be most welcome indeed! :-S
>
> Many thanks.
 
I've forwarded that KB to them - just keeping the feelers out there for now.
:-)
(The pressure will still be applied to us - even if they don't get around to
it immediately :-S. Such is life.)

I'll chase them up on all of this.

Many thanks!

Leigh

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message
news:Xns998EE6046B998veranoesthemutforsse@207.46.248.16...
> Hi Leigh,
>
> I assume that this means that KB 911682 didn't solve the problem?
> Nothing in the EventLog?
> It sounds like the Access Runtime package was deployed with a
> Software Installation GPO and published or assigned to all users.
> That doesn't work on a TS.
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> "LeighP" <LeighNews@NotThisBitDatabaseDevelopment.co.uk> wrote on
> 16 aug 2007 in microsoft.public.windows.terminal_services:
>
>> We have a client - remote with own IT (i.e. have never seen this
>> setup personally).
>> They're running Windows Server 2003 Standard Edition Terminal
>> Services.
>>
>> The server has Office 2003 Standard Edition installed on it.
>>
>> We have an Access 2003 Runtime application recently installed on
>> it. This same runtime application has successfully installed on
>> many hundreds of PCs and indeed several TS servers perfectly
>> well. It's an Access 2003 Runtime wrapped in an Installshield
>> expression package (uses an MSI).
>>
>> On this one instance - every attempt to launch the application
>> file (an Access mde) sees the whole install of the package fire
>> up and attempt to run again.
>> It has been fully removed - and then installed again clean. But
>> the behaviour persists.
>> Every launch of either the MDE file (or even the MSAcess.exe
>> itself!) merely relaunches the whole package installer.
>>
>> This behaviour occurs for Admin as well as limited users.
>>
>>
>> Any thoughts would be most welcome indeed! :-S
>>
>> Many thanks.
 
Vera,

When you say "assigned to all users" - do you mean installed with
permissions for all users to run?
In what way doesn't it work on TS - and what should be done in it's stead?

Cheers!

Leigh

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message
news:Xns998EE6046B998veranoesthemutforsse@207.46.248.16...
> Hi Leigh,
>
> I assume that this means that KB 911682 didn't solve the problem?
> Nothing in the EventLog?
> It sounds like the Access Runtime package was deployed with a
> Software Installation GPO and published or assigned to all users.
> That doesn't work on a TS.
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> "LeighP" <LeighNews@NotThisBitDatabaseDevelopment.co.uk> wrote on
> 16 aug 2007 in microsoft.public.windows.terminal_services:
>
>> We have a client - remote with own IT (i.e. have never seen this
>> setup personally).
>> They're running Windows Server 2003 Standard Edition Terminal
>> Services.
>>
>> The server has Office 2003 Standard Edition installed on it.
>>
>> We have an Access 2003 Runtime application recently installed on
>> it. This same runtime application has successfully installed on
>> many hundreds of PCs and indeed several TS servers perfectly
>> well. It's an Access 2003 Runtime wrapped in an Installshield
>> expression package (uses an MSI).
>>
>> On this one instance - every attempt to launch the application
>> file (an Access mde) sees the whole install of the package fire
>> up and attempt to run again.
>> It has been fully removed - and then installed again clean. But
>> the behaviour persists.
>> Every launch of either the MDE file (or even the MSAcess.exe
>> itself!) merely relaunches the whole package installer.
>>
>> This behaviour occurs for Admin as well as limited users.
>>
>>
>> Any thoughts would be most welcome indeed! :-S
>>
>> Many thanks.
 
When you install software through a GPO, you can either assign or
publish the software to users (and only assign to computers).

Simply put, "publish" means that the software is available for
users to install if they want to, and will be automatically
installed if they double-click on a document that needs the
application to open it (i.e. double-click a .xls file, and Excel
gets installed).
"Assign" means that it will be automatically installed when they
logon, if they want to or not.

This is a method to deploy software to workstations, but it doesn't
work on Terminal Servers. Users can't install software on a TS, and
it should be installed just once, while the server is in install
mode, to ensure multi-user functionality.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

"LeighP" <LeighNews@NotThisBitDatabaseDevelopment.co.uk> wrote on
17 aug 2007:

> Vera,
>
> When you say "assigned to all users" - do you mean installed
> with permissions for all users to run?
> In what way doesn't it work on TS - and what should be done in
> it's stead?
>
> Cheers!
>
> Leigh
>
> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote
> in message
> news:Xns998EE6046B998veranoesthemutforsse@207.46.248.16...
>> Hi Leigh,
>>
>> I assume that this means that KB 911682 didn't solve the
>> problem? Nothing in the EventLog?
>> It sounds like the Access Runtime package was deployed with a
>> Software Installation GPO and published or assigned to all
>> users. That doesn't work on a TS.
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> "LeighP" <LeighNews@NotThisBitDatabaseDevelopment.co.uk> wrote
>> on 16 aug 2007 in microsoft.public.windows.terminal_services:
>>
>>> We have a client - remote with own IT (i.e. have never seen
>>> this setup personally).
>>> They're running Windows Server 2003 Standard Edition Terminal
>>> Services.
>>>
>>> The server has Office 2003 Standard Edition installed on it.
>>>
>>> We have an Access 2003 Runtime application recently installed
>>> on it. This same runtime application has successfully
>>> installed on many hundreds of PCs and indeed several TS
>>> servers perfectly well. It's an Access 2003 Runtime wrapped in
>>> an Installshield expression package (uses an MSI).
>>>
>>> On this one instance - every attempt to launch the application
>>> file (an Access mde) sees the whole install of the package
>>> fire up and attempt to run again.
>>> It has been fully removed - and then installed again clean.
>>> But the behaviour persists.
>>> Every launch of either the MDE file (or even the MSAcess.exe
>>> itself!) merely relaunches the whole package installer.
>>>
>>> This behaviour occurs for Admin as well as limited users.
>>>
>>>
>>> Any thoughts would be most welcome indeed! :-S
>>>
>>> Many thanks.
 
Ah Lovely!

Forwarded and many thanks again.

Leigh

"Vera Noest [MVP]" <Vera.Noest@remove-this.hem.utfors.se> wrote in message
news:Xns998F78D3AB26Fveranoesthemutforsse@207.46.248.16...
> When you install software through a GPO, you can either assign or
> publish the software to users (and only assign to computers).
>
> Simply put, "publish" means that the software is available for
> users to install if they want to, and will be automatically
> installed if they double-click on a document that needs the
> application to open it (i.e. double-click a .xls file, and Excel
> gets installed).
> "Assign" means that it will be automatically installed when they
> logon, if they want to or not.
>
> This is a method to deploy software to workstations, but it doesn't
> work on Terminal Servers. Users can't install software on a TS, and
> it should be installed just once, while the server is in install
> mode, to ensure multi-user functionality.
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> *----------- Please reply in newsgroup -------------*
>
> "LeighP" <LeighNews@NotThisBitDatabaseDevelopment.co.uk> wrote on
> 17 aug 2007:
>
>> Vera,
>>
>> When you say "assigned to all users" - do you mean installed
>> with permissions for all users to run?
>> In what way doesn't it work on TS - and what should be done in
>> it's stead?
>>
>> Cheers!
>>
>> Leigh
>>
>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote
>> in message
>> news:Xns998EE6046B998veranoesthemutforsse@207.46.248.16...
>>> Hi Leigh,
>>>
>>> I assume that this means that KB 911682 didn't solve the
>>> problem? Nothing in the EventLog?
>>> It sounds like the Access Runtime package was deployed with a
>>> Software Installation GPO and published or assigned to all
>>> users. That doesn't work on a TS.
>>>
>>> _________________________________________________________
>>> Vera Noest
>>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>> TS troubleshooting: http://ts.veranoest.net
>>> ___ please respond in newsgroup, NOT by private email ___
>>>
>>> "LeighP" <LeighNews@NotThisBitDatabaseDevelopment.co.uk> wrote
>>> on 16 aug 2007 in microsoft.public.windows.terminal_services:
>>>
>>>> We have a client - remote with own IT (i.e. have never seen
>>>> this setup personally).
>>>> They're running Windows Server 2003 Standard Edition Terminal
>>>> Services.
>>>>
>>>> The server has Office 2003 Standard Edition installed on it.
>>>>
>>>> We have an Access 2003 Runtime application recently installed
>>>> on it. This same runtime application has successfully
>>>> installed on many hundreds of PCs and indeed several TS
>>>> servers perfectly well. It's an Access 2003 Runtime wrapped in
>>>> an Installshield expression package (uses an MSI).
>>>>
>>>> On this one instance - every attempt to launch the application
>>>> file (an Access mde) sees the whole install of the package
>>>> fire up and attempt to run again.
>>>> It has been fully removed - and then installed again clean.
>>>> But the behaviour persists.
>>>> Every launch of either the MDE file (or even the MSAcess.exe
>>>> itself!) merely relaunches the whole package installer.
>>>>
>>>> This behaviour occurs for Admin as well as limited users.
>>>>
>>>>
>>>> Any thoughts would be most welcome indeed! :-S
>>>>
>>>> Many thanks.
 
Back
Top