Upgrading from NT4 to Active Directory this weekend!

[iamwiz82]

Here is my plan, please critique.

Ghost PDC, BDC, and new server
Remove PDC from network
Promote BDC to PDC
Upgrade new PDC to Windows 2000 Server
Convert domain to Active Directory
Configure new server as DC, which will take over for the old PDC
Switch to Native Mode
Synchronize domain
Test user login
Test printing
Test joining of the domain
Test user creation

Once completed, we will be configuring another machine as a DC, as well. The old BDC will then be removed from the network. This is not this weekend, however.

Does everything look ok?

 

[stash]

Switch to Native Mode

Can't do this until all BDCs are gone.

 

[stash]

Also, any reason why you are going to 2000 instead of 2003?

 

[iamwiz82]

Originally posted by: STaSh

Switch to Native Mode

Can't do this until all BDCs are gone.

The BDC is getting promoted. The old PDC will stay off the network and will be used as a disaster recovery method, paired with the ghost images.

We are going to 2000 instead of 2003 because we like to stay a step back. Plus, the new DCs have been on the network for about a year now acting as print servers and we would prefer not to have to upgrade NT4 to 2003, upgrade two 2000 servers to 2003, plus all the other work. It's a time issue, since we will be affecting production.

EDIT: I will mention that we are using Win2k3 for our Terminal Server and it has it's share of bugs which are driving us nuts. Can't wait til SP1.

 

[stash]

We are going to 2000 instead of 2003 because we like to stay a step back.

You'll be more than a step back very soon. General support for Windows 2000 ends June 31st.

What kind of TS bugs have you had?

 

[iamwiz82]

Originally posted by: STaSh

We are going to 2000 instead of 2003 because we like to stay a step back.

You'll be more than a step back very soon. General support for Windows 2000 ends June 31st.

What kind of TS bugs have you had?

The main concern is Windows Article 832048, which has no fix, short of paying for support. Also, it takes about 5 minutes for someone to log off of the server via TS. I won't even mention the new licensing format with 2003. Trying to get a 25 character license key from a woman in a Call Center in India is akin to jabbing a fork in my eyeballs. I think we tried to communicate it back and forth about 10 times before I got it right. 😛

 

[stash]

The main concern is Windows Article 832048, which has no fix, short of paying for support.

Um, hotfix calls are free.

I won't even mention the new licensing format with 2003. Trying to get a 25 character license key from a woman in a Call Center in India is akin to jabbing a fork in my eyeballs.

There are some big changes to TS licensing in 2003, but the process you refer to is the same for 2000 or 2003. You should only need to do that process if you need to reissue license packs, like if you are changing license servers, for example. Initial activatation of the TSLS and license packs can be done online.

 

[iamwiz82]

Originally posted by: STaSh

The main concern is Windows Article 832048, which has no fix, short of paying for support.

Um, hotfix calls are free.

I won't even mention the new licensing format with 2003. Trying to get a 25 character license key from a woman in a Call Center in India is akin to jabbing a fork in my eyeballs.

There are some big changes to TS licensing in 2003, but the process you refer to is the same for 2000 or 2003. You should only need to do that process if you need to reissue license packs, like if you are changing license servers, for example. Initial activatation of the TSLS and license packs can be done online.

If you read the article, it states that it is only available to pay-support callers until SP 1 comes out. Because we are an Open License Agreement holder, things are a bit more lengthy to get numbers.

 

[stash]

If you read the article, it states that it is only available to pay-support callers until SP 1 comes out.

That's not what it says: http://support.microsoft.com/?kbid=832048

If you have the exact issue described in the article, call PSS and tell the tech router you want hotfix 832048. They will send you two emails...one with a link and one with a password.

If the hotfix does not fix the issue, you would need to open a paid case and speak with an engineer.

Because we are an Open License Agreement holder, things are a bit more lengthy to get numbers.

Your license agreement is irrelevant. The license install wizard in the TSLS console will ask you what license agreement you have. You then enter the appropriate information that came with your agreement and submit it over the Internet to the Clearinghouse. There is also a webpage where you can enter the same information, useful if you don't have an Internet connection from the TSLS.

https://activate.microsoft.com/getlkp.asp

 

[Sunner]

Out of curiosity, why do you have to call PSS to receive the fix?
Is it simply because they don't want people applying that fix "just in case" and then screw something up, only to make angry calls, or is there some other reason?

 

[stash]

Originally posted by: Sunner
Out of curiosity, why do you have to call PSS to receive the fix?
Is it simply because they don't want people applying that fix "just in case" and then screw something up, only to make angry calls, or is there some other reason?

Basically, yes. Hotfixes are not regression tested like the critical updates that get released to the public. This means that they aren't tested on the myriads of hardware and software combinations that critical updates and other 'public' patches are.

That's why we say that you must have the exact issue described in the article to get the hotfix.

 

[iamwiz82]

Originally posted by: STaSh

If you read the article, it states that it is only available to pay-support callers until SP 1 comes out.

That's not what it says: http://support.microsoft.com/?kbid=832048

If you have the exact issue described in the article, call PSS and tell the tech router you want hotfix 832048. They will send you two emails...one with a link and one with a password.

If the hotfix does not fix the issue, you would need to open a paid case and speak with an engineer.

Because we are an Open License Agreement holder, things are a bit more lengthy to get numbers.

Your license agreement is irrelevant. The license install wizard in the TSLS console will ask you what license agreement you have. You then enter the appropriate information that came with your agreement and submit it over the Internet to the Clearinghouse. There is also a webpage where you can enter the same information, useful if you don't have an Internet connection from the TSLS.

<a target=_blank class=ftalternatingbarlinklarge href="https://activate.microsoft.com/getlkp.asp">https://activate.microsoft.com/getlkp.asp</a>

Well, I just called PSS and they want a CC# no matter what. I believe this is the reason we are sticking with 2000 😉. I don't have to hope MS doesn't charge us for a bug in their program.

 

[stash]

Yes, they ask for a credit card, but you will not be charged Did you even ask the person on the phone about that? I don't know why they ask for a credit card for hotfixes, but that's what they do. But it will not be charged. There are plenty of people on this forum who have done this process, and I don't recall anyone ever having any problems. It is a very quick process. Microsoft is very clear that they will not charge a customer for a bug in the software.

And the process for getting hotfixes is exactly the same for 2000. Except that after June 31st, you won't be able to get any hotfixes without a paid support contract (I think the minimum yearly contract is $75k.

 

[iamwiz82]

The point is that they want a CC no matter what. I have no reason to give them one, whether or not they will charge me. The whole act of requiring me to jump through hoops is silly, IMHO.

 

[iamwiz82]

And so it begins!

 

[iamwiz82]

Everything is running smoothly, except my secondary DNS server. The service is up and running and shows no errors in the event log, but the DNS Manager complains that the server is not running DNS.

Any ideas?