Hey Everyone!
Just wanted to introduce myself as the next guy on the boards who will be performing a SCCM 2007 to 2012 migration without a clue as to what I'm doing!
Well, let me take that back, I am very familiar with building packages (and a little OSD), but not all of the other aspects of SCCM, especially SCCM's inner workings and troubleshooting. And since building packages apparently makes me the most knowledgeable SCCM guy here, that is how I get the project.
Now, all of this isn't a problem, it's just that it is exciting (to learn something new) and terrifying (OMG SCCM is complex!) all at the same time.
I just ordered the following books and will hopefully have them next week.
Mastering System Center 2012 Configuration Manager
http://www.amazon.co...duct/1118128982
System Center 2012 Configuration Manager (SCCM) Unleashed
http://www.amazon.co...duct/0672334372
And of course, my boss wants me to get started quicker than that. With that said, I have plenty of time to finish the project (EOY 2013), so I think that he just wants to tell management that the project is underway.
So, until I get the books and can start reading all 2200+ pages of them, I had a couple of questions.
As a general approach to the project, I was thinking of not using any of the migration tools. My initial thought was to stand up SCCM 2012 and then manually replicate all of the functionality. That way, hopefully I'll have a good understanding of how the system works as a whole, instead of just following the guides/books. Does that make sense, or am I out of my mind? (~750 Clients, ~35 remote sites connected via T1's, 40 or 50 packages, 1 OS image; so not a huge setup.)
As long as no boundaries are specified in SCCM 2012, then there is no harm in standing up SCCM 2012 in parallel with SCCM 2007, correct?
Any "gotcha!" moments that others had while working their SCCM 2012 projects? Especially stuff that was not in the books...
Other than the books, Technet, and this site; any other sites, books, etc. that I should be looking at?
Anyone have any good project plans for a SCCM 2012 implementation? If not, I should probably dust off that copy of MS Project that I hardly ever use and set up a project. Maybe even post the .mpp someday...!
Right now, there is ZERO documentation for our current SCCM 2007 setup. I mean documentation as to why the packages are put together the way they are, what software is included in our base image, etc. I tried googling it, but I don' think that I was searching for the right term, because all I could find was this site and the Technet documentation. I'm talking about the stuff that you would put into your internal IT Wiki for the help desk and other administrators to take a look at. Anyone have any links to any good examples?
Alright, I think that's enough for a while. I'm just eager to get started and didn't want to wait for my books!
If you have any questions or needed more detail, just let me know.
Thanks!
* Edited for spelling...