As long as your boundaries are set to include the clients, it doesn't make a difference. You're site server will detect the clients based on whether they are within the boundary, assuming that you already had Advanced SMS client on the client machines, then they will automatically detect the new site, when the new Site Server polls the Heartbeat....you can have two site servers running in parrallel if you wanted, serving the same boundry, and clients will just be associated with which ever one they recieve data from.
I have been creating many different test environments (different configs for the server sides), and I accidently set one up a PSS with a different site code (just kept the same site codes normally, cause it was just to test the collection stucture.
I checked the client that was on the network, and pressed the "auto detect" site, and it picked up the name of the new site server immediately.
Obviously, configure all your boundaries and everything BEFORE you enable any discovery methods. Enabling heartbeat discovery, which is what is needed for the site server establishment for the client, will get you the new site code, or your new connection.
So just configure your site server, then enable heartbeat and Act Dir Sys Discovery, and set Run As Soon As Possible. Everything should be populated within the next couple of minutes. Don't forget to update and refresh your collections.
Large sites this may take a while.
Hope that helps. It's weekend time....going on a trip. Hehehe
Neil J Cotton
UCLan Ba-SYS Development and Project Manager
NJC Technical Productions
Software Development | Network Consultancy | Wireless Network Provissions
Member of the IETF CAPWAP Work Group