GeoffW

Thanks for the nice set of migration info. I've depended on this site for making my SCCM 2007 experience as pleasant as possible. Happy to see that I can continue to do that with SCCM 2012. The logistics of actually doing the migration seem to be moderately complex. Or, I'm totally misunderstanding some of the issues. Since we are getting ready to bring up SCCM 2012, I'd like to understand the issue with boundaries and some of the timing issues for migration. From above it appears that SCCM 2012 and SCCM 2007, running in parallel at the same time, must either have different boundaries, or as you migrate over collections/computers to SCCM 2012, that are in a particular boundary (say subnets), you have to remove that boundary from the SCCM 2007 server. So, is this how it has to go? 1. Bring up SCCM 2012 and configure. Place it on a subnet that is NOT part of the SCCM 2007 boundaries. 2. Test the SCCM 2012 setup to make sure it works. Will need to create a SCCM 2012 boundary (and place in a boundary group) that is NOT contained in any of the SCCM 2007 boundaries. So, a different subnet. 3. Migrate over some advertisements/packages and test SCCM 2012 software distribution of those packages to some test machines in the new boundary group. Or, I guess you could also create some new applications and advertisements. 4. Once you are happy with the new SCCM 2012 service, start the migration in earnest. Note - Here is where I get a little confused over the sequence and timing. 5. Migrate over from SCCM 2007 a collection of computers that are all in a specific boundary/subnet. I'm assuming that you would need to then remove that boundary from SCCM 2007 and add a new boundary to SCCM 2012 that would comprise the subnet(s) for the computers that were in the collection you migrated. Not sure about the sequence of what you do first. 6. Once the boundary is in place in SCCM 2012 (and removed from SCCM 2007), you install the new SCCM 2012 client on all the computers that are now in the boundary (and a collection) that is part of SCCM 2012. Once that is done you can proceed to do your normal software distributions to those computers from SCCM 2012. 7. Repeat steps 5 and 6 for the rest of your boundaries and computers in SCCM 2007 until all computers have been migrated. 8. At the end of all this, SCCM 2007 should not have any boundaries configure on it. Note that I'm a little perplexed about the new SCCM 2012 site code. It has to be different that the site code used by SCCM 2007. But, isn't that site code info stored up in Active Directory (and possibly in DNS and WINS)? So, when/how to change the site code info on Active Directory? And once that information is changed (in order to be able to install the new client on all the migrated computers), won't that mean that you will lose the ability to install the client on any remaining SCCM 2007 boundaries? Hmmm. Does that mean you need to migrate all computers in the organization at the same time, remove all the boundaries from SCCM 2007, change the site code info in AD, and then install the new SCCM 2012 client on all computers at the same time? Sorta seems that way. If anyone can shed any light on the above questions, it would really help me out. Thanks, Geoff Weatherford CSU/CVMBS

Hopefully someone can help a confused current user of SCCM 2007. So, we currently use SCCM 2007. Great product that is actually made usable by sites such as this with all the guides. Much appreciated. Our current plan was to install SCSM 2010 and integrate it with SCCM 2007. But, we are being pressured to jump into SCCM 2012 by another group. I have three questions: 1. If we are going to make the jump to SCSM, should we just go straight to SCSM 2012 and skip SCSM 2010? 2. Since you need to integrate SCSM with SCCM, if we go to SCSM 2012 should we, at the same time, make the move/migrate to SCCM 2012? I'm a little concerned about creating additional work by integrating SCSM 2012 with SCCM 2007. Then later having to "break" that integration when we migrate SCCM 2007 to SCCM 2012. Seems like a lot less headache to do the following: a. Migrate SCCM 2007 to SCCM 2012. b. Then setup SCSM 2012 (and do the integration with SCCM 2012). 3. I'm confused about how all the System Center packages are being released. According to this Microsoft site, you purchase all of the System Center family in one package http://www.microsoft.com/licensing/about-licensing/SystemCenter2012.aspx#tab=3 Is that really what is required? If so, do you just pick and choose what you want to install afterwards? Or, can you purchase all the pieces separately (like was done with SCCM 2007, SCSM 2010, etc.)? Their "cloud" marketing is making my head ache : ) Thanks for any and all advice. GeoffW CSU

We will go ahead and work with the HTAs for SCCM 2007. Appreciate the link to the MDT Wizard editor. Thanks - GeoffW -

We are wondering if moving to SCCM 2012 (from 2007) would save us some required work. We are currently in a project for our college to prepare (with the help of this site and others, thank you very much : ) some HTA frontends to use with SCCM 2007. In particular, we want to allow helpdesk techs to bring up a computer and boot from a thumb drive, CD, or PXE boot and get a HTA that leads them through installaing a new operating system. It could ask for the name of the new computer to be used as a new entry in SCCM, or if this was a migration effort in which case it would retain the current name, whether a 32 bit or 64 bit image was required, etc., etc. Then they click on "go" and it all gets done. This will also allow us to, hopefully, use student temporary help. You have covered much of this in your HTA forum, so nothing new (and your info is very much appreciated). All that said, we are wondering if all the above is necessary for SCCM 2012? That is, is the functionality that HTA's provided in SCCM 2007 now already built into SCCM 2012? At least to the point of having minimally trained (or, just a way to speed things up) student employees safely and correctly install (or, migrate) new operating systems on a new (or to be refurbished) computer. If such is the case, then we may decide to spend the time migrating to SCCM 2012 instead of working on the HTA front ends. However, if HTA front ends are going to remain necessary for SCCM 2012, then we will spend the time creating HTA front ends for SCCM 2007 (and make the transition to SCCM 2012 much later this year). The automation/ease of use that HTA front ends provide is our biggest priority at this time. If anyone has any input on this question, I would most appreciate hearing it. Thanks, Geoff Weatherford CVMBS CSU