OIT will be re-labeling all the network jacks in all rooms. This will be good for us as most of the jacks were not labled correctly, and it will be good for them.

There should be no network downtime, however as the jacks get labeled there could be some minor distractions.

This is happening now, and could take a week or so to complete. Several research labs have already been completed while the rooms were being painted.

We have purchased several new switches and will be replacing the remaining older switches to upgrade the department to gigabit networking.

The following rooms will have their switches replaced, and will experience some network downtime

• 1118
• 1124
• 2208
• 2212
• 2244
• 3325
• 3329
• 3354

• 1118
• 1124
• 2208
• 2212
• 2244
• 3325
• 3329
• 3354

Currently we run our own Active Directory, however, BYU's Active Directory is now ready for use, and it is already populated with everyone's RouteY ids. Our virtual servers are managed via the VMware Infrustructure Client, which authenticates through the CS Active Directory (we have to create users first, then give them access). We will be migrating the authentication to VMware Inftrastructure Client over to BYU's Active Directory.

Any users that currently manage their virtual servers via the virtual infrastructure client could be effected. As long as we don't make mistakes when we set up access rights through BYU's AD, there should be no loss of access for Virtual server asministrators.

• There is no date set for this migration yet, we are still in the process of preparing the new environment, and testing. We would like to make this change the first part of June.

Currently we use radius to authenticate to our infrastructure (switches and routers). We will be building a new radius server and moving the authentication over to the new server.

This should only effect system admins and helpdesk, but it could cause loss of access to a device, which could slow down any change requests submitted.

There is currently no date set for this migration as we have not yet finished configuration and testing.

After several tests, we were confident that no user impact would be felt. The batteries were replaced

There should be no services interruption due to the battery replacement, as APC documentation states that the power will remain online during replacement. There is a chance though that some departmental servers will go down. I will have to verify, but I think these server have dual power supplies and are connected to an alternate power source, so even if the UPS drops the load, the servers will stay up.

• Saturday, May 2nd 10:00 pm
• Replace the batteries on the APC Smart-UPS 3000 in 1059.

The red light came on several weeks ago, indicating the batteries have died. I ordered batteries, and they have arrived, so we are ready to replace them.