Re: auto-updater




"Steve Zimmelman" <skz@xxxxxxxxxxxxxxxxxx> wrote in message
news:46af7f4c$1@xxxxxxxxxxxxxxxxxxxxxxxxx
In the world I live in, we absolutely do NOT want users making the
decision to update or not. Updates are mandatory and must install
seamlessly without user intervention. In a commercial app I wouldn't
execute the update process this way. But this is an internal corporate
application that must have everyone using the same version.

-Steve-


Geez! I wish we could enforce the same policy. The university world is a
little different than the corporate world. We have applications that are
considered mission critical spread across over 50 departments and schools.
Each school and, to a lesser extent, each department within those schools
and major divisions function very independently -- very much like medieval
fiefdoms. For the well-funded, larger departments with their own internal
IT staffs, update policies and where apps are installed are determined
locally. For example, the School of Arts and Sciences serves most of their
applications from a cluster of Citrix servers. They try and avoid touching
individual work stations as much as possible since they're spread all over
campus. For them, we can't allow the update process to even run since the
individual user has no authority to update the copy of the app on the Citrix
box. Some departments serve our applications from Novell file servers and
we don't really want an auto-update process running their either.
Fortunately, the bulk of our 500+ users have the applications installed on
their work stations so we only have a few exceptions we really have to deal
with.

For us, TMS' TWebUpdate has worked out very well. We've even got it working
pretty well with Vista by including an XP Manifest in the application that
requests privilege elevation at start-up. I'm probably going to need to
look more closely at how our apps work on Vista before Vista becomes
widespread on campus.

Ray Porter


.



Relevant Pages

  • Re: VFP9 SP2 on SP1 runtimes?
    ... I have an app that uses that type of update process. ... Just don't install into the program files folder I find that the update routine works just fine under Vista, both 32 and 64 bit flavors. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: ClickOnce Nightmares
    ... your app need to install the settings. ... LAN) you could create a logon script that will automatically install the ... DownloadOptions options, ServerInformation& serverInformation) ... FileAccess access, Boolean asyncHint) ...
    (microsoft.public.dotnet.framework)
  • Re: Saving Back-End Data As mdf
    ... complete code of a VB.NET console app. ... It's just an example to illustrate how a connection string is used. ... so it doesn't appear to be a problem with how or what I install. ... you access to the Microsoft Office Online Beta site'. ...
    (microsoft.public.access.formscoding)
  • Re: Run 10.20 App on 11.00 ?
    ... installed on both machines using the vendor's install scripts. ... > if the app links in libc.a then you basically up the creek because you have ... Use chatr to see what the dependent libraries are. ... an industrial control system made by Fisher Control Systems. ...
    (comp.sys.hp.hpux)
  • Re: Windows XP auto updates stinks!!
    ... just use one exploit whereas you have to test all patches. ... you needn't install them. ... so I ignore any updates to it. ... you install an incompatible app ...
    (microsoft.public.windowsxp.general)