Have you had any issues with clients not being able to connect to the SUP’s 
because of firewall issue?

 

Long story short, since SUP’s aren’t really assigned to boundary groups like 
DP’s and now recently MP’s clients are trying to connect to a SUP that is 
firewalled off.  If we have 4 SUP’s that are all part of the same forest, but 1 
SUP is behind a firewall 1 in 4 chance clients will be served that SUP and not 
be able to connect.  

 

Anyone else seen this?

 

Thanks

 

Rob

 

From: [email protected] [mailto:[email protected]] On 
Behalf Of Daniel Ratliff
Sent: Thursday, October 8, 2015 2:25 PM
To: [email protected]
Subject: RE: [mssms] How many SUP's supported on SCCM 2012 R2 SP1 CU1 primary.

 

We just had a case with Microsoft and moved all 6 SUPs at each primary to a 
shared DB and content. Works great.

 

Daniel Ratliff

 

From: [email protected] <mailto:[email protected]>  
[mailto:[email protected]] On Behalf Of Jason Wallace
Sent: Thursday, October 08, 2015 1:49 PM
To: [email protected] <mailto:[email protected]> 
Subject: Re: [mssms] How many SUP's supported on SCCM 2012 R2 SP1 CU1 primary.

 

You can have 4 SUPs sharing one WSUS database.

 

The tested number of SUPs in a primary site is 8


On 8 Oct 2015, at 18:37, Robert Spinelli <[email protected] 
<mailto:[email protected]> > wrote:

I can’t seem to find how many SUP’s are supported on SCCM 2012 R2 SP1 CU1?

 

I could of sworn at one point there was something on the website that showed 
that a primary supported a maximum of 4 SUP’s.

 

I don’t see that statement anymore. Is my Google-fu failing? Below is the 
section about SUP’s but no longer have a statement of how many it supports.

 

https://technet.microsoft.com/en-us/library/gg682077.aspx

<image001.png>

 

Thanks

 

Rob

 

 


The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material. If you receive this material/information 
in error,
please contact the sender and delete or destroy the material/information.

 




Reply via email to