Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problem running Office2K on PC's in a W2K Domain

Status
Not open for further replies.

ThamesTrader

Technical User
Jul 14, 2003
6
GB
HELP
Brief history
I have around 100 W2K professional PC's logging into a Novel network & placed into departmental workgroups, all PC's have Office 2K professional loaded & giving no problems.
The company have now purchase a W2K server and are about to start to migrate users over.

The Problem is that once a PC has been joined to the domain and a standard user logs in, I get the following error message when trying to run any of the Office products.
"Error 1706. No vaild source could be found for product Microsoft Office 2000 SR-1 Professional. The windows installer cannot continue."

I do not get this problem if I login as administrator or if the user logs in locally to the PC.

This is probably something simple but it has me foxed, any help gratefuly received.
 
Basically the problem is to do with permissions. When you log in as a user and try to use Office, it needs to set itself up for the user account. It normally would access the CD Drive (or whatever the source was of the installation) and write a few values to the workstation.
I had the same problem as you it could be either because the source of the installation is not present or the user account does not have permission to alter installed programs.
One possible fix, is to give them administrator rights, log in as them, load up Office, let it install etc, then change them back to their old permission state.
 
When adding the computers to a w2k server domain, a new domain profile is created on the PC. When the domain users were created on the workstations, were they given admin rights? If not, that will keep them from using the resources on the PC that were installed under a different profile. I'm switching everyone at my company from a Novell server to a w2k server. The domain/local user profile issue can cause problems. I ended up editing the registry so the local profile is always used. That way I didn't have to re-install MSOffice on any of the PC's.
 
SOULLESS, This works on a local machine but not one that is part of a domain, thanks anyway.

ALEXS0628, This sounds like a possible solution, any chance you could let me know the registry keys & values that you altered, thanks.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top