Office 2K on 2003 Terminal Server

[Guest]

I'm stumped, please help. We have a 2003 Terminal Server
running in Terminal Services mode. The server has been
working great while using other applications, but we are
now attempting to add Office 2K (particularly Access) to
the server.

We are aware of the installation procedure specific to
Terminal Services using TermSrvr.mst from the ORK tools.
We followed this installation procedure without a hitch.
Now anyone who is a member of the administrator group can
use Office, but when putting them into the appropriate
group (restricted by group policy), we are receiving the
error...

"Only administrators have permission to add, remove or
configure software during a Terminal Services Remote
session."

There is a setting in Group Policy that permits
Administrators to install and configure programs remotely,
but it only pertains to administrators and states other
users cannot install programs remotely.

Question, is there a work around in Office to avoid this
behavior? We do not have this difficulty with any other
software and suspect it has to do with office's installing
itself to individual profiles. Note: We tried using it
once giving the user administrative privileges and it
works fine, only to revert back to the previous behavior
once user is removed from administrators group.

Thanks,
Andy

P.S. We are currently TechNet Plus subscribers.

 

[ty_lamb]

I'm having the exact same problem but with Terminal Server 2000. I
you've found a solution I'd apprciate you passing it along.

Thx, Ty Lamb



wrote:

*I'm stumped, please help. We have a 2003 Terminal Server
running in Terminal Services mode. The server has been
working great while using other applications, but we are
now attempting to add Office 2K (particularly Access) to
the server.

We are aware of the installation procedure specific to
Terminal Services using TermSrvr.mst from the ORK tools.
We followed this installation procedure without a hitch.
Now anyone who is a member of the administrator group can
use Office, but when putting them into the appropriate
group (restricted by group policy), we are receiving the
error...

"Only administrators have permission to add, remove or
configure software during a Terminal Services Remote
session."

There is a setting in Group Policy that permits
Administrators to install and configure programs remotely,
but it only pertains to administrators and states other
users cannot install programs remotely.

Question, is there a work around in Office to avoid this
behavior? We do not have this difficulty with any other
software and suspect it has to do with office's installing
itself to individual profiles. Note: We tried using it
once giving the user administrative privileges and it
works fine, only to revert back to the previous behavior
once user is removed from administrators group.

Thanks,
Andy

P.S. We are currently TechNet Plus subscribers.

-
ty_lam

 

[ty_lamb]

I'm having the exact same problem but with Terminal Server 2000. I
you've found a solution I'd apprciate you passing it along.

Thx, Ty Lamb



wrote:

*I'm stumped, please help. We have a 2003 Terminal Server
running in Terminal Services mode. The server has been
working great while using other applications, but we are
now attempting to add Office 2K (particularly Access) to
the server.

We are aware of the installation procedure specific to
Terminal Services using TermSrvr.mst from the ORK tools.
We followed this installation procedure without a hitch.
Now anyone who is a member of the administrator group can
use Office, but when putting them into the appropriate
group (restricted by group policy), we are receiving the
error...

"Only administrators have permission to add, remove or
configure software during a Terminal Services Remote
session."

There is a setting in Group Policy that permits
Administrators to install and configure programs remotely,
but it only pertains to administrators and states other
users cannot install programs remotely.

Question, is there a work around in Office to avoid this
behavior? We do not have this difficulty with any other
software and suspect it has to do with office's installing
itself to individual profiles. Note: We tried using it
once giving the user administrative privileges and it
works fine, only to revert back to the previous behavior
once user is removed from administrators group.

Thanks,
Andy

P.S. We are currently TechNet Plus subscribers.

-
ty_lam

 

[ty_lamb]

I'm having the exact same problem but with Terminal Server 2000. I
you've found a solution I'd apprciate you passing it along.

Thx, Ty Lamb



wrote:

*I'm stumped, please help. We have a 2003 Terminal Server
running in Terminal Services mode. The server has been
working great while using other applications, but we are
now attempting to add Office 2K (particularly Access) to
the server.

We are aware of the installation procedure specific to
Terminal Services using TermSrvr.mst from the ORK tools.
We followed this installation procedure without a hitch.
Now anyone who is a member of the administrator group can
use Office, but when putting them into the appropriate
group (restricted by group policy), we are receiving the
error...

"Only administrators have permission to add, remove or
configure software during a Terminal Services Remote
session."

There is a setting in Group Policy that permits
Administrators to install and configure programs remotely,
but it only pertains to administrators and states other
users cannot install programs remotely.

