Office 2000 network installs cannot access original install share anymore

G

grolschie

Gerry Hickman said:
Hi,

Check the keys below to see if they've been changed. The long number may
be
slightly different on your system. Look our for line wrap.

HKLM\SOFTWARE\Classes\Installer\Products\904010001E872D116BF00006799C897E\So
urceList

LastUsed Source = n;1;\\Behemoth\Office2k Install\

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
{00010409-78E1-11D2-B60F-006097C998E7}\InstallSource

InstallSource = \\Behemoth\Office2k Install\

The install and uninstall sources are exactly the same. Now pretty much ALL
the pc's on our domain are complaining. The Windows Installer pops up at
login and cannot access the share. It has not priviledges. Yet we can
manually browse to the share as a logged in user.

If we browse to the share using the Windows Installer dialog box it is gets
access denied error when clicking on the share. It would seem that the
Windows Installer is not running as a domain account and cannot access the
share. The priviledges on the share is "everyone" = read.

We have made no changes to our Server 2003 shares and have not installed
Server 2003 SP1 even. No firewall on the server. The only thing I can
imagine happened is an update to XP such as Windows Installer 3.1 or
something.

thanks in advance,
grol.
 
G

grolschie

Gerry Hickman said:
Hi,

Check the keys below to see if they've been changed. The long number may
be
slightly different on your system. Look our for line wrap.

HKLM\SOFTWARE\Classes\Installer\Products\904010001E872D116BF00006799C897E\So
urceList

LastUsed Source = n;1;\\Behemoth\Office2k Install\

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
{00010409-78E1-11D2-B60F-006097C998E7}\InstallSource

InstallSource = \\Behemoth\Office2k Install\

The install and uninstall sources are exactly the same. Now pretty much ALL
the pc's on our domain are complaining. The Windows Installer pops up at
login and cannot access the share. It has not priviledges. Yet we can
manually browse to the share as a logged in user.

If we browse to the share using the Windows Installer dialog box it is gets
access denied error when clicking on the share. It would seem that the
Windows Installer is not running as a domain account and cannot access the
share. The priviledges on the share is "everyone" = read.

We have made no changes to our Server 2003 shares and have not installed
Server 2003 SP1 even. No firewall on the server. The only thing I can
imagine happened is an update to XP such as Windows Installer 3.1 or
something.

thanks in advance,
grol.
 
G

grolschie

Gerry Hickman said:
Hi,

Check the keys below to see if they've been changed. The long number may
be
slightly different on your system. Look our for line wrap.

HKLM\SOFTWARE\Classes\Installer\Products\904010001E872D116BF00006799C897E\So
urceList

LastUsed Source = n;1;\\Behemoth\Office2k Install\

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
{00010409-78E1-11D2-B60F-006097C998E7}\InstallSource

InstallSource = \\Behemoth\Office2k Install\

The install and uninstall sources are exactly the same. Now pretty much ALL
the pc's on our domain are complaining. The Windows Installer pops up at
login and cannot access the share. It has not priviledges. Yet we can
manually browse to the share as a logged in user.

If we browse to the share using the Windows Installer dialog box it is gets
access denied error when clicking on the share. It would seem that the
Windows Installer is not running as a domain account and cannot access the
share. The priviledges on the share is "everyone" = read.

We have made no changes to our Server 2003 shares and have not installed
Server 2003 SP1 even. No firewall on the server. The only thing I can
imagine happened is an update to XP such as Windows Installer 3.1 or
something.

thanks in advance,
grol.
 
G

grolschie

Gerry Hickman said:
Hi,

Check the keys below to see if they've been changed. The long number may
be
slightly different on your system. Look our for line wrap.

HKLM\SOFTWARE\Classes\Installer\Products\904010001E872D116BF00006799C897E\So
urceList

LastUsed Source = n;1;\\Behemoth\Office2k Install\

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
{00010409-78E1-11D2-B60F-006097C998E7}\InstallSource

InstallSource = \\Behemoth\Office2k Install\

The install and uninstall sources are exactly the same. Now pretty much ALL
the pc's on our domain are complaining. The Windows Installer pops up at
login and cannot access the share. It has not priviledges. Yet we can
manually browse to the share as a logged in user.

If we browse to the share using the Windows Installer dialog box it is gets
access denied error when clicking on the share. It would seem that the
Windows Installer is not running as a domain account and cannot access the
share. The priviledges on the share is "everyone" = read.

