It takes an hour to prepare GP to control Firefox. Maybe IE6 didn’t have to be distributed, but it’s easy enough to put Firefox on the image so it didn’t have to be deployed either.Ħ- It takes about 10 minutes to prepare Firefox to be deployed.

The vast majority of mainstream sites work just fine with Firefox.ĥ- IE7 is not part of XP so it still has to be deployed. Unless of course all your machines update directly from Microsoft.Ĥ- Matter of opinion. Which means IE7 needs to be deployed with another mechanism like IEAK or WSUS. Which is no different from setting up a third party patch server to update Firefox.ģ- There is no MSI for IE7. Check how many of your old plug-ins still work with Firefox 2.0 and you will know what I am talking about.ġ- As mentioned by Michael, there are third party tools.Ģ- There’s NO centralized updater for IE native to AD you separately set up a WSUS server.

Moreover, you can never be sure that these tools will still work when a new Firefox version comes out since the Firefox team does not officially support them.

However, you won't get all of them and you won't get the same ease-of-use as with IE. Of course, you can get third-party tools to supply some of the missing features in Firefox. Why would you want to manage a second browser in your network, anyway? Many desktop apps depend on the IE rendering engine, so you often have to support IE anyway.IE is part of the OS and doesn't have to be deployed, making it hard to justify the extra costs of deploying Firefox.(Firefox does not have ActiveX support, etc.) Many Web applications are designed for IE and don't work with Firefox.Firefox 2.0 does not provide official support for MSI packages.

There is no centralized patch management similar to Windows Server Update Service ( WSUS).There is no central management (no Active Directory, i.e., no Group Policy support).

Mozilla firefox version 2.0 or above