Email Migration – Info and Tutorials

6 12 2011

Updated 12/07/11 with additional information from IR

IR posted a notice about the email migration this morning, and linked to some additional information and screenshot tutorials that faculty might find helpful. Again, faculty will start migrating (by department) during Intersession, and you’ll get notification emails with specific details in advance.

As you look over the information, please let TAG know if you have any questions or concerns about the email migration process.  A few people have already asked about the firstname.lastname@scranton.edu addresses – we’re waiting for  a response from IR on those questions.

Links:

And here’s the announcement post from IR (link has been corrected):

The migration to the long awaited new email system, Microsoft Live@EDU, will begin later this month.  The new email platform will provide a robust email and calendar environment for all faculty, staff and students.

Migration to the new platform has already begun with the Planning and Information Resources division.  Later this month ALL student email accounts will be migrated from the current system to Live@EDU.  The student email migration will take place December 19th through December 21st.  The migration of faculty and staff email accounts will commence in January 2012.  Detailed information will be sent prior to the email conversion.

Additional information on the Live@EDU conversion is available at http://www.scranton.edu/it_training.

Questions and concerns about the account claim procedure and the Live@EDU conversion should be directed to the Technology Support Center at x4357 or techsupport@scranton.edu.

IR added more information in an email to the entire University community, including answers to some anticipated questions:

  • Email account conversions will be processed weekly on Monday and Tuesday evenings.
  • Conversions will be scheduled by department.
  • Pre-training and post-training sessions will be available.
  • Faculty members interested in converting during Intersession should email their interest to itservices@scranton.edu.
  • RoyalMail will remain available throughout the conversion.
  • You will continue to receive email addressed to you at your legacy email addresses (e.g., smithj2@scranton.edu).
  • Your login to Live@EDU will be your primary email address in firstname.lastname@scranton.edu format (e.g.,john.smith@scranton.edu). Sequence numbers will be added when required (e.g., john.smith3@scranton.edu).
  • Your login to all other University resources, including my.scranton.edu, will continue to be your existing user name (e.g., smithj2).
  • You must claim your Live@EDU account in order to continue receiving email. Following the conversion, all email addressed to you will be delivered to you at your Live@EDU account.
  • You will need to re-subscribe to any listservs or bulletin boards using your primary email address. You will no longer be sending email from your legacy email address.
  • CorpTime and Oracle Calendar will continue to be the corporate calendar solution until June 2012. Calendar users can begin using Live@EDU as a calendaring solution once converted to Live@EDU, however, all users will not be converted to Live@EDU until June 2012.




NYTimes Conference: Bringing Technology into the Classroom

19 09 2011

Update 9/23/11: Video from the conference is (for the moment, at least) available on the conference website.  The opening session and Lawrence Summers’ keynote were among the highlights.

———————————————–

This Thursday, September 22, the New York Times is hosting a conference in New York City called “Schools for Tomorrow: Bringing Technology into the Classroom.” The Times is bringing together influential thinkers to discuss “how technology can – and should – be integrated into the classroom.”

The agenda includes a nice variety of speakers who will be addressing questions like:

  • What should the classroom of tomorrow look like? How can we make the environment more conducive to learning?
  • Can technology really help learning, or are we seduced by the idea of using gadgets in the classroom?
  • How do we make the best use of the technology we currently have available, and on what should schools concentrate their budgets in the future?
  • How can we formalize peer-teaching, individual instruction and independent study, while protecting privacy, data and IP?

The entire conference will be streamed live.  While most of us won’t be able to see the whole thing, we thought it might be fun for interested faculty and staff to be able to watch at least a few sessions together.  So TAG will be showing the college stream throughout the day on campus. Unfortunately, we couldn’t find a room that was available all day long, so we’ll have to switch partway through:

Thursday, September 22  (full conference agenda here)

8:30am – 3:45pm in CTLE Conference Room STT 591
(Welcome, Opening Plenary, Keynote, and Sessions 1, 2, and 3)

4:15pm – 6:15pm in WML305
(Closing Session and Closing Debate)

Please join us for any or all sessions that interest you. All are welcome, and you can feel free to drop in and out as your schedule permits.  BYO coffee, snacks, or lunch.