We have made no changes to our Server 2003 shares and have not installed
Server 2003 SP1 even. No firewall on the server. The only thing I can
imagine happened is an update to XP such as Windows Installer 3.1 or
something.

thanks in advance,
grol.
 
G

grolschie

Gerry Hickman said:
Hi,

Check the keys below to see if they've been changed. The long number may
be
slightly different on your system. Look our for line wrap.

HKLM\SOFTWARE\Classes\Installer\Products\904010001E872D116BF00006799C897E\So
urceList

LastUsed Source = n;1;\\Behemoth\Office2k Install\

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
{00010409-78E1-11D2-B60F-006097C998E7}\InstallSource

InstallSource = \\Behemoth\Office2k Install\

The install and uninstall sources are exactly the same. Now pretty much ALL
the pc's on our domain are complaining. The Windows Installer pops up at
login and cannot access the share. It has not priviledges. Yet we can
manually browse to the share as a logged in user.

If we browse to the share using the Windows Installer dialog box it is gets
access denied error when clicking on the share. It would seem that the
Windows Installer is not running as a domain account and cannot access the
share. The priviledges on the share is "everyone" = read.

We have made no changes to our Server 2003 shares and have not installed
Server 2003 SP1 even. No firewall on the server. The only thing I can
imagine happened is an update to XP such as Windows Installer 3.1 or
something.

thanks in advance,
grol.
 
G

grolschie

Gerry Hickman said:
Hi,

Check the keys below to see if they've been changed. The long number may
be
slightly different on your system. Look our for line wrap.

HKLM\SOFTWARE\Classes\Installer\Products\904010001E872D116BF00006799C897E\So
urceList

LastUsed Source = n;1;\\Behemoth\Office2k Install\

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
{00010409-78E1-11D2-B60F-006097C998E7}\InstallSource

InstallSource = \\Behemoth\Office2k Install\

The install and uninstall sources are exactly the same. Now pretty much ALL
the pc's on our domain are complaining. The Windows Installer pops up at
login and cannot access the share. It has not priviledges. Yet we can
manually browse to the share as a logged in user.

If we browse to the share using the Windows Installer dialog box it is gets
access denied error when clicking on the share. It would seem that the
Windows Installer is not running as a domain account and cannot access the
share. The priviledges on the share is "everyone" = read.

We have made no changes to our Server 2003 shares and have not installed
Server 2003 SP1 even. No firewall on the server. The only thing I can
imagine happened is an update to XP such as Windows Installer 3.1 or
something.

thanks in advance,
grol.
 
G

grolschie

Gerry Hickman said:
Hi,

Check the keys below to see if they've been changed. The long number may
be
slightly different on your system. Look our for line wrap.

HKLM\SOFTWARE\Classes\Installer\Products\904010001E872D116BF00006799C897E\So
urceList

LastUsed Source = n;1;\\Behemoth\Office2k Install\

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
{00010409-78E1-11D2-B60F-006097C998E7}\InstallSource

InstallSource = \\Behemoth\Office2k Install\

The install and uninstall sources are exactly the same. Now pretty much ALL
the pc's on our domain are complaining. The Windows Installer pops up at
login and cannot access the share. It has not priviledges. Yet we can
manually browse to the share as a logged in user.

If we browse to the share using the Windows Installer dialog box it is gets
access denied error when clicking on the share. It would seem that the
Windows Installer is not running as a domain account and cannot access the
share. The priviledges on the share is "everyone" = read.

We have made no changes to our Server 2003 shares and have not installed
Server 2003 SP1 even. No firewall on the server. The only thing I can
imagine happened is an update to XP such as Windows Installer 3.1 or
something.

thanks in advance,
grol.
 
G

grolschie

Gerry Hickman said:
Hi,

Check the keys below to see if they've been changed. The long number may
be
slightly different on your system. Look our for line wrap.

HKLM\SOFTWARE\Classes\Installer\Products\904010001E872D116BF00006799C897E\So
urceList

LastUsed Source = n;1;\\Behemoth\Office2k Install\

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
{00010409-78E1-11D2-B60F-006097C998E7}\InstallSource

InstallSource = \\Behemoth\Office2k Install\

The install and uninstall sources are exactly the same. Now pretty much ALL
the pc's on our domain are complaining. The Windows Installer pops up at
login and cannot access the share. It has not priviledges. Yet we can
manually browse to the share as a logged in user.

