Computerized Testing and Computer Labs

24 02 2011

TAG has recently received concerns about the computers in the Hyland 102 computer lab not working properly when they’re needed for computerized testing.

Upon hearing the concerns, IR’s response was that none of the problems had been reported to the Technology Support Center – and they can’t fix computers if they don’t know they’re not working.  IR recommended that faculty be sure to report malfunctioning computers to the TSC, so that the right people can take care of them – and said that classroom and lab resources get the highest priority.

Does anyone have any comments on this? Have you had similar experiences? Do you report problem computers to the TSC when you come across them?





February IT Forum

18 02 2011

Yesterday, the Department of Planning and Information Resources held a very well attended forum where they discussed the switchover from RoyalMail to the new Microsoft Live@edu software to manage our university’s email. Some of the key points brought up were:

  • Your access information will likely change to a permanent, unique identifier (likely your R-number). Your e-mail address will not change.
  • Migration of users to the new system will begin in the Summer of 2011, starting with the staff.
  • Faculty email conversions are slated to begin (on a department-by-department basis) the 3rd week of the fall semester.
  • Early adopters are welcome! Starting in the Summer, any faculty who wishes to convert their email early will have the option to do so. When we find the procedure for this, we will let you know asap.
  • There is a hard limit of 10GB on the new email system. Requests for a more storage cannot be honored for any reason. This is due to the limits of the software implementation and is dictated by Microsoft.
  • Mail stored in your webmail will be moved to Live@edu without any effort on your part.
  • Mail stored on your local computer can be moved to the new system. There are a number of software packages IR is looking into that can facilitate this, but it will require some intervention by the user.
  • Since there is a 10GB limit, you should make sure you have less than 10GB of mail stored on your local drive. Vince Yanusauskas put together a short handout to check the amount of email stored on your local computer. You can find that here. If you are storing less than 9GB, you have nothing to worry about!
  • If you are storing files via Thunderbird or Outlook on your local hard drive, please post below how much you’re using. We’re interested in knowing how many faculty might run into this 10GB limit.

You can download the full presentations here.





Email Transition: A Note about Old Email

15 02 2011

TAG has heard some concerns among faculty lately about the upcoming email transition to Microsoft Live @ Edu.  Most of the concerns have centered around making sure old email can be migrated into the new system.  Here are a few clarifications:

  • If you use RoyalMail and Thunderbird, there are two places email can be stored.  Each faculty member currently has 200 MB of space on RoyalMail – that email is stored on an on-campus server.  But many people have additional email stored in “local mail” folders – this email is stored on your computer’s hard drive.
  • Email stored on the RoyalMail server (that 200 MB) will be migrated into the new Microsoft Live @ Edu cloud environment by IR.
  • Instead of the old 200 MB quota on the RoyalMail server, the Microsoft Live @ Edu system allows each user to store 10 GB worth of email.  We’ll soon be sending out some instructions for how to figure out how much email you have stored on your local system so you can tell how close you are to that limit.
  • There will be a way for faculty to migrate their local mail from their hard drive to the Microsoft Live @ Edu system.  We don’t have specifics from IR yet, but faculty will not lose access to their old email.  Faculty, as end users, will have to actively do something to help move their mail once the transition time comes – but we don’t have to do anything yet.  During the transition, CTLE TechCons will be on hand to help faculty with the migration.
  • IR is not against faculty migrating their email to Gmail instead of using Microsoft Live @ Edu, as long as we keep in mind issues of Personally Identifiable Information (PII).  The University has to comply with increasingly strict federal laws, like FERPA, that protect PII.  Any information dealing with a student’s “educational record” should not be stored on Google’s servers.

The bottom line is – don’t panic, you’ll still have access to your old email.  If you have questions or other concerns about the email transition, please let TAG know!





CNAC Update

9 02 2011

How did the CNAC update go for everyone this morning? Any problems?

 





IT Update: What it Means for Faculty

8 02 2011

All faculty and staff got an email from CIO Jerry DeSanto this morning, and  I thought it might be helpful to try to pull out and discuss what’s specifically relevant to faculty.  Here’s my take, though IR staff and administration are welcome to comment or clarify.

Jerry mentioned that IR has three priority projects:

1. “Converting the platform on which our enterprise resource planning system (Banner) runs on from VMS to Linux.” This change doesn’t have much of a direct impact on faculty, other than that it’s a major upgrade to the University’s infrastructure.

