Wins Migration

I apologize if this has been answered before.
I have a couple of questions

1. Currently have several Win2k Domain Controllers, 2 of them are also Wins
servers configured to push\pull with each other
I am planning on upgrading the domain to Win2k3. I was going to extend
the schema, then add new Win2k3 servers, move the roles and
decommission the old domain controllers.
What is the best procedure to move\decommission the old wins servers?
It is recommended that WINS be on a domain controller or is a member
server ok?

2. In looking at our current wins server I am noticing that there are
entries in database that are several years old. Some entries
are tombstoned on both wins servers with expiration dates years old and
periodic scavenging is turned on. They are not static entries. Some
entries only exist on one Wins server, the state is tombstoned and the owner
is the wins server it is on.
Why am I seeing these old entries in the database?
I must clarify that Database Verification is enabled on one of the Wins
server and not the other, could this be part of my problem?

Any help would be greatly appreciated

"Barrycuda" <(E-Mail Removed)> wrote in
news:(E-Mail Removed):

> I apologize if this has been answered before.
> I have a couple of questions
>
> 1. Currently have several Win2k Domain Controllers, 2 of them are also
> Wins servers configured to push\pull with each other
> I am planning on upgrading the domain to Win2k3. I was going to
> extend
> the schema, then add new Win2k3 servers, move the roles and
> decommission the old domain controllers.
> What is the best procedure to move\decommission the old wins
> servers? It is recommended that WINS be on a domain controller or
> is a member
> server ok?
>
> 2. In looking at our current wins server I am noticing that there are
> entries in database that are several years old. Some entries
> are tombstoned on both wins servers with expiration dates years old
> and periodic scavenging is turned on. They are not static entries.
> Some entries only exist on one Wins server, the state is tombstoned
> and the owner is the wins server it is on.
> Why am I seeing these old entries in the database?
> I must clarify that Database Verification is enabled on one of the
> Wins server and not the other, could this be part of my problem?
>
> Any help would be greatly appreciated
>
>
>

In terms of WINS, you do not need to install WINS on a DC.

Generally speaking the easiest way to migrate is to install the WS03 WINS
servers and add the W2K WINS servers as replication partners,then replicate
the databases to the new servers. Change DHCP options so that clients talk
to the new WINS servers. After the databases are fully replicated to the
new WINS servers, take the old WINS servers offline.

There is an NT4 WINS to WS03 WINS migration guide called "Migrating from
Windows NT Server 4.0 to Windows Server 2003", some of the info in there
might be helpful. If you want to check it out, it's at
http://www.microsoft.com/downloads/d...n&familyid=e92
cf6a0-76f0-4e25-8de0-19544062a6e6

--
James McIllece, Microsoft

Please do not send email directly to this alias. This is my online account
name for newsgroup participation only.

This posting is provided "AS IS" with no warranties, and confers no rights.

Thanks for the advice, any thoughts on my 2nd question?
I notice that viewing the Wins Server statistics, it is restarting every day
I get a 4098 event that Wins was terminated by the service controller



>> 1. Currently have several Win2k Domain Controllers, 2 of them are also
>> Wins servers configured to push\pull with each other
>> I am planning on upgrading the domain to Win2k3. I was going to
>> extend
>> the schema, then add new Win2k3 servers, move the roles and
>> decommission the old domain controllers.
>> What is the best procedure to move\decommission the old wins
>> servers? It is recommended that WINS be on a domain controller or
>> is a member
>> server ok?
>>
>> 2. In looking at our current wins server I am noticing that there are
>> entries in database that are several years old. Some entries
>> are tombstoned on both wins servers with expiration dates years old
>> and periodic scavenging is turned on. They are not static entries.
>> Some entries only exist on one Wins server, the state is tombstoned
>> and the owner is the wins server it is on.
>> Why am I seeing these old entries in the database?
>> I must clarify that Database Verification is enabled on one of the
>> Wins server and not the other, could this be part of my problem?
>>
>> Any help would be greatly appreciated
>>
>>
>>
>
> In terms of WINS, you do not need to install WINS on a DC.
>
> Generally speaking the easiest way to migrate is to install the WS03 WINS
> servers and add the W2K WINS servers as replication partners,then
> replicate
> the databases to the new servers. Change DHCP options so that clients talk
> to the new WINS servers. After the databases are fully replicated to the
> new WINS servers, take the old WINS servers offline.
>
> There is an NT4 WINS to WS03 WINS migration guide called "Migrating from
> Windows NT Server 4.0 to Windows Server 2003", some of the info in there
> might be helpful. If you want to check it out, it's at
> http://www.microsoft.com/downloads/d...n&familyid=e92
> cf6a0-76f0-4e25-8de0-19544062a6e6
>
> --
> James McIllece, Microsoft
>
> Please do not send email directly to this alias. This is my online
> account
> name for newsgroup participation only.
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.