During this first part of SCCM2012 R2 OSD we will see how to prepare our SCCM for OSD an how to capture our customized OS to use it in the next post as a reference image.
You already know that there is no in place upgrade from the old SCCM2007 to 2012 what if you had an existing SCCM 2007 …simply you will build your new SCCM 2012 as we did during the last 9 parts and then migrate you data from the 2007 SCCM.
In Microsoft System Center 2012 R2 Configuration Manager, the built-in migration functionality replaces in-place upgrades of existing Configuration Manager Infrastructure by providing a process that transfers data from active Configuration Manager 2007 sites. Migration can transfer most data from Configuration Manager 2007.
Migration can migrate most objects from Configuration Manager 2007 to System Center 2012 Configuration Manager. The migrated instances of some objects must be modified to conform to the System Center 2012 Configuration Manager schema and object format. These modifications do not affect the data in the Configuration Manager 2007 database.
You can migrate the following types of objects:
· Software distribution packages
· Virtual application packages
· Software Updates:
o Deployment packages
o Software update lists
· Operating System Deployment:
o Boot images
o Driver packages
o Task sequences
· Desired Configuration Management:
o Configuration baselines
o Configuration items
· Asset Intelligence customizations
· Software metering rules
Distribution Points are helpful when you have a branch office that has number of clients “less than 500 client” connected through WAN to your HO. You can distribute OS images and software packages through a DP which will reduce latency and bandwidth consumption. Packages will be distributed to the DP over the WAN once and the clients pull it from the local DP over the LAN.
First we need to add the SCCMAdmin account and the SCCM Site Server account to local administrators group on the machine that will be a DP, and open the required ports.
We are going to install one secondary site server for SCCM 2012 R2. Generally installing secondary site is recommended if you have Brach with more 500 clients in a remote location, this might overload the network even with the new 2012 Distribution point’s features. if you need software update point or management point at this branch you shoud go for secondary site too.
First we need to add the SCCMAdmin account and the SCCM Site Server account to local administrators group on the machine .
Roles / Role Services Required for Secondary Site:
Web Server (IIS) (Can be done by SCCM)
· Application Development:
· IIS 6 Management Compatibility:
Features Required for Secondary Site:
· Remote Differential Compression
. NET Requires both of the following:
During the first Part Part1 we have added the Software updated point and tried the Manual Software updates … Here comes the fun part
Automatic Deployment rule enables you to create update package automatically according to some criteria such as release date. It is possible for example to create update package automatically every month. Once the package is created, it is automatically deployed..
To create Automatic Deployment Rule, go to Software Library and right click on Automatic Deployment Rule and click on Create Automatic Deployment Rule