{
"name": "Adobe Acrobat",
"storage": {
"managed_schema": "schema.json"
},
...
}
Terakhir dikemas kini pada
23 Okt 2025
Learn how to prevent the What’s New page from opening automatically by configuring managed browser policies for the Acrobat extension.
System administrators can use the browser-managed storage schema to create feature flags and set policies in the registry. These policies allow the Acrobat extension to be preconfigured for all users in an organization. The extension reads and enforces supported policies using the storage.managed API.
The storage.managed_schema property indicates a file within the extension that contains the policy schema:
|
|
Schema to prevent auto-opening of the What’s New page
Use this schema to control the automatic opening of the What’s New page.
|
{ "type": "object",
"properties": { "DisableWhatsNewAutoOpen": { "title": "Disable auto-opening of What's New page", "description": "To disable the auto-opening of the What's New page, set DisableWhatsNewAutoOpen to true", "type": "string" } } } |
Configure the installed extension using Group Policy
Administrators can configure policies to turn on or off the features supported in the schema.json file.
Windows
-
Press Windows + R to open the Run command window.
-
Enter regedit in the Open field and select OK.
-
Based on your browser, update the following registry key. Create the registry key if it does not exist.
- Edge: HKLM\Software\Policies\Microsoft\Edge\3rdparty\extensions\elhekieabhbkpmcefcoobjddigjcaadp\policy
- Chrome: HKLM\Software\Policies\Google\Chrome\3rdparty\extensions\efaidnbmnnnibpcajpcglclefindmkaj\policy
- Chromium: HKLM\Software\Policies\Chromium\3rdparty\extensions\efaidnbmnnnibpcajpcglclefindmkaj\policy
Nota:For Chromium, you can also use the HKEY_CURRENT_USER hive instead of HKEY_LOCAL_MACHINE.
-
Create a new string key named DisableWhatsNewAutoOpen and set the value to true.
After configuring the policy, it appears in chrome://policy/.
macOS
-
Create a .plist file with the required configuration.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>com.google.Chrome.extensions.efaidnbmnnnibpcajpcglclefindmkaj</key>
<dict>
<key>DisableWhatsNewAutoOpen</key>
<dict>
<key>state</key>
<string>always</string>
<key>value</key>
<string>true</string>
</dict>
</dict>
</dict>
</plist>
The first key in your .plist file specifies the browser extension bundle ID to configure (for example, com.google.Chrome.extensions.efaidnbmnnnibpcajpcglclefindmkaj for Chrome).
Each policy entry includes metadata and a value. The state key controls how often the policy is enforced. Set it to always keep the policy active at all times.
-
Import the configuration using dscl.
$ dscl -u admin_username /Local/Default -mcximport /Computers/local_computer configuration.plist
-
Substitute admin_username with a valid administrator username, and configuration.plist with the path to the .plist configuration file you created. For simplicity, you can put the configuration.plist file on your desktop and run the commands from the desktop folder in Terminal.
-
If dscl complains that the path is invalid, create a node for the local computer with these commands:
$ GUID=uuidgen
$ ETHER=$(ifconfig en0 | awk '/ether/ {print $2}')
$ dscl -u admin_username /Local/Default -create /Computers/local_computer
$ dscl -u admin_username /Local/Default -create /Computers/local_computer RealName "Local Computer"
$ dscl -u admin_username /Local/Default -create /Computers/local_computer GeneratedUID $GUID
$ dscl -u admin_username /Local/Default -create /Computers/local_computer ENetAddress $ETHERRefresh policies as needed.
-
After running these commands, import the configuration again:
$ dscl -u admin_username /Local/Default -mcximport /Computers/local_computer configuration.plist
-
To apply changes immediately, run:
$ sudo mcxrefresh -n username
Replace username with the affected user’s account name.
If Chrome is running with the Managed bookmarks extension, the policy loads within 10 seconds. To load the policy immediately, select Reload policies in chrome://policy/.
Administrators can find detailed steps for configuring extension policies in the Chromium documentation.
