UMRA – Active Directory Automation Error Handling at 8:17 PM

If you haven’t already, please read my first post on where and how to download a trial version of User Management Resource Administrator, developed by tools4ever. UMRA

Download Trial Version of UMRA > http://www.tools4ever.com/download/
Download Trial Version of SSRPM > http://www.tools4ever.com/download/

UMRA – Active Directory Automation Error Handling

By now after reading and following my posts you should have some idea of how to create a
UMRA Automation project to automate student or staff account creation, or running account audits on your Active Directory. Now, we all know that your UMRA Automation projects sometimes will throw errors for different reasons, and depending on how many accounts or Active Directory objects you are trying to provision, your UMRA Automation logs can get quite large. I often find myself sometimes, running a UMRA Automation project that handles over 20k student accounts, and wont know if the UMRA Automation project threw and error until it is completely done, thus having four or five UMRA log files to search through, make this a little tuff sometimes, to figure out where it threw and error and why. So in this blog I will talk about ways to step up your UMRA projects to include some error handling, to show you what UMRA Automation project actually threw the error, and any other information in that script.

UMRA – AD Automation Error Handling How To

So I will keep this at a high level so you can get an idea of how you can take this UMRA Automation Error Handling and Error Logic and integrate it into other projects you might have.
What I will do is first create two non script items in my UMRA Automation project, one will be called “Error” the other is “No Error” within the 2 no action items, you will drag and drop a “Export Variables” action, this action will export to a file either on your desktop, or folder somewhere, the UMRA Automation project name, and then any variables you want to during and error. So for example if you have a project called “Student Creation” You can export the name, and maybe a studentid, or accountname when you throw this error, this way you can look into the account, or action and figure out what is going on. Now, you take this same approach on all the UMRA Automation projects you build, and now when you run your larger projects, you will have log file of what UMRA Automation projects threw and error, who it was on, and a even a datetime of when they happened.

Below is a quick screen show of how you can implement this UMRA Automation Error Handling into your projects.