Good afternoon, This may be more of a business process question than an application question, but I wanted to see if anyone out there has a solution.
The scenario that causes the problem is that we have transition periods for software between version updates. The basic flow of this is: 1) We have Visio 2007 as a standard and track our licenses for 2007. 2) Visio 2010 becomes available, and we begin purchasing licenses for 2010, but because we are in a transition period, we install Visio 2007. 3) Once the transition period is complete, we upgrade all users from 2007 to 2010. This approach has a few problems, though. The first is that it makes it difficult to track owned licenses versus installations. Basically, the situation like this is what would cause the problem: 1) User A requests Visio, and he purchases and gets Visio 2007 installed. 2) Later on, User B requests Visio, and because Microsoft has made 2010 available, User B purchases Visio 2010. 3) I.T. is not yet ready to upgrade the enterprise to 2010, so they install Visio 2007 on User B's machine. 4) In Asset Management, we track our Visio 2007 licenses in one Software Contract, and our 2010 licenses in another. The 2010 users have downgrade rights to 2007, but the 2007 users do not have upgrade rights to 2010. 5) When we perform a discovery, we see that both User A and User B have Visio 2007 installed, and in our reconciliation, we appear to be out of compliance on Visio 2007 by one license, and we appear to have a free Visio 2010 license. The other problem with this is that we won't be able to quantify what we really have available when we do queries against the Software Contracts. Based on the scenario above, when a new user goes to request Visio 2010, the system will think we have a license available, when in reality it is used for User B's 2007 installation. So if anyone has any suggestions on how to deal with this, we would greatly appreciate it. We are on ITSM 7.0 so any answers of how to track these related licenses better in 7.5 will be appreciated, but not as much as things that work on 7.0. Thanks, Shawn Pierson Remedy Developer | Southern Union Private and confidential as detailed here: http://www.sug.com/disclaimers/default.htm#Mail . If you cannot access the link, please e-mail sender. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
