Re: Reocurring schedules

From: Shehzad Khoja [MSFT] (srkhoja_at_online.microsoft.com)
Date: 02/25/05


Date: Fri, 25 Feb 2005 08:16:29 -0800

No. That is not what I am saying. For patches, the story is different. If
you schedule PatchInstall.exe or ScanWrapper to run every day then it will
run every day but it will only install patches that are not already
installed. If this is not happening then someone on
microsoft.public.sms.software_updates news group will be able to help you.
That news group is specifically for questions\issue specific to Software
Updates Management.

-- 
This posting is provided "AS IS" with no warranties, and confers no rights.
"shinabl" <shinabl@discussions.microsoft.com> wrote in message 
news:DBC4AE3F-1040-4DEB-AB54-BC06C47F4B2D@microsoft.com...
>I agree with ktp and just want to make sure I completely understand this. 
>I
> have a horde of patches that are being pushed to my workstation 
> collection.
> What I'm seeing is this: every day @ 9:00am some people are complaining 
> that
> their computers slow down.  When I used the software distribution
> troubleshooting tool, sure enough, patches that were ALREADY installed are
> running yet again!  Your saying there is NO way to tell the SMS client 
> "look,
> if the patch is there, just ignore this?".  Please let me know, this seems
> like a flaw to me.
>
>
> "ktp" wrote:
>
>> I don't doubt its usefulness, but there should be an option to "ignore if
>> already installed" ....  that would make a lot of sense in my opinion.
>>
>>
>> "Shehzad Khoja [MSFT]" wrote:
>>
>> > It may not be useful in your environment but it is definitely useful 
>> > for
>> > some of our other customers. Like a retail store can use daily 
>> > schedules to
>> > run a program which updates the inventory in their store or updates the
>> > price of each item for next day.
>> >
>> > Another example would be to run a tool which updates your anti-virus
>> > software...
>> >
>> > These are just few examples...
>> >
>> > -- 
>> > This posting is provided "AS IS" with no warranties, and confers no 
>> > rights.
>> >
>> >
>> > "ktp" <ktp@discussions.microsoft.com> wrote in message
>> > news:B9465B1F-DC75-418A-9E0F-0E9C54DF0CB8@microsoft.com...
>> > >I still think that is useless.   Why install a program twice?  How 
>> > >useful
>> > >is
>> > > it to install the same application, on a daily schedule?   Might be 
>> > > useful
>> > > for triggering scripts and such, but it sure makes software 
>> > > distribution
>> > > messy.
>> > >
>> > > "Shehzad Khoja [MSFT]" wrote:
>> > >
>> > >> If client misses the schedule then SMS will run the program next 
>> > >> time
>> > >> client
>> > >> gets on line. SMS doesn't forget to run a program if it was suppose 
>> > >> to
>> > >> run
>> > >> at 9 PM but machine was not shutdown at 9. SMS will run the program, 
>> > >> it
>> > >> missed to run next time machine restarts. If program failed and 
>> > >> failed
>> > >> with
>> > >> an error code which is not considered to be a non-fatal\retryable 
>> > >> error
>> > >> code
>> > >> then SMS will not re-run the program.
>> > >>
>> > >> List of these error codes are stored in SCF and you can add an error 
>> > >> code
>> > >> if
>> > >> you want SMS to retry on a particular error code it receives.
>> > >
>> > > What is SCF?
>> > >
>> > >>
>> > >> -- 
>> > >> This posting is provided "AS IS" with no warranties, and confers no
>> > >> rights.
>> > >>
>> > >>
>> > >> "ktp" <ktp@discussions.microsoft.com> wrote in message
>> > >> news:50D54992-25F8-42E4-83BA-D35B37A5E774@microsoft.com...
>> > >> >
>> > >> > Why does SMS continously install packages that have re-ocurring
>> > >> > advertisements?  I mean, shouldn't the client a) receive the
>> > >> > advertisement
>> > >> > again, then  b) check if the package was previously installed, and 
>> > >> > then
>> > >> > silently ignore it if it was?    This doesn't seem to be the case, 
>> > >> > it
>> > >> > just
>> > >> > installs, and install and installs the package.  IMO this a 
>> > >> > weakness in
>> > >> > SMS.
>> > >> >  Half the time clients seem to miss or fail the installs, and if 
>> > >> > they
>> > >> > are
>> > >> > set to install immediately (not occuring or schedule based) it 
>> > >> > will not
>> > >> > try
>> > >> > again, unless you make it re-occuring.   Seems like a catch 22 to 
>> > >> > me.
>> > >> >
>> > >> >
>> > >> >
>> > >> >
>> > >>
>> > >>
>> > >>
>> >
>> >
>> > 


Relevant Pages

  • Re: Reocurring schedules
    ... in SMS Software Distribution. ... >> Scenario where SMS will what we call 'merge' the schedule is if there are ... >>> There is a list of error codes which SMS considers as non-fatal error ... Why does SMS continously install packages that have re-ocurring ...
    (microsoft.public.sms.swdist)
  • Re: Patch push programs for Win2K domain world?
    ... install it on a domain controller, but you can install it on other servers ... files for patches and service packs of all kinds. ... > - Cannot find a reliable way to query a host or the controller itself for ... > - When scheduled for deployment, it sometimes took UE a few hours to push ...
    (microsoft.public.win2000.security)
  • Re: Activation problem with Office 2003
    ... necessity of those ubiquitous MS patches, patches to the patches and the ... the install and PFFFTTTT! ... into SafeMode, roll back using ERUNT, Recovery Mode, Repair Mode, etc., ... Either the conversion needs to be tweaked until ...
    (microsoft.public.office.misc)
  • Re: MS03-026 - are you patched? Windows Update isnt sure!
    ... registry checks to determine if a patch is installed on a given machine. ... Many patches install a registry key to indicate that they have been ...
    (NT-Bugtraq)
  • Re: [Full-Disclosure] MS Anti Virus?
    ... > running the firewall it shouldn't be an issue. ... you would only supposedly have new bugs in the latest revisions. ... >> had patches well in advance of the worm that impacted it, blaster, ... > If you install windows and attempt to either patch it or install firewall ...
    (Full-Disclosure)

Loading