Re: Incorrect Package Status
- From: "Scott Brimley [MSFT]" <scottbr@xxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 31 Mar 2005 11:19:55 -0800
You can force a refresh by going to that package in the MMC and clicking on
Distribution Points. Then right click on your problem server and choose
"All Tasks" then "Refresh Distribution Point". This will cause the source
to be copied to that distribution server again and the status messages that
go with that.
To force the same thing for all of them right click on "Distribution Points"
and choose "Update Distribution Points". This will increase the version
number of the source, but that is generally not a big deal unless people are
running the software right now.
--
Thanks
Scott Brimley [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
Additional Resources:
SMS 2.0 Resource Page:
http://www.microsoft.com/technet/prodtechnol/sms/sms2/default.mspx
SMS 2003 Resource Page:
http://www.microsoft.com/technet/prodtechnol/sms/sms2003/default.mspx
SMS 2003 Technical FAQ:
http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/default.mspx
"Jose Holguin" <JoseHolguin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:FBBC935B-C9B9-4AF3-ADFD-B4F5C45FF975@xxxxxxxxxxxxxxxx
> Hi,
> My SMS 2003 Primary Site is reporting in the Package Status that a Package
> is not installed in some of my Secondary Child Distribution Points
> eventhough
> it is there. How can I force an update of the status?
> Thanks,
> Jose
>
>
.
- Prev by Date: Re: Duplicate GUID problem with newuid.exe package
- Next by Date: Re: Download program from a remote distribution point isn't always detected
- Previous by thread: Package Dist. Errors 11203 and 1007
- Next by thread: Re: Download program from a remote distribution point isn't always detected
- Index(es):
Relevant Pages
|