Hello everyone, Since SCCM 2007 primary site server implementation along with following components require IIS web sites: SQL Reporting Services (SRS) installed on same server with SCCM 2007 primary site server. WSUS 3.0 SP2 installed on same server with SCCM 2007 primary site server. What is fail-safe recommended approach to make use creating custom web sites to offer these functionalities. I can think of following two ways to allocate web sites: Set A: 1. IIS default web site: Left for SCCM 2007 site-to-site or client-to-site communication. 2. Custom web site for WSUS. 3. Custom web site for SRS. Set B: 1. IIS default web site: Left for SRS. 2. Create SMSWEB custom web site for SCCM 2007 site-to-site or client-to-site communication. 3. Create custom web site for SRS. Please discuss implications fo doing either of the above; specially in terms of when solution has to be extended to add additional management points or software update points. What would be better approach? I've more tendency for Set A. Thanks. Regards, Shahzad.

In my environment I'm using SET A without any issues.Anoop C Nair - Twitter @anoopmannur MY BLOG: http://anoopmannur.wordpress.com SCCM Professionals This posting is provided AS-IS with no warranties/guarantees and confers no rights.

Thanks Anoop, Ok, considering Set A; would that support implementing management Points NLb'ed? My basic understanding of NLB is A) Two servers participating in NLB cluster. B) Both servers are multihomed. C) NLB service running on both NLB nodes. D) Management point configured appropriately. What about if I would like software update point to be NLB'd as well.?

I don't get what you're trying to do? MPs in an NLB have to be on their own dedicated systems so who cares if they're using the default IIS site? No other roles can share those systems. Same with Software Update Points. You're just introducing complexity without any return. Additionally, if you create and use custom websites (in the case when all three services are on a single system), then only one of them can use port 80. So now you're introducing more variables. Are you expecting the web sites in IIS to crash or having to recycle them often? If so, based on what? Like I said, this is just an unneeded layer of complexity. And you won't get any added scalability. If you are commited to going down this path, don't go with a custom SMSWEB -- I don't remember the the details, but there are a few cases where that totally doesn't work.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Hi Jason, If WSUS, SRS or SCCM's web sites are all going to use port 80.........then how could we possibly put them all together on same box?? say I've to install primary site server in following order: 1. Install SRS - this needs its web site. 2. Install WSUS - this needs it web site. 3. Primary site server. All 3 above are required to go on same box. if any of them share same port 80; why would this be a recommended order of installation for implementing Reporting, Software Update Point and Site Server on same box? Please clarify. Thanks. Shahzad.

See, best practice is to use custom site for WSUS. http://technet.microsoft.com/en-us/library/bb932162.aspx Anoop C Nair - Twitter @anoopmannur MY BLOG: http://anoopmannur.wordpress.com SCCM Professionals This posting is provided AS-IS with no warranties/guarantees and confers no rights.

See, best practice is to use custom site for WSUS. http://technet.microsoft.com/en-us/library/bb932162.aspx Anoop C Nair - Twitter @anoopmannur MY BLOG: http://anoopmannur.wordpress.com SCCM Professionals This posting is provided AS-IS with no warranties/guarantees and confers no rights.

They all use separate subsites in IIS. There is no conflict. I load all three all the time in both production and test/demo environments and there is never any conflict. As for WSUS on a separate site being a best practice, I don't disagree and was a proponent of that being a best practice for a while just because it separates the traffic on a dedicated port that could then be isolated and/or tracked. However, when you start doing IBCM or deploy ConfigMgr is a locked environment (network-wise) opening additional ports becomes a challenge while leaving everything on port 80 streamlines this greatly.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys