Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 829842 - Last Review: October 27, 2006 - Revision: 1.2
Systems Management Server 2003 Distribution Point Retains an Earlier Version of a Compressed Package
A Microsoft Systems Management Server 2003 (SMS 2003) distribution point retains an earlier version of a compressed package after you change the source files and redistribute the updated version of the package.
This behavior is caused when you perform the following steps in the order that they are presented:
- You create a package, and then click Use a compressed copy of the source directory on the Data Access tab in the Package Properties dialog box.
- The package is removed from the distribution point in the child site.
- You make changes in the package source directory.
- You then add the distribution point in the child site to the package.
Whenever you make changes to the package source files, the distribution points must be updated so that all the distribution points receive the updated copy of the compressed package.
To work around this behavior, you must update the distribution points. To do so, follow these steps:
- Click Start, point to Systems Management Server, and then click SMS Administrator Console.
- In the SMS Administrator Console, expand Site Database, expand Packages, and then expand the package that you want to update.
- Under the package name, right-click Distribution Points, click All Tasks, and then click Update Distribution Points.
This behavior may also occur when you click the
Always obtain files from source directory option on the
Data Access tab in the
Package Properties dialog box. When you add a distribution point to the package, the package will always copy from the source files directory. However, this is not the case when you add a distribution point in the child site. If you add a distribution point in the child site, a compressed copy of the package may be sent because child sites may not have access to the package source or because they may be connecting over a slow link. If you do not update the package correctly, the child site may still retain a compressed image of the old package. To update the child site, you must follow the steps that are described in the "Workaround" section of this article.
This behavior is by design.
APPLIES TO
- Microsoft Systems Management Server 2003
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