|
Posted by Wysiwyg on June 20, 2005, 11:47 am
Please log in for more thread options Roger,
Thanks for the reply.
I was never able to edit the limits on the server and Microsoft suggested I
reset the servers security settings with 'secedit'.
See article 313222 for how to do this:
http://support.microsoft.com/default.aspx?scid=kb;en-us;313222
I cringed at the thought but was willing to give it a try. However, before I
reset the security I thought that perhaps the domain security settings were
to blame. I logged on to the domain controller as the domain administrator
and ran 'dcomcnfg' from there. Under component services I added the problem
server as a new server to manage and was able to set all of the com security
settings remotely as 'edit limits' was no longer disabled. That resolved my
problem.
I don't know if resetting the security would have worked and Microsoft never
told me specifically what would cause the 'edit limits' option to be
disabled on the non-domain controller server.
Thanks again for replying, I'll save those registry keys for a reference if
there's another problem.
Bill Faulk
>
http://msdn.microsoft.com/library/en-us/com/html/cbfe62e6-c88f-4144-a5a7-4df872ee4f3a.asp
> discusses the changes to DCOM security in W2k3 Sp1 including how to adjust
> the
> limits directly in the registry. Now, as to why you have no ability to
> adjust these
> in the UI hopefully someone can answer (?)
>
> --
> Roger Abell
> Microsoft MVP (Windows Security)
>
> > I need to edit the DCOM server wide security limits on a Windows Server
> 2003
> > SP1 install. An application no longer functions after SP1 was installed
> and
> > I need to edit the limits but I can not do so since that button is
> disabled.
> > I can edit the defaults but the "Edit Limits" button is disabled (greyed
> > out) in dcomcnfg on the server properties.
> >
> > I am logging on as the domain administtrator and on the console. The
"edit
> > limits" option is not disabled on the XP clients. I suspect a security
> > policy on the server is the problem but I can not find any information
> > regarding which policy this would be. Searching with google I find
several
> > people with the same problem but no solutions yet.
> >
> > Any help is appreciated as I'm really stuck here.
|