RE: SCCM 2007 Error 0x80005000 creating mSSMSManagementPoint objec
Martin
Thx for your answer.
I gave full permision to System container and child to primary site server,
so i suppose SCCM should be able to create this objects himself, but his not.
"Sherry Kissinger [MVP]" wrote:
> You do not add anything to that container. Give your Primary site server's
> computer object rights to that container. It'll create the entries. The
> only time I've ever done anything in that container is to delete entries if
> something got foobar'd. But a human never creates entries in there. That's
> the servers' job.
>
> If you have (or plan to have) multiple site servers, what I usually do /
> recommend is you create a group in ad called something like
> "ConfigMgr_Site_Servers". Give that group rights to that container. Add all
> your Site Server computer Accounts into that group. Reboot your servers
> after adding them to an AD Group, so the tokens are correctly attached to
> your computer object when it's talking to AD.
>
> But if you only have a couple site servers, you can just add each computer
> account individually to that containers' security.
>
> If you are a super-small site, I've heard of some people just putting their
> site servers' computer account into Domain Admins--but I've never liked that.
> Feels too wide open when all you really need is access to that container.
> Although there are other things that having the computer object be a Domain
> Admin can help with; but again... security first. There are lots of other
> ways when you hit a security issue for other aspects of configMgr.
>
> "Martin" wrote:
>
> > Hi,
> >
> > I have installed System Center Configuration Manager 2007, i have extended
> > my AD schema by using extadsch.exe with success and without any errors.
> >
> > Then i try to configure it, so i opened ADSI edit, i was able to create
> > System Management container (in System container) but when i wanted to
> > create
> > new object of class mSSMSManagementPoint i got error:
> >
> > Operation failed. Error code: 0x80005000
> > An invalid directory pathname was passed
> >
> > Windows 2008, AD 2003 nativ level.
> >
Sherry Kissinger [MVP]
you defined security, those rights may not be valid until a reboot.
If that doesn't help, start looking at logs and/or error messages. Start
with Site Status ( in your console), and look for errors there. Generally,
really good tips are given on what to look for / fix when errors occur.
Martin
it turned out that it was necessary to wait 4 days for AD replication, now
everythink works ok
THX!