Microsoft Knowledge Base Email Alertz

(829837) - When you configure Microsoft Systems Management Server (SMS) 2003 to use package IDs that packages have used before, the SMS 2003 clients may not download and cache the new package.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 829837 - Last Review: October 27, 2006 - Revision: 1.2

Systems Management Server 2003 Clients Do Not Cache a New Package When You Reuse Older Package IDs

SYMPTOMS

When you configure Microsoft Systems Management Server (SMS) 2003 to use package IDs that packages have used before, the SMS 2003 clients may not download and cache the new package.

CAUSE

This problem may occur if the new package ID matches an older package ID that is still contained in the SMS 2003 client's cache. The cache content is from the old package, not the current package. The cache can indefinitely retain package IDs that were downloaded to the client if no additional cache space is required. As a result, the SMS 2003 clients have a package ID mismatch.

WORKAROUND

To work around this problem, empty the cache on the SMS 2003 client. To do so, use the following example VBscript code:
Set oUIResource = CreateObject("UIResource.UIResourceMgr")

    Set objCacheInfo = oUIResource.GetCacheInfo

    sTempLocation = objCacheInfo.Location

    objCacheInfo.Location = "c:\"

    objCacheInfo.Location = sTempLocation

APPLIES TO
  • Microsoft Systems Management Server 2003
Keywords: 
kbprb KB829837
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate