RE: SMS 2003 Query Software Distribution Status

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi! Thank you for listing out the different re-run possibilities in SMS. This
reaffirms my understanding and gives a common ground to discuss what it is
that I wanted to achieve with the collection based upon failed run.

I might be over thinking this and would appreciate any further thoughts
around what I'm trying to do.

Goal: To automatically run failed events that will not re-try. To produce
reports on 1st run failures.

Solution:
Advertisement 1 is sent and fails on 15% of our systems due to advertisement
time out, program exceeded run time. The error is due to the in-house package
is "stuck". A re-run typically fixes this. The package can take up 3hrs to
run.

Advertisement 2 is sent to the advertisement failed collection with
advertisement set to run every hour. This way the advertisement will not
re-run on successful systems and will eventually install on systems that
failed due to timeout.

Thank you again!

"Kim Oppalfens" wrote:

>
> Erm, ok time to admin something, I never fully read your post, I just
> noticed you had a query you didn't get working and started searching on
> the query.
>
> Now that I see you wanted this for rerunning an advertisement I might as
> well tell you a thing or two about re-running advertisements.
>
> This is what you should know about rerunning advertisements:
>
> 1) If you add an extra assignment time to an advertisement that already
> had an assignment time (which is not ASAP, logon, or logoff). The
> advertisement reruns on all clients including the successful ones.
>
> 2) If you create a new advertisement with the exact same program to the
> same collection, the advertisement only reruns on the failed clients.
>
> 3) If you want to force an advertisement to rerun that did not have an
> assignment time to begin with on all clients (the ones that did launch
> manually and the ones that didn't). You will have to create a new
> program within the package and a new advertisement (with an assignment)
> for this program.
>
> 4) If you want to rerun on a single client, we can delete the job on an
> sms 2.0 or sms 2003 legacy client, or some reg tweak wmi
> editing on an advanced client. Corey Becht's Initiate Advanced client
> actions tool at myitforum.com can help you with this.
> http://myitforum.techtarget.com/articles/8/view.asp?id=7099
>
> So in summary, instead of going through this rather painfull
> query/collection excercise you could have perfectly created a new
> advertisement targetting the same collection with the same package &
> program. Successful clients would have noticed they already ran this
> package/program combination and not rerun it, failed clients would see
> they haven't successfully finished this package/program combination and
> would rerun.
>
> Sorry I didn't catch this sooner, my bad.
>
> Kim Oppalfens
> MVP SMS
>
> In article <3D645839-7456-4D7E-B4B6-EDDAD4BA5E10@xxxxxxxxxxxxx>,
> BrianCfromBoulder@xxxxxxxxxxxxxxxxxxxxxxxxx says...
> > Thank you! The query worked as a collection and retrieved the systems so we
> > can easily target them for a re-run.
> >
> > When I pasted the statement into the collection query, it did give me a
> > syntax error, however this seems benign as the collection still works.
> >
> > Thank you again!
> >
> > "Kim Oppalfens" wrote:
> >
> > >
> > > A collection can only contain system resources, user resources or group
> > > resources.
> > >
> > > This statement would allow you to create a collection of all systems
> > > that reported this specific status message.
> > >
> > > select
> > > SYS.ResourceID,SYS.ResourceType,SYS.Name,SYS.SMSUniqueIdentifier,SYS.Res
> > > ourceDomainORWorkgroup,SYS.Client from SMS_StatusMessage as stat left
> > > join SMS_StatMsgInsStrings as ins on stat.RecordID = ins.RecordID left
> > > join SMS_StatMsgAttributes as att1 on stat.RecordID = att1.RecordID
> > > inner join SMS_StatMsgAttributes as att2 on stat.RecordID =
> > > att2.RecordID join sms_r_system as SYS on stat.machinename = SYS.name
> > > where stat.ModuleName = "SMS Client" and stat.MessageID = 10007 and
> > > att2.AttributeID = 401 and att2.AttributeValue = "S0020001"
> > >
> > > Kim Oppalfens
> > > MVP SMS
> > > In article <553F83A6-72FA-4083-912B-7A597B0907A1@xxxxxxxxxxxxx>,
> > > BrianCfromBoulder@xxxxxxxxxxxxxxxxxxxxxxxxx says...
> > > > Thank you for your reply! Yes, the query now works as intended. Question: How
> > > > to turn this into a collection.
> > > >
> > > > When I import the query I receive a message back when I click OK indicating
> > > > "The query statement that you entered is not valid. Please enter a valid
> > > > query statement."
> > > >
> > > > How can I use the query as a collection? Can a collection only contain
> > > > System Resource?
> > > >
> > > > "Kim Oppalfens" wrote:
> > > >
> > > > > In article <6918E94F-B77B-4660-BBF9-D29203CC4CD8@xxxxxxxxxxxxx>,
> > > > > BrianCfromBoulder@xxxxxxxxxxxxxxxxxxxxxxxxx says...
> > > > > > I found a solution that sort of works for me, but I need help fine-tuning it.
> > > > > > Basically I've modified the original script down to show me systems that
> > > > > > failed, but I need to hard code the Advertisement ID so it will work in a
> > > > > > collection and not prompt.
> > > > > >
>
> --
> Kim Oppalfens
> MVP SMS
> Computacenter Belgium
>
.

Relevant Pages

  • Re: SMS Adv. Client in Workgroups - does it work?
    ... make sure you have set the Advanced Network Access Account. ... >> Advanced clients in workgroup enviornments won't be supported until SP1 ... >> Microsoft MVP - SMS ... Manually running the advertisement on the client also fails. ...
    (microsoft.public.sms.admin)
  • Re: AD Group Members and SMS 2003 Software Distribution
    ... Advanced Clients. ... check the PolicyAgent.log for references to downloading policies. ... Advertisement policies have unique IDs, ... > all the files seem to make it properly to the various SMS ...
    (microsoft.public.sms.admin)
  • SMS 2003 - How can I re-run a program occasionally on client where it has already ran succesfully?
    ... Running SMS 2003, Advanced Clients, all Windows 2000+ clients ... Is there any way to create a package / program such that it can be ... advertisement causes some other difficulties in tracking the status ...
    (microsoft.public.sms.swdist)
  • Child Site Clients not receiving Advertisement
    ... Running SMS 2003 with Advanced Client at both the parent site and child ... clients at the child site receive the advertisement...even though the package ... "SMS Offer manager successfully processed new advertisement to all XP ...
    (microsoft.public.sms.swdist)
  • Re: SMS Adv. Client in Workgroups - does it work?
    ... Advanced clients in workgroup enviornments won't be supported until SP1 is ... Microsoft MVP - SMS ... Manually running the advertisement on the client also fails. ...
    (microsoft.public.sms.admin)