Re: Where does SMS look for software installs to report?
- From: "Garth" <Spam@xxxxxxx>
- Date: Fri, 11 May 2007 07:54:33 -0400
I'm with you Sherry, the only audit file that I know about, is the one with
SMS 1.2 so...
<sherrylkissinger@xxxxxxxxx> wrote in message
news:1178852272.068372.84110@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
"Audit file"? I'm not familiar with that term in relation to package
deployment. Perhaps if you posted the program line from the package;
i.e., if it's widgets.msi /qn or setup.exe /s Or what is the
package? Something internally created?
On May 10, 12:38 pm, P. Patel <PPa...@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:
I greaty appreciate all your suggestions. I will try your method in 2,
but I
am still interested in knowing where SMS looks to report back a package
was
successful. I was told by the package creator that I have to check the
audit
file, but all it has is "do note delete or modify this file." Is there
any
location I can check?
"sherrylkissin...@xxxxxxxxx" wrote:
I may be wrong, but it sounds like there are multiple questions here.
I interpret question #1 to be "Why does an advertisement report a
successful install, when it wasn't?" That is almost always attributed
to error-code handling. And unfortunately, there is no 1 direct
answer--it depends upon what was used in the program installation.
Was it a straight .MSI? A vbscript? a CMD or batch file? a .exe?
Since you've already sent it to such a large audience, changing the
package/program pair may be a moot point now. You may want to look at
post-install methods of determining success; like you have done, with
looking for the .exe of the application.
Question #2 is (I think) a Re-run the same package/program, even if it
was successful. There are multiple scripts or utilities available to
trigger a re-run of the same advert/package/program on a machine-by-
machine basis; but because you have such a large # of machines that
are missing the package... here's what I would do (and this is just a
suggestion, carefully evaluate whether or not this is valid for you).
I'd make a collection of the machines that are missing the
application; not machine name by machine name, but a query based
collection; something like "v_r_system.resourceid where
v_r_system.resourceid is not in (resourceid where
addremoveprograms.displayname = 'the new app') and limit that
collection query to my original collection for the original push.
That would result in the machines which were originally targetted, but
do not have the app. Then I'd make a new advertisement, same package/
program, and that advertisement would have a recurring schedule--
something that would be 1 day more than the Hardware Inventory cycle.
I.e., if your HW Inv is every 2 days, I'd have the recurring schedule
be every 3 days. So the end result would be that the advert would
run, and if successful, at their next hw inventory they'd report the
program is in Add/Remove Programs, and drop out of the collection, and
not need to have it be re-run. But as long as it continues to be
missing, it would continue to try to re-run.
Anyway--that's what I would do. And I have done similar things in the
past--there's a particular application that occasionally end users
would decide they didn't want anymore...and I just set up a recurring
ad to put it right back if it disappeared.
On May 9, 7:23 pm, P. Patel <PPa...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I'm deploying a 300MB+ package to nearly 1600 mobile stations. Most
stations
received the package fine and the entire package installed
successfully.
However, many, nearly 400 stations, report a successful installation
in the
report, but when I checked a handful of the 400 for the necessary
files to
run the program, only about 8 or 9 of the expected 28 objects
(folders &
files total) were present to the run the program properly. However,
the
report still said the ad was received and the package installed
successfully.
If that wasn't enough, I sent the backout EXE to uninstall the
originally
sent program and then trying to reinstall via another package push.
Now, the
report states that the package will not run because the prior install
was
successful, but it actually wasn't. Where does SMS look to see if the
package
was successful or not and what can I do to either clear it or delete
it so
the package can be re-pushed?- Hide quoted text -
- Show quoted text -
.
- References:
- Re: Where does SMS look for software installs to report?
- From: sherrylkissinger@xxxxxxxxx
- Re: Where does SMS look for software installs to report?
- From: P. Patel
- Re: Where does SMS look for software installs to report?
- From: sherrylkissinger@xxxxxxxxx
- Re: Where does SMS look for software installs to report?
- Prev by Date: Re: SMS reports causing lockouts
- Next by Date: SMS Collections seem to be locked.
- Previous by thread: Re: Where does SMS look for software installs to report?
- Next by thread: Re: SMS reports causing lockouts
- Index(es):
Relevant Pages
|
Loading
