Pushing Updates Out

[Scott]

I'm looking for a good way to *push* updates out. Web Updates, BITS,
and ClickOnce all seem to be based on the client *pulling* updates.
With our applications we normally have to deploy updates to the
database, business tier, and applications in sync. IOW, once the
database is updated I must ensure the old mid tier and application
versions are shut down until the database is updated, mid tiers
updated, and then the apps can be restarted.

I know there's probably not a prebuilt solution to handle the complete
scenario, but here's what I envision. I'd like to have a central
command center that allows me to see where all of my mid tiers and
applications are installed and let me know if they're currently being
used. If the applications are being used, I can send the user a message
or even close the app at some point. After everything is properly shut
down, I push the updates to the mid tier and application machines.

This would allow us to deploy our updates with just a few folks instead
of 10+.

Any thoughts on the best way to proceed with such a tool?

Scott C.

 

[Brock Allen]

You might want to look into Microsoft's SMS product.

-Brock
DevelopMentor
http://staff.develop.com/ballen

 

[Scott]

You might want to look into Microsoft's SMS product.

Thanks Brock. I've heard of SMS, but never used it. My impression is
that SMS isn't really portable. I want something that we could take
with us from site to site. Some of our customers may already have SMS,
but I'm not sure and don't want to require them to buy another piece of
software.

Scott C.

 

[Scott]

don't want to require them to buy another piece of software.

....unless it's from us. <g>

Scott C.

 

[StealthyMark]

If you are using an Windows 2000+ active directory server, you can specify
required software installation packages in the group policies. Sounds
perfect for your job.

Mark