David Sandlin Implementation of an Upgrade of the Local Area Network for Sugar Land Bible Church
Unit 8: 5/23/05 - 5/29/05
Tasks

1) Install and configure new server hardware. [Completed]
2) Install and configure Microsoft Small Business Server 2003. [Completed]
3) Upgrade pastor's PC to Windows XP. [Completed]
4) Install Microsoft Office 2003 Professional on pastor's PC. [Completed]

Decisions
The installation of Microsoft Office 2003 Professional on the pastor's PC was not initially scheduled for this week, but problems with his installation of Microsoft Office 2000 Professional required a reinstallation of the software. It was decided to go ahead and install the newer version of Office instead of reinstalling the older version. The installation of Office 2003 did not cause a delay in any of the scheduled tasks for this week thus making the decision an easy one.
Learning
1) I was working alone on the scheduled project tasks this week and did not receive any feedback from the parties involved in the project.
2) This week I used the new server hardware, Microsoft Small Business Server 2003, Windows XP and Microsoft Office 2003 Professional to complete the scheduled tasks. I learned the process for migrating a Windows 2000 Server system to Windows Small Business Server 2003. I also learned the importance of managing user profile information when upgrading operating systems on PC's.
3) The focus of my research for this week was to answer the question of how to migrate a Windows 2000 Server to Windows Small Business Server 2003. I utilized an online guide called Migrating from Small Business Server 2000 or Windows 2000 Server that I identified during the project planning phase in TS4991. This guide provided the necessary steps to successfully perform a server migration. It also provided worksheets for gathering the critical information required for the migration. I gathered the necessary information, followed the guide and ended up with a successful server migration.
4) This week I learned that the old axiom of whatever can go wrong will go wrong still holds true. I also learned that time estimates for completing tasks are just that, estimates. Unforeseen issues can quickly cause significant amounts of time to be required to complete a task. Therefore, it is important to be conservative when estimating time requirements.
Indicators
1) While the server migration went well the upgrade of the pastor's PC to Windows XP was more challenging and resulted in a significant amount of time being spent troubleshooting small issues. In addition, the server migration required slight configuration changes to the other PC's in the office. During the reconfiguration major problems were discovered on the youth pastor's PC which required a considerable amount of unplanned troubleshooting. Basically, the time requirements for the scheduled tasks were much more than I initially estimated.
2) I was able to stick to my project schedule very well. Even though the tasks took quite a bit more time than anticipated I was able to complete them and get a jump on the installation of Office 2003 on the office PC's.
3) I am very prepared to complete my project by Unit 10 as required. Everything is right on schedule.
4) It is very unlikely that I will have to resort to my contingency plan.

[Home]