Blackberry PRD-10459-016 Administration Guide - Page 194

Making the BlackBerry Web Desktop Manager available to users

Page 194 highlights

Administration Guide Making the BlackBerry Web Desktop Manager available to users Making the BlackBerry Web Desktop Manager 17 available to users Installing the client components of the BlackBerry Web Desktop Manager on users' computers By default, when users open and log in to the BlackBerry® Web Desktop Manager for the first time, the browser prompts them to accept a client authentication certificate and install the required RIMWebComponents.cab file. The RIMWebComponents.cab file provides the BlackBerry® Device Manager and USB drivers that users require to use the BlackBerry Web Desktop Manager. To install these RIMWebComponents.cab file, users must log in to their computers as a local administrator. If you use Microsoft® Active Directory® in your organization's environment, consider creating Windows® GPOs to install the client components of the BlackBerry Web Desktop Manager on users' computers automatically. When you use Windows GPOs, the browser does not display the security warning or installation prompts to users, and users do not require local administrator permissions to complete the installation process. Related topics Configuring the BlackBerry Web Desktop Manager, 197 Publish the client files for the BlackBerry Web Desktop Manager in a Windows GPO for Windows XP If you use Microsoft® Active Directory®, you can create a Windows® GPO to make sure that the browser settings are correct for your organization's environment. Alternatively, you can check the browser settings on users' computers and, if necessary, change them manually. 1. In the BlackBerry® Enterprise Server installation files, navigate to tools/RIMWebComponents. 2. Copy the RIMWebComponents.msi file to a shared network folder. 3. In Microsoft Active Directory Users and Computers, right-click the organizational unit that you want to assign the Windows GPO to. Click Properties. 4. On the Group Policy tab, click New. 5. In the Name field, type a name for the new GPO. 6. In the list of GPOs, click the GPO name. 7. Click Edit. 8. In the Group Policy Editor menu, click User Configuration > Software Settings. 9. Right-click Software Installation. Click New > Package. 10. Type the UNC path and name of the RIMWebComponents.msi. The path must be typed in UNC format (for example, \\ComputerName\Applications\Testing). 11. Click Open. 192

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406
  • 407
  • 408
  • 409
  • 410
  • 411
  • 412
  • 413
  • 414
  • 415
  • 416
  • 417
  • 418
  • 419
  • 420
  • 421
  • 422
  • 423
  • 424
  • 425
  • 426
  • 427
  • 428
  • 429
  • 430
  • 431
  • 432

Making the BlackBerry Web Desktop Manager
available to users
17
Installing the client components of the BlackBerry Web
Desktop Manager on users' computers
By default, when users open and log in to the BlackBerry® Web Desktop Manager for the first time, the browser
prompts them to accept a client authentication certificate and install the required RIMWebComponents.cab file. The
RIMWebComponents.cab file provides the BlackBerry® Device Manager and USB drivers that users require to use
the BlackBerry Web Desktop Manager. To install these RIMWebComponents.cab file, users must log in to their
computers as a local administrator.
If you use Microsoft® Active Directory® in your organization's environment, consider creating Windows® GPOs to
install the client components of the BlackBerry Web Desktop Manager on users' computers automatically. When you
use Windows GPOs, the browser does not display the security warning or installation prompts to users, and users
do not require local administrator permissions to complete the installation process.
Related topics
Configuring the BlackBerry Web Desktop Manager, 197
Publish the client files for the BlackBerry Web Desktop
Manager in a Windows GPO for Windows XP
If you use Microsoft® Active Directory®, you can create a Windows® GPO to make sure that the browser settings are
correct for your organization's environment. Alternatively, you can check the browser settings on users' computers
and, if necessary, change them manually.
1.
In the BlackBerry® Enterprise Server installation files, navigate to tools/RIMWebComponents.
2.
Copy the
RIMWebComponents.msi
file to a shared network folder.
3.
In Microsoft Active Directory Users and Computers, right-click the organizational unit that you want to assign
the Windows GPO to. Click
Properties
.
4.
On the
Group Policy
tab, click
New
.
5.
In the
Name
field, type a name for the new GPO.
6.
In the list of GPOs, click the GPO name.
7.
Click
Edit
.
8.
In the
Group Policy Editor
menu, click
User Configuration > Software Settings
.
9.
Right-click
Software Installation
. Click
New > Package
.
10.
Type the UNC path and name of the
RIMWebComponents.msi
. The path must be typed in UNC format (for
example, \\ComputerName\Applications\Testing).
11.
Click
Open
.
Administration Guide
Making the BlackBerry Web Desktop Manager available to users
192