Whether you’re a new administrator or an experienced consultant, you need to know these things to become a master of the ServiceNow force.
Whether you’re a new administrator or an experienced consultant, you need to know these things to become a master of the ServiceNow force.
O
ne of the most common LDAP integration requirements is to disable users in Service-now when they become disabled in the LDAP source.
Because the exact steps to set up this behavior vary depending on your LDAP setup and processes, this configuration isn’t something that can be predefined in Service-now. Typically a Service-now consultant assists with this setup and specific requirements are determined on a client-by-client basis. It has been my experience that there are two common approaches that can be used to disable Service-now users from LDAP. This article explains these approaches and how you can implement the needed functionality.
O
ne of the most basic needs that a customer has when building out their CMDB is extending it to match the types of CIs that they’re currently using in their company. This is especially true when bringing data in from a 3rd-party CMDB (such as IBM’s CCMDB, HP’s uCMDB, etc) with Service-now. Some of these CMDBs have hundreds of class types with scores of fields for each class. How can you get the 3rd-party data into Service-now when the schema is so different?
There are essentially four main steps to accomplish this: decide what classes and fields need to be brought across, create a mapping document, extend the Service-now CMDB to accept the new classes, and send the data from the 3rd party CMDB to Service-now.