|Title||Start Date & Time||End Date & Time|
|Service Maintenance Scheduled: RedHat Enterprise Linux systems||Wednesday, December 2, 2015 - 7:00am||Wednesday, December 2, 2015 - 7:30am|
|Service Maintenance Scheduled: HR Resources||Friday, November 20, 2015 - 5:00pm||Thursday, December 3, 2015 - 9:00am|
OIT is responsible for maintaining the campus area network and for connecting individuals and groups to University of Colorado network resources and the internet. Networking resources include cabling, switches, routers, subnets, IP addressing, DNS, wireless networks, off-campus access and more.
See below for a detailed list of services.
|Service||Who May Get It||Features|
|eduroam Secure Wireless||Faculty, staff, students, and visitors from participating eduroam institutions||The eduroam service is a secure federated wireless network service available on the CU-Boulder campus or one of the hundreds of other institutions in both the United States and world-wide.|
|UCB Wireless||All CU-Boulder affiliates with an active IdentiKey||UCB Wireless provides easy access to the network in approximately 90% of all indoor building space on campus.|
|Guest Wireless||Any guest visiting the CU-Boulder campus.||
Wireless access for CU-Boulder visitors that doesn't require an IdentiKey. Connections last for 18 hours.
|Wired Internet||Faculty, staff, and students||100Mb standard connections in university buildings, residence halls, and university apartments. 1Gb (GigE) connections for faculty and staff whose work would be impeded without GigE.|
|VPN (Virtual Private Network)||CU-Boulder affiliates with an active IdentiKey||A service that provides a secure on-campus network connection both on and off campus. Visit the VPN service page for downloads and documentation for the Cisco AnyConnect client, custom VPN service, and much more.|
|Name & Address Management||Faculty and staff||Static IP addresses for systems, printers, and devices.|
|Dynamic DNS||DDNS is available to any clients using private IP address space in the campus Active Directory.||Client systems should be on subnets in private IP address space. Client systems should be participating in the campus Active Directory.|