Before migrating clients from the
source hierarchy to a destination hierarchy, we must migrate the objects that
are associated with the client and we must then reinstall or reassign the
clients from the source hierarchy to the destination hierarchy. We need to
migrate the objects first so that they are available when the clients are
migrated.
Key notes on client migration;
- When we migrate clients from a source hierarchy, the
client software on the client computer updates to match the product version of
the destination hierarchy
- We can use any client deployment method to upgrade or
re-assign clients to the destination hierarchy
- Before we migrate a client, run a migration job to
migrate the information of the client which will be used in the destination
hierarchy
- Clients that migrated to the destination will retain
their deployment history for all the previous deployments to prevent them from
rerunning unnecessarily in the destination hierarchy
- Follow a phased client migration when migrating higher
number of devices
- To monitor the progress of migration, go to Migration
node of the Administration workspace in the Configuration Manager console
Client Migration and Data retention:
Only the following data will be retained on the clients
when we migrate a client from its source hierarchy to the destination
hierarchy;
- The unique identifier (GUID), which associates a client
with its information in the Configuration Manager database.
- The advertisement or deployment history
Before start re-assigning the clients to new hierarchy we need to;
- Create boundaries and boundary groups on the new
hierrchy
- Enable desired discovery methods and run them
There are different ways to re-assign the client to the
new environment. One of the best way is using a simple script.
SCCM Site code change using script:
There are many scripts available in the community to
change the site code. Identify and test desired script and create a package for
that script in the old environment.
I have used a script from here
Modify the script with your site code and copy into your
SCCM source location
Open SCCM console in old hierarchy then create a package
using above script.
Distribute the content to all the distribution points
then create a deployment and select the target device collection.
Before the script deployment, the Client status
will be No then site code and client activity will be empty on the destination hierarchy.
Once the script deployed and executed, the client’s status and site code will be updated in the console. We can monitor the change of site code in the SCCM console work space.
Next, enable automatic site-wide client push installation
so all the client versions will be updated to the hierarchy version.
In SCCM console go to \Administration\Overview\Site
Configuration\Sites then select Client
Push installation from Client
Installation settings from the top ribbon;
On the Client Push Installation Properties General tab;
- Select Enable automatic site-wide client push
installation
- Select System types as required
On the Accounts tab,
enter a new account or select an existing account from the Client Push installation accounts tab.
We need to have an account for the client push to work.
On the Installation properties we don’t have to change
anything as the default site code will be populated automatically.Click OK to Apply the settings
That’s it. Now the clients are assigned to the new
hierarchy and updated /or will update to the latest client version.
Click here
for complete SCCM 1511 Current Branch setup step by step guide.
Click here
for complete SCCM 1511 Current Branch step by step guide, step by step migration
guide, step by step monitoring and health check guide and step by step SCCM
Current Branch servicing guide.
Great post! Which script are you referring to in the script center ?
ReplyDelete