I created a package and set the primary site and 1 secondary site as distribution points. All was fine through 4 updates. The primary site refreshes package version within 5 minutes, but the secondary site has listed the package at version 4 and in an install pending state for the past week. Any ideas on what may be going on here?
I tried both pulling the source files from a UNC name and compressing and including them in the package. Also, this package is just a few reg edits so it's not pulling a lot of data.
SMS 2.0 SP3, primary site is W2K, secondary site is NT4.
I tried both pulling the source files from a UNC name and compressing and including them in the package. Also, this package is just a few reg edits so it's not pulling a lot of data.
SMS 2.0 SP3, primary site is W2K, secondary site is NT4.