Office 2000 network installs cannot access original install share anymore

[grolschie]

The time you've spent writing this message you could have already run the
script and analysed the log file.

Not so. I am not onsite as it is the weekend. I will try the script. Many
thanks.

OK, but that's crazy. Any document you open from outside your organization
could easily exploit your systems.

Many times bitten by MS updates. Seen many systems with screwy WI problems
with Office2K updates. So until now the concept is, if it's not broke, don't
fix it. But's it's broken now. LOL.

Besides, our XP updates are automatic and most users in our org do not run
as administrator.
grol

 

[grolschie]

The time you've spent writing this message you could have already run the
script and analysed the log file.

Not so. I am not onsite as it is the weekend. I will try the script. Many
thanks.

OK, but that's crazy. Any document you open from outside your organization
could easily exploit your systems.

Many times bitten by MS updates. Seen many systems with screwy WI problems
with Office2K updates. So until now the concept is, if it's not broke, don't
fix it. But's it's broken now. LOL.

Besides, our XP updates are automatic and most users in our org do not run
as administrator.
grol

 

[grolschie]

The time you've spent writing this message you could have already run the
script and analysed the log file.

Not so. I am not onsite as it is the weekend. I will try the script. Many
thanks.

OK, but that's crazy. Any document you open from outside your organization
could easily exploit your systems.

Many times bitten by MS updates. Seen many systems with screwy WI problems
with Office2K updates. So until now the concept is, if it's not broke, don't
fix it. But's it's broken now. LOL.

Besides, our XP updates are automatic and most users in our org do not run
as administrator.
grol

 

[grolschie]

The time you've spent writing this message you could have already run the
script and analysed the log file.

Not so. I am not onsite as it is the weekend. I will try the script. Many
thanks.

OK, but that's crazy. Any document you open from outside your organization
could easily exploit your systems.

Many times bitten by MS updates. Seen many systems with screwy WI problems
with Office2K updates. So until now the concept is, if it's not broke, don't
fix it. But's it's broken now. LOL.

Besides, our XP updates are automatic and most users in our org do not run
as administrator.
grol

 

[grolschie]

The time you've spent writing this message you could have already run the
script and analysed the log file.

Not so. I am not onsite as it is the weekend. I will try the script. Many
thanks.

OK, but that's crazy. Any document you open from outside your organization
could easily exploit your systems.

Many times bitten by MS updates. Seen many systems with screwy WI problems
with Office2K updates. So until now the concept is, if it's not broke, don't
fix it. But's it's broken now. LOL.

Besides, our XP updates are automatic and most users in our org do not run
as administrator.
grol

 

[grolschie]

The time you've spent writing this message you could have already run the
script and analysed the log file.

Not so. I am not onsite as it is the weekend. I will try the script. Many
thanks.

OK, but that's crazy. Any document you open from outside your organization
could easily exploit your systems.

Many times bitten by MS updates. Seen many systems with screwy WI problems
with Office2K updates. So until now the concept is, if it's not broke, don't
fix it. But's it's broken now. LOL.

Besides, our XP updates are automatic and most users in our org do not run
as administrator.
grol

 

[grolschie]

The time you've spent writing this message you could have already run the
script and analysed the log file.

Not so. I am not onsite as it is the weekend. I will try the script. Many
thanks.

OK, but that's crazy. Any document you open from outside your organization
could easily exploit your systems.

Many times bitten by MS updates. Seen many systems with screwy WI problems
with Office2K updates. So until now the concept is, if it's not broke, don't
fix it. But's it's broken now. LOL.

Besides, our XP updates are automatic and most users in our org do not run
as administrator.
grol

 

[grolschie]

The time you've spent writing this message you could have already run the
script and analysed the log file.

Not so. I am not onsite as it is the weekend. I will try the script. Many
thanks.

OK, but that's crazy. Any document you open from outside your organization
could easily exploit your systems.

Many times bitten by MS updates. Seen many systems with screwy WI problems
with Office2K updates. So until now the concept is, if it's not broke, don't
fix it. But's it's broken now. LOL.

Besides, our XP updates are automatic and most users in our org do not run
as administrator.
grol

 

[grolschie]

The time you've spent writing this message you could have already run the
script and analysed the log file.

Not so. I am not onsite as it is the weekend. I will try the script. Many
thanks.

OK, but that's crazy. Any document you open from outside your organization
could easily exploit your systems.

Many times bitten by MS updates. Seen many systems with screwy WI problems
with Office2K updates. So until now the concept is, if it's not broke, don't
fix it. But's it's broken now. LOL.