If we browse to the share using the Windows Installer dialog box it is gets
access denied error when clicking on the share. It would seem that the
Windows Installer is not running as a domain account and cannot access the
share. The priviledges on the share is "everyone" = read.

We have made no changes to our Server 2003 shares and have not installed
Server 2003 SP1 even. No firewall on the server. The only thing I can
imagine happened is an update to XP such as Windows Installer 3.1 or
something.

thanks in advance,
grol.
 
G

Gerry Hickman

Hi,

It's not related to MSIEXEC 3.1 per se, (at least not on Windows 2000); we
are running this on a big network and don't have this problem.

One thing I notice is that

\\Behemoth\Office2k Install\

is a path to a SHARE, it is not a path to a FOLDER. There's a KB article (I
can't remember where) that says you MUST use a subfolder for your
Administrative installation point with Office. e.g.

\\Behemoth\Apps\Office2k Install

I'm not sure why, or if this is suddenly a new rule with MSIEXEC 3.1.

Also, when your client PC tries to install a featuare, there should be a log
file in the user's temp folder. Check this file.

Also, set up verbose logging on a test PC and tell Office to install a
feature from your share, look at the log file and you may see what's
crashing it.
 
G

Gerry Hickman

Hi,

It's not related to MSIEXEC 3.1 per se, (at least not on Windows 2000); we
are running this on a big network and don't have this problem.

One thing I notice is that

\\Behemoth\Office2k Install\

is a path to a SHARE, it is not a path to a FOLDER. There's a KB article (I
can't remember where) that says you MUST use a subfolder for your
Administrative installation point with Office. e.g.

\\Behemoth\Apps\Office2k Install

I'm not sure why, or if this is suddenly a new rule with MSIEXEC 3.1.

Also, when your client PC tries to install a featuare, there should be a log
file in the user's temp folder. Check this file.

Also, set up verbose logging on a test PC and tell Office to install a
feature from your share, look at the log file and you may see what's
crashing it.
 
G

Gerry Hickman

Hi,

It's not related to MSIEXEC 3.1 per se, (at least not on Windows 2000); we
are running this on a big network and don't have this problem.

One thing I notice is that

\\Behemoth\Office2k Install\

is a path to a SHARE, it is not a path to a FOLDER. There's a KB article (I
can't remember where) that says you MUST use a subfolder for your
Administrative installation point with Office. e.g.

\\Behemoth\Apps\Office2k Install

I'm not sure why, or if this is suddenly a new rule with MSIEXEC 3.1.

Also, when your client PC tries to install a featuare, there should be a log
file in the user's temp folder. Check this file.

Also, set up verbose logging on a test PC and tell Office to install a
feature from your share, look at the log file and you may see what's
crashing it.
 
G

Gerry Hickman

Hi,

It's not related to MSIEXEC 3.1 per se, (at least not on Windows 2000); we
are running this on a big network and don't have this problem.

One thing I notice is that

\\Behemoth\Office2k Install\

is a path to a SHARE, it is not a path to a FOLDER. There's a KB article (I
can't remember where) that says you MUST use a subfolder for your
Administrative installation point with Office. e.g.

\\Behemoth\Apps\Office2k Install

I'm not sure why, or if this is suddenly a new rule with MSIEXEC 3.1.

Also, when your client PC tries to install a featuare, there should be a log
file in the user's temp folder. Check this file.

Also, set up verbose logging on a test PC and tell Office to install a
feature from your share, look at the log file and you may see what's
crashing it.
 
G

Gerry Hickman

Hi,

It's not related to MSIEXEC 3.1 per se, (at least not on Windows 2000); we
are running this on a big network and don't have this problem.

One thing I notice is that

\\Behemoth\Office2k Install\

is a path to a SHARE, it is not a path to a FOLDER. There's a KB article (I
can't remember where) that says you MUST use a subfolder for your
Administrative installation point with Office. e.g.

\\Behemoth\Apps\Office2k Install

I'm not sure why, or if this is suddenly a new rule with MSIEXEC 3.1.

Also, when your client PC tries to install a featuare, there should be a log
file in the user's temp folder. Check this file.

Also, set up verbose logging on a test PC and tell Office to install a
feature from your share, look at the log file and you may see what's
crashing it.
 
G

Gerry Hickman

Hi,

It's not related to MSIEXEC 3.1 per se, (at least not on Windows 2000); we
are running this on a big network and don't have this problem.

