SQL 2012 Installation

So I finally accomplished the SQL install today. Took me a while, but finally found the time. Linda was able to create the drives I needed on the SAN, so I could proceed.

This is my first SQL Server Install....that actually means something. We'll see how well it works out. So far, not even an error, which is plain awesome. I was able to get the the database, the temp DB, the logs and the program files all on separate drives, not only to keep things organized, but for troubleshooting purposes down the road. One more step in the right direction. Learning a lot. Got some final pre-reqs left (WADK, MDT, etc.) and then finally onto the install of CM12. I'm so ready to get in there and start messing around with things.

And so it begins....

This past week we configured our ConfigMgr 2012 server. We have two dedicated Dell PowerEdge M620 blade servers. We installed Windows Server 2012 on one of them, and it was pain in the arse. The blades were a couple revisions behind and needed to be updated to support the Server 2012 installation. After being on support chat and call with Dell, our network manager was able to get it installed and working smoothly.

Once that was complete, we decided it was necessary to put the server on a separate VLAN to allow only certain computers (our test machines) to talk to it. The reason being when we starting messing with software updates, and imaging (OSD), we don't want the server roles conflicting with our current operations and clients pulling down the wrong thing. Our senior network engineer is having a fun time with  Server 2012 and Dell's commands in the switch (versus Cisco). I'm being sarcastic. Though not complete, I believe some ACLs are all that are left and configuring our test machines with static IPs. He does great work, so I'm excited to see where that will take us. 

Hoping to get that finished up Monday or Tuesday, and then start working on getting Server 2012 configured correctly with necessary components before the actual installation of ConfigMgr 2012. I'll update later this week (hopefully with progress!).

Currently....

Before I begin to talk about where I'm going, first you need to understand where I'm coming from.

We are a school district with 14,000 clients spread across over 40 buildings. We currently have ConfigMgr 2007 in production. However, we do not utilize it to its maximum potential. In fact, we utilize I'd guess roughly 40% of the power it contains. The main purpose it serves currently, is our way to deploy software to users. MSI's, EXE's, etc. And it works. We also use it for pulling reports here and there. We do not use OSD or Software (Windows) Updates. Though we should. And we want to. With the new migration, these are two main features we hope to integrate, along with better hardware and software inventory. It's a big step for us. Some may find it easy, but for someone who has only been working with SCCM for less than a year and freshly out of college, I am nervous in the project I am about to undertake. I want to do this right, but I am not sure I will think of everything. That is it in a nutshell. I'll be starting our implementation soon.....so stay tuned!

Introduction

This is just a small blog for me to record my experience of implementing the new Configuration Manager 2012 environment into production at my present company. It will be a daunting task to say the least, but I am excited to get started on this adventure and see what comes of it. I feel as equipped as a newbie can. A couple of weeks ago I attended a training on CongfigMgr 2012 SP1 with Kent Agerlund, a Microsoft MVP. It was an incredible training and I learned a lot. For nearly the past year, I've kept up through blogs and Twitter about other migrations and implementations of the new SCCM and read some books. I am ready to actually get my hands wet with a real migration. I will keep you all posted on my adventure as I bring a new world of order to my company. Wish me luck!

Throughout this blog, I'm sure I will post issues I come across. If you subscribe, please feel free to comment and help me solve them. Or introduce me to different ways of thinking, or scripts (and more) that may make my job easier. That is the main purpose of this blog. Learning the tools of the trade as I go. Or you can watch me suffer....just keep encouraging me. ;)