University Technology Services
Dodge Hall
118 Library Drive
Rochester, MI 48309-4401

General Software Information


FAQ for Adobe Professional X License Agreement 

The purpose of this FAQ is to highlight terms and conditions specific to Adobe Professional X (v10) license agreement that require compliance from an auditing, support, legal, purchasing and technical perspective.  We know that Adobe will not modify the Terms and Conditions for any of the products they offer. It is important that you review the entire End User License Agreement before installing the product.

What am I as the Licensee agreeing to adhere to when using this product?

The licensee is responsible to review the entire End User License Agreement including any hyperlinks to named 3rd Party agreements and or links related to additional agreements with Adobe (such as Adobe support).

What documentation must I retain for an audit

It is important to keep all information related to the sale of the software for an audit, including but not limited to the Purchase Order, paid sales receipt, Serial number of corresponding software and or any information that is printable from an electronic download delivery method.    See section 13 for audit cadence and additional information.

Specifically, according to section 2.11 Dual Boot Platform you must provide proof of the operating system(OS) platform the license was purchased for and that the media sent (especially for dual media packages) that only the intended OS software is running.

Also specific to section 2.5 you must be able to provide a named user and the specific computer(s) associated that the software is running on.  A named user is also required for use of any Backup copies of the software as specified in section 2.7.

The License Agreement references Sections 14 and 16 regarding automatic connections to the internet and product activation.  Why does this happen?

Adobe may activate your products to verify licensing compliance and that the correct number of licenses (per SN#) are running on a giving computer (via IP address).  Per section 14.1. the software may cause your computer without notice to automatically connect to the Internet and communicate with an Adobe website or Adobe domain.  This communication may provide you with additional information, features and functionality.  No Personally Identifiable information is transmitted to the vendor when this happens (per section 14.1.2)  and whenever the software makes an Internet connection, the Adobe Privacy Policy shall apply.

What am I responsible for if an update or additional functionality is offered to me during one of the automatic Internet connections?

If you want to accept an update or additional functionality during an automatic update, it is important to comply with the terms and conditions for that specific update or functionality.  Per section 14.1.4 if you are not presented with additional terms and conditions, the terms of the original agreement shall apply.  Also, if the update is to a previous version of the software you must possess a valid license of the previous version before you can install the upgrade.

 YOU MAY CONTINUE to use the previous version if:

  • You continue to adhere to the license agreement for that version
  • The updated version is installed on the same computer as the previous version
  • You acknowledge that Adobe may not be obligated to support the previous version
  • The previous version (or copies of) are not transferred to another person or device unless the updates are also transferred

What is important to note regarding “Provided by Third Parties”

It is important to note that the software may facilitate your access to Third Party Online Services.  If you use these services, you do so at your own risk and your access and use is governed by the terms and conditions governed by that provider’s site.  Adobe may discontinue the availability of any Third Party Online services at any time.  Any dealings between you and the Third Party are between you and the Third Party Online Services, not Adobe, including privacy policies, use of personal information, warranties, goods and services, etc. It is important that you read the Terms and Conditions for that provider in its entirety.    See section 16.5.2 for more information.

What is important to note related to usage and restrictions related to specific products available in  Adobe Pro X?

Section 16.4 Font software- review Sections 16.4-16.4.5

Section Extended Document- These forms can be used to create a PDF form with data-enterable fields.  You can either do a) or b) for the term of the license. 

a)  Put the data-enterable PDF form on an unrestricted, open access web site, but limit the number of forms processed to 500. Or

b)  Put the data-enterable on a web site that is only open to 500 submissions.

Section 16.9 you may not install FlashPaper Printer on a server for multiple user access or modify or replace the FlashPaper Printer viewer user interface that displays FlashPaper documents.

Section 16.12 Contribute Publishing you shall not connect to the Contribute Publishing Services software unless you have purchased a license and agree to the terms and conditions for the service.

Section 16.13 Adobe Presenter-you will only install and use this add in on a desktop Computer and not on any Non-PC device.

The Export Controls states specific users are restricted from using the software.  Who falls under this category?

Adobe has updated the Export Rules in Section 9 to include the specific end user. Section 9c …“any end user who has been prohibited from participating in the U.S. export transactions by any federal agency of the U.S. government (each, a “Sanctioned Party”).  In addition, you are responsible for complying with any local laws in your jurisdiction which may impact your right to import, export or use the SoftwareYou represent and warrant that (i) you are not a citizen of, or located within, an Embargoed Country, (ii) will not use the Software for a Prohibited Use, and (iii) are not a Sanctioned Party.  All rights to use the Software are granted on condition that such rights are forfeited if you fail to comply with the terms of this agreement. 