2. “Implementing phase one of an Identity Access and Management (IAM) system.” The main impact of this change on faculty will be that we’ll soon be asked to use our R numbers as our user IDs.  We’ve discussed this previously on the TAG site, but as a quick reminder, the main reason IR gave us as to why this change is coming is so that each user will have a unique, immutable ID. And this needs to happen before we can move to Microsoft Live @ Edu.

3. “Establishing Active Directory domains for devices and individuals.” Active Directory is a Microsoft service that will sync your Windows account –  you’ll be able to access synced files from any computer on campus.

Jerry points out in the last paragraph of his email that a main impact these three projects will have on faculty is that they’re taking up quite a bit of time and energy on IR’s side – which means that we might need to be patient when we have special requests that require IR staff time.

Reactions, thoughts, comments?





TAG Members visit department meetings

7 02 2011

In February and March, TAG members will be visiting department meetings for each academic department. Our goals in attending these meetings are as follows:

  • Make sure all faculty members know about TAG
  • Solicit feedback on campus technology issues
  • Have faculty fill out a quick survey that will help us create a Knowledge Base (a listing of faculty who have tried using different technologies in the classroom, like clickers, social media, etc)
  • Invite faculty involvement in TAG either as a full committee member or as a participant on our TAG-Discussion list

We’ll look forward to seeing all of our fellow faculty members. Be sure to bring us your thoughts and comments on technology on campus.





CNAC upgrade

7 02 2011

Just a reminder that this Wednesday, you’ll have to log in again to CNAC in order to access the University network.

What’s CNAC? Click here for more than you ever wanted to know – Jeremy’s explanation.

Here’s the upgrade announcement from IR, emailed out to all faculty today:

On Wednesday, February 9th the re-authentication will also upgrade your CNAC client.  On Wednesday, all end-users will be prompted with the following:

NAC Agent 4.8.032 is available.  Do you want to install this update now?

Click OK and after a few minutes the new Cisco NAC Agent will install.

Once the install is complete, you should enter your University user name and password into the CNAC agent to gain network access.

This process will allow us to continually assess the validity and health of our computing environment.  A CNAC re-authentication process will routinely occur on the second Wednesday of each month.

Thank you for your patience and understanding as we implement these changes.  If you have any questions or concerns, please contact the Technology Support Center at 570-941-HELP or at techsupport@scranton.edu





IT Forum on Microsoft Live @ Edu

27 01 2011

IT Services is holding an IT Forum on the Microsoft Live @ Edu email transition coming up this summer. Here’s the announcement from the my.scranton portal:

Is your email in need of organization?

Do you need help with archiving old emails?

Learn some new tips and tricks for handling your email !

Come to the IT Forum on February 17th from 11:30 am to 1:00pm in BRN 509 and learn how to best organize your email, how to archive old emails to access later and some new tips and tricks for handling and your email.

Lunch will be served and there will be prizes!! All members of our community are encouraged to attend. Registration is required by February 15th, by emailing ITServices@scranton.edu.

 





Dr. Strangepage: Or How I Learned to Stop Worrying and Love the CMS

26 01 2011

Note: In light of some of TAG’s recent discussions about the CMS, we thought it might be useful to have a real live faculty member’s perspective on what it’s like to manage a departmental page.  Many, many thanks to Dave Dzurec for being willing to write up a post about his experiences working on the History Department’s page!

The migration of the History Department’s website to the CMS has not been without its bumps. There have been times when segments of the page have been a complete mess, there have been times when I’ve lost whole folders, there have been times when I’ve inadvertently changed the department chair’s picture to suggest that he is a member of the Italian Communist Party (not really, he did that himself). Migrating the content from the old site to the new was a great deal of work. Part of the challenge was learning the new system. Some of these challenges were ultimately beneficial as the process of migrating the site helped to familiarize me with some of the idiosyncrasies of the CMS (with a great deal of help from Sarah Johnson). Since we’ve manage to get the pages up and running, however, things have been relatively smooth. I try to review the page at least once every couple weeks to make sure everything is functioning and there’s nothing wrong with our links, I update student events (meetings of the Royals Historical Society, calls for applications to the Phi Alpha Theta, the History Honor Society) as they are announced, and once a semester I update the faculty news section, based on reports given to me by members of the department. There are of course still occasional bumps. This past semester, when we realized that our links to the department course offerings were out of date, I spent a good deal of time working with Ann Marie Stamford to correct the issue. On the whole, however, our current CMS software seems to be a reasonable option (at the very least, no better or worse than any of the alternatives available at the institutional level).