Question, is there a work around in Office to avoid this
behavior? We do not have this difficulty with any other
software and suspect it has to do with office's installing
itself to individual profiles. Note: We tried using it
once giving the user administrative privileges and it
works fine, only to revert back to the previous behavior
once user is removed from administrators group.

Thanks,
Andy

P.S. We are currently TechNet Plus subscribers.

-
ty_lam

 

[ty_lamb]

I'm having the exact same problem but with Terminal Server 2000. I
you've found a solution I'd apprciate you passing it along.

Thx, Ty Lamb



wrote:

*I'm stumped, please help. We have a 2003 Terminal Server
running in Terminal Services mode. The server has been
working great while using other applications, but we are
now attempting to add Office 2K (particularly Access) to
the server.

We are aware of the installation procedure specific to
Terminal Services using TermSrvr.mst from the ORK tools.
We followed this installation procedure without a hitch.
Now anyone who is a member of the administrator group can
use Office, but when putting them into the appropriate
group (restricted by group policy), we are receiving the
error...

"Only administrators have permission to add, remove or
configure software during a Terminal Services Remote
session."

There is a setting in Group Policy that permits
Administrators to install and configure programs remotely,
but it only pertains to administrators and states other
users cannot install programs remotely.

Question, is there a work around in Office to avoid this
behavior? We do not have this difficulty with any other
software and suspect it has to do with office's installing
itself to individual profiles. Note: We tried using it
once giving the user administrative privileges and it
works fine, only to revert back to the previous behavior
once user is removed from administrators group.

Thanks,
Andy

P.S. We are currently TechNet Plus subscribers.

-
ty_lam

 

[ty_lamb]

I'm having the exact same problem but with Terminal Server 2000. I
you've found a solution I'd apprciate you passing it along.

Thx, Ty Lamb



wrote:

*I'm stumped, please help. We have a 2003 Terminal Server
running in Terminal Services mode. The server has been
working great while using other applications, but we are
now attempting to add Office 2K (particularly Access) to
the server.

We are aware of the installation procedure specific to
Terminal Services using TermSrvr.mst from the ORK tools.
We followed this installation procedure without a hitch.
Now anyone who is a member of the administrator group can
use Office, but when putting them into the appropriate
group (restricted by group policy), we are receiving the
error...

"Only administrators have permission to add, remove or
configure software during a Terminal Services Remote
session."

There is a setting in Group Policy that permits
Administrators to install and configure programs remotely,
but it only pertains to administrators and states other
users cannot install programs remotely.

Question, is there a work around in Office to avoid this
behavior? We do not have this difficulty with any other
software and suspect it has to do with office's installing
itself to individual profiles. Note: We tried using it
once giving the user administrative privileges and it
works fine, only to revert back to the previous behavior
once user is removed from administrators group.

Thanks,
Andy

P.S. We are currently TechNet Plus subscribers.

-
ty_lam

 

[ty_lamb]

(Paths have been stripped for easier reading)
I got it to work. The first time I installed it I did

setupstd.exe transforms=TermSrvr.mst

I uninstalled it and then used

setupstd.exe transforms=TermSrvr.mst /qn+

I think that was the problem because it is working fine now


-
ty_lam

 

[ty_lamb]

(Paths have been stripped for easier reading)
I got it to work. The first time I installed it I did

setupstd.exe transforms=TermSrvr.mst

I uninstalled it and then used

setupstd.exe transforms=TermSrvr.mst /qn+

I think that was the problem because it is working fine now


-
ty_lam

 

[ty_lamb]

(Paths have been stripped for easier reading)
I got it to work. The first time I installed it I did

setupstd.exe transforms=TermSrvr.mst

I uninstalled it and then used

setupstd.exe transforms=TermSrvr.mst /qn+

I think that was the problem because it is working fine now


-
ty_lam

 

[ty_lamb]

(Paths have been stripped for easier reading)
I got it to work. The first time I installed it I did

setupstd.exe transforms=TermSrvr.mst

I uninstalled it and then used

setupstd.exe transforms=TermSrvr.mst /qn+

I think that was the problem because it is working fine now


-
ty_lam

 

[ty_lamb]

(Paths have been stripped for easier reading)
I got it to work. The first time I installed it I did

setupstd.exe transforms=TermSrvr.mst

I uninstalled it and then used

setupstd.exe transforms=TermSrvr.mst /qn+

I think that was the problem because it is working fine now


-
ty_lam