Final Blog Post

In completing this project, it did not unfold in the manner that I thought it would. My original expectation going into this project was that we would be deploying anti-virus software to each individual computer, but it turned out to be much more than that. In addition to anti-virus software, there was also a need to backup critical data on site. This would then lead to file sharing amongst the users in the Tallahassee office. In order to overcome the challenges that we faced throughout the project, I tried to coordinate the project in the best possible manner. This was accomplished by setting flexible deadlines and trying to be as timely as possible, but also understanding the new problems would arise and that we would need to overcome them in order to complete the project successfully. The most important thing that I realized in the beginning was that expecting everything to go smoothly was a false belief.

Some of the obstacles, in addition to those already mentioned, that were encountered include unknown user names and passwords, inability to connect to e-mail services, and the sponsor not being available at all times. By adding each of the computers to the domain and using administrator accounts, we were able to recover the lost user names and passwords. One of the computers would not connect to the correct mail servers to download the mail through Outlook. In order to resolve this issue, we looked at other user account setups on existing computers to find out the correct mail servers and port numbers. When the sponsor was unavailable, we worked as best as we could on other issues that did not involve her. We worked as much as possible to resolve all issues that did not require her input and delayed those decisions that did require her input until she was available.

This project took a lot more time than I had initially expected. My expectations were that this project was initially going to be more of a tech support style project, but ended up becoming a server deployment and implementation project instead. Because our initial assumptions were incorrect, the time to complete this project was extended. The most important thing that I learned about time estimation is that the project will always take much longer than I originally expected if we do not have all of the details about the issues beforehand.

One of the most useful classes in helping to complete this project was the Website Development class that I took in the fall of 2007. This class helped me greatly in the deployment of a server, securing the server, and enabling user rights management on the server. In addition, the networking classes and technical communication course helped a great deal as well. Being that we were dealing with a non-technical audience, it was crucial that we were able to adopt our message to our audience so that they knew exactly what we were planning to do and why it was vital to their organization for us to do so. Because I am currently fulfilling an internship were Active Directory is used, this greatly helped as well. If I had not already learned how Active Directory was used to setup users on the server, this project would have taken a lot more time. However, this project also helped me familiarize myself with Active Directory even more as well; this was my first deployment of the program to an organization.

My personal 'take-aways' form this project are learning to adopt a technical message to a non-technical audience, implementing a server into an environment that allows for more productivity, and working with users to determine their needs. This project did an excellent job of being able to exhibit my skills in the workplace. All of the skills that I learned at FSU were vital to this projects success in its entirety. One of the main things that I will be utilizing in my first project on the job is to estimate a lot more time for tasks. This was one of the major obstacles that we had to overcome in this environment because of the limited amount of time that we had to devote to this project. The project, overall, was not an easy one. However, these challenges have better prepared me to face more stringent challenges in the workplace and be able to overcome issues with the project itself and the people who partake in the project as well.

Week 11- Antivirus Distribution and Adding Clients to the Domain

Our goal on Thursday was to add all of the client computers to the domain, but this ended up not being the case. Because our sponsor coordinator was out of the office, we were unable to add any of the laptops to the domain. This is because each laptop has an administrator access account that we did not have access to. However, we were able to add all desktop computers to the domain. Each of the desktop computers had the existing anti-virus installed and it was replaced with the anti-virus that was deployed from the server instead. Next Thursday, all remaining computers will be able to be added to the domain.

We also created user accounts and folders for everyone in the office. This will allow them to log into the domain and be able to share files with each other. Each folder is secured so that no one else in the office is able to access it, unless they have been given administrative rights.

The goal for the next visit to the site is to present what we have accomplished for this semester. We will also display how the new technology is working and will work, what problems we ran into, and how the project will be continued through the summer semester.

Week 10-- Beginning of the End

We have received our anti-virus software for the server, so we have begun to deploy it to two test computers. Everything went well in this trial run and on Thursday of this week, we will be connecting all of the client computers to the server to allow them to receive updates, share files, and be able to log in to any computer. This week, we created the rest of the user accounts and set each of them up with a folder. Each user will have a folder for their own personal storage. These folders will only be accessible to them and the domain administrators. Also, there will be a shared folder where everyone can save files and allow others to access them from within the office. The last issue that is preventing us from getting everything correct is the password policy. This is forcing us to change each user's password, making it more secure, but also harder to remember. We worked on that issue this week, but were unable to resolve it for the time being. I or one of the group members, will be speaking with Casey this week to see if he can offer a solution to our problem.

