• Search

• Categories

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

• Recently Written

  • Planning ahead for asset collection during layoffs
  • The one Millionth Mouse delivered from Logitech
  • Software Cost Efficiencies
  • Good Content Best Feature of This Year’s IAITAM Conference
  • RFID World Heightens Interest in Active RFID for IT Assets
  • 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

• Blogroll

  • Miro Consulting

• Subscription

  •  Blog Articles
  •  Subscribe by Email
  • 

• Archives

  • December 2008
  • November 2008
  • October 2008
  • September 2008
  • August 2008
  • July 2008
  • June 2008
  • May 2008
  • April 2008
  • February 2008
  • January 2008
  • December 2007

• Members

  • Log in

During the June 30 webinar by Scott Rosenberg, he identified technology as one of the drivers for licensing changes and complexity. He highlighted multicore processors, virtualization, open source, mobile workforce and limited use/application specific software. I believe we are all seeing these technology changes. It seems to me that the discipline of making sure the license describes how the software can be used is our best defense. Clarifying where it can be used and by whom (and the number of people) applies no matter what. Our concern with being too explicit and limiting unnecessarily where it can be used must be set aside when facing new technology.

The best preparation in addition to what you do today would be to stop and think about how it can be used so that you uncover the new questions that haven’t ever been asked before.

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.

Your company wants to go with another disposal vendor.  While reading the terms and conditions, you see that they will be charging mileage for pick-ups. 

Your company wants to move the maintenance center or consolidate.  You notice that the evaluation does not consider the extra travel time and costs to reach those centers. 

It is time to look at our evaluation criteria and make sure that we consider the energy costs, especially mileage.  Where we might have been able to ignore it in the past, the rising cost of fuel is impacting our suppliers and outsourcers.  You can be sure that they will want your company to share the burden.

← Previous Page — Next Page →