Faculty & Staff Software:
Microsoft Client/Server Systems

Restrictions | Licensing | Managing Client Software

Our “Select Agreement” with Microsoft provides significant discounts on server software. When you purchase and install server software for any use at DU, it is your responsibility to understand the conditions of our agreement and honor them.

Usage Restrictions

We are not allowed to provide any commercial hosting services with products purchased under our agreement. An example of commercial hosting might be allowing a business that is not directly affiliated with DU to use software on DU servers in exchange for fees, goods or services in kind.

You may not disclose the results of benchmark testing for any server products to any third party without Microsoft's prior written approval.

Licensing Microsoft Server Products

Microsoft Server Products, such as Windows 2003 Server, Exchange Server, BackOffice, SQL and other server products require not only a license for each server running them but also a Client Access License (CAL) for each client accessing the server. CALs must match the version of the server; if the server is running Exchange 2003, the client must have an Exchange 2003 licensed install.

The maximum number of devices allowed to access a server is equal to the number of CALs purchased for that server. Microsoft refers to this as "per Server" mode.

Client Access Licenses (CALs)

Client Access Licenses (CALs) allow a client to access server-based applications. For applications covered under our Campus Agreement (see Single-User Software), you will not need to purchase CALs for DU employees. Please remember: Our Microsoft contract does not cover Client Access Licenses for students. If students need access to server-based applications, you will need to purchase the necessary licenses.

How to purchase licenses through our Select agreement

  • Determine if you need to purchase media (CDs)
  • Submit a Purchase Request for the proper number of licenses (one per system) and the necessary CDs

Don't forget to purchase media (CDs) as needed. When you make a purchase through our Microsoft agreements you are only purchasing a license to install. If you need media, include it as a separate item in your Banner Purchase Request. If you have pricing or other purchasing related questions, please contact Dave Wiley (dawiley@du.edu) for more information.

What about a license key?

When you purchase Microsoft products under the Select Agreement, you will receive a certificate with the specific license key. It is your responsibility to monitor the number of installs to ensure they do not exceed the number of purchased licenses.

Managing Client Software

Reinstalling software

You may have two license (or CD) keys for some software: one on a CD from the vendor or OEM (Original Equipment Manufacturer) of your computer or operating system and one on the CD obtained from UTS or given to you over the phone.

For operating systems, you must use the key you have for the actual operating system, NOT the one for an upgrade, if any. After you reinstall the operating system, then you can apply an upgrade. For the upgrade, you would use the key for the upgrade, which you probably obtained from UTS.

For other software, use the appropriate key for that software.

Cloning Several Computers

You need to use the Campus Agreement license key and software when cloning. You cannot clone with OEM software. If any of the machines are to be cloned, they MUST be reformatted and the Campus Agreement license media and key used to install the software.

If you attempt to image with a 1-2 CPU license of XP or 2003, it will not work, plus it would break copyright laws.

Using Ghost and SYSprep

In order to use Ghost and SYSprep, Microsoft has instructed us that we have to use the volume licensing media, which means machines have to be reformatted. Specifically, non-enterprise Windows XP OS versions only allow a maximum of 2 SYSprep configurations. After 2, the OS will not allow another sysprep session. For example, you create an image and run SYSprep. You then run Ghost and find you forgot a few things. SO, you go back to the master machine, make the changes and run SYSprep again. You then run Ghost and find again that you forgot a few things, but you cannot run SYSprep again.

More importantly, the OEM versions of XP allow 1 Product ID code for 1 CPU. If you create the image using the OEM version of XP and then try to use the Select Volume Purchasing Agreement key for the Ghost INI file, it will NOT work. It is critical that you understand that the OEM version of XP is DIFFERENT than the Select Volume Purchasing Agreement version of XP.

To acquire a recent version of Ghost, please contact:

Richard Henderlight (rhenderl@du.edu) 303.871.2109