We are having a problem with deploying Office 2000 as part of our standard image. Right now we have to load office 2000, and then pull out the registry entries made into the user profile we installed it on, and import it into default user.

If we don't do the importing and exporting of registry keys, office 2000 asks for the office CD when another user other than the one who installed it logs in and attempts to use any of the office products. This is even if we tell office to run all components from the hard drive. The problem is we are intsalling the media from our IS network drive, but the users don't have access to that drive, so it's going out and looking for that network drive and it's not mapped (and they don't have access to map it).

There has to be a better solution than doing all the registry exports and imports. I know we can copy down the install to the hard drive and do it there, but then we have to leave the office install folder on the hard drive and we don't want users mucking around in there.

What is a way that we can install the software and have it install for all users and never ask for a disk?

0 Comments   [ + ] Show Comments


Please log in to comment

There are no answers at this time
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


Answer this question or Comment on this question for clarity