S
Sajmon
Hi.
I have a problem that is quite annoying. I had a policy
that deployed Office 2000, it worked nicely except that
the users had to type in the product ID... So, I followed
the tips I had gotten, and made an administrative
installation of office 2000. Now when the client
computers try to install Office 2000, they recieve the
exact error messages mentioned on the page on the
following link.
http://support.microsoft.com/default.aspx?id=304746
The thing is, these files are on a Windows 2000 server
(not a DC)... I removed the directory with Office 2000,
and re-installed it from a CD. Still the same thing
happens. Within the folder I have other packages that are
working perfect... Office XP, Acrobet etc.
Any ideas? the resolution mentioned in KB isnt to useful
to me, since my packages are on a windows 2000 server
already, and not a NT file server.
Thanks for listening.
/Simon
I have a problem that is quite annoying. I had a policy
that deployed Office 2000, it worked nicely except that
the users had to type in the product ID... So, I followed
the tips I had gotten, and made an administrative
installation of office 2000. Now when the client
computers try to install Office 2000, they recieve the
exact error messages mentioned on the page on the
following link.
http://support.microsoft.com/default.aspx?id=304746
The thing is, these files are on a Windows 2000 server
(not a DC)... I removed the directory with Office 2000,
and re-installed it from a CD. Still the same thing
happens. Within the folder I have other packages that are
working perfect... Office XP, Acrobet etc.
Any ideas? the resolution mentioned in KB isnt to useful
to me, since my packages are on a windows 2000 server
already, and not a NT file server.
Thanks for listening.
/Simon