Comment below if you have any questions. We’ll hope to see you sometime on Thursday!





Connecting to the Academic Webserver

29 07 2011

IR has shared with us these instructions (PDF) for faculty and staff who need to update pages on the new academic server (not the CMS).

As always, if you have questions or run into any trouble, please let us know!

——————–

Update (8/1/11): Instructions were revised – the link now takes you to the corrected PDF. Thanks to Tim Cannon for catching the errors!





Track your tickets with Footprints

25 07 2011

At today’s IT Forum, Jim Franceschelli and Jason Wimmer presented on Footprints, the software that IT Services uses to track service tickets.  The U has been using Footprints for about two years, logging about 12,000 tickets so far.  This summer, IR has rolled out a new end user interface for Footprints, which is intended to help IT Services staff serve users more efficiently.  My notes on what faculty should know:

    • To date, there have been three ways you can report a problem or request a service from the Technology Support Center – you could call  (941-4357), email them, or walk up to the TSC desk in AMH.  Now, you can still use those three methods, but you also have the option of reporting a problem electronically through Footprints.
    • To get to Footprints, go to my.scranton.edu > University Links >  Footprints (under Administrative Links).
    • You’ll see three main options in the Footprints “Service Catalog”:

1. Report an IT Problem. Use this when something’s wrong and you need it fixed.  Pick the category of your problem (computer, phone, enterprise applications, audio/video, Royal Card, or cable tv), choose a subcategory from the options listed, fill out the form with as much information as possible, and then save it to submit the ticket. If you’re not sure exactly what category or subcategory to choose, just do your best – the TSC staff member reviewing the ticket can change the category to reroute the ticket if needed.

2. Change Management. Faculty probably won’t ever really need to use this option – it’s for modifications to existing University applications (changing Banner forms, querying Banner, etc).

3. Request an IT Service. This is for things like requesting multiple PCs for a special event, moving a VoIP phone, etc. You can also use this section to request installation of special software on a University PC. Just like #1, fill out the form with as much information as possible, and “save” to submit the ticket.

  • You can also use Footprints to check the status on a ticket, whether you called/emailed in a problem/request to the TSC or entered it into Footprints yourself.  Click on “Home” and choose from the dropdown menu of “My Requests” to see active and closed tickets. You’ll be able to see TSC staff members’ notes on what’s going on with your request (e.g., if you’ve reported a problem with ANGEL, Jason might leave a note that says that he’s waiting for a call back from ANGEL support staff).
  • Footprints also holds a Knowledge Base (see the link on the top of the page, next to Service Catalog), which holds keyword searchable solutions to common problems, written out by IT staff members.  Solutions are posted either in Q&A format or as step-by-step instructions.  The solutions are reviewed every six months to make sure they’re still accurate.  There are already 80 solutions posted, with more on the way.
  • Any University community member can contribute to the Knowledge Base – so TAG can use it to share technology shortcuts or tips that might be helpful to other faculty or staff.  Just write up your instructions and email them to ITServices@scranton.edu.

Hopefully, the end-user interface of Footprints will resolve some of the faculty concerns about communication with IR that TAG heard back on our Fall 2010 faculty questionnaire – so please give it a shot and let us know how it goes!

I’ll link to Jason and Jim’s slides when they go up, but in the meantime, post in the comments if you have questions.





How to request more space on Royal Drive

5 10 2010

IR encourages faculty to use Royal Drive to back up their files – and if you do this religiously, you’ll find that you run out of space on Royal Drive fairly quickly. But the good news is that you can request additional storage space.  Here’s how:

  1. Log in to my.scranton and go to the University Links tab.
  2. Look under Administrative Links (probably on the bottom left of your screen)
  3. Click on Footprints.
  4. Select Request an IT Service.
  5. Select RoyalDrive Requests.
  6. Select RoyalDrive Group Directory. This isn’t exactly what you need, but it will get your RoyalDrive request going in the right direction.
  7. Click Request this Service (top left).
  8. The form that appears should be prepopulated with your contact info, but make sure it’s correct.
  9. In the Description box, write out how much extra storage space you need (e.g., 1 GB) and provide the folder name for which you want storage (e.g., the RoyalDrive folder I use for Library work is “GroupsWeinbergmemoriallibraryLibraryDigital Services”).
  10. Click Save.