Besides, our XP updates are automatic and most users in our org do not run
as administrator.
grol

 

[grolschie]

Not so. I am not onsite as it is the weekend. I will try the script. Many
thanks.


Many times bitten by MS updates. Seen many systems with screwy WI problems
with Office2K updates. So until now the concept is, if it's not broke,
don't fix it. But's it's broken now. LOL.

Besides, our XP updates are automatic and most users in our org do not run
as administrator.
grol

The solution:
It turns out that even though the MS Office install folder share on our
domain server was shared with "everyone", the security settings were only
"domain-users". This has worked for well over 18 months, until the recent
auto-update broke it. Adding "everyone" to the folder security allows anyone
not on our domain to access it, and consequently the Windows Installer can
now do it's thing. This is weird, because the process always seemed to have
domain access when logged in as a domain user. It never used to do this,
but our entire network started doing this recently overnight. Weird.

However, now that is has access to the share, the MS Office 2000 Windows
Installer process continously chugs away, exits and then restarts, like it's
in an infinite loop. This goes on for about 5-10 minutes. After about then,
it stops.

grol

 

[grolschie]

Not so. I am not onsite as it is the weekend. I will try the script. Many
thanks.


Many times bitten by MS updates. Seen many systems with screwy WI problems
with Office2K updates. So until now the concept is, if it's not broke,
don't fix it. But's it's broken now. LOL.

Besides, our XP updates are automatic and most users in our org do not run
as administrator.
grol

The solution:
It turns out that even though the MS Office install folder share on our
domain server was shared with "everyone", the security settings were only
"domain-users". This has worked for well over 18 months, until the recent
auto-update broke it. Adding "everyone" to the folder security allows anyone
not on our domain to access it, and consequently the Windows Installer can
now do it's thing. This is weird, because the process always seemed to have
domain access when logged in as a domain user. It never used to do this,
but our entire network started doing this recently overnight. Weird.

However, now that is has access to the share, the MS Office 2000 Windows
Installer process continously chugs away, exits and then restarts, like it's
in an infinite loop. This goes on for about 5-10 minutes. After about then,
it stops.

grol

 

[grolschie]

Not so. I am not onsite as it is the weekend. I will try the script. Many
thanks.


Many times bitten by MS updates. Seen many systems with screwy WI problems
with Office2K updates. So until now the concept is, if it's not broke,
don't fix it. But's it's broken now. LOL.

Besides, our XP updates are automatic and most users in our org do not run
as administrator.
grol

The solution:
It turns out that even though the MS Office install folder share on our
domain server was shared with "everyone", the security settings were only
"domain-users". This has worked for well over 18 months, until the recent
auto-update broke it. Adding "everyone" to the folder security allows anyone
not on our domain to access it, and consequently the Windows Installer can
now do it's thing. This is weird, because the process always seemed to have
domain access when logged in as a domain user. It never used to do this,
but our entire network started doing this recently overnight. Weird.

However, now that is has access to the share, the MS Office 2000 Windows
Installer process continously chugs away, exits and then restarts, like it's
in an infinite loop. This goes on for about 5-10 minutes. After about then,
it stops.

grol

 

[grolschie]

Not so. I am not onsite as it is the weekend. I will try the script. Many
thanks.


Many times bitten by MS updates. Seen many systems with screwy WI problems
with Office2K updates. So until now the concept is, if it's not broke,
don't fix it. But's it's broken now. LOL.

Besides, our XP updates are automatic and most users in our org do not run
as administrator.
grol

The solution:
It turns out that even though the MS Office install folder share on our
domain server was shared with "everyone", the security settings were only
"domain-users". This has worked for well over 18 months, until the recent
auto-update broke it. Adding "everyone" to the folder security allows anyone
not on our domain to access it, and consequently the Windows Installer can
now do it's thing. This is weird, because the process always seemed to have
domain access when logged in as a domain user. It never used to do this,
but our entire network started doing this recently overnight. Weird.

However, now that is has access to the share, the MS Office 2000 Windows
Installer process continously chugs away, exits and then restarts, like it's
in an infinite loop. This goes on for about 5-10 minutes. After about then,
it stops.

grol

 

[grolschie]

Not so. I am not onsite as it is the weekend. I will try the script. Many
thanks.


Many times bitten by MS updates. Seen many systems with screwy WI problems
with Office2K updates. So until now the concept is, if it's not broke,
don't fix it. But's it's broken now. LOL.

Besides, our XP updates are automatic and most users in our org do not run
as administrator.
grol

