Managing distributed computer assets

Colleagues,

For the better part of a decade, we have not formally tracked university-owned personal computers (desktops, laptops) due to decision by the university to not track items costing less than $2500.  We have maintained and evolved fairly mature network connectivity policies that establish requirements for all devices connecting to a campus wired- or wireless networks (both university-owned or personal). 

Today, we’re migrating users and computers to a new federated directory service which involves movement away from legacy directories and discovery and connection of formerly unconnected devices.  While getting to a single directory will dramatically simplify our EA and give us single identity efficiency, it will also give us much needed visibility of distributed assets and help us tremendously in better handling security, software and asset management.  As you might expect, our migration teams are experiencing some pushback from users when they are told that all university-owned devices will be domain-connected. 

I’m hoping that some of you might be willing to share with me your local network and computer policies pertaining to things like domain-connection, requirements for connecting to university networks, etc.  I’d appreciate the input either here or offlist.

Thanks!

Rich.

____________________________

Richard A. Whitney, Ph.D.

CIO/VP Information Technology

University of Alaska – Anchorage

907-786-4754 (o)   |   907-360-7755 (c)

rich.whitney@uaa.alaska.edu

http://cio.uaa.alaska.edu

в

Be a UAA skeptic!!!   NEVER give any personal information to an email requestor.  No reputable organization will ever ask for your username, password, or any other personal information via email.