TUESDAY, FEBRUARY 07, 2012

Posts Tagged ‘LDAP’

Weekdays-only Scheduled Job

Monday, 14 February, 2011 09:15 Written by Mark Stanger
10 Comments

S

ervice-now allows you to run scheduled jobs at various intervals. Out of box, you are given the option to run scheduled jobs like imports on a specific day, day of the week, month, or at some other custom interval. There are certain intervals that just don’t work very easily with the default setup provided. One of these that can be challenging is the weekday-only schedule. In order to get a scheduled job to run only on weekdays, the recommendation is usually to set up 5 different scheduled jobs, one for each day of the week you want to run on. While this works, it’s really 4 more scheduled jobs that you don’t want to set up and manage. With some simple scripting and the use of the ‘Condition’ field, you can set up a single daily scheduled job to handle this scenario.

Learn more ...

Deactivating Users From LDAP

Wednesday, 01 September, 2010 14:30 Written by Mark Stanger
2 Comments

O

ne of the most common LDAP integration requirements is to disable users in Service-now when they become disabled in the LDAP source.

It is probably worth mentioning that you always want to deactivate user records (and most other records too) in Service-now instead of deleting them. Once a user record has been created in Service-now it should always remain in Service-now because that record could be linked to hundreds of other records (tasks, CIs, etc.). Deleting the record kills the relationship to those other records. Deactivating the record keeps that relationship in place.

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.

Learn more ...

The Best LDAP Integration Tip You’ve Never Heard Of

Wednesday, 30 June, 2010 10:49 Written by Mark Stanger
0 Comments

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.

Learn more ...

Latest Comments

  • Mark Stanger: This functionality doesn’t connect to an FTP server. See this line in the post above…...
  • Mark Stanger: The report page is back-end XML so there’s no way to directly manipulate the behavior of that...
  • Mark Stanger: Due to some ServiceNow limitations, the localhost MID server option had to be removed.
  • Matt Haak: Is it possible to use this with the local Mid Server (mid.server.localhost) It appears from this community...