Reassign Shared Distribution Point - Required free space

Hi All,
I’m working on the migration from SCCM 2007 R3 to SCCM 2012 R2 CU1 for our customer and currently I would to reassign our SCCM 2007 Secondary Sites to SCCM 2012 Distribution Points.
The “Reassign Shared Distribution Point Wizard” states that I need approximately twice the space of required content for the conversion:
... but in the following Technet article I read that the conversion requires available free disk space equal to the size of the largest package that is stored on the distribution point (see the extract below):
http://technet.microsoft.com/en-us/library/gg712275.aspx
To upgrade a distribution point from within the Configuration Manager console, the Configuration Manager 2007 site system server must meet the following conditions:
The      distribution point configuration and location must be eligible for      upgrade.
The      distribution point computer must have sufficient disk space for the      content to be converted from the
Configuration Manager 2007 content      storage format to the single instance store format. For      System Center 2012 Configuration Manager with no service      pack, this conversion
requires available free disk space equal to two      times the size of the existing data on the distribution point.
Beginning with      System Center 2012 Configuration Manager SP1 and      System Center 2012 R2 Configuration Manager, this conversion requires
available free disk space equal to the size of the largest package that is      stored on the distribution point.
Considering that the environment version is SCCM 2012 R2 CU1 (version: 5.0.7958.1203)
I do not know if it is
better to trust to MS article or to the Reassign DP Wizard statement. Is it really needed
all that free space in my DP in order to complete the migration?
Any help would be appreciated.
Thanks a lot.
Andrea

In my experience with R2 migrations you do not need double the space as was the case with RTM version.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Similar Messages

Script "upgrade shared distribution points"

