RE: Automatic Site Code Discovery was unsuccessful



Hi Michel

Thanks for the info. I already perform the options (2) as u mention
and follow this link http://support.microsoft.com/?id=883620 also.

I can now deploy any program using that resolution and can now generate any
report, but my problem now is even i apply the resulotion in our
Wins server. when I try to resolve the sms client using autmaotic discovery
i'm still getting this message "automatic site code discovery was
unsuccessful" . please advise me on this. i dont whats wrong


I just follow this instruction...

Windows Server 2003 and Windows 2000
To manually add the SMS_SLP and SMS_MP records to WINS in Microsoft Windows
Server 2003 and in Microsoft Windows 2000, follow these steps:1. Click Start,
click Run, type cmd, and then click OK.
2. Type the following commands at the command prompt, and then press ENTER
after each command:• netsh
• wins
• server

3. Add the SMS_SLP record. To do this, type the following command, and then
press ENTER:
add name name=SMS_SLP endchar=1A rectype=0 ip={ip addresses}
Note Make sure that you enclose the IP address in braces ("{ }").
4. Add the MP_SMSSiteCode record. To do this, type the following command,
and then press ENTER:
add name name=MP_SMSSiteCode endchar=1A rectype=0 ip={ip addresses}
Note Make sure that you enclose the IP address in braces ("{ }"). The
SMSSiteCode variable represents the three-character string (letters,
integers, or a combination of both) that is the code for the SMS site to
which the Management Point belongs. It is displayed in the SMS Administrator
Console.


thanks for ussual support
Robert


"Michel-Vincent" wrote:

Hello

Automatic Site Code Discovery is enabled by:

1. extending the AD Schema, OR
2. using a WINS static entry

Straight from the SMS FAQ:

"If you have extended the Active Directory schema, then the client will use
an LDAP query to determine the management point. If the schema has not been
extended, the client will perform a WINS record lookup."

More info in the Operations Guide.

Hope it helps
Cheers

MV
--
Michel-Vincent Leriche
http://spaces.msn.com/mvleriche


"SMS 2003 Report Error - Need help" wrote:

Hi Guy's

This is my first time i encountered this error: "automatic site code
discovery was unsuccessful". I would lik to know what is the solution and
cause of this problem. basically i was not encountered this problem in my
previous insyalltion od SMS server.

Action Taken:

1. Install Windows 2003 Server Ent. Edition
2. Install the SQL server 2005 Ent. Edition
3. Install the IIS and enabled the BITS
4. Install the SMS server 2003 with SP2

During the installation they prompt me to extend the Schema, but i'm not
seleted that option. i just insatlled the SMS 2003 without extending the
Shema Admin .

It's necessary to extend the schema admin? i just wondering only becuase in
our test lab machine i'm not extending schema admin, but i'm not get this
error. "automatic site code discovery was unsuccessful"


Our Comany using DNS name resolution only, and we don't have a WINS server.

need your help guys.


regards
robert








.



Relevant Pages

  • Re: Schema Update Problem
    ... rebooting the SMS server and re-running extadsch.exe from the sms server. ... I have confirmed the Schema Master is also my Master AD Server. ... Error code = 8245. ...
    (microsoft.public.sms.setup)
  • Re: replacing a sms server
    ... Domain computers that have an sms 2003 client installed can have it ... Windows Server System MVP - SMS ... It is advised to follow the procedure below, before any schema modifications ...
    (microsoft.public.sms.setup)
  • Re: replacing a sms server
    ... Domain computers that have an sms 2003 client installed can have it upgraded to sccm 2007 clients without you needing to manually uninstall the clients, so you should be fine there. ... Deactivating the server can be as simple as uninstalling it, make sure the objects are removed from the system management container in AD. ... It is advised to follow the procedure below, before any schema modifications are made, not just sms 2003 schema extentions. ...
    (microsoft.public.sms.setup)
  • Re: replacing a sms server
    ... to keep from the previous SMS server. ... domain computers that have the sms client installed. ... this is the safest way of extending your schema. ... Locate the server that is the schema master ...
    (microsoft.public.sms.setup)
  • Re: SMS_SITE_COMPONENT_MANAGER
    ... When extending the schema, is it done at the top-level domain or can it be ... I make the changes on the remote MP server and enter the WINS server address ... The Active Directory schema has not ...
    (microsoft.public.sms.admin)