Incorrect Policy Versions from MP

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

Incorrect Policy Versions from MP

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> Microsoft Systems Management Server >> SMS 2003 >> Incorrect Policy Versions from MP

Page: [1]

Message

<< Older Topic Newer Topic >>

Incorrect Policy Versions from MP - 7/30/2008 3:51:34 PM

jrider

Posts: 2
Score: 0
Joined: 7/30/2008
Status: offline

We are currently having an issue where a MP (and the secondary site MP's that use the same Site DB) is handing out the incorrect version of a policy and the clients in turn are trying to download a previous source version of the software which then aborts because the DP has the most recent version. Using MP Spy i can see that it has the incorrect PolicyVersion comparing against known working sites. I can also see in the SQL Database where it has the incorrect information.

Is there any way to trigger SMS to update its policy information on this site?

Things we have tried:
Restarted MP & Primary SMS Services
Re-Installed MP
Re-Created Senders/Addresses

Thanks

Post #: 1

RE: Incorrect Policy Versions from MP - 7/30/2008 4:32:27 PM

skissinger

Posts: 2110
Score: 134
Joined: 9/13/2001
From: Sherry Kissinger
Status: offline

The easiest thing to try first is "Update all Distribution Points" for that 1 package. Note: not a refresh. That'll trigger a new version for every DP, including the wrong ones.

_____________________________

mofmaster@smsexpert.com (version 2007) | http://www.smsexpert.com | http://www.sccmexpert.com
My Blog
Microsoft MVP - ConfigMgr

(in reply to jrider)

Post #: 2

RE: Incorrect Policy Versions from MP - 7/30/2008 5:00:07 PM

jrider

Posts: 2
Score: 0
Joined: 7/30/2008
Status: offline

Thanks for the quick reply!

We ended up solving it by disabling the advertisement, waiting about 10 minutes or so and then re-enabling it. This seemed to force an increment (2 times due to disable & enable) in the policy version and replication to the sites.

One thing to note however, the Version in the SQL DB for the Policy table is not the same as what is on the central site and I was informed that it doesn't necesarily have to be the same that it is just an independent version for that instance on that site and as long as the data returned is the same then all is well.

(in reply to skissinger)

Post #: 3