Central Device Management FAQ

What does Central Device Management mean?

• A process by which administrators are able to manage the deployment and security of devices and applications across an enterprise. 

What are the specific benefits of Central Device Management?

• Centralized management of university-owned devices will deliver efficient customer service, increase computer security, and provide other valuable options in support of strategic technology advancement across the institution.
  Gathering and maintaining accurate information about university-owned devices streamlines costs associated with application development, software installation, computing support, system administration, and software licensing.
• Limiting exposure of data stored on university-owned devices is a priority. Centralized device management is foundational to the best use of IT resources.

What is a managed device?

• A managed device will use a software tool to keep the device in a secure and stable state. The software reports the technical, internal components of the device such as brand, model, manufactured year, serial number, version of Windows or Apple macOS operating systems, and security vulnerabilities.
• The software can also be used to remotely install requested software and keep the OS up to date, with scheduled monthly updates.

Why are we doing this right now and in such a short time period?

• A majority of the Windows based computers on campus have had this software installed for years and it has been working successfully. The effort now is to focus on installing the software on the rest of the computers on campus. This applies to all Windows and Apple macOS devices.
• Because many faculty and some staff are off for the summer and this work needs to be completed before the start of the fall semester, the software must be deployed before the end of the spring semester. The efforts you are seeing now could not be initiated until proper preparations and planning had occurred.

Why wasn’t there more communication before it started?

• Each college or department may have unique rhythms and needs, so communications were shifted from the university-wide medium to the IT staff that locally support you so they can work directly with each college and department. IT support staff have been in contact with many of the department administrators to coordinate and communicate office visits by area.

What does the software being installed really do? Is it spyware?

• It is not for “spying” on your usage of the internet or your work. The software does not gather this information.
• It reports the brand, model, serial number, operating system version, machine address (aka – MAC address), and a list of installed software.
• Enables IT to centrally deploy fixes for security vulnerabilities to protect student data, research data and university data.
• Provides faster installations of enterprise software such as: Adobe, Microsoft Office, Zoom, Google Chrome, Goolge Earth, and desktop shortcuts for tools like Banner, BBLearn, VandalStar, etc.

Why is this software necessary?

• Is one piece of a strategic security plan for protecting personal data as well as university data.
• Is a part of required security compliance measures that today’s accreditation and grants are demanding.
• Helps you receive faster responses and often proactive support for technology incidents and requests.
• Provides information for decisions around technology and data risk management.
• Enables analysis to help manage device lifecycles and provides visibility into this segment of technology costs.
• Automates routines so IT staff can focus on work of a higher value to you and the university.

How will the software be installed?

• IT support staff will visit all offices in all units/departments/buildings across the Moscow campus at some point over the next six to eight weeks. Scheduling will go through departmental administration. IT support staff is doing everything we can to accommodate faculty and staff involved.
• If IT support staff does not visit you and your computer, it is likely that the software is already running on your computer.
• There will be drop-in sessions at the Student Technology Center at the TLC Rm 128.
• The top priority is to complete as many faculty device updates as possible before Dead Week and Finals Week, with a target completion date of April 19, two weeks ahead of the start of final exam week.
• Faculty devices not completed by April 19 will resume after May 15 (after final spring grades are completed).
• Staff/administration visits will continue beyond April 19, being mindful of areas involved in semester-end processes.
• Mac users must be present when IT support staff installs the software.
• Non Windows and non Apple macOS computers must be inventoried and manually added to IT asset management system.

Why do you have to come to our offices to install this software?

• An IT staff person may need to validate or modify device names and connections to enable the software to be installed.
• IT staff will need to work on the computer only when absolutely necessary to complete the software installation.
• You will have an opportunity to drop-in with your laptop at the Student Technology Center if an office visit isn’t possible or easily accommodated. Watch for announcements of these drop-in session dates and times.

What about IT staff potentially seeing FERPA protected data in our offices?

• IT support staff are all FERPA certified and as such, are legally and ethically obligated to protect the confidentiality of student records.

Will I be able to control when the software updates occur?

• One of the benefits to Central Device Management is that IT staff can schedule and communicate about when updates will occur. Where possible, the updates will give you a window of time for the updates to be deferred before requiring the update be completed (default is 24 hours). 
• These updates are scheduled by ITS staff to most often run overnight or otherwise after 5pm.
• If there are specialized needs, you can work with local IT support staff and may be able to request an adjustment to the rollout window.

Special Circumstances and Acknowledgements

We understand all plans have exceptions and special circumstances to consider, and the CDM program is no exception.

• Linux systems will be deferred to complete at a later date.These systems still need to be inventoried for CDM program
• Exceptions will be evaluated case by case.