The solution:
It turns out that even though the MS Office install folder share on our
domain server was shared with "everyone", the security settings were only
"domain-users". This has worked for well over 18 months, until the recent
auto-update broke it. Adding "everyone" to the folder security allows anyone
not on our domain to access it, and consequently the Windows Installer can
now do it's thing. This is weird, because the process always seemed to have
domain access when logged in as a domain user. It never used to do this,
but our entire network started doing this recently overnight. Weird.

However, now that is has access to the share, the MS Office 2000 Windows
Installer process continously chugs away, exits and then restarts, like it's
in an infinite loop. This goes on for about 5-10 minutes. After about then,
it stops.

grol

 

[grolschie]

Not so. I am not onsite as it is the weekend. I will try the script. Many
thanks.


Many times bitten by MS updates. Seen many systems with screwy WI problems
with Office2K updates. So until now the concept is, if it's not broke,
don't fix it. But's it's broken now. LOL.

Besides, our XP updates are automatic and most users in our org do not run
as administrator.
grol

The solution:
It turns out that even though the MS Office install folder share on our
domain server was shared with "everyone", the security settings were only
"domain-users". This has worked for well over 18 months, until the recent
auto-update broke it. Adding "everyone" to the folder security allows anyone
not on our domain to access it, and consequently the Windows Installer can
now do it's thing. This is weird, because the process always seemed to have
domain access when logged in as a domain user. It never used to do this,
but our entire network started doing this recently overnight. Weird.

However, now that is has access to the share, the MS Office 2000 Windows
Installer process continously chugs away, exits and then restarts, like it's
in an infinite loop. This goes on for about 5-10 minutes. After about then,
it stops.

grol

 

[grolschie]

Not so. I am not onsite as it is the weekend. I will try the script. Many
thanks.


Many times bitten by MS updates. Seen many systems with screwy WI problems
with Office2K updates. So until now the concept is, if it's not broke,
don't fix it. But's it's broken now. LOL.

Besides, our XP updates are automatic and most users in our org do not run
as administrator.
grol

The solution:
It turns out that even though the MS Office install folder share on our
domain server was shared with "everyone", the security settings were only
"domain-users". This has worked for well over 18 months, until the recent
auto-update broke it. Adding "everyone" to the folder security allows anyone
not on our domain to access it, and consequently the Windows Installer can
now do it's thing. This is weird, because the process always seemed to have
domain access when logged in as a domain user. It never used to do this,
but our entire network started doing this recently overnight. Weird.

However, now that is has access to the share, the MS Office 2000 Windows
Installer process continously chugs away, exits and then restarts, like it's
in an infinite loop. This goes on for about 5-10 minutes. After about then,
it stops.

grol

 

[grolschie]

Not so. I am not onsite as it is the weekend. I will try the script. Many
thanks.


Many times bitten by MS updates. Seen many systems with screwy WI problems
with Office2K updates. So until now the concept is, if it's not broke,
don't fix it. But's it's broken now. LOL.

Besides, our XP updates are automatic and most users in our org do not run
as administrator.
grol

The solution:
It turns out that even though the MS Office install folder share on our
domain server was shared with "everyone", the security settings were only
"domain-users". This has worked for well over 18 months, until the recent
auto-update broke it. Adding "everyone" to the folder security allows anyone
not on our domain to access it, and consequently the Windows Installer can
now do it's thing. This is weird, because the process always seemed to have
domain access when logged in as a domain user. It never used to do this,
but our entire network started doing this recently overnight. Weird.

However, now that is has access to the share, the MS Office 2000 Windows
Installer process continously chugs away, exits and then restarts, like it's
in an infinite loop. This goes on for about 5-10 minutes. After about then,
it stops.

grol

 

[grolschie]

Not so. I am not onsite as it is the weekend. I will try the script. Many
thanks.


Many times bitten by MS updates. Seen many systems with screwy WI problems
with Office2K updates. So until now the concept is, if it's not broke,
don't fix it. But's it's broken now. LOL.

Besides, our XP updates are automatic and most users in our org do not run
as administrator.
grol

The solution:
It turns out that even though the MS Office install folder share on our
domain server was shared with "everyone", the security settings were only
"domain-users". This has worked for well over 18 months, until the recent
auto-update broke it. Adding "everyone" to the folder security allows anyone
not on our domain to access it, and consequently the Windows Installer can
now do it's thing. This is weird, because the process always seemed to have
domain access when logged in as a domain user. It never used to do this,
but our entire network started doing this recently overnight. Weird.

However, now that is has access to the share, the MS Office 2000 Windows
Installer process continously chugs away, exits and then restarts, like it's
in an infinite loop. This goes on for about 5-10 minutes. After about then,
it stops.

grol