• Recently Written

  • Is SaaS the Recession Tactic for SW that Leasing was for HW?
  • Open Source Facing Compliance Issues Too
  • SIIA Cracking Down on Internet Software Pirates
  • New Addition to Team & Services
  • Software Licensing impacted by Technology Changes
  • HP ServiceCenter Tidbits
  • Energy Costs “Drive” New Ways to Look at Change
  • HP ServiceCenter Hints and Tips
  • Virtualization - the Server yes, but the Desktop?
  • Compliance Rates Lower Than Acceptable

• Categories

  • Company News
  • Industry Observations
  • ITAM (Asset Management)
  • ITIL and Service Management
  • Software License Compliance

• Search

  
  
  

• Archives

  • August 2008
  • July 2008
  • June 2008
  • May 2008
  • April 2008
  • February 2008
  • January 2008
  • December 2007

• Subscription

  •  Blog Articles
  •  Subscribe by Email
  • 

• Members

  • Log in

Controlling the “SYSADMIN” capability word in HP/Open View’s ServiceCenter

As a Consultant, I have had the opportunity to implement and customize ServiceCenter in a number of unique environments.  Sometimes, a small funcational change can be very important to the overall success of the project, so I thought I would share the occasional tidbit. 

In some organizations, some operators add users (operators) records routinely, but not at the SysAdmin level.   Confusion arises if those records mistakenly have the “SysAdmin” word on the capabilities word list.  This problem can be prevented by blocking admin or operators from adding the SysAdmin word to the capabilities word using format control.

The $lo.ucapex global variable is checked by the system to ensure that the operator has SysAdmin  rights before allowing the addition of SysAdmin capability word  by tailoring the format control (validations).  The validation will check the global variable to see if the operator adding a user has the SysAdmin capability word. If the validation is false then they’re not allowed to add the SysAdmin capability word.

Comments