The VPN connection between Middlebury and Monterey is seeing intermittent issues, dropping in and out. It’s being actively worked both here in Middlebury and in Monterey. This will impact all connections between the two campuses, including email and many Middlebury campus based services.
We will update this post when service has been restored.
UPDATE 4:00 PM:
The VPN has been stable since the last message. There is still a concern with the backup systems, but the active VPN is in good health.
There could be one more brief interruption (~2 minutes) before the end of the business day today. We’ll be working with the vendor over the next day or so to find root cause and bring us back to full redundancy.
~Zach Schuetz on behalf of ITS
Users of Adobe’s “Creative Cloud” products (formerly Creative Suite) may have noticed that in the Creative Cloud dashboard, there’s a prompt to “Update” any installed products to the CC 2015 editions. Although normally we recommend keeping software up-to-date, this is a major new version that comes with a few issues:
- There have been some reports of instability with the new software as compared to the 2014 editions.
- After updating from the CC dashboard, the license will not be recognized and the software will be in “trial mode”. This is an unfortunate side effect of the way Adobe does enterprise licensing.
At this point, our general recommendation is to stick with the 2014 version of your Adobe apps. We will update this post with more information as we test the new versions and establish a smooth upgrade path. In the meantime, those who wish to update to the 2015 editions (including “Adobe Acrobat Pro DC”), or have already done so, should make sure all new software that you want is installed, then update the license file. To do this, please do the following:
- Mac users should go to Self Service and run “Adobe CC 2015 License”.
- Windows users should submit a ticket with the MIDD number (on the blue sticker) of the computer in question, requesting to have the Adobe license updated.
If you have any questions, please contact the Helpdesk at 802.443.2200 or firstname.lastname@example.org. Thanks!
Information Technology Services
You may have noticed that no changes to our wireless networks took place yesterday (3/16). We are giving people more time to switch from Midd-standard to the new MiddleburyCollege network. If you haven’t already done so, please take this opportunity to connect your wireless devices to MiddleburyCollege. If you encounter any difficulties, contact the Technology HelpDesk for assistance.
The following wireless networks are currently available:
* MiddleburyCollege is the new, fast, and secure wireless network. A Middlebury username and password or guest account is required.
* MCPSK is the new wireless network for the limited devices that cannot connect to the MiddleburyCollege network, including the following: PlayStation, Xbox, Nintendo DS, Kindle, and Nook.
* Midd-standard continues to be available to provide wireless access to campus visitors.
* The eduroam network is available for guests from participating institutions who don’t have Middlebury credentials.
The MiddleburyCollege network went live on Tuesday, and devices of all kinds have been connecting successfully since. However, we want to give people more time to make the switch, so we will not be removing midd_secure on Monday but rather on the morning of Wednesday, March 11th. We anticipate that Midd-standard will be removed the following week as planned, with a possible delay of one to two days to allow time for those who need to move to the special MCPSK network that will be introduced on Wednesday.
Please take a moment now to connect your device to MiddleburyCollege so you won’t have anything to worry about as we retire midd_secure and Midd-standard. You may see a warning about the certificate, but it is safe to continue and connect. The most alarming warning comes from Windows 7, and looks like this:
Again, in this case it is safe to continue connecting – the certificate is valid, but some devices do not recognize it by default.
Special Note: College-owned Windows 7 laptops should not see the above certificate warning, but may see the following message:
This is misleading; if you click Close and wait 1-2 minutes, the connection should complete successfully.
If you are unsuccessful in connecting to Middlebury College after a minute or two, we suggest rebooting your device and trying again. Any warnings should only appear once – after that, your computer or device should save the configuration settings and reconnect quickly and smoothly from then on.
As usual, please direct specific issues to the Helpdesk; broad questions should be asked here so everyone can benefit from the discussion.
Middlebury College ITS
There was a minor technical issue that prevented us from making the wireless change planned for today (removing midd-unplugged and adding MiddleburyCollege). We are back on track to make the change tomorrow morning, March 3rd.
Further updates as events warrant. Please contact the Helpdesk (x2200) with any questions.
Middlebury College ITS
Over the course of the next several weeks, we will be replacing the wireless networks at Middlebury. (UPDATE 03/13: The first two changes are complete. The final update is scheduled for next Wednesday, March 18th.)
What do I need to do?
Starting March 2nd, please connect to the new secure wireless network named MiddleburyCollege (like midd_secure but better). Middlebury Faculty, Staff and Students will login with your standard Middlebury username and password. Guests will need to create a Middlebury guest account and use it to connect to MiddleburyCollege. This is not a change for change’s sake – we are confident that the end result will be a wireless network that is more convenient and more secure for everyone.
We are currently experiencing network difficulties in the Center for the Arts. We are on the scene and the problem will be resolved as quickly as possible.
This post was made in the fall, but technical issues delayed the implementation. We’re now ready to move forward.
Recently, we at the Helpdesk have spoken with many individuals who were disappointed with the interface and performance of NetStorage, but were unaware of other, usually superior ways to access their files.
In an effort to improve awareness, and in consultation with Central Systems and Network Services, we will be changing the go/middfiles shortcut, currently pointed directly to Netstorage, to lead to our main documentation about Middfiles. Using this documentation, users should be able to quickly connect using faster, better methods and be on their way.
We realize that this will be a significant change for some in our community, but we anticipate that over time, this will help people distinguish between Middfiles, the server system, and Netstorage, a web application that permits limited access to that system and is not intended for daily use. Netstorage will still be accessible via go/netstorage for edge cases like mobile devices that cannot use WebDAV.
The plan is to make the switch within the next few weeks. (EDIT: The changes have been made.) This post (available at go/middfileschange) will be updated with any new information.
As always, we invite your feedback via comments. For specific questions or issues, please make a ticket.