Collocating SQL or remote SQL for ConfigMgr/WSUS

[ranj]

Hi All

 

Wanted to bounce my thoughts with fellow members.

 

 

 

I am about to embark on a mini project for a customer. It's for a small experiment and a new network and infrastructure environment will be created on-premises. Unfortunately for this piece of work cloud is not an option. So a Virtualisation environment, SAN, networking, firewalls will all be procured.

 

I need to build MECM to help deploy a gold image to approx. 100 workstations, there are 2 variances of laptops I need to consider. As its an experiment it also not going to grow. I also need to ensure patching is configured for both clients and the small server estate being built.

 

 

 

So my thoughts are to build a new VM with MECM 2006 with the SUP role for WSUS and then use the OSD techniques with TS to build the Windows 10 image using PXE.

 

 

 

They will be building a SQL server to host a database for a third party application. My question is as its such a small environment should I put SQL on the same standalone server which will host the Primary site MECM server and SUP or it is doing a lot already and I should move the SQL stuff to a remote SQL rather than collocate?

 

 

 

From reading the docs I understand some considerations need to be taken into account to host both WSUS and ConfigMgr DBs within SQL (difference instances?) but because the environment will be so small my personal preference would be to keep it on same box, easier for me to deploy and easier for the customer to manage.

 

 

 

The security of the environment is high due to the nature of the customer.

 

 

 

What would others recommend and what would your approach be?

 

 

 

Many thanks

[free780]

MEMCM needs a particular collation for SQL. I'd probably use the same instance for the WSUS DB. The other app may require different SQL settings and does it have a front end that needs hosting? It may as well be on a seperate server.

[MartinByard]

MS recommend that the SQL is installed on the same box, unless you're in really large environments or want to use a HA cluster.

[ranj]

MS recommend that the SQL is installed on the same box, unless you're in really large environments or want to use a HA cluster.

 

Is this documented anywhere? pref from a Microsoft official source? I am struggling to find this....

[Boredguy]

For that load, your fine with the SQL on the same box.

If you put the SQL on a different box you would need to ensure you have the additional licence for it, as the SCEM/SCCM server licence only provides for the SQL server to be on the same box as the SCEM/SCCM server.

 

We have the SCCM and WDS running from the same DB for over 400 workstations with no issues