This means that you and your department are responsible to understand that all named users  or anyone who has access to the computer where the Software resides do not fall within this category.  This includes any employees, interns, grad assistants, student employees who can access the Software.  Please visit the Lists to Check website at:  if you are unsure if someone requiring access to this Software restricted from using it.

November 2010

Apple Apps

Apple Apps Purchase Process

Apple has created a method by which Oakland University constituents can purchase Apps intended for installation on university-owned iPads or similar devices. These purchases are made using university funds, so standard university purchasing policies apply. By purchasing Apps this way, departments avoid spending university funds on sales tax and departments have the opportunity to make bulk purchases which reduce costs. Departments are encouraged to bundle purchases or partner with other areas to purchase Apps in order to obtain the lowest possible price. Departments may purchase Apps through UTS in order to group purchases and obtain the lowest price possible. Software license agreements and purchases, including apps, are initiated by submitting the Software and Hosted Solution Checklist form.The overall process is:
  • Purchase a Voucher for a dollar amount; this works much like a gift card
  • Redeem the Voucher at the Apple Education Store for specific purchases
  • Note that Apps are non-transferable.  If purchased under one identity, ongoing maintenance cannot be transferred to another identify if the original identity is terminated.
Managing the Process

Before you start, please review Purchasing guidelines for the latest information about Apple purchases:  Purchasing - Preferred Vendor - Apple Planning Device Management
In order to manage this process efficiently, departments should elect one person to be the Device Manager for the iPads. The Device Manager will also be responsible for managing the Department iTunes Account. If the department wants to purchase Vouchers to purchase Apps, this person also assumes the responsibility of managing the Program Facilitator Account (see additional information regarding the optional Program Facilitator Accounts below). The Device Manager will assume responsibility for device (iPad) updates. An ideal cadence may be every 2-3 months, including App/OS updates. The Device Manager may elect to manage using the Configuration Utility. This utility allows the Device Manager to create, maintain, encrypt, and install configuration profiles.

When departments purchase new devices, the Device Manager is required to sync the device to the computer housing the associated Department iTunes account. During the set up process, the Device Manager will be prompted to follow a wizard to navigate through the set up process. It is critical that you “un-check” the “auto-sync” option for the device during this process. This allows all future updates to the device to back up, restore and add only the Apps associated to that specific device.

When the Device Manager is mentioned (below), this term may also apply as the Program Facilitator.

Department iTunes Account (Required)
Set up a department Shared NetID account to create a Department iTunes Account. This account is used to redeem App purchases and to register all of your department iPads to a single iTunes account. An existing department Shared NetID account can be used for this. If your department does not currently have a department Shared NetID, request one through the online forms website NetID- Shared Account Request Form.

Download the iTunes store onto the Device Manager’s computer (this can be either a Mac or Windows PC).
Review the process on how to create an iTunes App Store Account without a credit card The link will provide screen shots and step by step instructions. Once you are prompted, you will need to sign into Webmail using the Shared NetID account. Follow the links and prompts in the email from Apple to verify your account. You are now ready to sync devices and redeem Apps for your department.

Accessing and Downloading Apps
If UTS purchases Apps for you, we will attach an Excel Spreadsheet to the Software Request ticket. This Spreadsheet contains the URL link and the redemption code(s). You can manually type the URL into browser or simply click on it in the document to access iTunes. You will be asked to sign into the Department iTunes Account and the App will download to the Apps in iTunes library.

You cannot download Apps from the device itself unless your device has been synced to the department iTunes account first. Once your device has been synced you will be able to log into the Department iTunes Account through the device and redeem the code(s) sent to you. If you have synced your device to a personal iTunes account that data will be lost, including Free Apps. This is important because the university does not reimburse for software and this allows the departments to retain Apps purchased on university owned equipment after the individual leaves the department or university.
Free Apps
Purchase “Free” Apps through the Department iTunes account so that the App inventory is centrally located when the department users need to sync their devices to the Device Manager’s computer for updates. If your department obtains a Voucher to purchase Apps, or if your department loads free Apps on to a university owned iPad or similar device, note that the iPad use is governed by Policy #207 Business Expenditure Policies. It is therefore unacceptable to load personal entertainment, gaming or other Apps unrelated to the educational and business mission of the university. Purchase of iPads for prizes and awards is also governed by Policy #207 Business Expenditure Policies and is not acceptable. The device may be audited for installed software and licenses.