Week 9--The Learning Session, Account Demonstration, and Preview of Rollout

Thursday was a very productive day for our group. Each of us was on the site to begin securing all ports on the server and locking down features on the server. The problem we ran into though, was that a lot of the options for changing password policy were grayed out, which caused us to research the issue so that the users could maintain their current passwords. We also set up a few test folders on the server with various permissions. This will allow for administrative access to some folders, while others will only be accessible to the employee and any administrators on the server.

The next goal was to finish getting the e-mail set up for A.J. Smith. We ended up accomplishing this by copying the settings from another user's Outlook and we were able to setup the e-mail account so that he can access it on-site. This was our first test account too and this allowed us to set him up on the domain, as well as his e-mail and settings.

The largest project of the day was the demonstration of how the new system will work. We held a meeting for 30 minutes that started at 1:30pm on Wednesday. During this meeting, we first started off by re-introducing ourselves to everyone and setting the goal of our project when it is complete next month. We then took any initial questions about current problems they were having. After we answered their questions, we proceeded to give them a demo of how the setup will work. I guided them through this process on the laptop, and I, along with Jeff, Matt, and Andre, were able to answer their questions for them. The employees seemed very excited about what is to come. The reason we decided to give them a preview before it actually launches is because we want them to be able to ask questions before everything changes. We just wanted the new ideas to be able to sink in at first. Then, when the server is actually launched, we will go over it all again, but in more detail. This approach seemed like a positive idea because they would not be overwhelmed all at one time.

Goal for next week: Launch the server
Conditions: Anti-virus software MUST be on-site in order to do so

Week 8-Account Creation, Domain Setup, Ready Server for Launch

This week was our busiest week yet at Catholic Charities. On Thursday, we had our entire team there at the same time to prepare for our server go live over the next couple of weeks. On our visit this week, we began by trying to set up a new user's e-mail account on a spare computer. However, we were unable to complete this because we were provided with the incorrect log in information. Our next step was to get the server turned on and see where we were in the process of getting it ready to go live. There were several new Windows updates available so we made sure to install those right away. I then created two test accounts. I went to the spare computer and joined it to the domain on the server. Once this was successful, I attempted to use both of the test accounts that I had created. This proved to be successful.

The goal for next week is to launch the server, but we may need to give the tutorial to the employees of Catholic Charities first, depending on their availability. I will be discussing this with Debra over the coming days because we do not want to launch the server and then have them not understand how to use it correctly.

Week 6 & Week 7-Modifications to the Server Install

The goal for our group was to install the server this week, but because everyone from Catholic Charities in the Tallahassee office had to travel to the diocese in Pensacola, we were unable to perform that this week. This actually worked out well though because if we were able to install the server this week, any problems that were to arise during Week 7 would create issues for their organization. This is because our group is on spring break and no one would be in town to attend to the problems. I spoke to Debra and she informed me of this decision with plenty of advance notice. I also notified her that we would be installing the server the week that immediately follows spring break (Week 8). She also e-mailed me with some suggestions that her coworkers had asked her to send. These suggestions include learning how to use the new tools, how to better understand the Microsoft Office software on their computers, and how to decrease the amount of spam that they receive in their e-mail. These are all great suggestions that we will to take into account when we begin to prepare our "lunch and learn sessions" after spring break.

Week 5- The Server Install

This week was the week that the server was dropped off at Catholic Charities. Jeff and Matt were able to set the server up on-site and make sure that everything still worked as it had at his home. Because I was at the HIMSS Conference in Orlando this week, I was unable to provide any on-site support. However, I have designed a network diagram layout using Visio that shows how the network will be composed one it is successfully completed. The plan for next week is to setup Exchange Server on the server and promote it to a domain controller in a new forest. If all goes according to plan, the client computers will be connected to the server at the close of business on Thursday evening.

At the HIMSS Conference, I was able to see the new healthcare IT methods that are being implemented in medical practices across the country. These range from EMRs, to EHRs, and even to medical information for iPods and BlackBerrys. This experience allowed me to network with CIOs, CEOs, and COOs. By doing so, it allowed me to ask these professionals what they looked for in potential job candidates, as well as what types of certifications that they feel are necessary in their industry. I felt that this experience allowed me to see how the types of technology that we discuss in class are related to what is currently being developed now. The presentation on Google Health by Dr. Eric Schmidt was a great example of this. Google's new system is a combination of a PHR and EMR. This allows the patients and doctors to interact in one environment by sharing information with each other.