Beginning Tuesday, August 21, the college will switch to a new campus scheduling system, Schedule Evergreen. This system will make requesting and confirming campus spaces more transparent, provide students with clear and timely class schedules, and make it easier for you to promote events to the campus and the public.
What to Expect:
- Requesting Space: All requests to use any space on campus will be made through Schedule Evergreen, except for a few administrative conference rooms managed by specific areas.
- Publicizing and Viewing Campus Events Calendars: All requests for space will be accompanied with the option to publicize the event to either our campus community (i.e. students, faculty and staff ) calendar listed in my.evergreen.edu or to the public campus calendar listed on Evergreen’s webpage. Events will be publicized when space is assigned and confirmed.
- Resources for scheduling and promoting events information: A new webpage will go live when the new system launches with information about scheduling and promoting events on campus.
- Schedule Evergreen Overview Sessions: Beginning the week of August 20, we will offer informational sessions focused on non-curricular event scheduling. See below for the first dates and times. During this transition time, faculty can still use their usual method of requesting space for class by emailing Space Scheduling at email@example.com.
Overview Sessions Offered in Academic Computing Lab 2617: Wednesday, August 22, 3-4pm and Thursday, August 23, 1-2pm
As with any system transition, we expect there may be some hiccups along the way. We have amazing technical support and development teams that are prepared for this transition process. We appreciate your patience and support during these next few months. More information to follow!
If you have noticed the attractive construction wall at the entrance to the Computer Center and have been wondering what is going on, the Faculty and Staff Help Desk on the first floor will soon be moving into this new space and becoming the new Technology Support Center. Monday March 26th (break week), Mark Holm, Chris Granado and Andrew Su and their incredibly capable student techs will move upstairs to this new space. We will be offline for the day of March 26th while we make the move, but we should be fully up and operational by Tuesday March 27th.
To start with the hours, operations and support will be exactly the same as before. Over the ensuing months we will be exploring new synergies between technology support in the Computer Center and the faculty/staff help desk, aligning our approaches and discovering operational efficiencies. The vision is to provide a more straightforward and discoverable pathway for anyone on campus seeking technology support regardless of the issue.
As we move into this new configuration I have two favours to ask of you. The first is for patience as we figure out how best to deliver core support services in this new space. Things may take a little longer as we learn about and mitigate impacts from the move.
Secondly, and more importantly, please provide feedback on things you notice, experiences you have both positive and negative, or important issues you would like us to be aware of. At the end of the day we strive to provide the best possible technical support we can, and that is only possible if there is a strong feedback loop with the community we serve.
A special thanks to all the hard working staff in facilities – construction services and custodial services for all of their diligence and attention to detail in creating this exceptional space.
Evergreen is now moving forward with the migration from Banner 8 to Banner 9. This project has been in the works for many months now but it officially kicked off January 2018 in preparation for Oracle dropping support for the form technology that supports Internet Native Banner (INB), the forms interface for Banner 8. The deadline for this change is December 2018, a date not to far into the future.
What does this mean to Banner users on campus? Those who regularly use INB forms will find their work in an updated java-based interface now called Banner Admin Pages. The underlying infrastructure will still be for all practical purposes the same Oracle database. The way people interact with Banner though will shift considerably.
Over the next 4-8 months Banner users will be asked to engage in various levels of testing once Computing and Communication staff move the two platforms into a single/parallel infrastructure, so both Banner 8 and Banner 9 can be used at the same time.
We will be asking our Banner users to test Banner 8 work processes using the updated infrastructure during the month of March. April will then see a shift towards dedicated testing of college workflows in the Banner 9 Admin Pages. Onces these workflows satisfactorily meet the business needs of the different administrative offices, then they can completely migrate their workflows to the new Admin Pages in preparation of the December 31 cutoff of the INB technology. Below is the basic timeline for the project.
The Project Teams:
Business areas of the college are represented by an area lead. This team member will be responsible for attending implementation team meetings, helping coordinate testing as well as building training strategies for the workflows for their and associated areas who leverage similar forms.
Implementation Team Lead
||Curriculum and Registration
||Human Resources and Hiring
||Finance and Budget
Rip Heminway is the Banner 9 Project Manager and will be organizing and facilitating meetings for both the implementation and technical teams. Tony Alfonso is the chair of the Steering Committee who will be making decisions as necessary to ensure that an institutional perspective is maintained throughout the implementation process. The steering committee is tasked with defining/untangling policy related issues, securing critical resources and defining broad project outcomes.
Steering Committee Member
|Tony Alfonso (Chair)
||Computing and Communications
|Rip Heminway (PM)
||Computing and Communications
The management of the project and all documentation will be built in and shared via the Redmine Project Management platform that is maintained by Computing and Communications. If you would like to get access to this more detailed resource, please contact Rip Heminway at X6904.
If you have questions or comments about this plan, please leave them and they will be answered as quickly as possible.
Beginning Monday, October 3 the Time and Leave system at Evergreen will have an updated look and some enhanced views for supervisors. Computing and Communications, in partnership with Human Resources and Student Employment, is very excited to report that the Adobe Flash dependency that prevented many of us from accessing our Leave Requests or Time Tracking on mobile devices like smartphones and tablets is no longer an issue. Updated help articles, including videos, will be available via the Computing Wiki at http://wikis.evergreen.edu/computing/index.php/Time_and_Leave_Help. Enjoy!
Some have asked, what’s the news with all that talk of migrating Evergreen email to cloud Microsoft Office365? Here’s the deal. Computing and Communication (C2) staff worked very closely with Microsoft over the course of spring quarter and into early summer with the intent to go live with the new services before fall. Unfortunately, in the testing phase we discovered some flaws with some of the underlying technologies that we rely on to automate and manage these processes, The result is that we are re-evaluating a new timeline based on the need to upgrade these core legacy systems. Our focus has turned to re-architecting these systems which we refer to in the collective as Identity and Access Management (IAM). This will be the most pressing C2 project over the next few months and once this is completed we can turn back to Office365 and providing all those services to students, faculty and staff.
We will be transitioning the Orca academic file server to Windows 2012. There are a handful of reasons for doing this, including the fact that Orca is currently a 32bit Windows 2008 server and uses Windows dynamic disks for the programs share. Additionally, once the data is on Server 2012 we can take advantage of data deduplication which should reduce the total disk space consumed by at least 10-20%. This space savings is important as Orca is our largest file server.
The transition is intended to be as seamless and unnoticeable to end users as possible. The new server will assume the same name and IP address. Much of the data that needs to be copied from the dynamic disk will be copied over beforehand in order to reduce the necessary downtime. At this time I expect the final cutover to require the server to be unavailable for up to 2 hours. There was a prerequisite for this project of upgrading our ESXi infrastructure to version 5.5.
Project Manager: Josh Jordan
Team: Network Services
- Network Services
- Academic Computing (to help schedule the cutover and provide notification to students)
- Client Services (to help schedule the cutover and provide notification to staff/faculty)
Start: Feb 2014 (with prerequisite work done in Jan)
Jan: Upgrade ESXi to version 5.5 in order to support large virtual disks
End of February: Build replacement server
March 10th-24th – The programs share will be copied (at a slow rate so as not to interfere with normal access) to the new server.
Mar 24th – Apr 11th – Verify that disk quotas, quota templates, the pfcc program, and the various clients supported at Evergreen can connect properly. Also, make sure that DUC can properly provision and delete home directories.
April-May –Schedule cutover with client services and academic computing. This will be dependent on when downtime is acceptable for the server.
Any updates will be added to the documentation here: \\hurricane\PCCommon\Computing and Communications\Orca_Server2012_Migration
We will be moving two of our ExaGrid appliances to the Tacoma campus for storing offsite backups. The ExaGrid replication targets currently reside over in SEM II while the primary ExaGrid backup targets are in the machine room. This required us to first determine how much bandwidth was required to keep replication caught up and then to get the WAN link in Tacoma upgraded to 100Mb.
The project will not change the backup process – only the destination for offsite backups from another building on campus to the Tacoma campus. This should not impact end users at all.
Project Manager: Josh Jordan
Team: Network Services
Start: March 1st, 2014 (estimated)
Completion: April 4th, 2014 (estimated)
Mar 1st-16th – Dan will verify link speed between Olympia and Tacoma campuses and enable QoS rules in order to make sure ExaGrid replication traffic does not impact normal business traffic. He will also configure the necessary switch ports in the Tacoma network closet.
Mar 17th – If Dan’s testing and configuration has completed Josh will notify Albert Villemure at ExaGrid about the upcoming move and coordinate the IP address changes that are needed.
Mar 24th-28th – We will disable throttling on the SEM II link so replications can fully catch up. Then, we will notify the IT System Outage group that offsite backups will be unavailable during the move. Josh will then get keys and physically move the ExaGrid appliances to the Tacoma site and connect them to the network. Once connectivity has been verified Josh will do a test backup and monitor replication. ExaGrid will be notified when the work has been completed so they can monitor the replication as well.
Apr 2nd-4th – Josh will verify that backups are replicating at an acceptable rate to the Tacoma ExaGrid devices.
any updates will be added to the documentation here: \\hurricane\pccommon\Computing and Communications\ExaTac_Migration
The license on our current email gateway/spam filter is expiring soon and the hardware is approaching 5 years and support is ending. The Ironport appliance we currently use is a fantastic product with no equal and we have decided to replace the existing system with the latest version of the same product. Our current setup consists of 2 appliances but only one is licensed. The second serves as a spare in case of hardware failure. We only purchased one new appliance and we will keep the other two as spares. We keep the spare on and fully configured. Cutover is planned for 12pm, on Wed Feb 12th. This will result in a short period of less than 5 minutes where the off-campus mail flow is queued while we transition. No mail will be lost. Queueing is a normal and expected behavior for mail systems.
This project covers only the replacement of the hardware and configuration to exactly match the current configuration on the same software version. We are not making any changes to the configuration or functionality. The intent is zero impact to users and dependent systems.
Project Manager: Joe Pollock
Team: Network Services
- Barbara Caswell
- Joe Pollock
- Network Services
- Client Services (could be impacted by help desk calls if there are problems)
- Academic Computing (could be impacted by help desk calls if there are problems)
- Administrative Computing (could be impacted by automated mail failures if there are problems)
Start: Feb 3rd, 2014
Completion: Feb 12, 2014
Project Plan on Hurricane\PCCommon
This project is to upgrade Mysql databases (version 5.0) on paint to a new VM running Mysql 5.5. Separating paint’s functions into separate virtual machines will allow us to separate cpu/network/memory/io resources and thereby be able to identify and isolate problems. The VMware system has the possibility of having more I/O bandwidth and redundancy.
Mysql Scaling/Clustering: A single master instance will be started at this time. If there is a clear need for more servers AND we have buy in from other groups, I will make Mysql slave instances to offset the workload.
We start moving test databases in the week of January 23rd. If a week of testing works ok, then we will move the production databases February 1 – 14th.
If a database/application doesn’t work after the migration, the original database and application will be on paint until the problem can be resolved. In order to complete the goal of getting off of the old hardware, paint will have to be made into a virtual machine.
Jason Harris, Network Services
- Network Services
- Academic Computing
- Admin Computing
- Web Team
- Others TBD
Estimated Completion Date:
February 21st, 2014
Files, lists of databases, owners can be found in pccommon/mysql55upgrade
Project Summary: This project is to generate a new SSL certificate and replace the current certificate, which expires in February.
1) Find, secure, encrypt, and document a location to store sensitive files.
2) Get the cert:
a) Generate a new CSR from an Exchange 2010 server.
b) Request a duplicate certificate using the newly-generated CSR.
c) Download and store the duplicate certificate with new private keys in the secure location documented in step 1.
Target date for completing this step: 20 Dec 2013
3) Document the process to generate the certificate files required by the various platforms:
a) One .pfx for Windows containing the full cert chain
b) Multiple .pem files for Unix-type systems
c) Public-key-only .cer files, if necessary
Target date for completing this step: 27 Dec 2013
4) Update or create documentation listing all of the servers and associated services (including websites) which require the certificate.
Target date for completing this step: 17 Jan 2014
5) Install the certificate in all the places listed in the documentation mentioned in step 4, and
5a) Verify that all of the affected services (including websites) are actually serving the updated certificate.
Target date for completing this step: 31 Jan 2014
6) On 2/25/2014 @4pm, all the certificate updater staff members should be available to
a) fix any unexpected issues, or hopefully
b) celebrate a job well done.
Project Lead: Keith Hansen
Groups Involved: Network Services
Estimated Completion Date: 31 Jan 2014