Re: SMS-Site-001 could not be created, error code = 5 in hman.log

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

The hman.log looks good, it tells me that the SMS-Site-<sitecode>
exists and successfully updated. One interesting note though, it says
there are 'No Ranged IP boundaries are currently published for this
site.' So I wonder if that is part of the problem with the client not
pushing out. I looked in the ccmsetup.log and and it states that the
'Source \\<siteserver>\SMSClient\I386 is inaccessible (53).' I do have
local boundaries setup, and from class I learned that the advanced
client will not work without roaming boundaries setup so I took a
couple of our other subnet ranges and put them in the roaming
boundaries. I then clicked the checkbox 'Include site boundaries within
the local roaming boundaries of this site.' The 'Client Push
Installation Properties', under the accounts tab, has an account that
is part of the Enterprise Admins group, so it should work. Thanks for
the continuing help, getting closer to the fix.
Steve Thompson wrote:
"Dennis Backherms" <dbackherms@xxxxxxxxxxxxxxxxxxx> wrote in message
news:1166111023.574010.30270@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I did verify that the checkbox for that option was checked. I looked in
the system management container and do see that two classes are there;
these classes are SMS-MP-<sitecode>-<siteserver> and
SMS-SLP-<sitecode>-<siteserver>, shouldn't there be two more classes
though?

No, that sounds correct...

How does the hman.log look???

Steve Thompson wrote:
"Dennis Backherms" <dbackherms@xxxxxxxxxxxxxxxxxxx> wrote in message
news:1166101849.372329.192410@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
This is what I have done so far:

1. Went to AD users and computers, right clicked on the System
container and delegated control to the computer account of my SMS
giving full control.

As mentioned earlier, at this step, you need to choose the (advanced
options) that the computer account has full control to this folder +and
all
sub-folders+


2. Verified in the extadsch.log that the schema extension was
successful.

3. I went back to my domain controller, ran mmc and looked at the AD
schema to find out if the classes and attributes were there. Attributes
were present but there were no classes present.

4. I ran SMS Trace to view the hman.log and saw that it has not yet
attempted to create the SMS site again, so I will wait to see if, at
the next SMS update, the site will be created after the changes I made.
I know with SMS, it is a waiting game and not a server you can force.
P S Lakshmi Narasimha wrote:
Hello Dennis,

For extending the Schema for SMS you need to
follow
the
following steps.

1. Go to AD users and Computers.

2. Right Click on System's Container and Delegate control (Full
Control)
to
the Machine Account where SMS is installed.

3. Then go to the command prompt and run EXTADSCH.EXE (It will be
under
SMS\BIN\I386)

4.Then open up the EXTADSCH.LOG file that will be created under the C
drive
and check if the Schema has been successfully extended.

5. Then check in AD Users and Computer do you see SYSTEM MANAGEMENT
Container.

Have answered to your queries. If any further queries dyou can drop an
email
to me.

"Dennis Backherms" wrote:

I wish there would come a day when Microsoft creates a program that
will install and create the necessary functions for their products
to
work. I read, in the administration guide, if you want the system
management container to be created in the schema, you must manually
create the container after you perform the schema extension. Why
wouldn't the schema extension utility for SMS 2003 include this when
it
runs? Anyway, enough ranting, I am getting this annoying error, as
seen
in the subject line of this post, and have added the user account
that
has enterprise rights on the domain and I still receive the error.
What
am I doing wrong? Please do not simply say check user permissions or
make sure the SMS service account has rights to this container. If
you
want to reply with that, tell me where this service account is in
the
SMS admin console. Help would be greatly appreciated.





.

Relevant Pages

  • Re: Trouble Extending Schema
    ... The SMS Server account has full control of the new system ... I've tried running the extend schema application from each of the domain ... Could you be more specific on how you are "manually" extending the AD ...
    (microsoft.public.sms.setup)
  • Re: SMS-Site-001 could not be created, error code = 5 in hman.log
    ... container and delegated control to the computer account of my SMS ... Verified in the extadsch.log that the schema extension was ... I ran SMS Trace to view the hman.log and saw that it has not yet ...
    (microsoft.public.sms.admin)
  • Re: sms and AD
    ... >> After having sms 2 fail on us i have decided to bring forward the move to sms ... I cannot get sms to add files into the ad, the schema has been extended ... >> 'full' upgrade has not occured ... > The account that needs access is either the site server computer account ...
    (microsoft.public.sms.setup)
  • Re: SMS management of systems in a workgroup
    ... I have read some text regarding the Network Access Account. ... Check out the SMS Technical FAQ: ... the boundaries or remote boundaries should include the subnet of the ... We have installed the advanced client on them. ...
    (microsoft.public.sms.admin)
  • Re: ad schema extention
    ... I logged off the account I was logged in as because it wasn't in the ... schema admin group. ... >> I'm trying to extend the AD schema after I've installed SMS 2003 and I'm ...
    (microsoft.public.sms.setup)