Check the MS knowledgebase (there might be info in Office help too).
There is a process to follow and IIRC an installation file to run to get
Office 2000 working for terminal service users.
If my brain was awake I'd probably be able to give more detail, but all
I can remember is I read knowledgebase articles and followed the
instructions and I have a couple of Win2K terminal server users running
Office 2K w/no problems.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
[EMAIL PROTECTED]
Sent: Monday, August 13, 2001 9:08 AM
To: NT 2000 Discussions
Subject: Re: Install Office 2000 on W2K terminal server
I have not seen any replies, so I'll throw in my 2 cents...
I believe that this is a known limitation for numerous installs, could
Office be one of them? I seem to recall it has to do with the fact that
terminal server users actually have a different kind of registry/default
directory structure that a locally logged on user. Many installs make
assumptions about the Windows defaults and those assumptions are
incorrect
for a TS user. Also, I recall there are some restrictions placed on a
TS
user, especially since they are a virtual user. Maybe one of these
factors
limits the install of Office. Would not surprise me since the Office
install is quite complex and uses a large number of OS features.
Have you tried searching TechNet?
Paul Pawluk
<[EMAIL PROTECTED]> T
To: "NT 2000 Discussions"
<[EMAIL PROTECTED]>
Sent by: cc:
bounce-nt2000-42092
@ls.swynk.com bcc:
Subject:
Install Office 2000 on W2K
terminal server
08/09/01 03:44 PM
Please respond to
"NT 2000
Discussions"
Hello everyone.
Has anyone been able to successfully install Office 2000 on a Windows
2000
server running Terminal Server? I haven't, and here's what has happened
to
me so far:
I've tried to install Office 2000 using the Add/Remove Programs applet
in
the Control Panel per Microsoft's instructions (browse to the SETUP.EXE
file
on the Office 2000 Disk 1). I have also tried adding the
TRANSFORMS=path\TermSrvr.mst after SETUP.EXE on that command line, again
as
per Microsoft.
The installation gets about halfway through (as shown by the progress
bar),
then quits, saying that the installation could not write to a Windows
protected file. I disabled Windows File Protection through the
registry,
and the same error still occurs.
Thanks in advance for any thoughts that you have.
Regards,
Paul Pawluk
Texas Windstorm Insurance Association
[EMAIL PROTECTED]
--My karma ran over your dogma.
------
You are subscribed as [EMAIL PROTECTED]
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe send a blank email to [EMAIL PROTECTED]
------
You are subscribed as [EMAIL PROTECTED]
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe send a blank email to [EMAIL PROTECTED]
------
You are subscribed as archive@jab.org
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe send a blank email to [EMAIL PROTECTED]
