Microsoft Support Escalation Engineer Kevin McKinnerney has published the Test Lab Guide: System Center 2012 Configuration Manager. This new TLG uses the Base Configuration and SQL Server 2008 R2 TLGs to create a System Center 2012 Configuration Manager test lab, which includes stepping you through deploying an initial Configuration Manager client to CLIENT1.
Here is the lab configuration:
This test lab includes SQL Server 2008 R2 installed on APP1 and an additional server, CM1, the Configuration Manager 2012 server.
Thanks to Kevin, who is on a real TLG spree (see his Forefront Endpoint Protection 2010 stack)!
As always, enjoy!
Joe DaviesPrincipal Writer
GREAT TLG, I would strongly recommend it!
I had some minor issues during the configuration though. The hardest one was that I didn't have the right "collation" settings for my SQL server, but I managed to fix that one using this article - msdn.microsoft.com/.../ms179254.aspx
One question remains unanswered to me : is there a specific reason why you didn't use APP1 for the WSUS DB, but chose the "Use Windows Internal Database" option during WSUS setup?
Thanks for the comment. I have seen the SQL collation issue in the past but I did not encounter it when going through my installs while building this guide. I will have to do a new build and see if it appears. If it does I will look at adding additional steps to circumvent it.
A good question about using APP1 for the WSUS DB. I tend to use the internal db with WSUS for test labs just to remove a layer of complexity and reduce load on the SQL server. In a production environment I am sure you would want to use a full SQL server instance for WSUS.