The message before is spam and malicious. Do not follow the link.
From: Argonne National Laboratory <email@example.com> Sent: Mon Jul 08 18:57:31 CDT 2013
Latest news and updates are now available at the Argonne National
Laboratory news center. All recipients of this notification should
please lo-gin for more information using the link below.
Please use the link above to lo-gin for more information and possible
submit your feedback/comment.
MCS Help Desk
9700 S. Cass Avenue
Argonne IL 60439
© 2013 U.S. Department of Energy Office of Science
Hey, all. In reference to the announcement in May on upcoming changes in the environment (http://wp.me/p3jwfN-4e), I’d like to hold a town hall so you can get some first hand demos on how things will be happening, an update on where we are in the process, and get a chance to address any concerns or questions you might have.
I’ve booked room 4301 (the seminar-style room) and will be giving a brief talk with some live demos on Monday, July 15, at 2PM. There’ll be plenty of time for questions. I promise that for any questions we don’t have the answers, we will construct suitably believable and entertaining lies that will assuage any fears.
Well, no, not really. But you should still come.
The room has seats for 30 people. If that proves inadequate, I’ll schedule a second session.
The new MCS website is now live at http://www.mcs.anl.gov. This website is being run by CIS on their Drupal servers (the same infrastructure that runs www.anl.gov). Sites beyond the first level, such as personal webpages and project home pages, are still being hosted where they were previously.
More information will be coming soon as to how to get content changes onto the website, but right now we’re concerned with identifying any technical issues that may be present, and can focus on tweaking content in the coming weeks. Please take a moment to confirm everything is working as you’d expect. If you find a problem, let us know at firstname.lastname@example.org. We’ll fix what’s in our power to fix, and pass on to others that which is not.
For those curious as to how it’s all run now, the main website lives in CIS on their Drupal servers, but we still host the machine known as www.mcs.anl.gov. This machine will send requests for Drupal-hosted pages on to the lab’s servers, and otherwise serve up what it always has.
[Not sure why this wasn’t posted on Friday afternoon. It was supposed to be.]
Please see the enclosed notes from the Zimbra admin team. Thanks!
Saturday, May 25, we will be upgrading the Zimbra servers:
- OS patching and maintenance will be done
- more memory will be added to each server
- Zimbra will be upgraded from 7.2.2 to 7.2.3
The maintenance window for this procedure will begin at 9am on that Saturday. We anticipate completing the upgrade process by 2pm the same day.
During this period, the Zimbra server will be unreachable. You will not be able to check your mail, calendar, or anything else that is stored on the server. Incoming mail will be held and delivered when the OS patching is complete; no mail will be lost.
Upon completion, we’ll send an “all clear” message with any pertinent details.
If you have any questions or concerns, please contact your Zimbra Domain Admin, or your IT support staff.
– – CIS Zimbra Admins
Hey, all. We’ve got some upcoming changes in the MCS IT landscape over the rest of this calendar year, and it’s probably time to announce them to everyone at large. So, without further ado, let’s get right to it.
1) Argonne is phasing out Zimbra and migrating all Argonne Zimbra users to Microsoft Exchange.
Over the past year, Argonne’s been looking at ways to improve and streamline operations, and one of those fronts has been determining if there’s a genuine need to support multiple e-mail platforms. CIS formed a working group to look at the feasibility of going to a single solution (that solution being Exchange). I was part of that working group, and conducted interviews with a number of you to gather data on how we use Zimbra, and if there are any show-stopping reasons why we couldn’t use Exchange. There were representatives from every ALD on the working group, and we ultimately concluded that there was no technical reason we could not consolidate under a single service. In fact, we identified a number of advantages besides the obvious cost savings in running a single service, including improved coordination capabilities and vastly reduced support overhead for employees who move between divisions using different systems.
What does this mean for you? We’re still working that out. Timelines are very fluid at this point, and we’re working on the migration plan with CIS. They will be handling most of the effort involved in migrating people to the new service, as well as training users in changes they’ll see. We’re still gathering information, identifying potential difficulties, and helping to come up with solutions. So I don’t have anything concrete to tell you, yet, but I know word of this has been flying around already since the memo to division directors went out a little while ago. I haven’t announced anything until now because aside from “it’s going to happen at some point”, I don’t have anything really concrete to tell you.
During the working group’s evaluation, I switched over completely to Exchange and used it for a month. I found it to be perfectly capable, had no show-stopping issues, and I’m confident that once this is complete the overall user experience for e-mail and calendaring will be improved. I think that most of you won’t even notice the difference (except for the web interface changes).
There are some other changes that will come out of this process. For one, we’ll need a different solution for CI mail and calendar, since we can’t use CI authentication on the Exchange server (necessitating Argonne accounts for all e-mail users on it). We’ll deal with that issue separately and further announcements on that will go to the CI mailing list. Another change is that we’ll officially start supporting MS Outlook as a Mail and Calendar client. And, perhaps the biggest change, is announcement number 2.
2) MCS is phasing out MCS-only accounts and moving to Argonne accounts for all authentication (where possible).
With the integration of services, the onerous requirements of Argonne account policies, and a continuous drive to reduce duplication of effort, it’s become clear that the concept of the MCS-only account has to be phased out. The new e-mail service will require authentication using Argonne accounts, and Argonne as a whole is moving towards making that account be the single sign-on you use for all things Argonne. The feedback we’ve received from you, as well as our own experiences in supporting everyone has shown us that the problems resulting from remembering multiple account identities and passwords (with different password policies) far outweigh any benefit we derive from running our own account authentication system. So we’ve started working towards the model of using your Argonne account to access MCS resources.
What does this mean for you? Well, you’ll see some communication from us soon as we go through the various phases of the project. The first thing we need to do is handle cases where MCS usernames and Argonne usernames differ. We’re working with CIS on their policies regarding account names (specifically, releasing names of unused/deleted accounts for reuse), and coming up with the migration plan. In some cases, Argonne usernames will change, in some cases MCS usernames will change. It will ultimately be your decision which happens (and your e-mail address won’t change in either case, so don’t worry about that). If they already match (like mine), then congrats! You’re successfully through phase 1! Once we’ve got all usernames matched up, we’ll start rolling out the changes in our account management system such that it becomes a resource management system, using Argonne accounts as its back end.
You’ll still be able to get collaborator accounts for your collaborators, though that process will change slightly. We’ll have more details on that later, once we’ve got the process mapped out.
Later this summer I’ll schedule a town hall on both of these changes so you can see demonstrations and get better answers to the questions you’ll surely have.
3) Ken Raffenetti is leaving the group (but not MCS).
Over the next couple of months, Ken will be ramping down his involvement in the system administration side of MCS and ramping up his involvement with MPICH development, as he’ll be moving into Pavan’s group. While I’m not not happy to lose Ken’s services in the group, I’m delighted for this opportunity for him and very happy he’ll be staying with MCS and with Argonne. I’m confident he’s going to do very well in his new role! Congrats, Ken, and thanks for all you’ve done in your time with us in Systems!
That’s it for the announcements (for now). There will be more targeted communications on the various projects mentioned above, as well as general announcements on when the town hall will happen.
Please see this note regarding an outage of the on-site wireless network tomorrow morning. If you’re not going to be here, no worries. If you will be onsite, you can expect a brief interruption in wifi service.
> On Saturday, May 18 from 7am-11am, We will perform system maintenance on the Argonne Unified Wireless Network system.
> Cisco TAC engineers has advised us to perform a necessary code upgrade which will fix the signal issues in the wireless system.
> This upgrade does not affect any Argonne servers nor does it affect the Argonne VPN; BUT, if a user is onsite at Argonne
> and are using the Argonne Unified Wireless LAN while using the VPN at the same time; it’s possible a client will drop the VPN/wireless > LAN session until the Access Point reboots.
> After the system maintenance is complete, the wireless controllers and the wireless Access Point’s will be rebooted (in a staged
> occurrence). When the controllers come back online, an Access Point reboot will also occur (in a controlled manner) in order to
> receive the necessary software improvements. Each of the wireless access points will experience a 3-5 minute outage until all of > them have downloaded the patched software.
> Please contact the helpdesk at 2-9999 or email the helpdesk at email@example.com if you are having any wireless issues after the > patching.
> Thank you.
At 3:00pm today the Jenkins Continuous Integration server (jenkins-ci.mcs.anl.gov) will be rebooted in order to patch a kernel vulnerability that is being exploited. The outage should last approximately 15 minutes. Only users of that system will be affected.
CIS would like to take the morning of Saturday, May 25th to upgrade the Zimbra server to the latest version 7 release. The outage would last from 9AM until 2PM, during which time you’d be unable to reach your mail or calendar. If this window poses a particular problem for you, please let us know ASAP. This work was originally going to be done over this past weekend (May 11), but was postponed due to a request to have mail remain up during the weekend.
This weekend is a CIS IT Maintenance weekend. Please see the details below. The network outage window is 4 hours, though actual interruptions will be brief and sporadic as routers and switches are rebooted. The systems are redundant, so interruptions should be brief, but an outage window is announced in case unforeseen problems occur.
Please note building networking (ie, desktops and wireless) will have brief rolling outages throughout Saturday.
Also please note the MySQL databases, blogs, and wikis listed for Friday are ANL/CIS-provided and does not apply to those supplied by MCS Systems.
Systems & services affected
- Fri. Evening:
- MySQL databases, webapps, wikis, Sharepoint, wireless networks (brief rolling outages), building networks: 201 & 222, select Windows virtual servers (see RFCs for detailed list), blogs, wikis
- Important: ALL land-line telephones, analog & VOIP, will be down Fri. evening 18:00-19:00. Users should dial 630-252-1911 in case of emergency.
- All laboratory network connectivity, sporadic interruptions from 08:00 – 12:00. This will effect both onsite connectivity and remote access.
- Building networks: 214 & 240, wireless networks (brief rolling outages)
- No planned activities – systems nominal
Things that will not be affected 
- Email and calendar services
- Divisional IT services
 While not directly affected, most all services will suffer short periods of unavailability Sat. morning as a result of the network maintenance.