Re: InetOrgPersonPrevent Insufficient Rights

From: Lee Flight (lef_at_le.ac.uk-nospam)
Date: 12/10/04


Date: Fri, 10 Dec 2004 14:57:22 -0000

Is the account you are using in the Schema Admins group?

Lee Flight
"Ken Norton" <Ken Norton@discussions.microsoft.com> wrote in message
news:45589D46-6EEC-4137-AA32-9E229072D186@microsoft.com...
> When I try to modify the schema as domain admin, I receive insufficient
> rights error. All the FSMO roles are correct and DCDiag checks out
> correct.
> I have update schema permissions in the registry. Any Ideas?
>
> Thanks,
> Ken



Relevant Pages

  • Re: AD Schema Security
    ... account context able to change Schema Admins membership. ... > Eg. the Schema Admins group is empty and the Schema partition is not set ... > workstation which tries to update the schema as part of the install. ... Is there a way to ensure that there is no chance a rogue app ...
    (microsoft.public.win2000.security)
  • Re: ForestPrep
    ... > get a message that either I do not have enough permission ... Administrator must not be a member of the schema admins group. ... possible that the server holding the schema FSMO role is down or ...
    (microsoft.public.exchange.setup)
  • Re: Schema Master
    ... Person that can extend schema must be part of Schema Admins group, ... I haven't heard of recommendations of keeping schema master offline. ...
    (microsoft.public.win2000.active_directory)
  • RE: Adprep /Forestprerp Error on line 333
    ... Is this information in a knowledge base article that I can reference? ... an attribute so there is no conflict or a way to modify an attribute. ... > 2 Now dump out the schema with the following command: ... > preferredLanguage to COGNOSpreferredLanguage. ...
    (microsoft.public.windows.server.migration)
  • RE: Adprep /Forestprerp Error on line 333
    ... We are in the process of moving from a Windows 2000 domain to a Windows 2003 ... We are not currently running Exchange, but Exchange 2000 was used in ... > 2 Now dump out the schema with the following command: ... In the Modify dialog box, ...
    (microsoft.public.windows.server.migration)