Skip to content

Commit 619ac59

Browse files
KelvinTegelaargitbook-bot
authored andcommitted
GITBOOK-50: No subject
1 parent 05170e2 commit 619ac59

File tree

1 file changed

+2
-164
lines changed

1 file changed

+2
-164
lines changed

docs/deployment/chrome-edge-deployment-instructions.md

Lines changed: 2 additions & 164 deletions
Original file line numberDiff line numberDiff line change
@@ -32,171 +32,9 @@ Each profile contains **two OMA-URI settings**:
3232

3333
***
3434

35-
#### Step 2 – Create the Chrome Profile
35+
#### Step 2: Configuration
3636

37-
1. **Name**: `Chrome Extension – Check`
38-
2. **Description**: `Deploy and configure Check extension in Chrome`
39-
3. Under **Configuration settings**, click **Add**.
40-
4. Add the following **two OMA-URI entries**:
41-
42-
***
43-
44-
**Chrome – Force Install**
45-
46-
* **Name**: Chrome Extension – Install
47-
* **OMA-URI**:
48-
49-
```
50-
./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome/ExtensionSettings
51-
```
52-
* **Data type**: String
53-
* **Value**:
54-
55-
```json
56-
{
57-
"benimdeioplgkhanklclahllklceahbe": {
58-
"installation_mode": "force_installed",
59-
"update_url": "https://clients2.google.com/service/update2/crx"
60-
}
61-
}
62-
```
63-
64-
***
65-
66-
**Chrome – Extension Settings**
67-
68-
* **Name**: Chrome Extension – Settings
69-
* **OMA-URI**:
70-
71-
```
72-
./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome/3rdparty_extensions
73-
```
74-
* **Data type**: String
75-
* **Value**:
76-
77-
```json
78-
{
79-
"benimdeioplgkhanklclahllklceahbe": {
80-
"showNotifications": true,
81-
"enableValidPageBadge": false,
82-
"enablePageBlocking": true,
83-
"enableCippReporting": true,
84-
"cippServerUrl": "https://yourserver.com",
85-
"cippTenantId": "your-tenant-id",
86-
"customRulesUrl": "https://yourrules.com",
87-
"updateInterval": 24,
88-
"enableDebugLogging": false,
89-
"customBranding": {
90-
"companyName": "Your Company",
91-
"productName": "Check - Phishing Protection",
92-
"supportEmail": "support@yourcompany.com",
93-
"primaryColor": "#FF0000",
94-
"logoUrl": "https://yourcompany.com/logo.png"
95-
}
96-
}
97-
}
98-
```
99-
100-
***
101-
102-
#### Step 3 – Create the Edge Profile
103-
104-
1. Repeat the steps above to create a **second Custom profile**.
105-
2. **Name**: `Edge Extension – Check`
106-
3. **Description**: `Deploy and configure Check extension in Edge`
107-
4. Add the following **two OMA-URI entries**:
108-
109-
***
110-
111-
**Edge – Force Install**
112-
113-
* **Name**: Edge Extension – Install
114-
* **OMA-URI**:
115-
116-
```
117-
./Device/Vendor/MSFT/Policy/Config/Edge~Policy~microsoftedge/ExtensionSettings
118-
```
119-
* **Data type**: String
120-
* **Value**:
121-
122-
```json
123-
{
124-
"knepjpocdagponkonnbggpcnhnaikajg": {
125-
"installation_mode": "force_installed",
126-
"update_url": "https://edge.microsoft.com/extensionwebstorebase/v1/crx"
127-
}
128-
}
129-
```
130-
131-
***
132-
133-
**Edge – Extension Settings**
134-
135-
* **Name**: Edge Extension – Settings
136-
* **OMA-URI**:
137-
138-
```
139-
./Device/Vendor/MSFT/Policy/Config/Edge~Policy~microsoftedge/3rdparty_extensions
140-
```
141-
* **Data type**: String
142-
* **Value**:
143-
144-
```json
145-
{
146-
"knepjpocdagponkonnbggpcnhnaikajg": {
147-
"showNotifications": true,
148-
"enableValidPageBadge": false,
149-
"enablePageBlocking": true,
150-
"enableCippReporting": true,
151-
"cippServerUrl": "https://yourserver.com",
152-
"cippTenantId": "your-tenant-id",
153-
"customRulesUrl": "https://yourrules.com",
154-
"updateInterval": 24,
155-
"enableDebugLogging": false,
156-
"customBranding": {
157-
"companyName": "Your Company",
158-
"productName": "Check - Phishing Protection",
159-
"supportEmail": "support@yourcompany.com",
160-
"primaryColor": "#FF0000",
161-
"logoUrl": "https://yourcompany.com/logo.png"
162-
}
163-
}
164-
}
165-
```
166-
167-
***
168-
169-
#### Step 4 – Assign and Deploy
170-
171-
1. In each profile, click **Next** until you reach **Assignments**.
172-
2. Assign the profile to the groups you want (devices or users).
173-
* Device assignment is usually more reliable for browser extensions.
174-
3. Click **Create**.
175-
176-
***
177-
178-
#### Step 5 – Verify
179-
180-
* On a test machine, sync Intune (`Settings → Accounts → Access work or school → Sync`).
181-
* Restart Chrome and Edge.
182-
* Both browsers should:
183-
* Auto-install the extension.
184-
* Enforce the settings you defined.
185-
186-
You can double-check via registry:
187-
188-
* **Chrome**:
189-
190-
```
191-
HKLM\SOFTWARE\Policies\Google\Chrome\ExtensionSettings
192-
HKLM\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions
193-
```
194-
* **Edge**:
195-
196-
```
197-
HKLM\SOFTWARE\Policies\Microsoft\Edge\ExtensionSettings
198-
HKLM\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions
199-
```
37+
Documentation to follow
20038

20139
</details>
20240

0 commit comments

Comments
 (0)