Status
June 11, 2009
After running into issues with printing from non-domain attached workstations and laptops, we pushed the schedule back one week and adjusted the migration schedule for the first departments. We have an interim print solution for that scenario, and we have identified a long-term solution which will be developed before Fall Semester. We also resolved several issues which came up from the OCCS migration, and continue to work on a few issues which will not hinder progress with campus migrations.
May 11, 2009
Students were migrated to the Windows file system for their home directories and to Window printing in the labs and open printers. All data was migrated and will be maintained on the legacy system for 60 days in case there are any requests for data. There are a few issues still being worked out relative to printing to the open printers via MS-iPrint. Printing to the open printers via laptops is available, but automated driver installations do not always work. There are manual work-arounds, but the solution is not yet as seamless as we desire.
March 17, 2009
We met with SGA to inform them of the upcoming migration, to gain feedback and concerns, and to answer any questions. We received a recommendation to add a notice to IUser.odu.edu home page for instructions on remote access to home (H: drive) and shared (M: drive) files.
March 6, 2009
We set up a pilot with participants made up of OCCS engineers, TSPs and ASOG users. After running into some issues to overcome, we moved the OCCS engineers to the new environment and began working out issues so that we could schedule the remaining participants for migration. We had printer migration issues, network security issues and a few other issues to overcome.
February 16, 2009
We met with ASOG, banner users group, to inform them of the migration and to gain feedback from them. We got preliminary concerns and identified participants for a pilot so that we could address all concerns in advance of scheduling migration for departments which were represented. We met with TSPs to inform them of details of the Lab image requirements and the process for student account and data migration. We gained additional participants for our pilot test.
February, 2009
We set up a pre-production environment using our production hardware for file and print services, so that we could begin working out technical issues, refine our design and prepare for a pilot migration to test all aspects of file and print services. We began setting up our Blade Enclosure for blade servers supporting DNS and MFD printing to be housed.
December, 2008
We selected LANDesk as the desktop management and server patching software to replace ZENWorks Desktop Management. We began receiving servers for the clustered file and print environment, as well as replacement AD Controller servers and our Blade Enclosure. We set up a skeleton test Windows AD file and print environment. We established a project plan with major milestones being a Pilot to be run over Spring Break, OCCS migration, Student Migration between semesters, administrative departments migration beginning in summer 2009, and faculty migrations beginning in Fall Semester 2009.
Summer, 2008
We began researching and designing a new file and print environment for ODU's faculty, staff and student user communities, identifying all related services, tools and dependencies and beginning to plan replacement of existing services with an Active Directory, Windows File system, Windows Print system and an alternative Desktop Management Suite. We identified hardware requirements for the new file system.