Search the Community

Hi All, I have an issue with WSUS / SUP within SCCM SP2 R3. We currently have a primary server that is on it's last legs and have added a new primary server in the same domain directly above which will eventually replace the current server. The current server consists of an SCCM server and a SQL server (both physical boxes on 2008). The new box is a much more powerful beast (3 months old) and as such we have decided to host all roles on the one server. To this end we have got the servers runing together with no problems - software packages created at the root site can be distributed to the child site without issue. The problem we have is we are in the process of moving WSUS off the old box and onto the new (WSUS was a site role on the SQL server), we have the server working a treat on the new box with no issues BUT we cannot get the clients to talk to the new server without manually telling the client to talk to the new site (sites are set to autodiscover normally). Boundries have not been changed on the old site (we'll call it SC1 - boundries are set by active directory site), new root site picks up the boundries from the child (we'll call this SC2). Only way to get clients to talk to the new WSUS server is by manually changing the client site from SC1 ro SC2. can anyone give me any clues as to where to start with the diagnosis. I've checked the usual log files and the one thing that is interesting is that before you change site there is no mention f the location for WSUS int the "locationservices.log" but as soon as you change to the new site then hey presto you get the info populated ... "WSUS Path=http://SERVER.FQDN:80", Server="SERVER", Version='6' any help would be greatly appreciatd. cheers Jerry