Re: Challenge in software distribution
- From: "Rune Norberg" <runeno@xxxxxxxxxxxxxxxx>
- Date: Tue, 1 May 2007 00:30:54 +0200
It was something like what you are doing I was thinking of, but was kind of hoping to avoid as I have a couple of tousand objects defined already, and was hoping to avoid doubling those....
Anyway - thanks for the feedback.
/Rune
<sherrylkissinger@xxxxxxxxx> wrote in message news:1177847765.562235.54910@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Managing upgrades can be tricky; I'll tell you how we usually do it.
Whether or not this is the best way is debatable. Based on your
scenario, not everyone will have this application, correct? So some
people have App v1 already installed; but most don't. We approach
this with 1 package, 2 programs, 2 ads, and 2 collections for App v2.
One Ad/Program pair is for new installations of App v2, is an optional
advertisement. The other Ad/Program pair is for upgrades from v1 to
v2, and it is mandatory; where the target is a collection of machines;
and the query criteria for that collection is "all machines reporting
App v1". Since it's a query, eventually that collection will be empty
(because they will all get upgraded to the new version). At that
point, we expire the ad for a few months, and then we do cleanup of
obsolete ads. Since we do not have a lot of mobile, rarely-connect-to-
the-network laptops, we can usually get through upgrades within a week
or two (those pesky people on vacation always extend our deployment
time!)
On Apr 28, 7:20 pm, Matthew Hudson
<MatthewHud...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I don't know if this helps but when I this problem the application had a
switch to perform an upgrade. So I wrote a vbscript that looked for the
Registry entry. If it was there it did the /upgrade switch. It is wasn't
then it ran it without the switch. Without alittle more informaiton on the
switches or how the applications function I don't think I could offer any
more than this. I hope it helps on some level
--
-----------------------http://sms-hints-tricks.blogspot.com/
"Rune Norberg" wrote:
> Hi there
> I'm facing a scenario where I want users to be able to install > applications
> of their choise from Run Advertised Programs. Now - there challenge > comes
> when one of these programs is distributed in a new version. Obviously I > want
> to force upgrade on clients that already has installed the application, > but
> I still want it to be available from Run Advertised Programs for those > who
> didn't install the first version.
> Using core SMS functionality I see no other way of doing this than > creating
> 2 different collections (initial distribution + already installed > clients),
> and then use 2 different advertisements for those collections (not > mandatory
> vs. mandatory assignment). But this requires some duplicate work in > SMS, it
> doubles some of the objects and the detection mechanism must be done in > eash
> case (although for most it's must somehow be determined based on > Addd/Remove
> programs). Given a large number of applications I really don't wan't to > do
> this if I can avoid it.
> I've also been thinking about creating an local wrapper on the client > that
> recoqnizes if the advertisement was invoked by the user(install) or is
> running on an mandatory assignment (ie. upgrade if installed otherwize > do
> nothing). But that require some development, and I'm not even sure if > this
> can be done.
> So, I'm wondring if anybody has done/implemented such an solution and > can
> share some info and experiences?
> Rgds,
> Rune- Hide quoted text -
- Show quoted text -
.
- Next by Date: W2K3 SP2 Deployment Question ???
- Next by thread: Re: Challenge in software distribution
- Index(es):
Relevant Pages
|
