Hello,

I am seeing one very weird issue in my environment. I have primary and secondary site server both have SUP role installed. When i install client that falls under secondary site boundary it installs client just fine but it setup WSUS of Primary and not the secondary. 

Boundary setting is correct. There is no domain level GPO. machine is generating local GPO. Weird thing is some of the machine in same boundary did setup correctly. 

I.e 

Primary Server - > PRMMCMP01 with SUP PRMMCMP01:8530

Secondary Server -> SCDMCMP01 with SUP SCDMCMP01:8530

I have sccm client push enable with SMSSITECODE=AUTO. Client installation works fine but WSUS\SUP gets sets to PRMMCMP01:8530 instead of SCDMCMP01:8530 . As i said i have done extensive research on it boundary setup is correct and no domain level GPO. 

On those errored machine if i Uninstall clinet and install it again 

ccmsetup.exe  /noservice mp:/SCDMCMP01.teckcominco.loc SMSMP=SCDMCMP01.teckcominco.loc SMSSITECODE=P01 WSUS gets the right setting. What Should i do to correct this? why it is not setting up right WSUS on first place? Thank you

Hello,
We are faced the same problem. Decision could not be found. We would appreciate any information about this problem.

Thanks in advance.

Hi,

It turns out that it is a bug. There is one stored proc on server that needs to be modified in order to get the right WSUS. I have came to know that this has been resolved in current fixes.

• Marked as answer by Kanojia 17 hours 36 minutes ago

Hi,

It turns out that it is a bug. There is one stored proc on server that needs to be modified in order to get the right WSUS. I have came to know that this has been resolved in current fixes.

• Marked as answer by Kanojia Thursday, September 11, 2014 5:52 PM