FM Firefox CE 6.0.2 en US, first run page error
Testing the new package for FM Firefox CE 6.0.2 and when the browser is opened for the first time after updating, it directs me to http://www.mozilla.org/en-US/projects/f ... /firstrun/ which displays a clever Mozilla 404: Page Not Found page.
Re: FM Firefox CE 6.0.2 en US, first run page error
The URL has an extra "projects" section which shouldn't be there. I just checked in the en-US standard and community Frontmotion editions and this is only happening in the community edition. DraconPern will need to fix the MSI.
If you need to deploy right now you can do an administrative install and edit the Program Files\Mozilla Firefox\defaults\pref\firefox-branding.js file and remove the extraneous "projects" from the incorrectly set preferences in the file.
If you need to deploy right now you can do an administrative install and edit the Program Files\Mozilla Firefox\defaults\pref\firefox-branding.js file and remove the extraneous "projects" from the incorrectly set preferences in the file.
Re: FM Firefox CE 6.0.2 en US, first run page error
Thanks, jpa.
I normally just assign the msi for deployment through a GPO but figured I'd give the administrative install a try. However, I encountered an error code 2203 during the install. Anyone else encounter this?
I normally just assign the msi for deployment through a GPO but figured I'd give the administrative install a try. However, I encountered an error code 2203 during the install. Anyone else encounter this?
Re: FM Firefox CE 6.0.2 en US, first run page error
How are you doing the admin install? I can force that error by setting the admin installation directory to the same directory the MSI is located in. For example: MSI in C:\Temp and select C:\Temp as the admin install "Enter a new network location" directory.
If it's not that then you can write an MSIEXEC install log and see what it says.
If it's not that then you can write an MSIEXEC install log and see what it says.
Re: FM Firefox CE 6.0.2 en US, first run page error
That is how I was doing it, setting the admin install to the same directory where the MSI is located. Didn't realize that would cause an issue. I will try it in a separate directory. Thanks!