Re: Duplicate Sites

From: TerryM (nospam_at_hotmail.com)
Date: 06/24/04 

Date: Thu, 24 Jun 2004 14:32:37 -0400

Right,
no overlapping boundaries, not exactly sure how it came to be, but I do in
fact have some machines that are assigned to more than one site at a time.

If you go to each of the three primary sites and go to all systems and look
for a machine you will find some in multiple primary sites. These machines
though have different GUIDS attached to their names. In the Central site
database though these machines only show up once, with one of the GUIDs from
one off the primaries. So what happens is SW metering sends the SUM report
to the Central site and the central site gets to one of these machines and
says "I don't have this GUID in my Database". At that point it creates a
SUR file and will keep retrying that file forever and never move on to the
rest of that file or any of the other SUM files in that inbox. So they all
just start piling up. If I delete the SUR file then it tries to process the
next SUM file. and the same thing occurs.

I just think it is silly of SMS not to move on and keep processing what it
can when it gets in this situation.

So anyway now I need to clean up the various databases which is going to
take a while and I have no guarantee that more machines wont start doing
this since I don't know exactly how it happened to begin with. I believe
though it has something to do with how the help desk will fix machines.

If someone has a problem with their laptop, instead of sending the whole
laptop to HQ, they just send the Hard Drive. The Hard Drive is then put in
a similar laptop and fixed. Then it is returned to the user. I think
because of the different MAC address, etc.. SMS is assuming it is a clone,
and gets a new GUID and site assignment. Then when sent back out to the
field and put in another laptop it again assumes something is different
because the MAC address and does that again.

So then I get multiple records for the same name??

SMS Should do it like this:
A machine gets assigned to a site, it checks to see if it is assigned to a
different site (registry check probably) if so it notifies the other site
that the machine is getting changed to the new site. The old site could
then forward the history files or whatever else to the new site and then
deletes the records immediately.

At least that's how I would do it.

Terry

""Lee Li[MSFT]"" <leelili@online.microsoft.com> wrote in message
news:pJO0bScWEHA.2616@cpmsftngxa10.phx.gbl...
> Dear Terry,
>
> Thank you for your update.
> Please note one machine can only be assigned to one SMS at one time. In
the
> SMS 2003 the boundary settings cannot be overlapped, I am not sure how you
> assign one specifc machine to two sites at same time and even with
> different GUID. If you first assign the SMS client to one site and then
> uninstall the SMS client, then move it to another SMS site and reinstall
> the SMs client, we should consider the SMS client is now assigned to the
> second SMS site and there is no any relationship with the previous SMS
site
> any more and you should delete the client in the collections of the first
> SMS site server. Also in this condition, it is a normal behaviour for the
> SMS site server does not process the SW Metering for the client in the
> first site any more because now it is managed by the second SMS site.
>
> Have a nice day!
>
> Sincerely,
>
> Lee Li
> MCSE2000, MCDBA2000
> Microsoft Partner Online Support
>
>
> Get Secure! - www.microsoft.com/security
>
> ====================================================
> When responding to posts, please "Reply to Group" via
> your newsreader so
> that others may learn and benefit from your issue.
> ====================================================
> This posting is provided "AS IS" with no warranties, and
> confers no rights.
>

Relevant Pages

  • Re: SMS Clients - Workgroup - Not getting policy
    ... Attempting to retrieve default management point from ... machines trying to connect to different SMS primary servers. ... advertised programs and do not have the sms client configured. ...
    (microsoft.public.sms.admin)
  • Re: Backup and reinstall
    ... I played with this in my test lab, and the machines did not report in until ... You have laptops with SMS agents on them. ... > correctly provided site code & site server name. ...
    (microsoft.public.sms.setup)
  • Re: SMS Clients - Workgroup - Not getting policy
    ... I have also ensured that they're using the correct wins servers and that the SLP can be resolved. ... functioning correctly and I'm only having problems with some machines that are in workgroups; and having the same problem with different workgroup machines trying to connect to different SMS primary servers. ... These machines have 0 items in run advertised programs and do not have the sms client configured. ... CAS.log is showing "Software Distribution Site Settings for the client are missing from ...
    (microsoft.public.sms.admin)
  • Re: Not run SMS
    ... Hardware and software inventory run once a week. ... > If you disable the SMS client on the machine, ... these machines are running the SMS 2003 ...
    (microsoft.public.sms.admin)
  • Re: Not run SMS
    ... If you disable the SMS client on the machine, ... these machines are running the SMS 2003 ... > Advanced Clinet, however, when they become test machines the network ...
    (microsoft.public.sms.admin)
Quantcast