In addition to concerns about ease of use, there has been some concern about individual faculty pages. Within the History Department, faculty continue to be responsible for their own pages. I have simply linked to individual pages from our faculty/staff page. When one of our faculty members moved his personal page to a new site, I simply updated the link. As I understand it, the move to the CMS has had no direct impact on individual pages and we continue to have a great degree of autonomy in maintaining our individual sites. [Note: TAG is currently working with PR to set up a protocol for how faculty can request websites. Existing websites will be moved over to a new academic server. See our post on The Straight Dope on Faculty Websites for more details.]

From the consumer side, response to the final product has been generally positive. Over the course of the past couple of years and three job searchers, we have received a number of compliments from various job candidates about the overall appearance and ease of use of our department webpage. While I realize that it’s highly unlikely for a job candidate to insult a potential employer (especially given the realities of the job market in the humanities), the fact that they made special note of the quality of the pages is, I think, illustrative of the quality of our redesigned web presence.

One area of concern I do have is the issue of general responsibility for maintaining these pages. There doesn’t seem to be a great deal of consistency across the University about who is in charge of department sites. The CMS workshops I have attended have included everyone from department secretaries, to faculty, to members of the PR department. I think it would be beneficial to define roles and expectations more clearly. For department secretaries, is the addition of maintaining a department webpage to their already large workload a reasonable expectation? For faculty (and on a personal note) while I don’t find maintaining the department webpage to be terribly onerous and my department has certainly counted the work I have done as service in my annual evaluation, is working on a department site the best use of faculty time?





Meeting Notes 1/24/2011

25 01 2011

Sorry for the outburst of posts today! But just wanted to share some news from our TAG meeting yesterday.

The meeting centered around our frighteningly long to-do list and how to tackle all of TAG’s various projects.  One of our main discussion points was how to get more faculty actively involved in TAG – so if anyone has any suggestions, please let us know! We’re hoping that our departmental meeting visits in early Spring 2011 will help us recruit more willing victims volunteers.  If not, we may have to cut back on our project list.

Here’s a snapshot of some of the projects we’re working on, somewhat in order of priority:

  1. Transition to Microsoft Live @ Edu email.  This transition will have two main impacts on faculty.  Firstly, faculty who currently use Thunderbird will need to adjust to a new interface (Outlook desktop client or web client).  Secondly, IR is still exploring ways to migrate faculty email both from the current RoyalMail server and especially from faculty local drives to Live @ Edu cloud storage.  TAG is figuring out the best ways for us to be involved in this transition – whether that means training faculty on the new interface, participating in discussions about migration strategies, etc.
  2. Classroom Mediation Survey. TAG is working with IR, Academic Affairs, and the CTLE to put together a survey that will determine what classroom technology is used in what classrooms, so that equipment budgets can be allocated more efficiently.
  3. User ID change. TAG’s role here will basically be to help get the word out to faculty so that no one will be surprised come March/April when they need to log in with their R number.
  4. Knowledge base. TAG hopes to provide here on our website lists of faculty who use certain classroom technologies (see, for example, our list of campus resources on Facebook and other social media) – so that if you’re interested in trying out a new technology tool in your classroom, you’ll know who on campus you can talk to about it.
  5. Faculty websites. TAG is working with PR to establish protocols for requesting and building faculty websites within the new CMS.  We’re on track to have two models to show other faculty, one built using a basic template and one built using an advanced template.
  6. Faculty scholarship database. Word has it that Academic Affairs is reviewing products for tracking and cataloging faculty publications. TAG hopes to provide faculty feedback on the products reviewed before a decision is made.
  7. Keeping the TAG website up to date. We hope that this website becomes (if it isn’t already) a useful resource for faculty.
  8. Evaluating and providing feedback on technology training for faculty.

If you or anyone you know would be interested in and willing to lend a hand on any of these projects, please let us know!

Last but not least, TAG’s next major step is to visit a department meeting in early Spring 2011 for each department on campus. We’re currently working on developing talking points for those visits. Keep an eye out for your TAG liaison at your next faculty meeting!