And that’s it – you should get an email confirmation from IR in a few days when your storage space has been added. You should also be able to track the status of your request in Footprints.

(Note: This post was updated 8/31/2011 to reflect the new Footprints request system)





Using Gmail to read UofS Email

30 09 2010

UPDATE 1/10/2012: These instructions are for the University’s old RoyalMail system, which has been superseded by Microsoft Live@Edu. You can find updated instructions in our January 2012 post on Email Migration for Gmail Users.

————————————–

DISCLAIMER : There are important security and policy issues in regards to storing University of Scranton data on non-University of Scranton hardware.  For more information, please see the end of this document

—————————————–

If you’re like me, you’re an email pack-rat. Who knows when something might be useful? You like to hang on to emails and save them, archive them in folders, and squirrel them away until…. you fill up your email quota and go through all your emails, purging pictures and documents from years ago, shedding a few tears for each one. In this post, I’m going to walk you through what, in my opinion, is your best option: migrating everything into your Gmail account.

Why Gmail? Other than its ubiquity (you probably already have a Gmail account!), the email quota itself is worth the switch. Your email quota on RoyalMail is 200 MB, thoughpower users can increase this quota by request. Gmail’s current quota? 7498MB. That’s about 37 times more storage space, AND it keeps increasing. (Need more than that? You can get it, but Google will charge you a couple bucks a month.)

This FAQ will step you through using Gmail for all your University of Scranton email. Other options exist, of course. For example, you can set up email forwarding in RoyalMail (go to settings, mail, choose “enable mail forwarding,” and provide an address). Thunderbird is also an option, but that leaves the mail locally on your computer. Gmail is a web-based program and accessible from anywhere you can get an internet connection, and it will fetch your email is exactly the same manner as Thunderbird will.

So here’s the ever important question: How can I set up my RoyalMail in Gmail?

  1. First, get a Gmail account.  It’s free, quick, and easy.
  2. Next, once you log in, click “Settings” in the upper right hand corner.
  3. Go to “Accounts and Import” and click the button to “Add a POP3 email account”.
  4. A window will pop up asking for the email address that you would like to check. For me, it’s sepinskyj2@scranton.edu
  5. This will open a new window. Type in your password (don’t worry, it’s secure. Just make sure it says “https” in the address bar, and your browser shows you a closed padlock).
  6. Now you have to check some things and set up a couple of options (click “Learn More” in the Gmail window to get even more info). First, make sure the “POP Server” is set to “royalmail.scranton.edu” Port “110”. Gmail is usually smart enough to set this one automatically.
  7. “Leave a copy of retrieved messages on the server” : Normally, Gmail will download the mail locally and then delete from RoyalMail. Your mail will be in your Gmail account, but that is the only place where it is stored. If you would like to access your mail via royalmail.scranton.edu as well as Gmail, click this box. Be warned though, you will still have to worry about your RoyalMail quota!
  8. “Always use a secure connection (SSL) when retrieving mail.”: The University’s servers do not appear to support SSL. Make sure this box is unchecked.
  9. “Label incoming messages”: You have the option to automatically put a label on all the mail coming in from this account. Labels in Gmail are like folders in other mail applications. This will help you keep your “work email” separate from your personal email, if you want to make this distinction.
  10. “Archive incoming messages”: Gmail allows you the option to simply not put the messages in your main inbox. Chances are, you don’t want this button checked.
  11. Click “Add Account” and you should be set to check your mail! It will attempt to access the account and give you an error if you cannot.
  12. Next, you want to make sure that you can send email as your Scranton self, as opposed to your Gmail self. I definitely recommend this, as it looks much more professional. Starting from the same page: Settings -> Accounts and Import, under “send mail as”, click on the button to “send mail from another account”.
  13. Type in your name if it’s not already there, and add your Scranton email address. Click Next Step.
  14. Now you have an option:
  • “Send through Gmail (easier to set up)” : This is easier. BUT, it just looks like the mail is sent from you. It’s doesn’t actually get sent through the university servers. The only place you’ll see a difference is in the email header. If you use this method, it’ll say something like sent by you@scranton.edu, but the actual electronic breadcrumbs will be myaccount@gmail.com. If you’re ok with that, go ahead and click there. They’ll send you a verification email, click the link, and you’re good to go.
  • “Send through yahoo.com SMTP servers (recommended for professional domains)” : This will make sure that it’s not Gmail that’s sending your mail. Gmail will connect to the University’s web server, and literally tell the University’s server to send the mail – so your mail will literally be coming from the University’s computers. When you select this, you’ll be given a set up other options to type in. Simply set: SMTP Server to royalpo.scranton.edu, Port: 465, and make sure you type in your username and password. (Here, you can select SSL if you would like). Click Next, and you’ll get a confirmation e-mail that you’ll need to click. Once you get it, and follow the instructions there, you’re good to go!

