Win 2000 Conversion

Thursday, October 14, 2004

Automating Tasks Before Mini-Setup

Automating Tasks Before Mini-Setup

Monday, September 27, 2004

Windows 2000 System Requirements

From Jason Silva -
Windows 2000 System Requirements

Windows 2000 Active Directory Migration Tool

From Jason Silva -

Windows 2000 Active Directory Migration Tool

Adsizer.exe: Active Directory Sizer

From Jason Silva -

The Active Directory Sizer tool allows you to estimate the hardware required for deploying Active Directory in your organization. The estimate provided is based on your organization's usage profile, domain and site topology.
Adsizer.exe: Active Directory Sizer

Jason Silva arrives and he sends out three documents for us all to fill out. He also sends us some links that I'll blog next.

Wednesday, September 22, 2004

Blain, John and I have a teleconference to discuss Jason Silva and our concerns.

Blain, John and I have a teleconference with Jason Silva who will help us with AD Design.

Tuesday, September 21, 2004

Windows 2000 Conversion gets approval .

Friday, September 17, 2004

Don turns in PIER to Heidi and Darrell and cc's me.

I turn in finalized PIER to Don.

Don and I have a meeting for me to finalize the PIER form.

For the past couple of weeks, Don has been going through the inventory getting as close to exact numbers as possible for what needs to be replaced and what needs to be converted.

Wednesday, September 08, 2004

From Blain, a link - 288358 - How to install the Active Directory client extension

288358 - How to install the Active Directory client extension

Friday, September 03, 2004

Don gives me feedback that I am heading in the right direction and moving forward.

He should have some pricing next week on any external help that we'll need.

Made some changes to the Task List today, added a Date column.

Sent an e-mail to John, Blain, Don and Rick asking for several items to be completed.

Wednesday, September 01, 2004

Unable to work on Task List the past two days, perhaps this afternoon or tomorrow.

Trying to complete inventory and I have many hours left on that.

Monday, August 30, 2004

Have a 1/2 hour meeting with Don to discuss my latest Task List that I submitted.

Gave me several items to implement within it.

Told me firmly that we would not be going to Server 2003 and that we would not have our own managed WAN.

Discussed getting outside help for workstation conversion and Active Directory planning.

Friday, August 27, 2004

Have an hour and a half long conference call with John and Blain to discuss my spreadsheet/task list. Made a few changes. Discussed some items. John will send me some notes.

Was unable to work on better task list Monday - Wednesday, barely touched it Thursday.
Spent quite abit of time on it this morning. I'm very unhappy with the results.
I have setup a teleconference with John and Blain at 2 pm today.

Friday, August 20, 2004

Had hour long meeting with Don. He gave me clearer directions on the task list that I need to complete.

Tuesday, August 17, 2004

Created a Win 2000 Conversion Task List ROUGH draft with 4 different phases.
Included is who would do what, by what date and the cost.

Awaiting feedback.

User State Migration Tool

One of the key challenges of migrating to Windows® 2000 Professional is how to deal with migrating the user state of each machine. User state is a collection of the user's settings—such as address books, folder options, dial-up networking connections—and the user's data, including spreadsheet and word processing documents.

In the past, companies have been forced to write complex scripts or migrate the items manually. Both of these processes are time consuming and labor intensive.

In order to help customers more effectively manage the overall deployment of Windows 2000 Professional, Microsoft has released a resource kit utility that allows an administrator to selectively migrate a user state from a source machine and apply it to a target machine.
User State Migration Tool

These resources are referenced in the Windows 2000 Resource Kits and lead to information that is useful to Windows 2000 users. The links are listed alphabetically, exactly as they appear in the Resource Kits.
Microsoft Windows 2000 Resource Kits - Web Resources

Windows Server 2003 System Requirements

Windows 2000 System Requirements

Monday, August 16, 2004

This paper outlines the planning processes and considerations when migrating Microsoft® Windows NT® domains to Microsoft Windows® 2000 and the Active Directory™ service. New Windows 2000 utilities, tools, and technologies make migrating users and computers, while maintaining access to resources, a straightforward task.
Microsoft Planning Migration from Windows NT to Windows 2000

Upgrading a Windows NT Domain to Windows 2000

Migration Strategy to Windows 2000 Pro

Migrating to Windows 2000

Craft a detailed plan when migrating to Windows 2000 Server

Windows 2000 Project Overview

Microsoft Windows 2000 Deployment Planning Guide

Deployment Planning Guide

Good document full of information.
Windows 2000 Migration: Best Practices

Windows Server 2003 Benefits. Improvements from Windows 2000

Windows 2000 Security Represents A Quantum Leap
InformationWeek.com

Windows 2000 Active Directory Planning and Deployment Resources

A word of warning: Do not rush into your Active Directory deployment process without first reading everything you can about planning and implementing AD. Once you start, you cannot go back unless you tear down your entire directory structure and start from scratch. And a poorly planned Active Directory structure can be a nightmare to administer. Take your time, and get it right the first time!

Looks like a good site! - Marc
Windows 2000 Active Directory Planning and Deployment Resources

Thursday, August 12, 2004

