Managing policies.json in larger company
I haven't found any information about policies.json in context of mass deploying it over the network. In my case we don't have GPO available so policies.json would be nice but how to centralize this feature instead of placing it in every PC one by one ??? Can it be shared via UNC so changes can affect all that use it?
Chosen solution
Yeah, in your scenario I think you're better off just using the symlink idea.
Read this answer in context 👍 1All Replies (7)
Policies.json is designed to be per Firefox install, so there's no built in way to do this.
You could use a symbolic link to map the file to something on a remote server:
https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/mklink https://sourcedaddy.com/windows-7/how-to-create-symbolic-links-to-shared-folders.html
Do you use any software to handle deployments/customizations on your clients?
Thanks for the reply.
We don't have any deployment tools. We did have FOG but it kinda failed. I was thinking about PSTools but there are many subnets as well as IP's do change frequently. I was thinking yesterday about sym links.
Maybe I'll just bite the bullet and place the symbolic link on each PC and every new PC will have it on board.
Sorry I don't have a better answer.
Another think I thought of was you could do a .reg file with the policies but users would have to click and install.
Policies in the registry is an interesting idea. Could be useful for fresh installs. Although sym link could be better idea for more dynamic environment.
In that case what I'll apply registry policies and then place policies.json in Mozilla folder (and change something in that file)? Will JSON file overwrite the registry or the other way around ? (I know that GPO stands higher than json)
> In that case what I'll apply registry policies and then place policies.json in Mozilla folder (and change something in that file)? Will JSON file overwrite the registry or the other way around ? (I know that GPO stands higher than json)
Right now, GPO wins over JSON completely (json isn't read).
I have a patch that will be coming in the next release (hopefully) that will make GPO and JSON merge (with GPO winning if the same entry is in both JSON and GPO)
Mike Kaply said
Right now, GPO wins over JSON completely (json isn't read). I have a patch that will be coming in the next release (hopefully) that will make GPO and JSON merge (with GPO winning if the same entry is in both JSON and GPO)
Hm, going by that logic it seems that .reg files are out of the question because they will always overwrite JSON file...
I was thinking about making fresh install, configure them with .reg files and attach sym link policies.json file that I could change at any time on the central server.
Modified by Serpher
Chosen Solution
Yeah, in your scenario I think you're better off just using the symlink idea.