Desire2Learn Day – April 24

14 04 2014

Reposting an all-faculty email from CTLE/IR:

Dear Faculty,

Please join us for
Desire2Learn Day
Brennan Hall, Room 509 (Rose Room)
Thursday, April 24, 2014

Several sessions for faculty members will be conducted during the day, as outlined in the schedule below. The highlight of the day will be the lunchtime forum for faculty Desire2Learn – More Than Just a Course Management System.

Desire2Learn is a next generation learning solution, addressing key challenges related to learner engagement, retention, and outcomes. Its design and functionality represent a shift from the simple course management capabilities of an LMS, to a highly pervasive, perceptive, and personal learning experience. Come learn about the advantages of using Desire2Learn for your teaching, and some of its key features, from Desire2Learn representatives.

Also hear about the “real-life” experience of one of our own faculty members, Dr. George Gomez, who is using the D2L learning environment this semester.

You must register by April 16 for the lunch/presentation here (select IT Forum).

All other events on the schedule below are available on a walk-in basis.

  • 10:00-10:30 AM   D2L Open Office Hours – come and ask any questions you have about Desire2Learn
  • 10:30-11:00 AM   Using Wiggio & Blogs in Desire2Learn
  • 11:00-11:30 AM   Incorporating Panopto video into Desire2Learn
  • 11:30-1:00 PM   Lunchtime Presentation: Desire2Learn – More than just a course management system.  Registration Required. Deadline is April 16, 2014.

The following afternoon sessions are open to both faculty and students.

  • 1:15-1:45 PM   Desire2Learn Mobile apps (Binder, Assignment Grader)
  • 1:45-2:15 PM   Using Notifications in D2L
  • 2:15-2:45 PM   Social Media in D2L
  • 2:45-3:30 PM   D2L Open Office Hours – come and ask any questions you have about Desire2Learn




Encryption with TrueCrypt

8 03 2014

Update 2014-07-02: Support for TrueCrypt has been discontinued! Information Security recommends using 7Zip instead – see instructions (.docx).

——————————————————————————-

At our last TAG meeting, Adam Edwards and Scott Finlon from Information Security demonstrated automated Identity Finder scans as well as encrypting files with TrueCrypt (which is free and open source :). At our next TAG meeting, we’ll be starting to identify which departments can move forward with automated scans — so as a reminder, you’ll all want to make sure that any confidential or sensitive information stored on your desktop is safely encrypted.

Scott has sent along some brief  instructions (PDF) for encrypting a folder of files using TrueCrypt — the first page is set up and the second is everyday usage.  Please contact Information Security if you have any questions about encryption.

You can also run your own Identity Finder scan in the meantime – see IR’s Quick Guide if you need help getting started.

Many thanks to Adam and Scott for their guidance on this issue!

 





Email Migration for Gmail Users

10 01 2012

DISCLAIMER: IR has warned TAG that faculty need to be extremely careful about using Gmail.  Our Information Security Manager Tony Maszeroski says, “Individuals shouldn’t, in general, be storing their University credentials on external systems… 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 Tony’s Guidance on the Use of Cloud Applications by Individuals for details.

—————————-

Not that TAG recommends it, but on the off chance that some of you might be using Gmail to read your University email, and should you hypothetically want to continue doing so, you will need to change your account settings in Gmail after your University email has been migrated (see the migration schedule here).

1. The morning after your overnight migration, log in to my.scranton and claim your new account (step by step instructions).

2. The last step of claiming your account is logging out and logging back in to my.scranton, so that you see the Live@Edu icon in the upper right of your my.scranton home page.  Click on that icon to get into your Live@Edu account.

3. Look for a question mark at the top right of your Live@Edu web app. Click on it and select “About” from the drop down menu.

4. You’ll get a page of information. From this page you need:

  • External POP setting: Server name, Port, and Encryption method
  • External SMTP setting: Server name, Port, and Encryption method

5. Log in to your Gmail account.

6. At the top right of Gmail, click on the gear icon and select “Mail Settings.”

7. Click on “Accounts and Import.”

8. Under “Check Mail using POP3,” click on “Add a POP3 mail account you own.”

9. In the pop-up window, put your new Live@Edu email address – for most of us, that’s firstname.lastname@scranton.edu.

10. You’ll then be asked for your mail settings:

  • Your username is your new email address – firstname.lastname@scranton.edu
  • Your password is your new password (remember, you had to reset it when you claimed your Live@Edu account).
  • POP Server – put in the server name that you found on the “About” page of your Live@Edu account.
  • Port – put in the POP port number from your “About” page.
  • Check the box for “Always use a secure connection (SSL) when retrieving mail”.
  • “Leave a copy of retrieved messages on the server”: If this box is not checked, Gmail will download the mail locally and then delete from Live@Edu. 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 Live@Edu as well as Gmail, click this box.
  • “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.
  • “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.” Gmail will attempt to access the account and will show you an error message if it cannot.

12. Next, Gmail will ask you if you want to be able to send mail from your University email account. If so, click “Next Step.”

13. Pick your display name. Your email address should already be there.

14. “Treat as an alias” – Gmail historically has treated your added email addresses as aliases, so it treats mail sent from your scranton.edu address the same way as mail sent from your Gmail address. The option to deselect “Treat as an alias” is pretty new – see Google’s explanation here.  For most of us, you’ll probably want to continue treating your scranton.edu address as an alias, so keep this box checked.

15. Click “Next Step.”

16.  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. 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 scranton.edu SMTP servers”: This will make sure that your mail will be sent through Live@Edu’s servers.  If you select this, you’ll be given a form to type in. Use the SMTP server, port, and encryption method from your Live@Edu “About” page to fill in the remaining boxes.  Your username is still your email address – firstname.lastname@scranton.edu.

17. Click “Add Account.” Gmail will send you a confirmation email. Click the link in that email, or enter the confirmation code and click “Verify.”

18. Done!  Go back to “Accounts and Import” under “Mail Settings” to delete your old account from “Send Mail As” and “Check Mail Using POP3.”

19.  Update any listservs, etc that you subscribe to with your new address.  Don’t forget — you’ll still receive email sent to your old address (lastname2@scranton.edu), but you won’t be able to send mail from that address.





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.




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.