Migration Planning Index Systems Administrator Guidelines
Note: 10-9-2013 Much of my documentation was made with HTML and SQL databases. Not to mention my last migration plan was from Windows 2000 Pro to Windows 2002 / XP Pro. It's been a few years.
I'm pulling off information to get you started and I am creating a master document to add to my Master Admin docs. I'm putting together a simple mailing list and running a ticket system for migration issues. I'd like to start collecting form you any issues you see or think you're going to have. It's best to list the items so to plan a good approach.
System Migration Index
- Contact List
- Mailing List
- Chain of Authority (Hierarchy)
- Responsibility (you and your group)
- Verbal Communications
- Written Communications
Computer and Network Guidelines
- Systems Administrator - IT Support / Preparation
- Technoloy Support
- Terms and Usage
- Global Policy
- Local Policy
Call Center (CSR) Support
- Technical Hotline
- Telephone Contact Number
- Email Contact Address
- Message and Alerts Email or service address
- Customer Satisfaction
- Normal Schedules
- After Normal Hours
- Quality of Work
- Inventory List of Equipment
- Service Provided by
You know you are the best the industry has to offer.
You and your team if you're lucky enough to work with a group of IT Pro's can handle just about any technical issue that you might face without skipping a beat in your productivity.
As a team or One or More you'll be held to the highest expectations that any individual can imagine from any organization. You're not only the face of future for your client or company but you're going to be weighed every day from this day based on your successes during your migration.
You know you are good and what makes you better than others is you know when you are limited or have reached your experience limits. At that point you know it's best to find those with the most experience in the product areas you require advanced support with. Your thought process is near perfect when you look online for other systems administrators working with migration issues. We know our resource links and we know the difference between those that blog a story and those that make the stories.
I ask that you find someone that will share work with you and not say "Give it to me and I'll do it" you need to learn to make your migration work and working with a person or hiring someone to do the job for you isn't going to teach you a thing. Unless this is your last migration I suggest you hire or contract those willing to work and share how the work is completed.
It's Teamwork and that's the number one Priority here!
Keep your updated contact list within arm's reach at all times. If you use a planner or a tablet always have it ready to look up your people. Lists should be updated as soon as a change has been made. If you are working with many people find a good location on your website or here to publish contact information.
Many of you may have never used a mailing list before. It isn't the same as a mass email going out to everyone in the CC or BCC lines. It's an actuall send to one that sends to many list. This method of communications is very helpful when you are working with a group that is on the job. You can send a question via email and be reading the answer without having to look up everyone's individual email addresses. I'll be managing a mailing list for those looking to share in the experiences of your migration. XtremeComputer.Com will host
I like to offer s simple example of what many times we forget to do and when we do it's just adding hours to our work schedule.
Preperation to remove a computer form the network.
- Copy the user information and applications data specific to the user.
It is often times easier to copy the C:\USER\%USERNAME%\ folder or the %APPDATA% for Microsoft .DOT templates that could leave you wondering what is wrong with your word document.
- Note which config or user profile was in use.
- Note the computer name.
- Check the local Admin account for the system. Be sure to create a local admin account if none has been created. Give the admin account a password for the local machine.
- Remove the computer from the network domain by adding it to the WORKGROUP.
- Restart your computer.
- Login as local admin.
- Note the IP address if you use static note all configurations for all NICs.
- Shutdown the computer and disconnect the network cable.
- Remove any special components that have been installed in this computer if you are upgrading hardware.
- Identify device drivers for any third party special cards found in the computer you are removing from the network.
- Remove and note any USB devices. Note Model numbers and serial numbers.
You are using a list so you can enter all the information into a master list and email that list daily to your project manager.
Without a complete inventory of your system your migration might need 2 or more return trips when the users announces things aren't working as they did before the migration.
You'll also need to identify any hardware or software that your new OS doesn't have on a list of supported applications.
You did run your applications script right?
You didn't forget to list all currently installed software did you?
Ok, so we didn't record all the Network maps. Not a big deal, we have that info in the system logs and the Active directory. But just in case you do not have access to that information you need to note the network connections for this user.
I have had my checklist in a XLS file and my data collected in the same file with the tab name of the computer. I will create a document if I have time that can link to your SQL server.