I thought some folks on the EDUCAUSE Software Licensing CG might have some thoughts in response to your inquiry so am forwarding your message from the Policy CG email list so that they might reply to you directly.
Associate Director, IT Strategic Sourcing
University of California, Procurement Services
Email: [log in to unmask]
From: EDUCAUSE Policy Discussion Listserv [mailto:[log in to unmask]] On Behalf Of James Farr
Sent: Monday, March 20, 2017 12:02 PM
To: [log in to unmask]
Subject: [POLICY-DISCUSSION] Decommission Unsupported Software / Hardware
It may be an oldie and a goodie, but should we keep it or replace it? We are looking to update our process on how to deal with unsupported software and hardware. We are considering placing the decommissioning process right in the purchase policy to eliminate the number of policies people need to look during their planning process, but want to know how others are handling this.
Do you have an approved process to follow when the college needs to decommission unsupported computer equipment?
Where is this policy/ process documented?
Can you share this document?
Are exceptions allowed? (Ex, we use software XYZ which only works on Windows XP. There is nothing as good on the market today so we need to keep using software XYZ?) If so, what limitations are placed on that equipment (must not be on the network, must not allow unknown media on the machine)?
James Farr ’05 G’12
Director of Information Security
[log in to unmask]
Visit the EDUCAUSE Policy website at http://www.educause.edu/policy.
Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/discuss.