By Joseph Yedid
Installing and setting-up Configuration Manager (CM) can be a long and time consuming task, but CM Admins can make this even more complicated for themselves. And yes, this is possible! For this example I am using CM12 SP1 R2.
Here is the recipe for a complicated environment:
– 1 part Remote SQL Server (with a default instance and non-standard port, or a named instance)
– 1 part WSUS Server with SSRS
– 1 part CM Server
Start with the SQL server and install all necessary components except the reporting services. Decide if you are going to use the default instance name or a named instance.
· For a default instance with non-standard port, after the installation is done, you will need to change the port for which SQL communicates over. See this post.
· For a named instance, after installation, you will need to change the port for which SQL communicates over to a dynamic port. See this post.
WSUS Server with SSRS
Next, onto server number two; install SQL Server with the database engine and reporting services. Install WSUS next. Do not install the Windows Internal Database. Use the database option instead.
On all 3 servers, ensure you have opened all SQL ports in the firewalls, either the assigned non-standard port or the dynamic port you have chosen.
Now with the SQL ports open, begin to install CM on the CM server and mix the ingredients. If all goes well, the CM setup won’t implode like a soufflé.
Why would you want to make this task even more complicated in the first place? Well for me, I do a lot of testing and need to cover as many scenarios possible. Others might do this to keep the SQL Server I/O contained to a single box. Whatever your reasons, hopefully you will find that this helps to make life a bit easier!
By Joseph Yedid