search

MicrosoftDocs / SCCMdocs

Configuration Manager documentation public repo
https://docs.microsoft.com/sccm/
Creative Commons Attribution 4.0 International
251 stars 361 forks source link

Reassign a distribution point to a Secondary Site #1677

Closed AlexCesarini closed 4 years ago

AlexCesarini commented 5 years ago

I understand the Reassignment of the DP has only been tested with Primary sites, although the UI allows reassignments to secondary sites as well and I've done several tests and it worked ok, in my environments. Is there any known reason why it should not work for secondary sites as well?

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

aczechowski commented 5 years ago

Thanks @AlexCesarini for the feedback. Sorry if you got that impression, we do test and support moving DP from Primary to Primary and Secondary to Primary. We've also tested Primary to Secondary although that’s probably the least used path.

ChrisKibble commented 5 years ago

Do we think this needs to be called out specifically in the doc? "Starting in version 1802, this feature lets you reassign a distribution point from a primary or secondary site to another primary or secondary site without redistributing the content." perhaps?

AlexCesarini commented 5 years ago

That would be perfect IMHO, I know of several customers that did not use it on secondary sites because it was not documented.

Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Chris Kibble notifications@github.com Sent: Tuesday, July 2, 2019 10:20:53 PM To: MicrosoftDocs/SCCMdocs Cc: AlexCesarini; Mention Subject: Re: [MicrosoftDocs/SCCMdocs] Reassign a distribution point to a Secondary Site (#1677)

Do we think this needs to be called out specifically in the doc? "Starting in version 1802, this feature lets you reassign a distribution point from a primary or secondary site to another primary or secondary site without redistributing the content." perhaps?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/SCCMdocs/issues/1677?email_source=notifications&email_token=AIXQ74QAMYVTNUU2R2ZUUKTP5PBDLA5CNFSM4H4D55X2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZCSSYI#issuecomment-507849057, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIXQ74Q72YQC7EAROZWCUETP5PBDLANCNFSM4H4D55XQ.

aczechowski commented 5 years ago

Thanks @ChrisKibble for the suggestion. Perhaps divide into two sentences for simplicity:

Starting in version 1802, this feature lets you reassign a distribution point to another site without redistributing the content. The target and destination sites can be either a primary or secondary site.

Anoni-Mouse commented 1 year ago

Hi I have issues with this. We are in the process to flatten our SCCM infrastructure by removing the secondary sites and replace them by distribution points and when necessary MP as well. We have a remote secondary site and a DP assigned to this secondary site. From SCCM console, when I try to reassign the DP to my primary site, I get the following error

** [42000][50000][Microsoft][SQL Server Native Client 11.0][SQL Server]Error! Failed to update sql data for reassign distribution point. : spMoveDistributionPoint***

There are no other roles installed on the server other than the DP role. I also have checked this query and fortunately I have no records:

SELECT * FROM DistributionContentVersion DCV LEFT JOIN DistributionPoints DP ON DP.NALPath = DCV.DPNALPath WHERE DCV.SiteCode <> DP.SMSSiteCode

Still I do not understand what the issue really is!

From SQL, I tried to run this:

EXEC spMoveDistributionPoint 'PRI', '["Display=\FQDN"]MSWNET:["SMS_SITE=SS1"]\FQDN'

But I got the following error

Msg 50000, Level 16, State 1, Procedure spMoveDistributionPoint, Line 321 [Batch Start Line 7]

Error! Failed to update sql data for reassign distribution point.

I have looked at tons of other articles on the web, but none solved my issue

EDIT: We solved the issue by removing the content from that DP. Only when we removed the content we could successfully reassign the DP. Afterwards we distributed the content and now it is working. So this means the first query isn't enough and there is some other part of the database that has to be queried to figure out if there are issues or not.