Actually, it came from Internal Audit.
They've already taken away some of our access at the DB level to certain tables 
(approval and changes, as they are SOX related).
Then they came back and wanted to take away our admin access all together (i.e. 
no Admin Tool)....
So I had to argue with them for about an hour before it was finally agreed that 
we would look at logging when and admin logs in to the User tool or Admin tool

I can capture Admins logging in to the User tool,
I just need to capture it when it's an admin logging in to the Admin Tool as 
well.
Still thinking DB trigger on a table.

LJ, I know you were just mentioning a new feature in 7.5, and a possible 
solution.
:)
I was just giving BMC a little bit of grief and my .5 cent on upgrading...
We spent 2 years upgrading to ITSM 7.1, and every horror story you hear, we 
experienced.
So we are not going to be upgrading anytime soon.

From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Reiser, John J
Sent: Friday, July 30, 2010 11:26 AM
To: [email protected]
Subject: Re: Capturing when an Admin Login is used

**
Matthew,
Sounds like you are trying to catch a rogue admin doing some midnight 
developing. " I can make all your tickets get reassigned to Pete for $50"
How about the Server Events form?
I will capture the changes made though it will not let you know when the admin 
logged in. That would in the User.log or via the init-form setting.
HTH,
---
John J. Reiser
Senior Software Development Analyst
Remedy Administrator/Developer
Lockheed Martin - MS2
The star that burns twice as bright burns half as long.
Pay close attention and be illuminated by its brilliance. - paraphrased by me
From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Matthew Perrault
Sent: Friday, July 30, 2010 11:38 AM
To: [email protected]
Subject: EXTERNAL: Re: Capturing when an Admin Login is used

**
Thanks guys.
Ya I tried adding some code to the AR System:License Review form,
but that's a Vendor form, and it didn't work :(.
I look into the INIT form, though, but I really needed to capture when the 
Admin tool is logged into.
I'm thinking if there was a table in the DB, I could write a DB trigger on that 
to insert into a different table,
Then drop a view form on that table

As far as upgrade to 7.5 (it'll solve all your problems! MMMMOOOOOOOOO-plop 
plop-->Bull....)
That's not going to happen any time soon.
I heard the same thing on upgrading to 7.1...needless to say, I was less than 
impressed.
"Fool me once, shame on you. Fool me twice, shame on me."


From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of LJ LongWing
Sent: Friday, July 30, 2010 9:58 AM
To: [email protected]
Subject: Re: Capturing when an Admin Login is used

**
Matthew,
As John mentioned, you could use the Init form, but that only works in the user 
tool...not Admin or Web...your best option in my opinion is to upgrade to 7.5 
and turn on the user license monitoring feature...then write a filter on these 
forms to do what you need....outside of upgrading, I believe your only other 
option is the user log.

**
Matthew,
 Look for the INIT_Form in the docs.
You have to add it to the ar.cfg file. I loads in the back ground and you can 
use it to push data to your "Spy on the bad admin" form;^>
Can ya tell it's Friday?

---
John J. Reiser
Senior Software Development Analyst
Remedy Administrator/Developer
Lockheed Martin - MS2
The star that burns twice as bright burns half as long.
Pay close attention and be illuminated by its brilliance. - paraphrased by me


From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Matthew Perrault
Sent: Friday, July 30, 2010 8:11 AM
To: [email protected]
Subject: Capturing when an Admin Login is used

**
All,
I'm trying to capture when a specific Administrator Login is used to login to 
the User or Admin Tool.
I need to take that information, and save the ID and the Timestamp into a 
Form/Table so that it can be reported off of monthly.
While I could turn on the User Logging (from the Server Information form), and 
run a Perl Script to convert it into a CSV,
that means I would have to be doing the reporting (which I want to avoid).
It also means that Log could get pretty big.

Does anybody have any suggestions/ideas on how I can do this with Remedy Work 
Flow?
I thought there was a way, but I can't remember.

ARS 7.1 Patch 8
ITSM 7.1
MS SQL Database 2005
Windows Server 2003

Thanks in advance
Matt P.
_attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_
_attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_
_attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_
_attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"

Reply via email to