Microsoft released another Technical Preview release, this time 2207, and it has a new feature, Distribution point content migration. According to the official blog post this will come in handy when you need to migrate your distribution point content from one dp to another, in particular because of the first 2 points listed below.
Quote
There are multiple scenarios where the content of one distribution point needs to be migrated to another distribution point.
Cloud distribution points (CDP) hosted on Azure classic services are getting deprecated by mid of 2024. You need to migrate CDP content to another distribution point.
Migration of cloud migration gateway v1 (CMGv1) hosted with *.cloudapp.net domain is also getting deprecated, hence you may need to migrate CMGv1 content to another distribution point.
You may need to migrate local distribution point content to other local distribution point or CMG.
As I don't have either (1) or (2) I will test scenario (3).
Step 1. Satisfy the prerequisites
One of the prerequisites is that the user performing the migration has the "Copy to Distribution Point" permission enabled under the Distribution Point permissions. As my user account is a Full Administrator, that requirement is already met.
The other requirements are listed below.
If you want to deprecate the source distribution point, make sure that the source and destination distribution points have the same boundary group.
The destination distribution point should be installed already and able to receive the content.
Step 2. Migrate a distribution point using Powershell
As the current solution does not work in the Console, we need to use Powershell to do the migration. On the Configuration Manager server, open a Powershell cmd prompt via the console,
As the ability to monitor this via the console is not yet available, you'll need to once again monitor things using Powershell. The command this time is
The result should tell you if it's in progress, completed and so on.
Step 4. Monitor the content being migrated
The docs incorrectly listed the cmdlet as Get-CMDistributionPointContentMigrationStatus but that doesn't work, see below.
Here is a screenshot of the docs... (as of 2022/07/10), I've informed them of the error, so I'm sure it'll be fixed soon
Using the power of the TAB key, I figured out the correct command and here it is:
Get-CMDistributionPointMigrationContentStatus
I think that the status (4) means that it's still in progress but I've asked the Microsoft Product Group for comment. As you can see below the source DP lists this packageID as a large package so it will take more time to complete.
and sure enough, after more minutes in transit, the status changes from 4 to Success
So there you have it, content migration from one distribution point to another using Powershell built into ConfigMgr works very nicely indeed, is that cool or what ?
Introduction
Microsoft released another Technical Preview release, this time 2207, and it has a new feature, Distribution point content migration. According to the official blog post this will come in handy when you need to migrate your distribution point content from one dp to another, in particular because of the first 2 points listed below.
As I don't have either (1) or (2) I will test scenario (3).
Step 1. Satisfy the prerequisites
One of the prerequisites is that the user performing the migration has the "Copy to Distribution Point" permission enabled under the Distribution Point permissions. As my user account is a Full Administrator, that requirement is already met.
The other requirements are listed below.
Step 2. Migrate a distribution point using Powershell
As the current solution does not work in the Console, we need to use Powershell to do the migration. On the Configuration Manager server, open a Powershell cmd prompt via the console,
and try the following
for example...
Start-CMDistributionPointMigration -SourceDistributionPointName cm01.windowsnoob.lab.local -DestinationDistributionPointName webserver.windowsnoob.lab.local
as shown here...
The fact that it didn't error was a good start.
Step 3. Monitor the migration using Powershell
As the ability to monitor this via the console is not yet available, you'll need to once again monitor things using Powershell. The command this time is
Let's give it a try.
Get-CMDistributionPointMigrationStatus -SourceDistributionPointName cm01.windowsnoob.lab.local -DestinationDistributionPointName webserver.windowsnoob.lab.local
The result should tell you if it's in progress, completed and so on.
Step 4. Monitor the content being migrated
The docs incorrectly listed the cmdlet as Get-CMDistributionPointContentMigrationStatus but that doesn't work, see below.
Here is a screenshot of the docs... (as of 2022/07/10), I've informed them of the error, so I'm sure it'll be fixed soon
Using the power of the TAB key, I figured out the correct command and here it is:
Get-CMDistributionPointMigrationContentStatusI think that the status (4) means that it's still in progress but I've asked the Microsoft Product Group for comment. As you can see below the source DP lists this packageID as a large package so it will take more time to complete.
and sure enough, after more minutes in transit, the status changes from 4 to Success
So there you have it, content migration from one distribution point to another using Powershell built into ConfigMgr works very nicely indeed, is that cool or what ?
Related reading
cheers
niall
Share this post
Link to post
Share on other sites