Re: HELP DEINSTALLED PRIMARY CHILD

From: SMSMan (SMSMan_at_discussions.microsoft.com)
Date: 08/11/04 

Date: Wed, 11 Aug 2004 10:33:03 -0700

OK we'll give that a try.

"Stan White [MS]" wrote:

> I misunderstood your issue, sorry.
> It looks like you still have the de-installed site registered in AD and will
> need to manually remove the entries (using ADSIEDIT).
> --
> --
> Stan [MSFT]
> --
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> --
> --
>
> "SMSMan" <SMSMan@discussions.microsoft.com> wrote in message
> news:E8A7EC7E-CCC2-4024-A9C5-A2BF4FB2FA02@microsoft.com...
> > The log is actually from the ClientLocation.log from one of the clients,
> > sorry for the confusion.
> >
> > "SMSMan" wrote:
> >
> >> Thanks for the reply. I understand that clients only report to primary
> >> sites.
> >> When we hit the discover button, the child assigns itself to the primary
> >> site that was deinstalled. To be more specific, we had two primary sites:
> >> SSA
> >> and 007. 007 server name is ssasvsmsp1870 and was a child site to SSA. We
> >> decided that having the second primary site was overkill and so we
> >> deinstalled it and put a secondary in it's place, site code is 014 and
> >> server
> >> name is ssasvsmss1870 - secondary to the SSA primary. When I hit the
> >> auto-discover button on the client, the client still points to 007, when
> >> it
> >> should assign itself to SSA. The LocationServices.log file show's the
> >> following:
> >>
> >> <![LOG[Current AD site of machine is
> >> sms-1870Senter]LOG]!><time="12:18:10.484+420" date="08-10-2004"
> >> component="LocationServices" context="" type="1" thread="1908"
> >> file="lsad.cpp:215">
> >> <![LOG[Current assigned site code for the client is
> >> '007']LOG]!><time="12:18:10.968+420" date="08-10-2004"
> >> component="LocationServices" context="" type="1" thread="1908"
> >> file="lsad.cpp:2386">
> >> <![LOG[Attempting to retrieve default management point from
> >> AD]LOG]!><time="12:18:11.046+420" date="08-10-2004"
> >> component="LocationServices" context="" type="1" thread="1908"
> >> file="lsad.cpp:2040">
> >> <![LOG[Retrieved Default Management Point from AD:
> >> SSASVSMSP1870]LOG]!><time="12:18:11.078+420" date="08-10-2004"
> >> component="LocationServices" context="" type="1" thread="1908"
> >> file="lsad.cpp:2046">
> >> <![LOG[Persisting the default management point in
> >> WMI]LOG]!><time="12:18:11.078+420" date="08-10-2004"
> >> component="LocationServices" context="" type="1" thread="1908"
> >> file="lsad.cpp:2565">
> >> <![LOG[Persisted Default Management Point Location
> >> locally]LOG]!><time="12:18:11.109+420" date="08-10-2004"
> >> component="LocationServices" context="" type="1" thread="1908"
> >> file="lsad.cpp:2571">
> >> <![LOG[Attempting to retrieve proxy MP from
> >> AD]LOG]!><time="12:18:11.125+420" date="08-10-2004"
> >> component="LocationServices" context="" type="1" thread="1908"
> >> file="lsproxymp.cpp:828">
> >> <![LOG[Client has been reassigned, refreshing MP
> >> information]LOG]!><time="12:18:11.125+420" date="08-10-2004"
> >> component="LocationServices" context="" type="1" thread="2168"
> >> file="scheduledcleanupendpoint.cpp:163">
> >> <![LOG[Current AD site of machine is
> >> sms-1870Senter]LOG]!><time="12:18:11.171+420" date="08-10-2004"
> >> component="LocationServices" context="" type="1" thread="1908"
> >> file="lsad.cpp:215">
> >> <![LOG[Attempting to retrieve default management point from
> >> AD]LOG]!><time="12:18:11.234+420" date="08-10-2004"
> >> component="LocationServices" context="" type="1" thread="2168"
> >> file="lsad.cpp:2040">
> >> <![LOG[Retrieved Default Management Point from AD:
> >> SSASVSMSP1870]LOG]!><time="12:18:11.281+420" date="08-10-2004"
> >> component="LocationServices" context="" type="1" thread="2168"
> >> file="lsad.cpp:2046">
> >> <![LOG[Persisting the default management point in
> >> WMI]LOG]!><time="12:18:11.281+420" date="08-10-2004"
> >> component="LocationServices" context="" type="1" thread="2168"
> >> file="lsad.cpp:2565">
> >> <![LOG[Persisted Default Management Point Location
> >> locally]LOG]!><time="12:18:11.296+420" date="08-10-2004"
> >> component="LocationServices" context="" type="1" thread="2168"
> >> file="lsad.cpp:2571">
> >> <![LOG[Retrieved Proxy Management Point from AD:
> >> SSASVSMSP1870]LOG]!><time="12:18:11.296+420" date="08-10-2004"
> >> component="LocationServices" context="" type="1" thread="1908"
> >> file="lsproxymp.cpp:835">
> >> <![LOG[Attempting to retrieve proxy MP from
> >> AD]LOG]!><time="12:18:11.312+420" date="08-10-2004"
> >> component="LocationServices" context="" type="1" thread="2168"
> >> file="lsproxymp.cpp:828">
> >> <![LOG[Attempting to retrieve local MP from
> >> AD]LOG]!><time="12:18:11.343+420" date="08-10-2004"
> >> component="LocationServices" context="" type="1" thread="1908"
> >> file="lsad.cpp:2504">
> >> <![LOG[Current AD site of machine is
> >> sms-1870Senter]LOG]!><time="12:18:11.343+420" date="08-10-2004"
> >> component="LocationServices" context="" type="1" thread="2168"
> >> file="lsad.cpp:215">
> >> <![LOG[Current AD site of machine is
> >> sms-1870Senter]LOG]!><time="12:18:11.375+420" date="08-10-2004"
> >> component="LocationServices" context="" type="1" thread="1908"
> >> file="lsad.cpp:215">
> >> <![LOG[Retrieved local Management Point from AD:
> >> SSASVSMSP1870]LOG]!><time="12:18:11.437+420" date="08-10-2004"
> >> component="LocationServices" context="" type="1" thread="1908"
> >> file="lsad.cpp:2514">
> >> <![LOG[Retrieved Proxy Management Point from AD:
> >> SSASVSMSP1870]LOG]!><time="12:18:11.453+420" date="08-10-2004"
> >> component="LocationServices" context="" type="1" thread="2168"
> >> file="lsproxymp.cpp:835">
> >>
> >> Any clues as to why this whould be happening?
> >>
> >> "Stan White [MS]" wrote:
> >>
> >> > Advanced clients always assign to a primary site, never a secondary.
> >> >
> >> > --
> >> > --
> >> > Stan [MSFT]
> >> > --
> >> > --
> >> > This posting is provided "AS IS" with no warranties, and confers no
> >> > rights.
> >> > --
> >> > --
> >> >
> >> > "SMSMan" <SMSMan@discussions.microsoft.com> wrote in message
> >> > news:37727B60-814E-4448-8E15-424D11C2D61C@microsoft.com...
> >> > > We removed a primary child sms server and made it a secondary server,
> >> > > changing the server name as well. The secondary server is up and
> >> > > running,
> >> > > the
> >> > > communication seems fine. Logs show that it was able to publish its
> >> > > info
> >> > > into
> >> > > AD. Now when we try to reassign the clients to the new site manually
> >> > > (using
> >> > > the auto discover feature) they default to the old primary site name.
> >> > >
> >> > > --
> >> > > SMS Admin
> >> >
> >> >
> >> >
>
>
>