One thing I notice is that

\\Behemoth\Office2k Install\

is a path to a SHARE, it is not a path to a FOLDER. There's a KB article (I
can't remember where) that says you MUST use a subfolder for your
Administrative installation point with Office. e.g.

\\Behemoth\Apps\Office2k Install

I'm not sure why, or if this is suddenly a new rule with MSIEXEC 3.1.

Also, when your client PC tries to install a featuare, there should be a log
file in the user's temp folder. Check this file.

Also, set up verbose logging on a test PC and tell Office to install a
feature from your share, look at the log file and you may see what's
crashing it.
 
G

Gerry Hickman

Hi,

It's not related to MSIEXEC 3.1 per se, (at least not on Windows 2000); we
are running this on a big network and don't have this problem.

One thing I notice is that

\\Behemoth\Office2k Install\

is a path to a SHARE, it is not a path to a FOLDER. There's a KB article (I
can't remember where) that says you MUST use a subfolder for your
Administrative installation point with Office. e.g.

\\Behemoth\Apps\Office2k Install

I'm not sure why, or if this is suddenly a new rule with MSIEXEC 3.1.

Also, when your client PC tries to install a featuare, there should be a log
file in the user's temp folder. Check this file.

Also, set up verbose logging on a test PC and tell Office to install a
feature from your share, look at the log file and you may see what's
crashing it.
 
G

Gerry Hickman

Hi,

It's not related to MSIEXEC 3.1 per se, (at least not on Windows 2000); we
are running this on a big network and don't have this problem.

One thing I notice is that

\\Behemoth\Office2k Install\

is a path to a SHARE, it is not a path to a FOLDER. There's a KB article (I
can't remember where) that says you MUST use a subfolder for your
Administrative installation point with Office. e.g.

\\Behemoth\Apps\Office2k Install

I'm not sure why, or if this is suddenly a new rule with MSIEXEC 3.1.

Also, when your client PC tries to install a featuare, there should be a log
file in the user's temp folder. Check this file.

Also, set up verbose logging on a test PC and tell Office to install a
feature from your share, look at the log file and you may see what's
crashing it.
 
G

Gerry Hickman

Hi,

It's not related to MSIEXEC 3.1 per se, (at least not on Windows 2000); we
are running this on a big network and don't have this problem.

One thing I notice is that

\\Behemoth\Office2k Install\

is a path to a SHARE, it is not a path to a FOLDER. There's a KB article (I
can't remember where) that says you MUST use a subfolder for your
Administrative installation point with Office. e.g.

\\Behemoth\Apps\Office2k Install

I'm not sure why, or if this is suddenly a new rule with MSIEXEC 3.1.

Also, when your client PC tries to install a featuare, there should be a log
file in the user's temp folder. Check this file.

Also, set up verbose logging on a test PC and tell Office to install a
feature from your share, look at the log file and you may see what's
crashing it.
 
G

grolschie

Egad! It's been working sweet for well over a year. Using the Windows
Installer dialog I can browse to \\behemoth. The very second I click on the
"Office2k Install" share I get access denied. Yet any domain user on our
system can browse to that share using Windows Explorer. It seems that WI has
zero domain priviledges (like its forgotten its part of a domain), or the MS
2000 installer part is screwed. The group "everyone" has read acces to that
share.

I am not sure of an elegant way to fix as we have over 80 pcs with it
installed.
grol
 
G

grolschie

Egad! It's been working sweet for well over a year. Using the Windows
Installer dialog I can browse to \\behemoth. The very second I click on the
"Office2k Install" share I get access denied. Yet any domain user on our
system can browse to that share using Windows Explorer. It seems that WI has
zero domain priviledges (like its forgotten its part of a domain), or the MS
2000 installer part is screwed. The group "everyone" has read acces to that
share.

I am not sure of an elegant way to fix as we have over 80 pcs with it
installed.
grol
 
G

grolschie

Egad! It's been working sweet for well over a year. Using the Windows
Installer dialog I can browse to \\behemoth. The very second I click on the
"Office2k Install" share I get access denied. Yet any domain user on our
system can browse to that share using Windows Explorer. It seems that WI has
zero domain priviledges (like its forgotten its part of a domain), or the MS
2000 installer part is screwed. The group "everyone" has read acces to that
share.

I am not sure of an elegant way to fix as we have over 80 pcs with it
installed.
grol
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top