Did you try it? Did it work? Let us know in the comment section below!

P.S. Anyone have any tips and tricks for how they manage their mail in Gmail?

———————————————————————————–

Follow-up from Anthony Maszeroski, Information Security Manager at The University of Scranton:

Regarding your most recent post about using Google to read your
university mail:

a.) We really should emphasize that individuals shouldn’t, in general,
be storing their University my.scranton credentials on external systems.
Some institutions have gone as far as writing this into policy.

b.) There are HUGE potential issues with storing University email on
external systems that end users need to be aware of (FERPA,
Court-ordered eDiscovery, Business continuity (access to separated
employee’s email accounts), International legal jurisdiction, PATRIOT
act requests, etc.) See attached draft.

I know that your intentions were good in publishing this article, but it
isn’t sound advice to do this for University-provided email accounts
that are used to conduct official business.

Draft of Potential Security Issues





Software updates and access control (and a tutorial on the network structure of the University)

2 09 2010

MAJOR EDITS 9:35PM, 09-02-2010

Jim Franceschelli posted an update to the university community regarding the newest round of updates that will be coming to campus computers from Information Resources (IR; website). Here is a brief summary of how this will affect faculty and staff at the university.

0) This is the first apparent step (from the faculty point of view) of the more virtualized, transparent interaction between faculty machines and the campus network. While it may not appear so from our point of view, it makes the organization much cleaner on the server-side, i.e., the network administration becomes simpler and less complex, compartmentalizing the network by user type. This is coming right off the heels of a major network rebuild by IR, which means fewer network down times, and shorter network outages (which is a very good thing).

1) Previously, faculty computers did not need to “authenticate” to get access to the university network. This means that any computer plugged into a wall port that was designed for faculty use was allowed full access to the faculty network. This was then controlled on a port-by-port basis: Any computer plugged into the port in your office was connected to the faculty network, regardless of who the computer actually belonged to. And, if you plugged your computer into a port normally relegated for student use, you were relegated to the student network space, which left you unable to access certain network resources (departmental printers, for example). With the recent upgrades to the campus network, each network port now has the ability to be assigned to any virtual network. This means that, when you plug in your computer, you can be assigned to any of the on-campus networks (wireless, student, faculty, staff, dining services, etc., all have their own designated “network space”). Thus, instead of making the decision as to what network you belong to based on where you are connecting your computer, the decision as to what network you belong to is based on who you are and what community you are a part of (e.g., administration, faculty, dining services, etc.). So… where does this new update fit into the whole scheme?

2) The key in the previous point is that your digital identity is now the factor in deciding what network resources you have access to. Over and above that, for security purposes, IR would really like to allow you access to those resources, making sure that you are the one using it, not someone else who has somehow managed to get onto your computer. At the present time, there is no additional level of authentication, i.e., anyone using your computer looks like you. The first and foremost reason for requiring you to install Cisco Network Admission Control is to make sure that the only person accessing your network resources is you. Thus, this piece of software will require you to log in with your my.scranton username and password (which no one else other than you knows anyway, right?). But what about this “up to date packages” part of it all? Well…