I did send the chkupgrd.exe (otherwise known as Windows 2000 Readiness Analyzer) file to Amy Woolford at Cedar Crest this afternoon. She does have a fairly nice Dell and is running Windows 98.
The program did take awhile to run on her machine and as you can see from a sample of the upgrade.txt file below, it found quite afew issues. It is the same kind of thing you see when you are doing a Windows 2000 upgrade from Windows 98.
The thing I hate the most is when it does not find the network adapter.
This project won't be a boatload of fun.

Hardware--------This section of the report describes hardware compatibility issues.
Incompatible Hardware
The following hardware may not support Windows 2000 withoutadditional files. Please see the Microsoft Windows 2000 HardwareCompatibility List athttp://www.microsoft.com/windows2000/compatible/ for a list ofcompatible hardware. (Some of the following entries might be softwarethat is registered as hardware.)
Display adapters Intel(r) 82815 Graphics Controller
Monitors Dell E770s (not currently present) Dell E771p (not currently present)
Other devices HP DeskJet 1220C Printer hp deskjet 930c series hp deskjet 960c series TOSHIBA e-STUDIO65 Series-PCLXL
Printer Hewlett-Packard DeskJet 1220C (not currently present) Hewlett-Packard DeskJet 930C (not currently present)
Sound, video and game controllers SoundMAX Integrated Digital Audio
System devices Intel(R) 82801BA/BAM SMBus Controller - 2443
You can continue with the upgrade, but the hardware may not workuntil you supply the additional files.

Software Incompatible with Windows 2000---------------------------------------This section lists information about programs that are incompatiblewith Windows 2000. Before upgrading, evaluate how important theseprograms are to you.
Software That Does Not Support Windows 2000
Setup has found programs on your computer that do not support Windows2000. Contact your software vendors to obtain updates or Windows2000-compatible versions. If you don’t update these programs beforeyou upgrade, the programs will not work.
Client Access (in Control Panel) Nero ImageDrive (in Control Panel) XG Synth Driver (in Control Panel)
Before you upgrade to Windows 2000, you should remove anyincompatible programs. After the upgrade, uninstall might not work.Add/Remove Programs in Control Panel can help you uninstall mostprograms. Click Start, point to Settings, click Control Panel, andthen click Add/Remove Programs.

John, Blain and I had a teleconference today at 3 pm.

We discussed things such as upgrading the workstations, the remote locations such as in California, inventory, and cleaning up User Manager.

We discussed the pros and cons of running the upgrade on a workstation or installing a fresh copy. We didn't come to a conclusion.

Inventory must be as close to 100% as possible and I know mine has had alot changes in the past 6 weeks. Unfortunately I will still have quite a few more changes in the coming weeks.

Nothing has changed in User Manager since we became P2S and we have had many employees leave us since then and there are many groups that aren't being used as well. This will be an important thing to do before upgrading the servers.

We won't have a meeting tomorrow but we will probably on Monday or Tuesday. I think the next thing Don will want sometime next week is a task list of who will do what and when. We didn't discuss that at all today.

John and Blain promised they would continue to think about things and send me stuff.

Found it! You can run this from the hard drive.
TUCOWS Miscellaneous Utilities Windows 2000 Readiness Analyzer

This requires 2 floppy disks.
Windows 2000 Installation Readiness Analyzer Download and Use

This looks like a great link.
Download tools and utilities that help you manage and support Windows 2000.
Windows 2000 Tools and Utilities

An interesting article.
One interesting quote - "In short, if you don't have a 300 MHz CPU and 128 MB of RAM, forget Windows 2000."
It also had an interesting link - "Hardware compatibility is the single biggest issue facing any upgrade. Before slapping down any dough on Windows 2000 Professional, be sure to download Microsoft's free Windows 2000 Readiness Analyzer. This tool will analyze your system and report potentially incompatible hardware devices and software applications. While it's not exhaustive, it's an excellent first step." but it appears to be a deadend now.
Paul Thurrott's SuperSite for Windows: Should you upgrade to Windows 2000? A Windows 2000 technology showcase

This link is handy only if you know the make and model of your computer, devices or software.
Check Hardware and Software Compatibility

I begin to get myself in order.

I create a Win 2000 Conversion folder within Notes to organize all the e-mail. I create a physical folder to put any printed documentation into.

I begin surfing the internet for some help, I imagine there will be a ton of useful information out there since many many companies have already accomplished what we are about to do.

Wednesday, August 11, 2004

We have our first meeting on this project.

We discuss things like converting machines during business hours, server hardware upgrades, server consolidation, getting an exact inventory to map out the plan of upgrade, Active Directory design, policies (no new machines to be deployed with W98 or lower and keep an accurate update on the inventory), conversion kits, and actual deployment.

Don asked for a volunteer, John did volunteer but I decided to as well and I got the final nod (wish me luck!).

Don would like some firm documentation sometime next week.

I setup a meeting with John and Blain for Thursday afternoon at 3 pm.

Friday, August 06, 2004

Don sends out an e-mail with an attachment stating he has a new challenge for us.
Wants us to think about the tasks ahead to convert the workstations to Windows 2000, the servers to Windows 2000 and implement Active Directory. He'll also need a project leader and we'll meet next week.

Thursday, August 05, 2004

Win 2000 Conversion

With this blog I hope to document this project.