So now we are going to create and SQL server, this will also be our SCCM server further down the road.
So, follow the same process we used to create the File server and create an SQL server.
Add two additional drives for SQL DBs and SCCM packages, and MS Updates.
So, when you have done all that, let’s get installing SQL.
Firstly, if you do not have SQL Server 2012 you can get it from here:
Once installed and placed into your ISO folder and you have attached the new ISO folder to your XenConsole you can then place the SQL ISO into the DVD Drive.
Run the setup file
New SQL Server Stand-alone installation or add features to an Existing installation
We are going to get our SQL server ready for SCCM at the same time.
Setting up Support Rules:
Accept licensing terms.
Select any Product updates:
Let the Install Setup complete:
You can ignore the Firewall warning:
Under Setup Roles, select SQL Server Feature Installation:
Select the required Instance Features:
Allow Installation Rules to complete its check:
Give the instance a name, or leave as default:
This will set our Citrix Instance as the default DB Instance, if you don’t want it to be default, selected Named Instance and change it to something more personal.
We want to point our DB to the additional Drive we created earlier. So select Instance Root Directory, and select the folder structure you created on your additional drive. Or choose the local folder location if you wish. I have placed the SQL DB Directory into the E drive where i wanted to store them.
Disk space check:
Change the standard SQL service accounts for the service account we created earlier, and change the startup service type to automatic for SQL Server Agent.
Add some security accounts, these should be the SQL-Admin group we created earlier, your current admin account and the service account.
Check the Data directories screen to ensure they are going to where you want them to go…
Do the same for analysis Services Configuration:
for Reporting Services Configuration we will do an install only:
Ignore the error reporting. unless you want it.
Let it run through the install:
It should now be completed:
Our SQL Instance is now installed.
If you are going to be running through an SCCM install with me then we are going to install another SQL Instance. If not, then please skip to the next blog post.
So from the installer menu, we are going to select New SQL stand-alone installation.
Ensure Perform a new installation of SQL Server 2012 is selected.
Select Evaluation for Product Key, and Accept the Licensing Terms.
Select Server Feature installation, add the same roles as we did before:
Move onto the Instance Configuration Page.
Change the name to WINSCCM, or whatever you want it to be called.
Change the DB directory to the already made folder structure we created on our additional attached drive.
Ensure Disk Space requirement is completed
Again change the service accounts to one we created earlier. Change Startup process to Automatic for SQL Server Agent.
Now select the TAB for Collation.
Change the Database Engine Collation to SQL_Latin1_General_CP1_CI_AS
OK that, and select Next. Add in your current user, and the SQL service account and Administrator groups. Select Next again.
Do the same for Analysis Service Configuration.
Under reporting services Configuration, just select Install.
Either opt in or out of error reporting.
Progress to install the new Instance. The second instance should now complete.