Office 2007 Upgrades 7/27/2009

Posted on by

Beginning at 6:00 p.m on Monday, July 27, 2009, Technology Services will deploy Microsoft Office 2007 to opt-in faculty and all staff computers. Office 2007 will be installed on all campus labs and e-classroom computers for the 2009-2010 academic year.

To facilitate a successful installation, staff and faculty opting in to the deployment should “Restart” their computers when leaving work on July 27. PCs should be left on and at the “CTRL+ALT+DEL” login screen. For more information on the deployment, including training and what to expect after deployment, visit our Office 2007 Web pages.

Maintenance Patch Detail for 7/26/09

Posted on by

The following production servers were patched today, OS patches only:

Linux:

  • orcas
  • baker
  • Tahoma
  • purgatory
  • styx
  • hades
  • gehenna
  • moodle
  • quixote
  • mysql
  • oraweb

And the following Windows servers:

  • Alexandria
  • BE1
  • BE2
  • BE3
  • CLTACC1
  • CLTACC2
  • CMS
  • DHCP-1
  • EPO
  • FE1
  • FE2
  • ILLIAD
  • INTCHK
  • KEEPER
  • MAURY2
  • MBS1
  • MBS2
  • MBS3
  • MEDIA
  • MERLIN2
  • MSPROJECT
  • PROJECTS
  • SANJUAN
  • UPSCA03
  • VASHON
  • VERONICA
  • VIAWARP
  • VMMON
  • WEBSERVER1
  • WEBSERVER2

Exchange 2007 Interface Upgrade Postponed

Posted on by

Updated 7/26/09 @ 3:10PM

All changes were backed out and all mail delivery is back to normal by 3:00 PM.

Due to unforeseen issues with the Exchange 2007 interface upgrade today, the change is postponed.

Currently we are reverting back to the previous configuration, which should be complete by 3:00 PM today.  During the change and roll-back periods (8:00 AM to 3:00 PM Sunday, August, 26th) some mail sent from outside of the University may not have been accepted.  Any user sending email that failed will get an error message and will be able to re-send the message after 3:00 PM.

This post will be updated when the roll-back is complete.

Non Production patch maintenance

Posted on by

We are currently experience patch related issues with the following non-production servers ( Pilchuck, Lummi, Kickstart and Moodle2). We are working to resolve these issues as quickly as possible. A notification will be sent out as soon as these issues have been resolved.

6/28/09 Maintenance Window Details

Posted on by

See the post in the “Maintenance Windows” catagory for the public communication.

This month the Sophos PMX servers were patched with the latest Linux patches, and upgraded to the latest PureMessage version.

We also did the following non-recuring tasks:

  • Upgraded Alexandria’s MD3000 Firmware
  • Upgraded AntiVirus to EPO on Webserver1 and Webserver2
  • Cleared stale VSS copies on SanJuan

Finally, all production Windows servers were patched:

  • Alexandria
  • BE1
  • BE2
  • BE3
  • CBORDFSS
  • CLTACC1
  • CLTACC2
  • CMS
  • DHCP-1
  • DM-1 to DM-8
  • EPO
  • FE1
  • FE2
  • ILLIAD
  • INTCHK
  • KEEPER
  • KRONOS
  • LENEL
  • MAURY2
  • MBS1
  • MBS2
  • MBS3
  • MEDIA
  • MERLIN2
  • MICROS
  • MSPROJECT
  • ODYSSEY
  • PROJECTS
  • SANJUAN
  • UPSCA03
  • VASHON
  • VERONICA
  • VIAWARP
  • VMMON
  • WEBSERVER1
  • WEBSERVER2

[Complete] Next Maintenance Window 6/28/09

Posted on by

This month’s outage was completed 1:30PM.  All services other than Cascade Web and Banner were available by noon as expected.

The next production maintenance window is Sunday, June 28th, from 8:00 AM to 4:00 PM.

From 8:00 AM to Noon, all services may be intermittently or entirely unavailable, including:

  • E-mail
  • Personal and departmental file shares (on Alexandria and Merlin2)
  • Database Applications:  Cascade, FAMIS, Millennium, and Banner

Please note that Cascade Web and Banner will continue to be unavailable until 4:00 PM.

OID Test groups and group members recreated today

Posted on by

The Groups container was accidentally deleted in the OID test database today and had to be re-created based on priv data in the Summit database.
Here are the steps we had to do to recover everything:
1. Recreate the Groups container.
Export the Groups container definition (as an LDIF command) from the OID production instance, and import it into OID test. You’ll need an LDAP browser tool to do this, like JXplorer.
2. Recreate all the AD groups.
Set the status of all the pugetsound domain groups in the privilege table to PA and run
privcmd.resolve_pending_privdef on each one.
3. Recreate the members in the AD groups.
Set the status of all AD person_privilege records to PA and run privcmd.resolve_pending_privs.
4. Recreate the portal group container.
Export the portal.070109.134036.113589000 container definition (as an LDIF command) from the OID production instance, and import it into OID test. You’ll need an LDAP browser tool to do this, like JXplorer.
5. Recreate all the portal groups.
Set the status of all the portal groups in the privilege table to PA and run
privcmd.resolve_pending_privdef on each one.
6. Recreate the members in the portal groups.
Set the status of all portal person_privilege records to PA and run privcmd.resolve_pending_privs.
7. Address any unusual configuration issues.
ViewsFlash groups have a special setup, the administrator group is a member of the creator group, so that has to be done manually.

Office 2007 Compatibility Files Installed on Campus Computers

Posted on by

In preparation for the Office 2007 deployment in late July, Microsoft Office Compatibility files will be installed on campus computers this evening. In addition, we will be performing system scans over the next few days to ensure PCs meet the minimum requirements for Office 2007.

No action is needed from the campus community and the files will be automatically applied upon rebooting after June 23, 2009. The reboot may take a minute or two as files are applied.

To install the Microsoft Office Compatibility Pack on your home computer, follow the links on our download page.

Visit our Web site for information on today’s preparation phase or the coming Office 2007 project.