SMS Clients & Sites Association 1

[InfrArch]

Couldn't you please help me with the following SMS2003 related issue:

Customer has 3 SMS sites, - Central SMS Site (A01) , Primary SMS Site (B01) and Secondary SMS Site (001). Clients which works under WinNT4.0 Worstation with SMS 2003 legacy client associated with SMS Site 001 (Secondary Site). Then these clients are upgraded to WinXP with the Advanced SMS Client. This SMS Client can not associate itself with the Primary SMS Site but rather tries to associate itself with the Secondary SMS Site and fails. In SMS Client logs I can see the following:

Assignment Site Code for the site 001 is B01 site codes do not mach.

If on this failed client I push the button to start Site Autodiscovery it's momentally find the right site (Primary) and all works OK. So, it seems , that after the OS upgrade SMS advanced client tries to bount itself to the old site (Secondary) and fails and at the same time do not perform an autodiscovery procedure by itself.

Waiting for your answer ASAP.

Regards,
Victor

 

[tbrennans]

The problem I would think would be that since they clients are now advanced clients they cant talk to the secondary site because advanced clients cant talk to a secondary site.

(thus the failure) so you need to make sure the roaming boundaries in the primary site include the secondary site. and that the secondary site boundaries are changed so there is no overlapping.

You will probably need to make an MP at the secondary site to work as a Proxy MP and change your DP into a protected DP (if you want to go that route. If the only reason you had a secondary was to service your legacy clients and they are all gone, I'de get rid of it. If it was over a wan link then I'd go with the pmp and pdp.