Here is a scup catalog I've been looking at for a client:
http://patchmypc.net/scup

$1.00 per machine (managed with sccm) per year.

Christopher Catlett
Consultant | Detroit


Sogeti USA
Office 248-876-9738 |Fax 877.406.9647 
26957 Northwestern Highway, Suite 130, Southfield, MI 48033-8456
www.us.sogeti.com

-----Original Message-----
From: [email protected] [mailto:[email protected]] On 
Behalf Of Kent, Mark
Sent: Monday, December 02, 2013 10:13 AM
To: [email protected]
Subject: RE: [mssms] RE: Managing applications

Thinking about that for sure.

Mark Kent (MCP)
Sr. Desktop Systems Engineer
Computing & Technology Services - SUNY Buffalo State

-----Original Message-----
From: [email protected] [mailto:[email protected]] On 
Behalf Of Nick Moseley
Sent: Wednesday, November 27, 2013 1:20 PM
To: [email protected]
Subject: RE: [mssms] RE: Managing applications

You may want to look at SCUPdates
http://www.shavlik.com/products/scupdates/datasheet/ 


-----Original Message-----
From: [email protected] [mailto:[email protected]]
On Behalf Of William Jackson
Sent: Wednesday, November 27, 2013 11:15 AM
To: [email protected]
Subject: [mssms] RE: Managing applications

> I am looking for a little feedback/guidance in regards to managing 
> applications that update frequently, using the new App model.

I create a new application for each new version.

For example, when a new version of Firefox comes out, I copy the source files 
for the previous version and replace what needs replacing to accommodate the 
new installer. In SCCM I copy the application for the previous version and edit 
the copy, changing anything that needs changing -- version number, source 
directory, detection methods, &c. I include the version number in the 
application name, but I leave it out of the display name for the Application 
Catalog.

I make the new version supersede the old version. I delete deployments for the 
old version and deploy the new version. I update any task sequences that were 
installing the old version to install the new version (I can imagine this would 
suck if you had more than a few task sequences that install applications).

Your specific example of Google Chrome is actually an exception for me.
Chrome's auto-updating works so well that I don't bother making a new 
application for it unless I don't have anything else to do. I don't even know 
what the current version of Chrome is these days, and the MSI version number 
does not match the browser version number anyway.

In contrast, I can probably rattle off the current versions of Firefox, Flash, 
Java, and Adobe Reader without looking. These are the applications I package 
the most.

William

















Reply via email to