Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Den här webbplatsen har begränsad funktionalitet medan vi utför underhåll för att förbättra din upplevelse. Om en artikel inte löser ditt problem och du vill ställa en fråga har vi vår gemenskap som väntar på att hjälpa dig på @FirefoxSupport på Twitter, /r/firefox på Reddit.

Sök i support

Akta dig för supportbedrägerier: Vi kommer aldrig att be dig att ringa eller skicka ett sms till ett telefonnummer eller dela personlig information. Rapportera misstänkt aktivitet med alternativet "Rapportera missbruk".

Läs mer

How to deploy a new extension disabled after adding it via GPO

  • 3 svar
  • 3 har detta problem
  • 22 visningar
  • Senaste svar av Mike Kaply

more options

Hello!

We are using Firefox ESR 60.x.x.x and GPO for our company. If I deploy a new extension via GPO it is automatically enabled. So, if it is only for a small group of people, thousands of others have to disable it manually or ask questions about it.

Is there way to deploy a new extension via GPO disabled?

Thanks!

Hello! We are using Firefox ESR 60.x.x.x and GPO for our company. If I deploy a new extension via GPO it is automatically enabled. So, if it is only for a small group of people, thousands of others have to disable it manually or ask questions about it. Is there way to deploy a new extension via GPO disabled? Thanks!

Alla svar (3)

more options

You can create a separate group policy that deploys the extension that you're talking about in Group Policy Management.

Then you can link that policy only to the users that require the extension, eg. via an AD Security group or OU.

Tim

more options

Thx Tim, but this isn't what I'm looking for.

I don't want to create for every extension a GPO if only a small group of people need it.

No other solution? Is Firefox not designed for large companies?

more options

We don't currently have that feature, but I'm considering it. I'm in the process of rewriting how we handle all extension installation.