- Microsoft Identity Manager 2016 Handbook
- Table of Contents
- Microsoft Identity Manager 2016 Handbook
- Credits
- About the Authors
- About the Reviewers
- www.PacktPub.com
- Preface
- 1. Overview of Microsoft Identity Manager 2016
- 2. Installation
- 3. MIM Sync Configuration
- 4. MIM Service Configuration
- 5. User Management
- Additional sync engine information
- Portal MPRs for user management
- Configuring sets for user management
- Inbound synchronization rules
- Outbound synchronization rules
- Provisioning
- Managing users in a phone system
- Managing users in Active Directory
- Temporal sets
- Self-service using MIM Portal
- Managing Exchange
- More considerations
- Summary
- 6. Group Management
- 7. Role-Based Access Control with BHOLD
- 8. Reducing Threats with PAM
- 9. Password Management
- 10. Overview of Certificate Management
- 11. Installation and the Client Side of Certificate Management
- 12. Certificate Management Scenarios
- 13. Reporting
- 14. Troubleshooting
- 15. Operations and Best Practices
- Expectations versus reality
- Automating run profiles
- Best practices concepts
- Backup and restore
- Backing up the synchronization encryption key
- Restoring the MIM synchronization DB
- Restoring the MIM service DB and portal
- Additional backup considerations
- Operational health
- Database maintenance
- SQL best practices
- MIM synchronization best practices
- MIM portal best practices
- Other best practices
- Summary
- Index
The following are some best practices of the MIM portal:
- Minimize the use of dynamic nesting and the use of negative (NOT) conditions in sets and groups. A good rule of thumb is to stay under five NOTs.
- Disable the verbose tracing of MIM Service when not needed.
- Be aware that exposing self-service reset internal and external could be a Denial of Service endpoint if you have Active Directory configured to lock out.
- Back up custom workflow code and pages and manage them as you would any production source code.
- Do not delete the default workflows that come with the product.
- Keep an eye on expired portal requests. If you see requests building up beyond the retention time (default 30 days), then you may need to run the SQL job
FIM_DeleteExpiredSystemObjectsJob.
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.