I'm encountering an issue where scup is publishing the incorrect Source Path for updates it publishes to CM/WSUS. When I import an update the Source Path will be a location on one of the 5 CM site server's Wsus instances (iehttp://{siteserver}:8530/12/{longguid}.cab) Which server is chosen of the 5 seems to be random. If I get lucky and it picks the #2 server I will be able to download the package. If it picks one of the other site servers the download fails. I'm verifying the source path by right clicking on an update --> properties --> Content Information --> source path.
I have some workarounds for now but am looking for a permanent fix.
Here's some details regarding our environment:
Server 1: Primary, hosts the CM db and WSUS db, has WSUS management components installed
Server 2: CM Site server running the DP, MP, and SUP roles. Full WSUS install, this server is the main wsus server acting as the upstream source for the other 4 site servers. Has rights/access to the internet.
Servers 3-6: CM Site server running the DP, MP, and SUP roles. Full WSUS install. No access to the internet.
All servers run Server 2012 R2
CM version: 2012 R2
SCUP version: 2011