Warning: Cannot modify header information - headers already sent by (output started at /home/sites/alchemy-lab.com/products/atn/asset-network.html:3) in /home/sites/alchemy-lab.com/tracker.inc on line 133

Warning: Cannot modify header information - headers already sent by (output started at /home/sites/alchemy-lab.com/products/atn/asset-network.html:3) in /home/sites/alchemy-lab.com/tracker.inc on line 144

Warning: Cannot modify header information - headers already sent by (output started at /home/sites/alchemy-lab.com/products/atn/asset-network.html:3) in /home/sites/alchemy-lab.com/tracker.inc on line 151

Warning: Cannot modify header information - headers already sent by (output started at /home/sites/alchemy-lab.com/products/atn/asset-network.html:3) in /home/sites/alchemy-lab.com/tracker.inc on line 158
Asset Network
  Alchemy Lab
Network Management
  Download | Buy Now! | Detailed Description | Other Articles

Asset Network

Overcoming licensing hurdle

Purchasing asset network software site licenses (unlimited) works for common applications, but it's not likely that expensive programs like Photoshop or AutoCAD are going to be on each workstation just because it's an architecture and design company. There is no such position as "Software License Agreement Control Officer", so even though it may not be in the job description, system administrators are charged with making sure there are no violations with asset network program. "Corporate Software Piracy Tops 12 Billion" is the headline of ComputerWorld's May 20, 2000, article. Four years later the problem is just as big or even bigger. Unauthorized software installation by employees is a big, big liability that quickly leads to big, big lawsuits. Daily checks to make sure that no licensing agreement is violated and purchasing additional licenses if needed should be a part of daily routine

Workstation anatomy

In order to be able solve problems, IT staff has to have information about each workstation in asset network software. At the very least asset network management should include:

  • Computer specifications - motherboard, hard-drive, RAM, network card, etc. Each hardware component has to be well characterized too.
  • Software specifications - what software is installed on this particular workstation; what version it is; what patches and updates are available for each software title are they installed, etc.
  • Workstation profile - is there enough disk space and RAM; what services are available and which ones are currently running, etc.
  • Location of each workstation - as in building two, third floor, QA quarters.
  • How this workstation is connected to network
  • Names of people who use this particular workstation
Copyright (c) Alchemy Lab, 1999-2008 | Site Map