The user is likely to become unhappy because their account
won??™t work as anticipated. In fact, the account can become unstable. In a worst case scenario, the
instabilities could cause system crashes and data loss (this scenario is rare, but you always have to
work as if you??™ll be the unlucky individual who has it happen to them). If you can??™t make the
changes before the user gets into work, specifically have the user log out of the system, perform the
configuration task, and ask the user to log back in. Using this approach will reduce user frustration.
620 APPENDIX D
LISTING OF BEST PRACTICES
The same approach also applies to a group. Many group level changes can cause instabilities in
the affected accounts. Normally, you??™ll want to make group changes when everyone is logged out
to ensure that the changes take effect the next time the users of the group log back into the system.
TIP
Some users are invariably going to cheat. It??™s possible to stand behind the user, watch them
log out, and then go back to your office to perform the reconfiguration while they log back into the
system. Inevitably the user will call back sometime later saying they were logged out, yet the
instabilities that they??™re telling you about can only occur if they were logged in while you made
the required account changes.
Pages:
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380