Program Facilitator Account (Optional)
UTS has a facilitator account and can purchase Apps for any department. We will attach the redemption codes to the software request ticket and JV the department for the cost.  The department can keep an inventory of App purchases from the information sent in the software request tickets. Departments that order multiple copies of a similar App or order in high volume (20 or more of the same App) will want to create a Program Facilitator account to benefit from volume discount pricing. This is an option for departments that will purchase large volumes on a regular basis. This account will allow the department to redeem Voucher Cards. Quotes for Voucher Cards can be created on the Apple Education Store site (see Purchasing web site under Preferred Vendors). A requisition must be sent to Purchasing with the quote for purchase to be completed. Voucher values start at a minimum of $100. If your department requires the Program Facilitator account, your department will be required to create a second account, the Program Facilitator Apple ID Account. This account cannot be the same as your Department iTunes account. Therefore, you must contact the Purchasing Manager to create your Program Facilitator Apple ID Account.

Next Steps: Program Facilitator Accounts
The next series of instructions apply ONLY to departments who require the OPTIONAL Program Facilitator Account.

Create the Program Facilitator Account 
  • Go to and click on “Manage my Account” link.
  • Login with:
  • Apple ID (Facilitator ID created with the help of the Purchasing Manager).         
    Password:  Temporary password - Follow prompts to change your password. Please record this information for your records. When you’re finished, click “Save Changes.”
  • When finished, go to, select the Education Store and sign in with the Apple ID (Facilitator ID) and Password.
Purchasing Vouchers
  • Go to Apple Higher Education store.
  • "Find Your School" enter Oakland University
  • Type in Rochester and Click “Find”.
  • When you see Oakland University and Choose "Sign In".
  • On the Top menu “Solutions and Offerings” select Volume Purchase Program Credit.
  • Select Customize Amount and enter the dollar amount of the Voucher you want to purchase (Minimum is $100.00; purchase in $100.00 increments).
  • Enter your VIP account information as requested
  • Select “Add to Cart"
  • Select "Send Proposal" found just below the Checkout button
  • Submit your requisition to purchasing with the attached proposal.
  • Apple Voucher gift cards are usually delivered via FedEx or Priority mail.

Redeeming Voucher

  • Go to and sign in with Apple ID: (Program Facilitator ID).
  • Click Redeem Voucher.
  • Enter Volume Voucher Code on back of gift card.
  • Click Redeem.
  • Account will be updated with the new dollar amount
Buying Apps
  • Go to and sign in with Apple ID: (Program Facilitator ID).
  • Under Education Store Search for requested App (note iPad versus iPhone Apps).
  • Notice: iPad vs iPhone Apps
  • Click on App
  • Under Purchase Details heading, enter in quantity.
  • Press Continue.
  • Press Buy.
  • Code(s) will be emailed to the Program Facilitator email account.

July 2017


Chromebook Device Management

Decisions to make before/at time of purchase:

  • Designation of a lab manager who will be responsible for managing the devices.
  • Creation of a department shared NetID if your department does not already have one.  This is done so that shared devices are not tied to a specific employee’s NetID.  If that employee changes departments or leaves, UTS can assist with account management including password reset.   If the department needs to create a department shared account, complete the form under Net ID - Shared Account:
  • Once this information is decided, open a UTS project ticket for “Chromebook Device Management setup.”
  • Chromebooks are registered to a main account for Oakland University. By default devices are enrolled into the top level user organization which is managed by UTS. After enrollment they may be moved into your sub organizational unit (steps listed below). 

