RE: Documents open ReadOnly (Word 2003) even when "Edit in .." is

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



We opened a Microsoft Premier call for this and Ayla (the MS resource) found
a solution - the user did not have registry permission on the
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Office key (unless they were
local admin of course).

We decided to go full blast and grant full access to
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Office
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MediaProperties
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft

as well as file locations
C:\Program Files\Common Files\Microsoft Shared
C:\Program Files\Common Files\System
C:\Program Files\Microsoft Office

I do not think it will solve lamar's issue though - we had a different
symptom.

Regards,
JamesA


"lamar" wrote:

I am experiencing the same thing. If the user closes the doc and then reopens
(using the same "Edit in.." procedure), it will open correctly in
non-readonly mode. We have been working with Msoft for over 6 months --
collecting network logs, testing, running queries against the SITE database,
etc.; all for no help.

I don't think they have any idea. Maybe it will be better in the next version.

"GijimaAst Consultant" wrote:

We have tested the registry key setting and it did not resolve the issue.

The only available solution at this stage is to add the user to the
"Administrators" group on his desktop. This is not a proper solution since
it violates desktop security policy at the customer.

I need to explain this behavior - why would a user need local admin
permission?

PS - I have compared the "local security policy" on the two different
offices - no significant difference. I cannot locate a folder that may be
locked down. Both offices allow ActiveX components for Trusted Sites and the
Sharepoint server is in the list of Trusted sites.

I am totally out of ideas... Need your help!

Thanks,
JamesA

"GijimaAst Consultant" wrote:

Hi,

A specific subset of our customer's userbase cannot edit Sharepoint
[SPS2003 SP2] documents in Microsoft Word 2003. The users follow the exact
same procedure and has the same software stack (Word 2003 on Windows XP2) as
others who can edit. The documents are checked-out correctly and they use
the "Edit in Microsoft Word" option. The problem is that the document opens
with "Read-only" in the title bar and cannot save back.

One significant difference is that the "error" group are not
administrators on their local PC. Once we assign them this permission, the
problem is resolved.

The customer does not want to give local administrative permission to all
users on the network. There are also other network sites where the users
also does not have local admin permissions, yet their Sharepoint / Word 2003
read-write functionality behaves correctly. We are unable to locate the
fine-grained permission that causes this behavior.

I found a reference to a KB article that may solve the issue -
http://support.microsoft.com/?kbid=870853 talks about adding a
OpenDocumentsReadWriteWhileBrowsing key to the registry. The customer is
not prepared have us test this and is requesting more information on this
key's behavior.

I am looking for an explination of what this key actually does or if there
is another solution to the "ReadOnly in non-local-administrator" problem.

Thank you,
JamesA
.



Relevant Pages

  • RE: Users adding printers
    ... When a domain user who is not in local admin group logons on workstation, ... it's not recommended to give user too much permission. ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • resol
    ... Verify that the user who is trying to install the hotfix or the update has local Administrator permissions. ... You do not have permission to update Windows XP with local admin rights ... We have local admin rights on the workstations. ...
    (microsoft.public.windowsupdate)
  • Re: Local admin right
    ... use Group Policy Restricted Groups to enforce membership of local computer ... > account to local admin group to run some applications. ... > used this permission to grant someone else to access that box too. ...
    (microsoft.public.security)
  • unable to create shedule task
    ... I have followed this article to safeguard our network for conficker virus. ... modification for schedule task and no permission to task folder in windows ... now i have removed this entry from GPO and force the update. ... i am logged in is local admin group member and task that i wants to run ...
    (microsoft.public.security.virus)
  • unable to create shedule task after following http://support.microsoft.com/kb/962007 article and rem
    ... I have followed this article to safeguard our network for conficker virus. ... modification for schedule task and no permission to task folder in windows ... now i have removed this entry from GPO and force the update. ... i am logged in is local admin group member and task that i wants to run ...
    (microsoft.public.windows.server.general)