3) As we said, this is the first apparent step in the upgrade of our campus network. With the installation of Cisco Network Admission Control, not only does it allow you to authenticate* to the network, this software has some additional advantages over a simple password-only based authentication. Cisco Network Admission Control, when running, has the ability to look at your critical software components (e.g., windows system files, web-browser updates, critical system patches, etc.) and make sure that no identified security vulnerabilities are present. This is not currently implemented into the installation configuration. It will be implemented in the near future (there is a possibility for an October timeline, but this is still in flux), with the added benefit of eventually prompting and directing you through the install of these critical software updates (eventually even doing so automatically) and patches to make sure your computer is safe, protected, and able to get onto the internet.** So where do you fit into the picture?

4) In order to implement this level of security, you will need to have Cisco Network Admission Control installed on your computer. Starting on 09/08/2010 in the first and second floor, west wing of St. Thomas (and following the schedule posted here), IR will be converting the behind-the-scenes infrastructure such that you will not be able to log on to the campus network without Cisco Network Admission Control installed! Once they have implemented this change, your internet browser will alert you of the required software and will (painlessly) step you through the installation procedure to install Cisco Network Admission Control on your machine. You will then be able to log in with your my.scranton username and password*** and continue to access the campus network and the world wide web at your leisure! So… what comes next?

5) As the behind-the-scenes updates from IR progress, you will be periodically required to re-authenticate to the network. This will simply provide some additional security, and allow Cisco Network Admission Control to periodically make sure everything is still A-OK on your computer, look for any flaws or critical system components that have been compromised or are in need of updating, and, eventually, even perform those updates for you! This exciting feature is coming soon to a computer near you!

Please see the below post e-mailed to the faculty today. If you have any questions or comments, please post them below. You can also join the discussion at tag-discussion@royallists.scranton.edu (see this post for instructions on how to sign up!).

* By “authenticate”, I mean “be recognized by”. This is just like showing an ID badge, swiping your Royal Card, or typing in your password at an online shopping site. You are proving your authenticity to the program, and it is allowing you access to whatever resources you are requesting, provided you have met all of its criteria.

** The extra time spent installing the updates is far shorter than the time it takes to fix your computer if it becomes infected with a virus. Currently, it takes nearly 3 full days of analysis whenever a computer is infected by a virus to make sure that no restricted information was passed to an outside source. This is a much more detailed and rigorous process than most are aware of, stemming from federal regulations regarding privacy laws. Hopefully we can post something about this is a future blog entry.

*** The login information for your computer will not change! Thus, your preferred username and password needed to start windows will not change. This will only affect your ability to access network resources (i.e., software not directly installed on your machine).

To All University of Scranton Faculty and Staff:

The University of Scranton provides our campus community with a robust environment consisting of over 2,000 desktop and laptop machines. Managing and ensuring the security of these machines has become increasingly challenging. In order to improve our services to you and increase our information security posture, we will be making changes to the way that desktop systems look and how they operate. Upcoming changes include a move to Internet Explorer 8.0 for using services found @scranton.edu sites, use of Firefox as the default internet browser, automation of additional third party application updates, a change in our anti-virus protection, and the deployment of Windows 7.

The next change that you will experience starting on September 7th is the deployment of the Cisco Network Access Control (CNAC) system for all computers connecting to the University network. This system will require end-users to go through a process similar to the one currently used to connect to the wireless network (RoyalAir); meaning that you will be required to authenticate — enter your username and password — before gaining access to the network. The CNAC system will help us to validate that only individuals who should have access to our network resources will have access and, eventually, will help us to monitor the “health” (up-to-date patches, operating systems, etc) of the desktops that are connecting to our network. Collectively, this will insure a more robust and secure electronic working environment for all of us.

The implementation of CNAC will begin on September 7th and is expected to take 30 days for campus wide implementation. The implementation will occur in small network segments that are grouped by building and by floor. Network changes will be made overnight and users of the segment will notice the change the following morning. To assist end-users, information about the planned schedule for deployment can be found at www.scranton.edu/CNAC-Deployment . IT Services staff will be available and located in each of the affected areas as we work our way across campus.

We appreciate your patience and understanding as we continue to improve. If you have any questions or concerns, please contact the Technology Support Center at 941-Help or at Techsupport@scranton.edu

Special thanks to Jim Franceschelli and Tony Maszeroski for their help in writing and correcting the above tutorial.