RE: SMS 2003 Query Software Distribution Status


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 2003 Query Software Distribution Status
    ... query is custom to begin with, I cannot use the SMS Query Design. ... advertisements, not multiple schedule times within the advertisement. ... > advertisement is going to run 3 times on all clients. ... >> Any client that was successful the first advertisement would only run once. ...
    (microsoft.public.sms.admin)
  • Rerun Advertisement does not work
    ... Has anyone else experienced a problem with getting clients to rerun a program ... where the previous attempt to run this program was not successful. ... The rerun only seems to fail if the advertisement does not have a recurrence ...
    (microsoft.public.sms.swdist)
  • RE: Rerun Advertisement does not work
    ... If you add another schedule time, only clients that Failed or did not ... > The rerun only seems to fail if the advertisement does not have a recurrence ... > happy to rerun the program on a new mandatory assignment. ...
    (microsoft.public.sms.swdist)
  • RE: SMS 2003 Query Software Distribution Status
    ... actually corresponds to my point 1 in rerunning. ... Being an advertisement that has multiple schedules. ... rerun on all systems, failed & successful alike. ... clients that failed once would then rerun the ...
    (microsoft.public.sms.admin)
  • SMS Report shows more Clients as in the Collection
    ... I created an advertisement to a query-based collection (must be adv. ... Testcollection are 49 clients but only 45 with the criteria so in the query ... based collection are only 45 clients. ...
    (microsoft.public.sms.admin)