Re: Office 2000 network installs cannot access original install share anymore



Hi,

I was aware of the task of checking NTFS permissions, but I assumed you had either already done it, or (if you'd ran the logs properly), you'd have seen the errors relating to permissions. It could be anywhere in the tree.

On my own network, we certainly do NOT have "EVERYONE" anywhere on the NTFS of any of our server computers. We do, however, set all share permission to EVERYONE:F. Our Office share is read-only for domain users only.

grolschie wrote:
"grolschie" <grolschie@xxxxxxxxxxxxxxx> wrote in message news:...

"Gerry Hickman" <gerry666uk@xxxxxxxxxxx> wrote in message news:%23mjhVeriFHA.708@xxxxxxxxxxxxxxxxxxxxxxx


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. :-)



We have not installed any Office2k service packs until now as everything has been running smoothly since day one until now.

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




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





--
Gerry Hickman (London UK)
.



Relevant Pages

  • Re: Allow saves and reads but not edits
    ... I had to give Domain Users List and Read ... > are seeing in the NTFS permissions editor. ... > and due to temp files the Creator Owner Modify ...
    (microsoft.public.win2000.security)
  • Re: Allow saves and reads but not edits
    ... I had to give Domain Users List and Read ... >> are seeing in the NTFS permissions editor. ... >> and due to temp files the Creator Owner Modify ...
    (microsoft.public.win2000.security)
  • Re: Windows 2003 Server and IIS 6.0: Domain users cant access my web site :(
    ... > On a DC I use IIS 6.0 because I have internel web site. ... NTFS permissions for Domain Users is: ... But I give Full Permissions of Domain users on NTFS and then Web site ...
    (microsoft.public.inetserver.iis.security)
  • Re: restricting access to a page
    ... If you've set the NTFS permissions properly, regular domain users won't be ... > in the folder have matching permissions. ...
    (microsoft.public.inetserver.iis.security)
  • Re: "Preparing to Install" Message - Word 2007 - No Solution ?
    ... Outlook 2007 Performance Update:http://pschmid.net/blog/2007/04/13/105 ... using the Windows Installer Cleanup Utility to remove any ... this it seems it could actually be a vista issue with permissions. ... references to registry keys that couldn't be accessed helped confirm ...
    (microsoft.public.office.misc)