Do NOT turn on or allow anyone to log on to Chrome before enrollment or the device will need to be ‘wiped/power washed’ prior to enrollment.   Failure to perform this step will not allow the device to register with Google.

  • The NetID password must be synchronized with the Google Chromebook password, using the steps documented here:; Select Gmail IMAP/POP Password Synchronize Utility.
  • When typing in the user name in the Chromebook it must be the full NetID including the full domain name (i.e.

Decisions to make before the enrollment process:

  • Tag and name your devices – have the information handy because at enrollment, a device will only be identifiable by serial number; you will later have a chance to add/modify the identifying information.
  • Think about the uses of the devices and how they will be managed:

o   Do you want them to start up to a certain webpage?

o   Custom wallpaper?

  • If you wish to apply different ‘policies or settings’ to some of the devices, you will need separate organizational units for each ‘group’ that will share a policy (i.e.  If you have 10 Chromebook for student use and two larger Chromebase units for kiosks they would need to live in separate organizational units (ou).   A ticket will need to be submitted to UTS for the creation of the organizational units you will need, or you may be given permissions to create the “ou’s”
  • By default, devices are enrolled into the top level user organization which is managed by UTS. After enrollment, they can be moved into your sub organizational unit. 


Helpful articles and tips to read before you begin the enrollment process:

  • Be patient, if you are enrolling multiple devices at once, many behave differently and have unique errors.  Dedicate time to work through them and note that often the speed of the process will not be consistent.
  • Enrollment guidance
  • Ephemeral mode


When you are ready to enroll the devices:

  1. Turn on device.  You will see a welcome screen where you can configure Language, Keyboard and Wi-Fi. Select Grizznet and Continue.  Helpful hint: on the network drop-down you will be able to see the Wi-Fi Mac Address if you need to collect that information. 
  2. The next screen will be your Google Chrome OS Terms. Read, then select Accept and continue.
  3. Complete your connection to the Internet through the screens.
  4. Select ‘Students, Faculty and Staff’ and select Start. 
  5. Use your shared lab account NetID to register the device.
  6. And wait…. at times the process can hang up at this screen or not show this screen at all.  If you encounter “This host is already registered”, wait 1-2 minutes.  You may see “Chrome updates automatically screen” and the process will work itself out or go to a spinning circle.  If successful, the next screen will be the Chrome login screen.  Press ‘Ctrl-Alt-E’ to get to the Enterprise Enrollment Screen.
  7. If the registration screen is not progressing or displaying an error, check the date and time of your machine.  If the date is off, the device may not be recognized properly
  8. If “This host is already registered” does not update and the wireless icon still has the exclamation point by it, disable the Wi-Fi, shut down the Chromebook and restart.  Follow the screens upon restart and it may resolve the issue.
  9. If you see the spinning circle and have waited 1-2 minutes try pressing ‘Ctrl-Alt-E’ to get to the Enterprise Enrollment Screen.
  10. At times you may also see ‘oops, something went wrong with signing in’. Try pressing ‘Ctrl-Alt-E’ combination again and wait.  If this does not work – you may need to shut down and restart.  Sometimes the screen will reappear again after restart, but by pressing the ‘Ctrl-Alt-E’ combination again and waiting the enterprise enrollment screen will appear.  At times it happens immediately, other times there can be a 30 second to 1 minute delay. Be patient.
  11. At the enterprise enrollment screen, sign in to with your shared lab account NetID.
  12. Continue the sign in process at the sign in screen
  13. You will see a “enrolling your device screen”.
  14. If successful, you will see the green checkmark and success screen. Click Done and your device is ready to manage/use.  At this point your device is in the top level domain. Go to your Device Management page to move it into the correct organizational unit or sub unit.


Managing your devices:

  1. In Google Apps, select the Admin icon – this is the Admin console from which you will manage your devices.  
  2. From your Admin Console, select Device Management.  
  3. Select the ‘Chrome Devices’ icon (Choose chrome management to edit settings for User, Public Session, Devices and App Management –or - choose Chrome devices to see all of the devices in your organizational units).  
  4. You will see the latest enrolled (provisioned) device.
  5. Click on the blue serial number.  Choose Custom Fields.  
  6. Select Edit.  
  7. Add your device and location to the Asset ID and Location fields so it will be more easily identifiable in the list of devices. 
  8. Save when finished.
  9. Return to the Chrome Devices list by selecting Chrome devices in the menu ladder
  10. Put a checkmark next to the newly provisioned device and in the Move to drop-down menu, select the organizational unit where you would like it to be placed. Highlight your selection and choose Move to Organization. 
  11. You may encounter different screens, messages and/or errors.   Screenshot images may change as they are updated by the Chrome browser/login process. These changes are beyond the scope of this document, but perhaps have been encountered by another Chromebook management user.  Please inquire.



Google Ordering Processing Requirements Form:

This form needs to be completed each time a department want to manage Chromebooks for their area.  When the UTS ticket is opened to initiate the request to be added to the main account for Oakland University, UTS will need to complete the form and submit it to Google.

October 2015 

& Imaging

Document Management & Imaging

Current State

Banner Document Management (BDM) is the preferred campus enterprise document imaging solution. There is also a legacy campus implementation of EMC (Documentum) ApplicationXtender.

Banner Document Management is a centrally funded software solution available to campus departments. We are gradually implementing the solution through the campus. Information about implementation plans can be obtained by sending an email to Consulting services for implementation are provided by Strata Information Group (SIG).

The Value-Added Reseller supporting the legacy Documentum environment is MetaSource. We are not adding user departments to this environment.

Departments are responsible for implementation and training costs, unless UTS has arranged for project funding. Departments are responsible for the purchase of a scanner, scanner maintenance and supplies, and ongoing training and support.

Department References

UTS maintains a list of departments using the Documentum solution in production. There are 3 departments on campus willing to demo the system:

  • Development and Alumni Relations
  • Undergrad Admissions
  • Purchasing

System Components

The Banner Document Management environment consists of the following components:

  • ApplicationXtender- Web browser access from the end user’s computers to view, modify, organize, index and store scanned documents based on the end users’ authorized permissions.
  • Banner (although not required for all applications)
  • Scanner – Specific hardware device to create document images, including maintenance and supplies to operate the hardware.
The Documentum document management environment consists of the following components:
  • ApplicationXtender- Web browser access from the end user's computers to view, modify, organize, index and store scanned documents based on the end users’ authorized permissions.
  • Kofax Capture- Software that captures and stores information from the images scanned.
  • Ascent Capture license- Scan station software that converts the paper documents into images, text and data for delivery into the document management system.
  • Scanner – Specific hardware device to create document images, including maintenance and supplies to operate the hardware.

Procurement Process

There are 3 groups involved in the implementation of document imaging system:

  • Requesting Department
  • Purchasing
  • UTS

The Requesting Department should be prepared to answer the following questions:

  • Is a scanner in place or does one need to be ordered?
The Requesting Department will need at least one scanner. If the Requesting Department already owns a scanner, the Requesting Department will need product details to verify compatibility. The departments who have deployed the system can make suggestions or recommendations. The rest of the system, including accessing scanned documents, can be accessed using standard desktop computers.

  • How many end users are involved in your project?
How many users will access the documents? Consider both end users in the Requesting Department and those in other departments with whom the Requesting Department intends to share documents.

  • Define a name for your ApplicationXtender Group.
The name of the Requesting Department should be used as the first component of a Group Name. In the Banner Document Management System you may wish to have multiple groups with varying privileges. Additionally, the Banner Document Management system allows for Document Level Security groups which can give or take away user access to specific document types.

  • What documents will be scanned?
The Requesting Department will estimate the number of document pages scanned each year. The Requesting Department will also classify and organize the documents by type. What documents will be scanned, and what documents are outside project scope? Please note that document storage is a cost for the university. Documents already stored electronically in a different system should not be stored again in the document management system. Consider whether document storage will be implemented going forward, or whether historical files are also included in the scanning project.

  • How will documents be indexed?
An indexing scheme for organizing the documents must be defined. Documents must be indexed so that the documents can be easily found and retrieved. Student numbers and names are often useful for indexing student files, for example. A cross-referenced index (such as student name and student number) is better than a single index (such as student number alone) to avoid processing errors.

  • The Requesting Department will decide who will be responsible to scan and index.
Departments usually have one designated person for this task; this is typically a full time job depending on document volume. If the project includes scanning historical files, a plan for short-term staffing assistance may be needed.

  • After documents are scanned, designated users will need access permissions to the documents.
The Requesting Department needs to define document access permissions. The options for Documentum are:
  1. Modify – Users who can view and modify documents in ApplicationXtender
  2. Scan – Users who Scan and Validate in Kofax; these users also typically have the ability to modify documents in ApplicationXtender
  3. View – Users who View documents in ApplicationXtender
Banner Document Management groups need to have their privileges defined in accordance with the group function. Some examples are:
  1. Admin - Full scan, index, deletion, annotation and redaction privileges
  2. Maintenance - Scan and index privileges, page deletion privileges
  3. Scan - Scan and index privileges, no deletion privileges
  4. View - Display and print privileges
A list of Banner Document Management user privileges can be found here: Insert link

  • Create a security map for the documents.

This is easiest if you make a grid, such as this table (example):






Identification Documents (i.e., birth certificates, visas, etc.)

Main Office




Identification Documents (i.e., birth certificates, visas, etc.)

Scanning team




Identification Documents (i.e., birth certificates, visas, etc.)





Project Approval

Once the Requesting Department has all of the above information available, open a ticket with UTS by sending an email to

UTS will assign the UTS Consultation Group, including Purchasing, to the ticket. The Requesting Department will work with Purchasing to obtain a quote so that the project costs can be determined.

Purchasing will provide the contact information for SIG, obtain a Statement of Work (SOW) and a quote for the training and implementation fees.

Once the Requesting has approved the SOW, the quote, and the necessary funding source, the department will initiate a Purchase Requisition on the department’s fund using standard university purchasing procedures. The Requesting Department will submit a second requisition to purchase the scanner, if needed.

At that point, UTS will update the ticket categories to Departmental Applications, Imaging / Document Management. Ticket assignments will change to Windows System Administrators, Systems Integrator, Data Administration, and Operations Manager to the ticket.

If the project is not approved, UTS will instead resolve the ticket.

Account Creation

Based on the information in the ticket, Data Administration will update the Account Creation form to support the project. In the case of Banner Document Management, the Requesting Department's existing Banner Access form can be altered to include the necessary user groups. Once Data Administration has updated the forms, the Requesting Department will access and complete the Documentum Account Request form or the departmental Banner Access form found on the webpage Please allow 2-3 business days for these accounts to be created. Thereafter, new account requests are submitted via the form.

For Documentum use, create a ticket with UTS by sending an email to to request access to the following folder on Appx01 for all the users who will have the Kofax client installed on their desktop systems:  C:\Documents and Settings\All Users\Application Data\Kofax\CaptureSV

Installation and Training

Banner Document Management training from SIG generally lasts two and a half days with the remaining half day optional for additional questions and concerns. Topics covered in BDM training are:

Training outcome goals
System overview
Document types, indexes and queries
Banner integration
Forms and context rules
User and group privileges and security
Process development


Digital Signage

Oakland University has a campus wide solution for digital signage through Visix Software. Departments interested in purchasing digital signage will need a dedicated Content Manager/Content Creator and a Department Representative to manage the hardware installation (this can be the same person).

The Content Manager will be responsible to take web-based, end-user training for the software. Departments must plan at least 90 days for the completed installation process including “Go Live.”

The process for Digital Signage procurement and installation is described below.



Contact Purchasing to obtain quotes for hardware including but not limited to:

  • Static and Interactive Displays (various sizes available)
  • Mounting brackets
  • Content players - these devices are mounted directly to the display and run the content from the software
  • Device Controllers - these devices manage the power on/off of the device at set times
  • Installation
Facilities Management
  • Contact Facilities Management to schedule a walk thru to review and identify the approved location to mount the digital display.


Contact the following departments after a requisition has been submitted. All of the following requests can be entered in parallel to the requisition being submitted.


A ticket will need to be created before any hardware is delivered. Create a ticket by sending an e-mail to requesting Digital Signage. Some work cannot be performed until after the hardware is installed. You will be required to keep UTS updated in the ticket as each stage of the installation process is completed. This ticket will track:

  • The request for a network data drop if one is required. The data drop will require 2 data ports. There is an additional charge to the purchase for this work.
  • The request for a Dynamic Host Configuration Protocol (DHCP) for the Content Player and the Device Controller and configuration of the Device Controller.
  • The request for configuration of the Content Player.
Facilities Management

These requests should be submitted in parallel to the UTS tickets above.

  • Submit a work order for electrical. Static televisions require 2 electrical outlets and interactive stations require 4 outlets. There is an additional charge for this work.
  • Contact Capital Planning and Design to schedule the hardware installation for both the mounting brackets and the displays with the vendor. The mounting brackets and displays are installed separately. The content player should be installed with the power button and USB ports exposed with the ability to access them as needed. The Device Controllers need to be configured by UTS BEFORE they are installed.
UHR Technical Training
  • Contact UHR for the Visix Software end user software training.
  • View the introduction video and pass a short assessment. Once you have passed the assessment, it will direct you to the training enrollment page.
  • As a content creator, the two webinars you need to enroll in are:
    • Content Creation
    • Managing Content
  • Once the training is complete, UHR will create a ticket to request an account for the Content Manager. The account login for the digital signage software will be Content Manager’s NetID.

A detailed training guide is available once the training webinar has been completed.

Communications and Marketing
  • Contact your C&M account representative to review and discuss the approved templates for use. To find your account manager review the Account Manager Directory