Keeping Up with Distribution Points-SysManSquad | Systems Management Squad

[utterances-bot]

Keeping Up with Distribution Points-SysManSquad | Systems Management Squad

A community blog and subsidiary of WinAdmins.io

https://sysmansquad.com/2021/02/17/keeping-up-with-distribution-points/

[cheesebox]

Brett, thank you for this article. It's helped me greatly in my research of setting up Pull DP's and maintaining content library health. I thought you may want to know, we had an issue with your content reconciliation script. It seems once the content validation cycle completes and it issues its "2386" MessageID, there can be a delay before the site database gets updated with the content validation messages (over 50 seconds in our case). If the reconciliation script runs before the database is updated, it will determine that none of the packages on the DP were validated successfully. In our case that meant over 1400 packages were redistributed to the DP, which took several days to complete. I've made some amendments to the script so it checks the database is ready before continuing. I'm happy to share, if you're interested.

[BirdyBA]

Cheesebox, I'm interested in your improved script. Please can you share it. Thanks in advance!

[cheesebox]

Hi Brett

I've attached the updated Content Reconciliation script, as well as a sample log.

The main addition is the function "$dbReadinessCheck" which checks whether the 2384 and 2386 messages have been written to the site database. It will retry a number of times (defined by $MaxCount) and will only refresh packages once the database has been updated.

I don't know if the database issue is unique to us. It may be due to the size of the environment - we have over 50,000 endpoints, and the site database is hosted on a different server to the primary server, both of which might contribute to some latency in database transactions.

All the best

Piers PackageReconciliation.txt PkgRec_MyDP.fabricam.com_2024-03-01-22-29-15.log