I don't do provisioning, so this is just an educated guess:

This might be more of a hack than what you are already doing, but maybe it will give you some ideas.

(Do step 3 once first. If it turns up any matches in binary files, this approach won't work - at least, not without a lot of experimental tweaking that might have to be modified with new releases.)

1. Create a new Firefox install on another machine (which never had Firefox or other Mozilla stuff installed on it) to use as a template.

Don't do anything else to it that you don't want all users to have. Make sure there's nothing "interesting" in any of the other directories under $HOME/.mozilla - like bits from other apps and that only the one new user profile has been created under $HOME/.mozilla/firefox.

Copy $HOME/.mozilla (using cp -a, etc.) as a template (MT for short).

2. On each new machine, install MT as $HOME/.mozilla (Make sure the new files are owned by the current user and group.) This will give each user the same profile name random-string.default. If you want to, you can rename it to anything else you like as long as you also change the entry in profile.ini that points to it.

3. This might work as is. I can't tell because my profile is old with a lot of modifications. Just to make sure:

   grep -rl template-user-name * | less

in the profile sub-directory tree. (You only do the less part once. It will either always or never be an issue.)

If it comes up empty, you're done. If not:

4. Take the output from the above grep (making sure it ends up with full relative paths in it) and use it to loop across all those files using sed -i (or a similar tool) to replace template-user-name with the current user name wherever it occurs.

This should be OK as long as it doesn't turn up any matches in binary files. With binary files, all bets are off.

HTH

I don't do provisioning, so this is just an educated guess:

This might be more of a hack than what you are already doing, but maybe it will give you some ideas.

(Do step 3 once first. If it turns up any matches in binary files, this approach won't work - at least, not without a lot of experimental tweaking that might have to be modified with new releases.)

1. Create a new Firefox install on another machine (which never had Firefox or other Mozilla stuff installed on it) to use as a template.

Don't do anything else to it that you don't want all users to have. Make sure there's nothing "interesting" in any of the other directories under $HOME/.mozilla - like bits from other apps and that only the one new user profile has been created under $HOME/.mozilla/firefox.

Copy $HOME/.mozilla (using cp -a, etc.) as a template (MT for short).

2. On each new machine, install MT as $HOME/.mozilla (Make sure the new files are owned by the current user and group.) This will give each user the same profile name random-string.default. If you want to, you can rename it to anything else you like as long as you also change the entry in profile.ini that points to it.

3. This might work as is. I can't tell because my profile is old with a lot of modifications. Just to make sure:

   grep -rl template-user-home-directory * | less

in the profile sub-directory tree. (You only do the less part once. It will either always or never be an issue. Replace template-user-home-directory with the actual path of the user directory on the original machine.)

If it comes up empty, you're done. If not:

4. Take the output from the above grep (making sure it ends up with full relative paths in it) and use it to loop across all those files using sed -i (or a similar tool) to replace template-user-home-directory with the current user home directory wherever it occurs.

This should be OK as long as it doesn't turn up any matches in binary files. With binary files, all bets are off.

HTH

I don't do provisioning, so this is just an educated guess:

This might be more of a hack than what you are already doing, but maybe it will give you some ideas.

(Do step 3 once first. If it turns up any matches in binary files, this approach won't work - at least, not without a lot of experimental tweaking that might have to be modified with new releases.)

1. Create a new Firefox install on another machine (which never had Firefox or other Mozilla stuff installed on it) to use as a template.

Don't do anything else to it that you don't want all users to have. Make sure there's nothing "interesting" in any of the other directories under $HOME/.mozilla - like bits from other apps and that only the one new user profile has been created under $HOME/.mozilla/firefox.

Copy $HOME/.mozilla (using cp -a, etc.) as a template (MT for short). (Make sure the new files are owned by the current user and group.)

2. On each new machine, install MT as $HOME/.mozilla This will give each user the same profile name random-string.default. If you want to, you can rename it to anything else you like as long as you also change the entry in profile.ini that points to it.

3. This might work as is. I can't tell because my profile is old with a lot of modifications. Just to make sure:

   grep -rl template-user-name * | less

in the profile sub-directory tree. (You only do the less part once. It will either always or never be an issue.)

If it comes up empty, you're done. If not:

4. Take the output from the above grep (making sure it ends up with full relative paths in it) and use it to loop across all those files using sed -i (or a similar tool) to replace template-user-name with the current user name wherever it occurs.

This should be OK as long as it doesn't turn up any matches in binary files. With binary files, all bets are off.

HTH

I don't do provisioning, so this is just an educated guess:

This might be more of a hack than what you are already doing, but maybe it will give you some ideas.

(Do step 3 once first. If it turns up any matches in binary files, this approach won't work - at least, not without a lot of experimental tweaking that might have to be modified with new releases.)

1. Create a new Firefox install on another machine (which never had Firefox or other Mozilla stuff installed on it) to use as a template.

Don't do anything else to it that you don't want all users to have. Make sure there's nothing "interesting" in any of the other directories under $HOME/.mozilla - like bits from other apps and that only the one new user profile has been created under $HOME/.mozilla/firefox.

Copy $HOME/.mozilla (using cp -a, etc.) as a template (MT for short).

2. On each new machine, install MT as $HOME/.mozilla (Make sure the new files are owned by the current user and group.) This will give each user the same profile name random-string.default. If you want to, you can rename it to anything else you like as long as you also change the entry in profile.ini that points to it.

3. This might work as is. I can't tell because my profile is old with a lot of modifications. Just to make sure:

   grep -rl template-user-name * | less

in the profile sub-directory tree. (You only do the less part once. It will either always or never be an issue.)

If it comes up empty, you're done. If not:

4. Take the output from the above grep (making sure it ends up with full relative paths in it) and use it to loop across all those files using sed -i (or a similar tool) to replace template-user-name with the current user name wherever it occurs.

This should be OK as long as it doesn't turn up any matches in binary files. With binary files, all bets are off.

HTH