Hi
We have about 400 SCCM 2007 Secondary Sites and need to migrate them to SCCM 2012 SP1 Distribution Points. As you can image we don't want to click 400 times during migration wizard.
Is there a way to script the upgrade of all shared distribution point? e.g. powershell or SDK (C# or VBScript)
Many, many thanks in advance,
Wolfgang

Try with "update-help" (see REMARKS)...
I get following short information:
NAME
Start-CMDistributionPointUpgrade
SYNTAX
Start-CMDistributionPointUpgrade -SiteCode <string> -SharedDistributionPoint <IResultObject#SMS_MigrationDP>
-CertificateExpirationTimeUtc <datetime> -AllowPreStaging <bool> [-PublicFqdn <IResultObject#SMS_MigrationDP>]
[-InstallationAccount <IResultObject#SMS_SCI_Reserved>] [-InitiateConnection <bool>] [-InstallInternetServer
<bool>] [-ClientConnectionType <ClientConnectionTypes> {Intranet | Internet | InternetAndIntranet}]
[-EnableAnonymous <bool>] [-MinFreeSpaceMB <int>] [-PrimaryContentLibraryLocation <DriveType> {Automatic | A | B |
C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z}]
[-SecondaryContentLibraryLocation <DriveType> {Automatic | A | B | C | D | E | F | G | H | I | J | K | L | M | N |
O | P | Q | R | S | T | U | V | W | X | Y | Z}] [-PrimaryPackageShareLocation <DriveType> {Automatic | A | B | C |
D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z}]
[-SecondaryPackageShareLocation <DriveType> {Automatic | A | B | C | D | E | F | G | H | I | J | K | L | M | N | O
| P | Q | R | S | T | U | V | W | X | Y | Z}] [-EnablePxeSupport <bool>] [-AllowRespondIncomingPxeRequest <bool>]
[-EnableUnknownComputerSupport <bool>] [-ComputersUsePxePassword <securestring>] [-UserDeviceAffinity
<UserDeviceAffinityType> {DoNotUse | AllowWithManualApproval | AllowWithAutomaticApproval}]
[-MacAddressForRespondingPxeRequest <string[]>] [-PxeServerResponseDelaySeconds <int>] [-ValidateContentSchedule
<IResultObject#SMS_ST_RecurWeekly>] [-ContentValidationPriority <Priority> {Lowest | Low | Medium | High |
Highest}] [-BoundaryGroup <IResultObject#SMS_BoundaryGroup[]>] [-AllowFallbackForContent <bool>]
[-PathForSavingMigratedPackage <string>] [-WhatIf] [-Confirm] [<CommonParameters>]
Start-CMDistributionPointUpgrade -SiteCode <string> -SharedDistributionPoint <IResultObject#SMS_MigrationDP>
-CertificatePath <string> -AllowPreStaging <bool> [-PublicFqdn <IResultObject#SMS_MigrationDP>]
[-InstallationAccount <IResultObject#SMS_SCI_Reserved>] [-InitiateConnection <bool>] [-InstallInternetServer
<bool>] [-ClientConnectionType <ClientConnectionTypes> {Intranet | Internet | InternetAndIntranet}]
[-EnableAnonymous <bool>] [-CertificatePassword <securestring>] [-ForceWhenDuplicateCertificate <bool>]
[-MinFreeSpaceMB <int>] [-PrimaryContentLibraryLocation <DriveType> {Automatic | A | B | C | D | E | F | G | H | I
| J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z}] [-SecondaryContentLibraryLocation
<DriveType> {Automatic | A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W
| X | Y | Z}] [-PrimaryPackageShareLocation <DriveType> {Automatic | A | B | C | D | E | F | G | H | I | J | K | L
| M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z}] [-SecondaryPackageShareLocation <DriveType> {Automatic |
A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z}]
[-EnablePxeSupport <bool>] [-AllowRespondIncomingPxeRequest <bool>] [-EnableUnknownComputerSupport <bool>]
[-ComputersUsePxePassword <securestring>] [-UserDeviceAffinity <UserDeviceAffinityType> {DoNotUse |
AllowWithManualApproval | AllowWithAutomaticApproval}] [-MacAddressForRespondingPxeRequest <string[]>]
[-PxeServerResponseDelaySeconds <int>] [-ValidateContentSchedule <IResultObject#SMS_ST_RecurWeekly>]
[-ContentValidationPriority <Priority> {Lowest | Low | Medium | High | Highest}] [-BoundaryGroup
<IResultObject#SMS_BoundaryGroup[]>] [-AllowFallbackForContent <bool>] [-PathForSavingMigratedPackage <string>]
[-WhatIf] [-Confirm] [<CommonParameters>]
ALIASES
None
REMARKS
Get-Help cannot find the Help files for this cmdlet on this computer. It is displaying only partial help.
-- To download and install Help files for the module that includes this cmdlet, use Update-Help.

SCCM 2012 and SCCM 2007 Shared Distribution Points

I am building a new SCCM 2012 site (primary and 4 secondaries) besides a SCCM 2007 site (primary, 3 secondaries and 65 DPs).
I migrated all objects from SCCM 2007 to SCCM 2012 which worked well.
I migrated a client from SCCM 2007 to my SCCM 2012 environment and that worked well. Then i push some packages from SCCM 2012 to my migrated client which worked as well either.
Then I switch on the SHARED DISTRIBUTION option in the migration section and now my migrated SCCM 2012 client only can access the SCCM 2007 DPs and packages from SCCM 2012 DP can't be accessed anymore...in Software Center the packages will stay at 0% downloading....
Is that normal behavior after enabling shared DPs ?

Did you ever find a solution for this? I am experiencing the same issue.
I have an IP address range boundary for testing SCCM 2012. After enabling shared distribution option SCCM 2012 migrated boundaries from SCCM 2007. My test IP address range boundary has two boundary groups... One is the SCCM 2012 Boundary group
pointing towards the SCCM 2012 DPs. The 2nd is the automatically created "Boundary Group for SCCM 2007 distribution point."
With both of those in there I can only push SCCM 2007 packages to the SCCM 2012 clients. SCCM 2012 packages come back in the logs as "Calling back with empty distribution points list." If I remove the automatically created "Boundary Group for SCCM 2007 distribution
point" from the test IP boundary then SCCM 2012 clients will properly download from the SCCM 2012 DPs, but now the SCCM 2007 packages fail to download to the SCCM 2012 test clients.
I assume I have some kind of boundary issue but am at a loss of resolving it. Either that or I have the shared dp concept down incorrectly. Shouldn't I be able to have a boundary that has SCCM 2012 clients that uses the 2012 DP for 2012 content but the 2007
DP for 2007 content while I am migrating?
Thanks for any help
- Ryan

State Migration Point Minimum Free Space

I am in the process of doing OS deployment with Windows 7. I have a State Migration Point in place with minimum free space threshold of 100mb. My question is, will my task sequence error out and fail prior to formatting the drive and installing Windows 7
if the minimum free space is met and all the data cannot be captured? I am nervous that if this threshold is met all user data on a system is not able to be captured and the task sequence continues on to format the drive and install the OS.
Thanks,
Mike
Solutions Architect

Yes, the prepare state capture task will fail if it can't find an SMP with free space on it thus causing the TS as a whole to fail assuming you haven't selected the ignore failure option on the task or any of its parent groups. That's doesn't necessarily
guarantee that there is enough free space or that multiple simultaneous task sequences couldn't cause issues though thus you should plan accordingly, monitor the free space instead of leaving it to chance, and enable the auto cleanup feature with a rational
period of time.
Jason | http://blog.configmgrftw.com

File Vault requires free space equal to size of Home Folder?

Is it true that File Vault requires you maintain free disk space equal to the size of your home folder? Or is that only necessary in order to create the vault in the first place?

I'm really sorry but I still am no clear if you gave me an answer to my original question, which was "Is it true that File Vault requires you maintain free disk space equal to the size of your home folder?"
I understand I need to have free space equal to the size of my Home Folder for initial encryption.
I understand I need to have free space equal to the size of my Home Folder should I decide to restore (or unencrypt) the encrypted folder. This is easy to do by simply moving files off to an external drive.
I understand that having a full drive can result in degredation of system performance.
What is still not clear to me, is whether I must maintain that space during day to day operation.
Realistically, my Home Folder is about 90GB, after having removed graphics and music files. I would prefer not to have to maintain 90gb of free space during normal operation. If my drive has 30gb or more of free space, that should be more than enough to maintain reasonable system performance.

Pull Distribution Point Requirements (BITS?)

We have recently migrated to all SCCM 2012 infrastructure. All of our recent deployments are Server 2012 but we have a lot of Server 2008 R2 64bit. There is a lot of documentation online and some say BITS is required for DPs and some say not. Our packages
have been struggling to reach our DPs and Pull DPs. Does anyone have any opinion if BITS should be installed on DPs or Pull DPs. I know I have read that BITS is not required on Server 2012 however it states nothing about Server 2008 R2 64bit. Any opinion or
experience would be helpful.

Nothing specific to Pull DP...
Windows Server 2012 or Windows Server 2012 R2:
http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_Win2k12SiteSystemPrereqs
With System Center 2012 Configuration Manager, the distribution point site system role does not require Background Intelligent Transfer Service (BITS). When BITS is configured on the distribution point computer, BITS on the distribution point computer is
not used to facilitate the download of content by clients that use BITS
A pull-distribution point is considered to be a client when it accesses another distribution point to obtain content.

SCCM 2012 shared distribution point reassignment - old SCCM 2007 folders/files delete

Ok, I've looked, googled, binged, and cannot find any definitive answer on this, I've even asked a Microsoft Engineer, and I fear they are just as confused as I am, please help!
The scenario: I'm migrating from SCCM 2007 to 2012 and of course have shared DP's, I reassign a shared DP and this is what I expected to happen but did not - all the old .pck files from 2007 (in the SMSPKG folder on the OLD DP) should have been deleted AFTER
the content was converted into the single instance store, they are still there! if they are supposed to be there...why then is it called a SINGLE instance store if there are TWO folders containing compressed source files??? Also, the files in my OLD SMSPKGD$
(extracted source for 2007) are still there as well, even though prior to the reassignment of the DP I changed all of my deployments to download/run locally...what gives?
The end result of me reassigning my DP is the new content is essentially doubling the space taken up on the drive...not cool. Can I delete the content of the legacy folders (either the .pck or the folders in SMSPKGD$)?
Terry

Hi,
"The folder is used to temporarily store PCK files that get transferred to child or secondary sites. If you don't have any of those, the folder won't ever have anything in it. Even if you do have one of those, it'll still be empty most of the time because
PCK file storage in 2012 is temporary only."
For more information:http://social.technet.microsoft.com/Forums/en-US/2c5e6049-8566-4638-8ba8-3768c74c53f6/smspkg-folder-on-primary-site-server-which-is-not-a-dp?forum=configmanagergeneral
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

How long until Deleted Content from Distribution Point frees disk space?

Hopefully this is an easy question for you guys with more experience with the product.
Yesterday, I created a new software distribution group for Office 2013 SP1, both 32 and 64bit. I didn't really understand at the time that it was going to download nearly 8GB into my /sources folder...which is where I save my package contents. I
would have not expected this download to exceed approx 2GB.
Since I indicated that it should also be distributed to my Distribution point, which is the same server, it also increased the disk usage in the /sccmcontentlib folder, as well as increasing the amount of space used in my SQLDatabase which is on the same
drive. It was never deployed to anything.
Since I'm not yet ready to deploy this update to clients, but have a few others things to do instead, I wanted to delete the content from the distribution point to free up some disk space.
I went into Software Library, Deployment Packages, went to properties of my Office2012_SP1 deployment, went to Content Locations, picked my single distribution point from the list, and chose Remove.
However, no disk space was cleared on my drive. I've still got 6GB free on my 120GB volume, so I'm not out of space.
Is this something where a scheduled job will come through and process this removal and free up the disk space? Or is there a way to kick of the process manually?

It was never setup as an application.
It was a Windows Update, which was added to a software update group. Then, I went to the software update group and right clicked and chose Download. I created a new deployment package, and then distributed the content to one of my distribution
point.
By doing that, I understood that it would create the D:\sources\WindowsUpdates\Office2013_SP1 folder and put the deployment files there. And I also see that because that content was set to a distribution point, it copied it there into the ContentLib.
So, I wanted to remove the data from ContentLib, so I went to the Deployment Package, went to Content locations and removed my Distribution Point.
So, are you saying that in order to remove the ContentLib, that I have to remove the entire Deployment Package?
I thought by removing the Content Location it would remove it from the DP, and if I later wanted to add it back ,I could go back to the Deployment Package, go into Properties and add a DP back to the content location.

2012 -- 2012 Migration: How to Reassign Distribution Points that Reside on Source Secondary Site Servers to the Target Site

Source hierarchy AAA is at 2012 R2 CU3 and contains a primary site and 14 secondary sites (A01 through A14). The 14 secondary site servers hold the following roles:
Site system
Management Point
State migration point
Site server
Site database server
Component server
Distribution Point
Target hierarchy BBB is also at 2012 R2 CU3 and contains only a primary site. The goal is to "downgrade" the severs at source secondary sites A01 through A14 to distribution points.
AAA was added as a source site. Data gathering was done. A migration job was created an run, and distribution points from the source hierarchy were shared to allow a phased migration of the clients.
We have reach the point where we are ready to reassign distribution points in sites A01 through A14 from AAA to BBB, but none of the shared distribution points are eligible for reassignment. We surmise that since the DP role is not the only role on
these servers (as you can see from the bullet list above), they are ineligible for reassignment. We are unable to remove most of the roles. In fact, the only 2 roles that can be removed are the DP role itself, and the State Migration
Point. If we delete the secondary site, it removes ALL roles...not leaving any behind...including the one we need...DP.
My question is 2-part:
Is our assumption correct? Must a DP role be the only one on the server for a DP to be eligible for reassignment?
Is there any way we can reassign these DPs instead of deleting everything and building them from scratch?
These secondary site servers are in branch offices and host a lot of distributed packages. It would be very inconvenient to have to rebuild the DPs from scratch and redistribute all those packages over the WAN.

Full Disclosure: I have never used this tool myself. I intend to, however the opportunity or time to do so has not yet arisen.
You could use the techniques outlined in CloneDP (https://gallery.technet.microsoft.com/scriptcenter/CloneDP-for-SCCM-2012-SP1-825ce5b1) to create prestage media on each DP and rebuild. That at least would prevent redistributing over the WAN
Ken provides a nice writeup too: http://blogs.technet.com/b/kensmith/archive/2013/08/01/migrating-the-content-library-between-distribution-points-in-sccm-2012-sp1.aspx

"Enable distribution-point sharing for this source site" did not showing SCCM 2007 DPs as SCCM 2012 content shares for CM12 clients

Hi
We have one central site server and three primary site servers in SCCM 2007 and completed the SCCM 2012 migration as single hierarchy.
During the migration, We have configured SCCM 2007 Central site server as source hierarchy for data gathering process and configured the "Enable distribution-point sharing for this source site" to make SCCM 2007 distribution points
as SCCM 2012 content shares to serve SCCM 2012 migrated clients. Now we are facing a problem that one of the primary site server's data gathering process did not gather SCCM 2007 DPs even though we configured "Enable distribution-point sharing for this
source site" but data gathering process is completing successfully.
Is anyone have idea, why these SCCM 2007 DPs did not appearing as SCCM 2012 content shares under "Shared Distribution Points"
Thanks in Advance
srkr

Now we are facing a problem that one of the primary site server's data gathering process did not gather SCCM 2007 DPs even though we configured "Enable distribution-point sharing for this source
site" but data gathering process is completing successfully.
Earlier all the shared DPs are showing under Shared Distribution Points ? Or since starting itself these DPs are not showing down? Have you checked migmctrl.log for some clue?
Anoop C Nair (My Blog www.AnoopCNair.com)
- Twitter @anoopmannur -
FaceBook Forum For SCCM

Setup was unable to use existing system partition because it does now contain the requiered free space.

I try to install it, but i select my free (fresh formated) partition with 35GB free space and i see:
Setup was unable to use existing system partition because it does now contain the required free space.
if i select partition with partition that does not contain the required i see
"Windows cannot be installed to Disk 0 Partition 1. (show details)"
so what is it? what can i test?
My Disk has 250GB, my partitions:
C: 8MB - Boot (7MB Free) - FAT
D: 37,5GB - WINXP (27,9GB Free space) - NTFS
E: 35,3GB - New (35,2GB Free) - NTFS - i want to install on it
F: 160GB - Data (6GB Free) - ntfs

kolorafa_ said:
I try to install it, but i select my free (fresh formated) partition with 35GB free space and i see:
Setup was unable to use existing system partition because it does now contain the required free space.
if i select partition with partition that does not contain the required i see
"Windows cannot be installed to Disk 0 Partition 1. (show details)"
so what is it? what can i test?
My Disk has 250GB, my partitions:
C: 8MB - Boot (7MB Free) - FAT
D: 37,5GB - WINXP (27,9GB Free space) - NTFS
E: 35,3GB - New (35,2GB Free) - NTFS - i want to install on it
F: 160GB - Data (6GB Free) - ntfs
Is this 8MB "Boot" partition (formatted as FAT???) something you created when you partitioned this disk for the Windows XP installation, or is this an 8MB OEM partition that you've somehow assigned drive letter C: to?
I wouldn't be surprised at all that your error message is being generated because thsi "BOOT" partition, labelled as drive C:, is only 8MB in size, and you can be absolutely positive that an 8MB partition is going to generate this error: "Setup was unable to use existing system partition because it does not contain the required free space."
The correct answer really depends on whether that drive C: is the boot (sic) (the proper terminology is to call it the system partition) partition for the Windows XP installation. If it is, then you're going to have some repair work to do on your Windows XP installation first, so that you can free up that 8MB partition.
In any event, I'm fairly certain that the solution is going to require the removal of that 8MB partition, as you've suggested in your most recent post.
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

Internal Hard Drive Free Space Issue

Hey,
I recently upgraded my 17" MacBook Pro from Tiger to Snow Leopard but the upgrade seems to have created a number of problems, the most notable being the lack of free space now available on my internal hard drive.
I also had to install a trial version of Aperture 3.0.3 in order to access my aperture library as the older version of Aperture is not compatible with Snow Leopard.
At this point the free space available on my internal hard drive was 36GB and my aperture library was 39GB. I had to uninstall Photoshop Elements 9 in order to create enough free space to open this library.
I bought an external hard drive and after some organising (importing and exporting to and from external hard drive), I eventually moved all photo files/folders, projects and libraries onto this external drive, leaving only one in-progress project (about 3GB) left on the internal volume.
I also exported my iTunes library and any other files to this external drive.
All trashes have been emptied.
The problem is that, despite all this clear-out, I now only have 2GB of free space on the internal hard drive.
I ran Disk Inventory X and it shows that my home folder is using 155GB of space, which seems ridiculous considering there is in effect nothing left on my laptop save for the application programs and the one remaining project.
I have manually checked through this folder and all its subfolders and have found nothing that would accumulate to this amount of space.
I have repaired an issue with the internal volume, but it is now showing a “minor” problem with the volume header.
If someone can provide and explanation/solution to this I would be very grateful as it is severely slowing my workflow at the moment.
Thanks

Baresi:
I suggest that you begin with Repair Disk
Insert Installer disk and Restart, holding down the "C" key until grey Apple appears.
Go to Installer menu (Panther and earlier) or Utilities menu (Tiger) and launch Disk Utility.
Select your HDD (manufacturer ID) in the left panel.
Select First Aid in the Main panel.
(Check S.M.A.R.T Status of HDD at the bottom of right panel, and report if it says anything but Verified)
Click Repair Disk on the bottom right.
If DU reports disk does not need repairs quit DU and restart.
If DU reports errors Repair again and again until DU reports disk is repaired.
If DU reports errors it cannot repair you will need to use a utility like Tech Tool Pro or Disk Warrior
I recommend that you make sure that you make a bootable clone of your entire volume using a utility like SuperDuper or Carbon Copy Cloner.
You should also seriously consider installing a larger capacity drive.
cornelius

Distribution Point migration status in CM12 console

Hi,
We are using sccm 2012 r2 cu2. we are in middle of migration.
We have in sccm 2007 under secondary site server name assd1 it contain MP and DP role.
Under ASSd1 server i was created one of the distribution point server and copied all the package to the new server assd2.
I created this new distribution point last week.
Today I gathered data from sccm 2007 to sccm2012.
Previously I did the same almost 5 servers and after sccm2012 administration-->under site hierarchy--> shared distribution point it shows. after that i will migrate to sccm2012 DP
but this server not showing. but when i saw migctrl.log i can see the log
The DP assd2.xxx.org is eligible for upgrade
but not showing under administration-->under site hierarchy--> shared distribution

Issue got resolved..

Monitoring and troubleshooting in-place distribution point upgrades

I have a shared SCCM 2007 secondary site server that I'd like to upgrade to a SCCM 2012 Distribution Point. I went to the Administration>Migration>Source Hierarchy>Shared Distribution Points and right clicked and hit Upgrade and then proceeded
through the Upgrade Shared Distribution Point Wizard. Then under Administration>Migration>Distribution Point Upgrades, monitored that status, but even though I left it overnight, the status is still "Upgrade distribution point." I checked under
the Monitoring>Distribution Status>Distribution Point Configuration Status and selected the name of my distribution point and noticed that I'd forgotten to add the Site Server's computer account to the local admin group on my Distribution Point Server.
But even though I've corrected that, the status of the upgrade has not changed and there is nothing of note in resource manager indicating that the process is underway.
Are there any additional logs to monitor the progress of the in-place Distribution Point upgrade? Are there any other troubleshooting steps I can do to determine why the status of the upgrade isn't complete?

Hi all
I would like to share my experience with migrating from SCCM 2007 Distribution Points to SCCM 2012. We have in our test environment 39 secondary site systems with the role of distribution points and I wanted to play with the migration feature "Share
Distribution Point" scenario. In the night in which I had prepared the Secondary sites using the migration wizard, 30 of the 39 sites completed in approximately 3 hours with the status "Completed upgrade distribution point". On all distribution
points the same completion date was entered. It seems that a task at specific times in the background check again whether the migration is complete and the status is consolidated. The remaining 9 Distribution Points were then completed almost exactly after
12 hours.
I then inquired about the migrated packages. On the night not a single package came in the status 'Targeted'. After about 12 hours I saw at once that now at least the distribution points were recorded in most packages. The status 'Installed' but got no distribution
point. I then startet at about 10 packages an update distribution job. These then became the status of 'Installed' more than 4 hours later. Then the weekend was between and on Monday morning, no other distribution points were listed as 'Installed'. I checked
local on the distribution point, if all of the packages was converted. This was the case, not only the 10 I have updated. The packages then should be available during deployments, I think. But I have not tested it.
If you have looked at a package converted times more precise, the status of most distribution point is 'Unknown'. I then googled for this situation, and I have found this
article. There seems to be a bug which is currently in a solving process.
For me, there are two solutions for this problem:
1. Waiting for the hotfix and the problem is then solved centrally. By the fact, that we migrate the 340 Secodary Sites in 3 weeks, I don't think that this hotfix will be available.
2. Depending on the number of distribution points and packages it may be helpful if all 'targeted' packages are again updated. In this 'Unknown' status situation I simply do not know if the packages are really available or not.
I found another problem with the Distribution Point migration. Actually with the migration of SCCM 2007 Secondary Site Server to SCCM 2012 remote Distribution Point, an uninstallation of the secondary site server should be performed. We had tested this with
SCCM 2012 RTM and it was working at that time. With the update to SCCM 2012 SP1 here again seems a problem with the migration to be added. In the SCCM 2007 environment, the Secondary Site Server were removed during migration. But not local uninstalled, even
after 3 days.
Conclusion to the Distribution Point in SCCM 2012 SP1 migration:
As always, you just have to have patience until the migration jobs are completed. Certain tasks must then be carried out by hand. In my view, the missing log information is the biggest problem. Without the log information I was blind
during the migration. If you only have a short window for migration and like us, that we need to migrate 340 Secondary Site Server in the production environment, the scenario must be carefully considered. We proof now to not migrate the Secondary Sites with
the Migration Wizzard, but start from the ground up a new installation of Distribution Points followed by the necessary sync packages.
Kind regards Stefan Somogyi

Cancel Distribution Point Reassignment Greyed Out

I executed a Reassign Distribution Point to a server and by default selected D$ as the share to copy to because all of our DP servers are setup on D: EXCEPT for this particular server which has D: as the CD-ROM and E: as the shared drive which is Also used
as a file share so changing the drive letter may not be the best option. With that being said, I would like to cancel the Distribution Point Reassignment and reconfigure the properties of this particular job to use E: as the share to copy to and re-run the
reassignment however the Cancel Distribution Point Reassignment is greyed out so it seems that I am unable to cancel this process and with a lot of time spent on researching I have not found a solution for this. Please help!

Hi,
We may see the buttons grayed out when some settings are not configured properly. Please check the requirement in this article:
CEP summary – Upgrade SCCM 2007 Secondary sites and/or DP’s to SCCM 2012 DP’s
http://configmgrblog.com/2011/11/30/cep-summary-upgrade-sccm-2007-secondary-sites-andor-dps-to-sccm-2012-dps/

Reassign Shared Distribution Point - Required free space

Similar Messages

Maybe you are looking for