Updating Versions of FireFox with SCCM

[CPSCCM]

Hi there anyweb,

 

You mentioned in one of your How-to's that you would be doing one that describes how to update software versions eg. Firefox 3.0.5 once deployed to a PC to version 3.5.0. This would be extremely useful as we have a number of internal applications that we want to deploy with SCCM and they change on a weekly basis.

 

Thanks

[anyweb]

i think you are referring to this

 

To make updating versions of Firefox easier (this will be covered later in this guide) we will rename the file from Firefox Setup 3.0.1.exe to Firefox.exe. We then copy that file to d:\sccm_packages\apps\firefox (your path may vary).

 

 

followed by this bit

 

update distribution points on a schedule

 

 

the important bit here is to set this to some value that suits your environment, once a week, once a month, whatever suits you, and.. when you get a new release of Firefox, let's say Firefox 3.0.9 you simply rename it toFirefox.exe and copy it to the Source path listed above, sccm will copy that on the pre-defined schedule and you'll have a new version of Firefox available

 

does that help ?

[CPSCCM]

Makes sense but just need clarity on one thing, for example we have a program internally called BCTT and for this case lets call it BCTT 1.0 so I will follow the same process you have defined in your article to push bctt 1.0 to all the users. Now when we have new rates the developers will give us a new program BCTT 2.0 for example and we want this now pushed to everyone as soon as they log in or as soon as possible so when they use the program they are all using the same rates. What would be the best approach for this?

 

 

i think you are referring to this

 

 

 

 

followed by this bit

 

update distribution points on a schedule

 

 

the important bit here is to set this to some value that suits your environment, once a week, once a month, whatever suits you, and.. when you get a new release of Firefox, let's say Firefox 3.0.9 you simply rename it toFirefox.exe and copy it to the Source path listed above, sccm will copy that on the pre-defined schedule and you'll have a new version of Firefox available

 

does that help ?

[Denali]

 

the important bit here is to set this to some value that suits your environment, once a week, once a month, whatever suits you, and.. when you get a new release of Firefox, let's say Firefox 3.0.9 you simply rename it toFirefox.exe and copy it to the Source path listed above, sccm will copy that on the pre-defined schedule and you'll have a new version of Firefox available

 

does that help ?

 

This method will update the package to the new version of Firefox and distribute it to new members of the collection. But other than creating a new package... How do you distribute the new version of Firefox to all the members that received Firefox from the original package?

[Peter van der Woude]

You can rerun the advertisement. See also: http://technet.microsoft.com/en-us/library/bb681010.aspx

[CPSCCM]

You can rerun the advertisement. See also: http://technet.microsoft.com/en-us/library/bb681010.aspx

 

 

Hey guys thanks for all the input, I kinda figured that I would have to re run the advertisement to get it to redistribute it to all users again. Thats what I plan to do when I start using SCCM to distribute my inhouse applications.

[CPSCCM]

Hey guys thanks for all the input, I kinda figured that I would have to re run the advertisement to get it to redistribute it to all users again. Thats what I plan to do when I start using SCCM to distribute my inhouse applications.

 

Just wondering if any of you know why I'm getting waiting for content on 4 machines I'm tesing deplyment on. I killed the package I created as per the steps described on the forum for deploying because I messed with it too much. SO i recreated everything as per the guide again and now it just sits there at "Waiting for Content"

 

Any ideas

[Peter van der Woude]

Did you distribute the package to the DP again?

[CPSCCM]

Did you distribute the package to the DP again?

 

Figured it out. I used the tool kit for the first time conencted to oone of the machines. Since I deleted a previously intalled package called Firefox 3 and recreated a new one with the same name the client thought that it already had it. So what I did was i reran the advertisement and it started redeploying it.

 

So what is everyone doing for updating versions of software? Are you guys just creating new packages and then just removing/Disabling the old one's? Maybe I should move this to the main section so I can better press on these questions?