Sunday, Sep 05, 2010
Login

Category: Import Sets

The Best LDAP Integration Tip You’ve Never Heard Of

O

ne of the basic (but often forgotten) guidelines that should be followed whenever you consider importing any data into your Service-now instance is to only import the information that is actually necessary within the tool. Just because you CAN import the data into Service-now doesn’t necessarily mean that the data SHOULD be imported or that it has any value. Even if somebody thinks the data has value within Service-now, you should also consider if that value outweighs the work and trouble of importing and maintaining that data going forward. This is particularly true for CMDB and old ticket data but is also true of user data imported from LDAP. One thing that a lot of people don’t realize is that you can end up with ‘garbage’ data from LDAP but that it is also very simple to configure your system to prevent this from happening.


Defining the ‘Run as’ User for a Scheduled Import

Recently I had a client ask me why all of their imported records showed up as being updated and created by the person who initially created the import. The problem, they said, was that the imported records were being created and updated on a scheduled basis by the system so it really wasn’t a particular person who was creating the records. While I agreed that it was a problem, I wasn’t sure at the time why it was happening or what the solution was. Now I know!


 

Recent Comments

  • Scott Stechmesser: Awesome script to use. Works great. How would you modify it to be able to copy a Catalog UI Policy?
  • Tulio: Perfect!!! Thanks for this.
  • Ron Methias: Another reason why I have stopped going to the official SN documentation sites and make the GURU my...
  • Richard Huss: Ingenious – and somewhat simpler than the way the Incident Resolution best practice plugin does...
  • valor: Joe, that’s one of the reasons why I’m parsing out the URL instead of trying to get the page...