Follow on from ConfigMgr – A Newbie Experience.
Kent Agerlund describes a couple of tasks in his book that are suggested to be undertaken directly after install of your site server.  These tasks include running through applying any updates (Cumulative Updates or Hotfixes), creating a ConfigMgr source directory to store content such as drivers, software updates, applications etc, tweaking SQL & setting up your database recovery model, and basic discovery with Active Directory, great advice!
I’ll run through some of these as I did them on my site server amongst others.
Updates / Rollups
Firstly I ran CU3.  A simple next, next finish install because my site is clean and fresh.  This update contains an update to the console so be wary that something’s on there will change especially if you’re working from a book.
It was at this point I stumbled across the website below which documents version numbers for ConfigMgr.  Checking my version numbers revealed that there are a few revisions above CU3.  So, first I downloaded SP1 for ConfigMgr 2012 R2 and installed that.  Pretty straight forward install, nothing too taxing and after the Service Pack had installed I then applied CU1 for SP1 to bring me up to latest revision.

References – Version Number Reference – CU3 – SP1 – CU1 for 2012 R2 SP1

Create a SOURCES$ Directory
Swiftly followed by creating a source directory.  Create your SOURCES$ share on a drive of your choice, recommended to be separate to your site server but not always possible (if not separate look into some form of backup in case of any failure to any disk array).
Edit your Log Files
Next you need to edit your Log file size so the size of the log doesn’t exceed the size of the partition you have stored it on.  Within SQL Server management, right click on the site database and select Properties.  On the Files tab, scroll to the grey button with three dots in to edit the properties.  The sizes you set here depend on a few things such as your earlier calculations, and what size your drive partitions are.  I wont advise what they should be because there will always be someone that disagrees with the way things are worked out so do a little research on what you think they sizes should be compared with the sizes of your drives.  The spread sheet (written and shared by Kent Agerlund) from my ConfigMgr – A Newbie Experience post will give you some if not all of the data for your environment.
Database Recovery Model
With version of ConfigMgr previous to ConfigMgr 2012R2, you would normally explore the maintenance tasks however with 2012R2 you can use a SQL database backup.   I think there is still some value in exploring these maintenance tasks and familiarising yourself with them, especially if your going to be working with or supporting multiple versions of ConfigMgr, but for this example I’m going to use the SQL backup solution.  From within SQL Server Management Studio I check to see if the SQL Server Agent is started (if not start it) and then I right click on Maintenance Plans and select Maintenance Plan Wizard giving it a name and a schedule I then chose the tasks I want to perform and run through the rest of the wizard changing the obvious settings and accepting the defaults.  Read the windows you are presented with and each one is self-explanatory really.  I chose any clean up tasks followed by a full database backup and set it to run daily backing up all DBs and to put the backups into a folder called SQLBackUp and put the log into a folder called SQLBackUpLog. Just makes it easier to manage.
Is everything running sweet?
Finally I’ll just check my site is running OK and there are no errors by looking in Monitoring / System Status / Site Status and Component Status to make sure I have green ticks all the way.  If any of them are running with warning or errors these must be solved before we move on.  We want things running as smoothly as possible.  To check out what is amiss, right click on the problematic service and select to view error/warning messages for the previous days and review them.  I’d suggest you start yourself a little error code reference book to refer back to so you can remember how to fix something when it crops up again, a few months later.
I hope this is useful to you all.

0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *