![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png){kind=small}
Pass. The. rum. NOW.
Mar. 30th, 2010 08:43 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
jecookSo we have this really flaky and persnickity system at $work that talks to our HR system and provisions and de-provisions users automatically, based on what job code they are assigned, and what entitlements said job code has in a seperate (I.E., maintained in-department) database. The general process is thus: HR adds Joe Luser to their system and assigns them a job code that has a network account provisioned for it. This software trolls their system a couple times a day looking for new users, terminated users, transfers, etc. Upon seeing one of these changes, it takes the appropriate action: for new users, or transfers, it looks up their new job code and the entitlements for their new position, and re-provisions their account accordingly.
Cue the HI-LARITY, frustration, aggravation, and rage (in that order) when they bounce a user between three or four different job codes within a couple weeks of a new user starting. Oh, Did I mention that these different job codes don't exist in the program's entitlement database and have to be manually added by one of the IT staff? And that just after we fix it the first (and then second, and third!) time, they transfer them to a new code for reasons unexplained to us?
Yeah, Guess who got to un-tombstone someone's email and AD account for probably the fourth or fifth time in the past three weeks. Kitty is... displeased. For that matter, neither is the user, who probably thinks the entire IT department is comprised of a bunch of incompetent anus rangers.
Oh yeah, and the software itself? Occasionally, it goes into a corner and refuses to generate accounts until we reboot the server it lives on. And even rarer (thank BOG) we have to manually manipulate the provisioning database it uses to correct data that gets put in wrong, or (in another case today) was a case of a person re-using an employeeID of someone entirely different.
My only saving grace is that we are looking at getting rid of this software, which will hopefully result in something that's a bit more... resiliant of screwups and not held togather with chewing gum and 'hello kitty' stickers.
Cue the HI-LARITY, frustration, aggravation, and rage (in that order) when they bounce a user between three or four different job codes within a couple weeks of a new user starting. Oh, Did I mention that these different job codes don't exist in the program's entitlement database and have to be manually added by one of the IT staff? And that just after we fix it the first (and then second, and third!) time, they transfer them to a new code for reasons unexplained to us?
Yeah, Guess who got to un-tombstone someone's email and AD account for probably the fourth or fifth time in the past three weeks. Kitty is... displeased. For that matter, neither is the user, who probably thinks the entire IT department is comprised of a bunch of incompetent anus rangers.
Oh yeah, and the software itself? Occasionally, it goes into a corner and refuses to generate accounts until we reboot the server it lives on. And even rarer (thank BOG) we have to manually manipulate the provisioning database it uses to correct data that gets put in wrong, or (in another case today) was a case of a person re-using an employeeID of someone entirely different.
My only saving grace is that we are looking at getting rid of this software, which will hopefully result in something that's a bit more... resiliant of screwups and not held togather with chewing gum and 'hello kitty' stickers.
