Advice Needed on Migration

Hello im currently running a network for a client that has three HP DL380G4
Servers running Windows Server 2003. They have 1 Domain Controller (DC1), 1
Exchange Server (MS1) & 1 ISA Server (ISA1). The DC1 Server has had many
issues over the last month that are ongoing so the client has decided to
replace ther server, upto now i have only installed new systems from the
ground up, this is my first time of replacing a current server with new
hardware, i need to know how much work is involved in this in regards to
Active Directory, links to the Exchange Server etc.

Any links to help guides would be great.

Hello Lee,

- On the old server open DNS management console and check that you are running
Active directory integrated zone (easier for replication, if you have more
then one DNS server)

- run replmon from the run line or repadmin /showrepl (only if more then
one DC exist), dcdiag and netdiag from the command prompt on the old machine
to check for errors, if you have some post the complete output from the command
here or solve them first. For this tools you have to install the support\tools\suptools.msi
from the 2003 installation disk.

- Install the new machine as a member server in your existing domain

- configure a fixed ip and set the preferred DNS server to the old DNS server
only

- run dcpromo and follow the wizard to add the 2003 server to an existing
domain

- if you are prompted for DNS configuration choose Yes (also possible that
no DNS preparation occur), then install DNS after the reboot

- for DNS give the server time for replication, at least 15 minutes. Because
you use Active directory integrated zones it will automatically replicate
the zones to the new server. Open DNS management console to check that they
appear

- if the new machine is domain controller and DNS server run again replmon,
dcdiag and netdiag on both domain controllers

- if you have no errors, make the new server Global catalog server, open
Active directory Sites and Services and then double-click sitename, double-click
Servers, click your domain controller, right-click NTDS Settings, and then
click Properties, on the General tab, click to select the Global catalog
check box (http://support.microsoft.com/?id=313994)

- Transfer, NOT seize the 5 FSMO roles to the new Domain controller (http://support.microsoft.com/kb/324801)

- you can see in the event viewer (Directory service) that the roles are
transferred, also give it some time

- reconfigure the DNS configuration on your NIC of the 2003 server, preferred
DNS itself, secondary the old one

- if you use DHCP do not forget to reconfigure the scope settings to point
to the new installed DNS server

- export and import of DHCP database (if needed) (http://support.microsoft.com/kb/325473)

- backup WINS (http://technet.microsoft.com/en-us/l.../cc727901.aspx)

- restore WINS (http://technet.microsoft.com/en-us/l.../cc727960.aspx)

- in Exchange system Manger under "Recipients" reconfigure the "Recipients
update service" to the new DC/GC

Demoting the old DC (if needed)

- reconfigure your clients/servers that they not longer point to the old
DC/DNS server on the NIC

- to be sure that everything runs fine, disconnect the old DC from the network
and check with clients and servers the connectivity, logon and also with
one client a restart to see that everything is ok

- then run dcpromo to demote the old DC, if it works fine the machine will
move from the DC's OU to the computers container, where you can delete it
by hand. Can be that you got an error during demoting at the beginning, then
uncheck the Global catalog on that DC and try again

- check the DNS management console, that all entries from the machine are
disappeared or delete them by hand if the machine is off the network for ever

- also you have to start AD sites and services and delete the old servername
under the site, this will not be done during demotion

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Hello im currently running a network for a client that has three HP
> DL380G4 Servers running Windows Server 2003. They have 1 Domain
> Controller (DC1), 1 Exchange Server (MS1) & 1 ISA Server (ISA1). The
> DC1 Server has had many issues over the last month that are ongoing so
> the client has decided to replace ther server, upto now i have only
> installed new systems from the ground up, this is my first time of
> replacing a current server with new hardware, i need to know how much
> work is involved in this in regards to Active Directory, links to the
> Exchange Server etc.
>
> Any links to help guides would be great.
>

Thanks for that it will be a real help form me but i have two questions
following that.

1. The old server will be removed from the network so the new server will be
the DC/AD Server but i have to give that server the same ip address as the
one i am removing from the system, is that ok and do i run it on a temporary
address then change it once the old server is off the network?

2. Is it best practice to give the new domain controller a different name to
the old one even when the old server is no longer on the network?

Thanks Again

"Meinolf Weber [MVP-DS]" wrote:

> Hello Lee,
>
> - On the old server open DNS management console and check that you are running
> Active directory integrated zone (easier for replication, if you have more
> then one DNS server)
>
> - run replmon from the run line or repadmin /showrepl (only if more then
> one DC exist), dcdiag and netdiag from the command prompt on the old machine
> to check for errors, if you have some post the complete output from the command
> here or solve them first. For this tools you have to install the support\tools\suptools.msi
> from the 2003 installation disk.
>
> - Install the new machine as a member server in your existing domain
>
> - configure a fixed ip and set the preferred DNS server to the old DNS server
> only
>
> - run dcpromo and follow the wizard to add the 2003 server to an existing
> domain
>
> - if you are prompted for DNS configuration choose Yes (also possible that
> no DNS preparation occur), then install DNS after the reboot
>
> - for DNS give the server time for replication, at least 15 minutes. Because
> you use Active directory integrated zones it will automatically replicate
> the zones to the new server. Open DNS management console to check that they
> appear
>
> - if the new machine is domain controller and DNS server run again replmon,
> dcdiag and netdiag on both domain controllers
>
> - if you have no errors, make the new server Global catalog server, open
> Active directory Sites and Services and then double-click sitename, double-click
> Servers, click your domain controller, right-click NTDS Settings, and then
> click Properties, on the General tab, click to select the Global catalog
> check box (http://support.microsoft.com/?id=313994)
>
> - Transfer, NOT seize the 5 FSMO roles to the new Domain controller (http://support.microsoft.com/kb/324801)
>
> - you can see in the event viewer (Directory service) that the roles are
> transferred, also give it some time
>
> - reconfigure the DNS configuration on your NIC of the 2003 server, preferred
> DNS itself, secondary the old one
>
> - if you use DHCP do not forget to reconfigure the scope settings to point
> to the new installed DNS server
>
> - export and import of DHCP database (if needed) (http://support.microsoft.com/kb/325473)
>
> - backup WINS (http://technet.microsoft.com/en-us/l.../cc727901.aspx)
>
> - restore WINS (http://technet.microsoft.com/en-us/l.../cc727960.aspx)
>
> - in Exchange system Manger under "Recipients" reconfigure the "Recipients
> update service" to the new DC/GC
>
> Demoting the old DC (if needed)
>
> - reconfigure your clients/servers that they not longer point to the old
> DC/DNS server on the NIC
>
> - to be sure that everything runs fine, disconnect the old DC from the network
> and check with clients and servers the connectivity, logon and also with
> one client a restart to see that everything is ok
>
> - then run dcpromo to demote the old DC, if it works fine the machine will
> move from the DC's OU to the computers container, where you can delete it
> by hand. Can be that you got an error during demoting at the beginning, then
> uncheck the Global catalog on that DC and try again
>
> - check the DNS management console, that all entries from the machine are
> disappeared or delete them by hand if the machine is off the network for ever
>
> - also you have to start AD sites and services and delete the old servername
> under the site, this will not be done during demotion
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>
> > Hello im currently running a network for a client that has three HP
> > DL380G4 Servers running Windows Server 2003. They have 1 Domain
> > Controller (DC1), 1 Exchange Server (MS1) & 1 ISA Server (ISA1). The
> > DC1 Server has had many issues over the last month that are ongoing so
> > the client has decided to replace ther server, upto now i have only
> > installed new systems from the ground up, this is my first time of
> > replacing a current server with new hardware, i need to know how much
> > work is involved in this in regards to Active Directory, links to the
> > Exchange Server etc.
> >
> > Any links to help guides would be great.
> >
>
>
>

Hello Lee,

AD is based on DNS, so there is no need for changing the ip to the old one.
If you still will do it change it and check that the record in DNS zones
will also update.

Using the same name for the new DC creates additional workload for you and
requires a temp DC to remove the old one and free the name for the new one.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Thanks for that it will be a real help form me but i have two
> questions following that.
>
> 1. The old server will be removed from the network so the new server
> will be the DC/AD Server but i have to give that server the same ip
> address as the one i am removing from the system, is that ok and do i
> run it on a temporary address then change it once the old server is
> off the network?
>
> 2. Is it best practice to give the new domain controller a different
> name to the old one even when the old server is no longer on the
> network?
>
> Thanks Again
>
> "Meinolf Weber [MVP-DS]" wrote:
>
>> Hello Lee,
>>
>> - On the old server open DNS management console and check that you
>> are running Active directory integrated zone (easier for replication,
>> if you have more then one DNS server)
>>
>> - run replmon from the run line or repadmin /showrepl (only if more
>> then one DC exist), dcdiag and netdiag from the command prompt on the
>> old machine to check for errors, if you have some post the complete
>> output from the command here or solve them first. For this tools you
>> have to install the support\tools\suptools.msi from the 2003
>> installation disk.
>>
>> - Install the new machine as a member server in your existing domain
>>
>> - configure a fixed ip and set the preferred DNS server to the old
>> DNS server only
>>
>> - run dcpromo and follow the wizard to add the 2003 server to an
>> existing domain
>>
>> - if you are prompted for DNS configuration choose Yes (also possible
>> that no DNS preparation occur), then install DNS after the reboot
>>
>> - for DNS give the server time for replication, at least 15 minutes.
>> Because you use Active directory integrated zones it will
>> automatically replicate the zones to the new server. Open DNS
>> management console to check that they appear
>>
>> - if the new machine is domain controller and DNS server run again
>> replmon, dcdiag and netdiag on both domain controllers
>>
>> - if you have no errors, make the new server Global catalog server,
>> open Active directory Sites and Services and then double-click
>> sitename, double-click Servers, click your domain controller,
>> right-click NTDS Settings, and then click Properties, on the General
>> tab, click to select the Global catalog check box
>> (http://support.microsoft.com/?id=313994)
>>
>> - Transfer, NOT seize the 5 FSMO roles to the new Domain controller
>> (http://support.microsoft.com/kb/324801)
>>
>> - you can see in the event viewer (Directory service) that the roles
>> are transferred, also give it some time
>>
>> - reconfigure the DNS configuration on your NIC of the 2003 server,
>> preferred DNS itself, secondary the old one
>>
>> - if you use DHCP do not forget to reconfigure the scope settings to
>> point to the new installed DNS server
>>
>> - export and import of DHCP database (if needed)
>> (http://support.microsoft.com/kb/325473)
>>
>> - backup WINS
>> (http://technet.microsoft.com/en-us/l.../cc727901.aspx)
>>
>> - restore WINS
>> (http://technet.microsoft.com/en-us/l.../cc727960.aspx)
>>
>> - in Exchange system Manger under "Recipients" reconfigure the
>> "Recipients update service" to the new DC/GC
>>
>> Demoting the old DC (if needed)
>>
>> - reconfigure your clients/servers that they not longer point to the
>> old DC/DNS server on the NIC
>>
>> - to be sure that everything runs fine, disconnect the old DC from
>> the network and check with clients and servers the connectivity,
>> logon and also with one client a restart to see that everything is ok
>>
>> - then run dcpromo to demote the old DC, if it works fine the machine
>> will move from the DC's OU to the computers container, where you can
>> delete it by hand. Can be that you got an error during demoting at
>> the beginning, then uncheck the Global catalog on that DC and try
>> again
>>
>> - check the DNS management console, that all entries from the machine
>> are disappeared or delete them by hand if the machine is off the
>> network for ever
>>
>> - also you have to start AD sites and services and delete the old
>> servername under the site, this will not be done during demotion
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> Hello im currently running a network for a client that has three HP
>>> DL380G4 Servers running Windows Server 2003. They have 1 Domain
>>> Controller (DC1), 1 Exchange Server (MS1) & 1 ISA Server (ISA1).
>>> The DC1 Server has had many issues over the last month that are
>>> ongoing so the client has decided to replace ther server, upto now i
>>> have only installed new systems from the ground up, this is my first
>>> time of replacing a current server with new hardware, i need to know
>>> how much work is involved in this in regards to Active Directory,
>>> links to the Exchange Server etc.
>>>
>>> Any links to help guides would be great.
>>>

Hello Meinolf please find below the test results foe netdiag and dcdiag, i
would be grateful if you could check them for me also how do i check if im
running an Active Directory Intergrated Zone?


Also these tests were taken when the server was online but for the last 3
weeks it seems to go offline every 2 hours and needs rebooting to restore
connectivity with the network - i have installed new network card and dealt
with all errors that were in event viewer - this server was due to be
replaced in May but as i could not seem to resolve the issue we have decided
to replace it now.


DCDIAG Test Results:

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>dcdiag

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site\DC1
Starting test: Connectivity
......................... DC1 passed test Connectivity

Doing primary tests

Testing server: Default-First-Site\DC1
Starting test: Replications
......................... DC1 passed test Replications
Starting test: NCSecDesc
......................... DC1 passed test NCSecDesc
Starting test: NetLogons
......................... DC1 passed test NetLogons
Starting test: Advertising
......................... DC1 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... DC1 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... DC1 passed test RidManager
Starting test: MachineAccount
......................... DC1 passed test MachineAccount
Starting test: Services
......................... DC1 passed test Services
Starting test: ObjectsReplicated
......................... DC1 passed test ObjectsReplicated
Starting test: frssysvol
......................... DC1 passed test frssysvol
Starting test: frsevent
......................... DC1 passed test frsevent
Starting test: kccevent
......................... DC1 passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0xC0001B78
Time Generated: 01/20/2009 13:59:12
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0001B58
Time Generated: 01/20/2009 14:13:38
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000416
Time Generated: 01/20/2009 14:13:46
Event String: The DHCP/BINL service on the local machine,
An Error Event occured. EventID: 0xC0040007
Time Generated: 01/20/2009 14:35:36
Event String: The device, \Device\CdRom0, has a bad block.
An Error Event occured. EventID: 0xC0040007
Time Generated: 01/20/2009 14:35:45
Event String: The device, \Device\CdRom0, has a bad block.
An Error Event occured. EventID: 0xC0040007
Time Generated: 01/20/2009 14:35:51
Event String: The device, \Device\CdRom0, has a bad block.
An Error Event occured. EventID: 0xC0040007
Time Generated: 01/20/2009 14:36:01
Event String: The device, \Device\CdRom0, has a bad block.
An Error Event occured. EventID: 0xC0040007
Time Generated: 01/20/2009 14:36:07
Event String: The device, \Device\CdRom0, has a bad block.
An Error Event occured. EventID: 0xC0040007
Time Generated: 01/20/2009 14:37:38
Event String: The device, \Device\CdRom0, has a bad block.
An Error Event occured. EventID: 0xC0040007
Time Generated: 01/20/2009 14:37:44
Event String: The device, \Device\CdRom0, has a bad block.
An Error Event occured. EventID: 0xC0040007
Time Generated: 01/20/2009 14:37:50
Event String: The device, \Device\CdRom0, has a bad block.
An Error Event occured. EventID: 0xC0040007
Time Generated: 01/20/2009 14:37:57
Event String: The device, \Device\CdRom0, has a bad block.
An Error Event occured. EventID: 0xC0040007
Time Generated: 01/20/2009 14:38:04
Event String: The device, \Device\CdRom0, has a bad block.
An Error Event occured. EventID: 0xC0040007
Time Generated: 01/20/2009 14:38:11
Event String: The device, \Device\CdRom0, has a bad block.
An Error Event occured. EventID: 0xC0040007
Time Generated: 01/20/2009 14:38:21
Event String: The device, \Device\CdRom0, has a bad block.
An Error Event occured. EventID: 0xC0040007
Time Generated: 01/20/2009 14:38:27
Event String: The device, \Device\CdRom0, has a bad block.
An Error Event occured. EventID: 0xC0040007
Time Generated: 01/20/2009 14:38:34
Event String: The device, \Device\CdRom0, has a bad block.
An Error Event occured. EventID: 0xC0040007
Time Generated: 01/20/2009 14:38:41
Event String: The device, \Device\CdRom0, has a bad block.
An Error Event occured. EventID: 0xC0040007
Time Generated: 01/20/2009 14:38:48
Event String: The device, \Device\CdRom0, has a bad block.
An Error Event occured. EventID: 0xC0040007
Time Generated: 01/20/2009 14:38:54
Event String: The device, \Device\CdRom0, has a bad block.
An Error Event occured. EventID: 0xC0040007
Time Generated: 01/20/2009 14:39:06
Event String: The device, \Device\CdRom0, has a bad block.
An Error Event occured. EventID: 0xC0040007
Time Generated: 01/20/2009 14:39:13
Event String: The device, \Device\CdRom0, has a bad block.
An Error Event occured. EventID: 0xC0040007
Time Generated: 01/20/2009 14:39:22
Event String: The device, \Device\CdRom0, has a bad block.
An Error Event occured. EventID: 0xC0040007
Time Generated: 01/20/2009 14:39:28
Event String: The device, \Device\CdRom0, has a bad block.
An Error Event occured. EventID: 0xC0040007
Time Generated: 01/20/2009 14:39:35
Event String: The device, \Device\CdRom0, has a bad block.
......................... DC1 failed test systemlog
Starting test: VerifyReferences
......................... DC1 passed test VerifyReferences

Running partition tests on : TAPI3Directory
Starting test: CrossRefValidation
......................... TAPI3Directory passed test
CrossRefValidation

Starting test: CheckSDRefDom
......................... TAPI3Directory passed test CheckSDRefDom

Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation

Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom

Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation

Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom

Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom

Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom

Running partition tests on : ne-rfca
Starting test: CrossRefValidation
......................... ne-rfca passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ne-rfca passed test CheckSDRefDom

Running enterprise tests on : ne-rfca.local
Starting test: Intersite
......................... ne-rfca.local passed test Intersite
Starting test: FsmoCheck
......................... ne-rfca.local passed test FsmoCheck

C:\Documents and Settings\Administrator>





NETDIAG Test Results:


Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>netdiag

......................................

Computer Name: DC1
DNS Host Name: DC1.ne-rfca.local
System info : Microsoft Windows Server 2003 (Build 3790)
Processor : x86 Family 15 Model 4 Stepping 1, GenuineIntel
List of installed hotfixes :
KB890046
KB893756
KB896358
KB896422
KB896424
KB896428
KB899587
KB899588
KB899589
KB899591
KB900725
KB901017
KB901214
KB902400
KB904706
KB905414
KB907265
KB908519
KB908521
KB908531
KB910437
KB911280
KB911562
KB911564
KB911567
KB911927
KB912919
KB914388
KB914389
KB916281
KB917159
KB917344
KB917422
KB917537
KB917734
KB917953
KB918439
KB918899
KB920214
KB920670
KB920683
KB920685
KB921398
KB921883
KB922582
KB922616
Q147222


Netcard queries test . . . . . . . : Passed



Per interface results:

Adapter : Local Area Connection 5

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : DC1
IP Address . . . . . . . . : 25.14.168.11
Subnet Mask. . . . . . . . : 255.255.255.192
Default Gateway. . . . . . : 25.14.168.1
Dns Servers. . . . . . . . : 25.14.168.11
25.31.11.2


AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed
No remote names have been found.

WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{1FE061C8-E0AE-40AD-977B-41D671C4707A}
1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


NetBT name test. . . . . . . . . . : Passed


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Passed
PASS - All the DNS entries for DC are registered on DNS server
'25.14.168.11
'.
[WARNING] The DNS entries for this DC are not registered correctly on
DNS se
rver '25.31.11.2'. Please wait for 30 minutes for DNS server replication.


Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{1FE061C8-E0AE-40AD-977B-41D671C4707A}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{1FE061C8-E0AE-40AD-977B-41D671C4707A}
The browser is bound to 1 NetBt transport.


DC discovery test. . . . . . . . . : Passed


DC list test . . . . . . . . . . . : Passed


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Passed


LDAP test. . . . . . . . . . . . . : Passed


Bindings test. . . . . . . . . . . : Passed


WAN configuration test . . . . . . : Skipped
No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

Note: run "netsh ipsec dynamic show /?" for more detailed information


The command completed successfully

C:\Documents and Settings\Administrator>


"Meinolf Weber [MVP-DS]" wrote:

> Hello Lee,
>
> AD is based on DNS, so there is no need for changing the ip to the old one.
> If you still will do it change it and check that the record in DNS zones
> will also update.
>
> Using the same name for the new DC creates additional workload for you and
> requires a temp DC to remove the old one and free the name for the new one.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>
> > Thanks for that it will be a real help form me but i have two
> > questions following that.
> >
> > 1. The old server will be removed from the network so the new server
> > will be the DC/AD Server but i have to give that server the same ip
> > address as the one i am removing from the system, is that ok and do i
> > run it on a temporary address then change it once the old server is
> > off the network?
> >
> > 2. Is it best practice to give the new domain controller a different
> > name to the old one even when the old server is no longer on the
> > network?
> >
> > Thanks Again
> >
> > "Meinolf Weber [MVP-DS]" wrote:
> >
> >> Hello Lee,
> >>
> >> - On the old server open DNS management console and check that you
> >> are running Active directory integrated zone (easier for replication,
> >> if you have more then one DNS server)
> >>
> >> - run replmon from the run line or repadmin /showrepl (only if more
> >> then one DC exist), dcdiag and netdiag from the command prompt on the
> >> old machine to check for errors, if you have some post the complete
> >> output from the command here or solve them first. For this tools you
> >> have to install the support\tools\suptools.msi from the 2003
> >> installation disk.
> >>
> >> - Install the new machine as a member server in your existing domain
> >>
> >> - configure a fixed ip and set the preferred DNS server to the old
> >> DNS server only
> >>
> >> - run dcpromo and follow the wizard to add the 2003 server to an
> >> existing domain
> >>
> >> - if you are prompted for DNS configuration choose Yes (also possible
> >> that no DNS preparation occur), then install DNS after the reboot
> >>
> >> - for DNS give the server time for replication, at least 15 minutes.
> >> Because you use Active directory integrated zones it will
> >> automatically replicate the zones to the new server. Open DNS
> >> management console to check that they appear
> >>
> >> - if the new machine is domain controller and DNS server run again
> >> replmon, dcdiag and netdiag on both domain controllers
> >>
> >> - if you have no errors, make the new server Global catalog server,
> >> open Active directory Sites and Services and then double-click
> >> sitename, double-click Servers, click your domain controller,
> >> right-click NTDS Settings, and then click Properties, on the General
> >> tab, click to select the Global catalog check box
> >> (http://support.microsoft.com/?id=313994)
> >>
> >> - Transfer, NOT seize the 5 FSMO roles to the new Domain controller
> >> (http://support.microsoft.com/kb/324801)
> >>
> >> - you can see in the event viewer (Directory service) that the roles
> >> are transferred, also give it some time
> >>
> >> - reconfigure the DNS configuration on your NIC of the 2003 server,
> >> preferred DNS itself, secondary the old one
> >>
> >> - if you use DHCP do not forget to reconfigure the scope settings to
> >> point to the new installed DNS server
> >>
> >> - export and import of DHCP database (if needed)
> >> (http://support.microsoft.com/kb/325473)
> >>
> >> - backup WINS
> >> (http://technet.microsoft.com/en-us/l.../cc727901.aspx)
> >>
> >> - restore WINS
> >> (http://technet.microsoft.com/en-us/l.../cc727960.aspx)
> >>
> >> - in Exchange system Manger under "Recipients" reconfigure the
> >> "Recipients update service" to the new DC/GC
> >>
> >> Demoting the old DC (if needed)
> >>
> >> - reconfigure your clients/servers that they not longer point to the
> >> old DC/DNS server on the NIC
> >>
> >> - to be sure that everything runs fine, disconnect the old DC from
> >> the network and check with clients and servers the connectivity,
> >> logon and also with one client a restart to see that everything is ok
> >>
> >> - then run dcpromo to demote the old DC, if it works fine the machine
> >> will move from the DC's OU to the computers container, where you can
> >> delete it by hand. Can be that you got an error during demoting at
> >> the beginning, then uncheck the Global catalog on that DC and try
> >> again
> >>
> >> - check the DNS management console, that all entries from the machine
> >> are disappeared or delete them by hand if the machine is off the
> >> network for ever
> >>
> >> - also you have to start AD sites and services and delete the old
> >> servername under the site, this will not be done during demotion
> >>
> >> Best regards
> >>
> >> Meinolf Weber
> >> Disclaimer: This posting is provided "AS IS" with no warranties, and
> >> confers
> >> no rights.
> >> ** Please do NOT email, only reply to Newsgroups
> >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
> >>> Hello im currently running a network for a client that has three HP
> >>> DL380G4 Servers running Windows Server 2003. They have 1 Domain
> >>> Controller (DC1), 1 Exchange Server (MS1) & 1 ISA Server (ISA1).
> >>> The DC1 Server has had many issues over the last month that are
> >>> ongoing so the client has decided to replace ther server, upto now i
> >>> have only installed new systems from the ground up, this is my first
> >>> time of replacing a current server with new hardware, i need to know
> >>> how much work is involved in this in regards to Active Directory,
> >>> links to the Exchange Server etc.
> >>>
> >>> Any links to help guides would be great.
> >>>
>
>
>

Hello Lee,

Open DNS management console and highlight the Forward/Reverse lookup zone,
in the right pane you will see type.

From dcdiag, for the errors displayed there under "systemlog" check the event
viewer system log. There you should find errors, which are maybe resolved.
To make sure you can save and delete the systemlog and wait 2 days, then
run dcdiag again. Rest seems to be fine.

From netdiag, the servers are not in the internet i hope, because you didn't
use private ip range. Why 25.31.11.2 from a different ip range? Is it your
ISP? For domain connectivity use only domain internal DNS servers, so point
the server to the DC/DNS that should be removed.


If not done i would also update to SP2 and latest patches.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Hello Meinolf please find below the test results foe netdiag and
> dcdiag, i would be grateful if you could check them for me also how do
> i check if im running an Active Directory Intergrated Zone?
>
> Also these tests were taken when the server was online but for the
> last 3 weeks it seems to go offline every 2 hours and needs rebooting
> to restore connectivity with the network - i have installed new
> network card and dealt with all errors that were in event viewer -
> this server was due to be replaced in May but as i could not seem to
> resolve the issue we have decided to replace it now.
>
> DCDIAG Test Results:
>
> Microsoft Windows [Version 5.2.3790]
> (C) Copyright 1985-2003 Microsoft Corp.
> C:\Documents and Settings\Administrator>dcdiag
>
> Domain Controller Diagnosis
>
> Performing initial setup:
> Done gathering initial info.
> Doing initial required tests
>
> Testing server: Default-First-Site\DC1
> Starting test: Connectivity
> ......................... DC1 passed test Connectivity
> Doing primary tests
>
> Testing server: Default-First-Site\DC1
> Starting test: Replications
> ......................... DC1 passed test Replications
> Starting test: NCSecDesc
> ......................... DC1 passed test NCSecDesc
> Starting test: NetLogons
> ......................... DC1 passed test NetLogons
> Starting test: Advertising
> ......................... DC1 passed test Advertising
> Starting test: KnowsOfRoleHolders
> ......................... DC1 passed test KnowsOfRoleHolders
> Starting test: RidManager
> ......................... DC1 passed test RidManager
> Starting test: MachineAccount
> ......................... DC1 passed test MachineAccount
> Starting test: Services
> ......................... DC1 passed test Services
> Starting test: ObjectsReplicated
> ......................... DC1 passed test ObjectsReplicated
> Starting test: frssysvol
> ......................... DC1 passed test frssysvol
> Starting test: frsevent
> ......................... DC1 passed test frsevent
> Starting test: kccevent
> ......................... DC1 passed test kccevent
> Starting test: systemlog
> An Error Event occured. EventID: 0xC0001B78
> Time Generated: 01/20/2009 13:59:12
> (Event String could not be retrieved)
> An Error Event occured. EventID: 0xC0001B58
> Time Generated: 01/20/2009 14:13:38
> (Event String could not be retrieved)
> An Error Event occured. EventID: 0x00000416
> Time Generated: 01/20/2009 14:13:46
> Event String: The DHCP/BINL service on the local machine,
> An Error Event occured. EventID: 0xC0040007
> Time Generated: 01/20/2009 14:35:36
> Event String: The device, \Device\CdRom0, has a bad block.
> An Error Event occured. EventID: 0xC0040007
> Time Generated: 01/20/2009 14:35:45
> Event String: The device, \Device\CdRom0, has a bad block.
> An Error Event occured. EventID: 0xC0040007
> Time Generated: 01/20/2009 14:35:51
> Event String: The device, \Device\CdRom0, has a bad block.
> An Error Event occured. EventID: 0xC0040007
> Time Generated: 01/20/2009 14:36:01
> Event String: The device, \Device\CdRom0, has a bad block.
> An Error Event occured. EventID: 0xC0040007
> Time Generated: 01/20/2009 14:36:07
> Event String: The device, \Device\CdRom0, has a bad block.
> An Error Event occured. EventID: 0xC0040007
> Time Generated: 01/20/2009 14:37:38
> Event String: The device, \Device\CdRom0, has a bad block.
> An Error Event occured. EventID: 0xC0040007
> Time Generated: 01/20/2009 14:37:44
> Event String: The device, \Device\CdRom0, has a bad block.
> An Error Event occured. EventID: 0xC0040007
> Time Generated: 01/20/2009 14:37:50
> Event String: The device, \Device\CdRom0, has a bad block.
> An Error Event occured. EventID: 0xC0040007
> Time Generated: 01/20/2009 14:37:57
> Event String: The device, \Device\CdRom0, has a bad block.
> An Error Event occured. EventID: 0xC0040007
> Time Generated: 01/20/2009 14:38:04
> Event String: The device, \Device\CdRom0, has a bad block.
> An Error Event occured. EventID: 0xC0040007
> Time Generated: 01/20/2009 14:38:11
> Event String: The device, \Device\CdRom0, has a bad block.
> An Error Event occured. EventID: 0xC0040007
> Time Generated: 01/20/2009 14:38:21
> Event String: The device, \Device\CdRom0, has a bad block.
> An Error Event occured. EventID: 0xC0040007
> Time Generated: 01/20/2009 14:38:27
> Event String: The device, \Device\CdRom0, has a bad block.
> An Error Event occured. EventID: 0xC0040007
> Time Generated: 01/20/2009 14:38:34
> Event String: The device, \Device\CdRom0, has a bad block.
> An Error Event occured. EventID: 0xC0040007
> Time Generated: 01/20/2009 14:38:41
> Event String: The device, \Device\CdRom0, has a bad block.
> An Error Event occured. EventID: 0xC0040007
> Time Generated: 01/20/2009 14:38:48
> Event String: The device, \Device\CdRom0, has a bad block.
> An Error Event occured. EventID: 0xC0040007
> Time Generated: 01/20/2009 14:38:54
> Event String: The device, \Device\CdRom0, has a bad block.
> An Error Event occured. EventID: 0xC0040007
> Time Generated: 01/20/2009 14:39:06
> Event String: The device, \Device\CdRom0, has a bad block.
> An Error Event occured. EventID: 0xC0040007
> Time Generated: 01/20/2009 14:39:13
> Event String: The device, \Device\CdRom0, has a bad block.
> An Error Event occured. EventID: 0xC0040007
> Time Generated: 01/20/2009 14:39:22
> Event String: The device, \Device\CdRom0, has a bad block.
> An Error Event occured. EventID: 0xC0040007
> Time Generated: 01/20/2009 14:39:28
> Event String: The device, \Device\CdRom0, has a bad block.
> An Error Event occured. EventID: 0xC0040007
> Time Generated: 01/20/2009 14:39:35
> Event String: The device, \Device\CdRom0, has a bad block.
> ......................... DC1 failed test systemlog
> Starting test: VerifyReferences
> ......................... DC1 passed test VerifyReferences
> Running partition tests on : TAPI3Directory
> Starting test: CrossRefValidation
> ......................... TAPI3Directory passed test
> CrossRefValidation
> Starting test: CheckSDRefDom
> ......................... TAPI3Directory passed test
> CheckSDRefDom
> Running partition tests on : ForestDnsZones
> Starting test: CrossRefValidation
> ......................... ForestDnsZones passed test
> CrossRefValidation
> Starting test: CheckSDRefDom
> ......................... ForestDnsZones passed test
> CheckSDRefDom
> Running partition tests on : DomainDnsZones
> Starting test: CrossRefValidation
> ......................... DomainDnsZones passed test
> CrossRefValidation
> Starting test: CheckSDRefDom
> ......................... DomainDnsZones passed test
> CheckSDRefDom
> Running partition tests on : Schema
> Starting test: CrossRefValidation
> ......................... Schema passed test
> CrossRefValidation
> Starting test: CheckSDRefDom
> ......................... Schema passed test CheckSDRefDom
> Running partition tests on : Configuration
> Starting test: CrossRefValidation
> ......................... Configuration passed test
> CrossRefValidation
> Starting test: CheckSDRefDom
> ......................... Configuration passed test
> CheckSDRefDom
> Running partition tests on : ne-rfca
> Starting test: CrossRefValidation
> ......................... ne-rfca passed test
> CrossRefValidation
> Starting test: CheckSDRefDom
> ......................... ne-rfca passed test CheckSDRefDom
> Running enterprise tests on : ne-rfca.local
> Starting test: Intersite
> ......................... ne-rfca.local passed test Intersite
> Starting test: FsmoCheck
> ......................... ne-rfca.local passed test FsmoCheck
> C:\Documents and Settings\Administrator>
>
> NETDIAG Test Results:
>
> Microsoft Windows [Version 5.2.3790]
> (C) Copyright 1985-2003 Microsoft Corp.
> C:\Documents and Settings\Administrator>netdiag
>
> .....................................
>
> Computer Name: DC1
> DNS Host Name: DC1.ne-rfca.local
> System info : Microsoft Windows Server 2003 (Build 3790)
> Processor : x86 Family 15 Model 4 Stepping 1, GenuineIntel
> List of installed hotfixes :
> KB890046
> KB893756
> KB896358
> KB896422
> KB896424
> KB896428
> KB899587
> KB899588
> KB899589
> KB899591
> KB900725
> KB901017
> KB901214
> KB902400
> KB904706
> KB905414
> KB907265
> KB908519
> KB908521
> KB908531
> KB910437
> KB911280
> KB911562
> KB911564
> KB911567
> KB911927
> KB912919
> KB914388
> KB914389
> KB916281
> KB917159
> KB917344
> KB917422
> KB917537
> KB917734
> KB917953
> KB918439
> KB918899
> KB920214
> KB920670
> KB920683
> KB920685
> KB921398
> KB921883
> KB922582
> KB922616
> Q147222
> Netcard queries test . . . . . . . : Passed
>
> Per interface results:
>
> Adapter : Local Area Connection 5
>
> Netcard queries test . . . : Passed
>
> Host Name. . . . . . . . . : DC1
> IP Address . . . . . . . . : 25.14.168.11
> Subnet Mask. . . . . . . . : 255.255.255.192
> Default Gateway. . . . . . : 25.14.168.1
> Dns Servers. . . . . . . . : 25.14.168.11
> 25.31.11.2
> AutoConfiguration results. . . . . . : Passed
>
> Default gateway test . . . : Passed
>
> NetBT name test. . . . . . : Passed
> No remote names have been found.
> WINS service test. . . . . : Skipped
> There are no WINS servers configured for this interface.
> Global results:
>
> Domain membership test . . . . . . : Passed
>
> NetBT transports test. . . . . . . : Passed
> List of NetBt transports currently configured:
> NetBT_Tcpip_{1FE061C8-E0AE-40AD-977B-41D671C4707A}
> 1 NetBt transport currently configured.
> Autonet address test . . . . . . . : Passed
>
> IP loopback ping test. . . . . . . : Passed
>
> Default gateway test . . . . . . . : Passed
>
> NetBT name test. . . . . . . . . . : Passed
>
> Winsock test . . . . . . . . . . . : Passed
>
> DNS test . . . . . . . . . . . . . : Passed
> PASS - All the DNS entries for DC are registered on DNS server
> '25.14.168.11
> '.
> [WARNING] The DNS entries for this DC are not registered correctly
> on
> DNS se
> rver '25.31.11.2'. Please wait for 30 minutes for DNS server
> replication.
>
> Redir and Browser test . . . . . . : Passed
> List of NetBt transports currently bound to the Redir
> NetBT_Tcpip_{1FE061C8-E0AE-40AD-977B-41D671C4707A}
> The redir is bound to 1 NetBt transport.
> List of NetBt transports currently bound to the browser
> NetBT_Tcpip_{1FE061C8-E0AE-40AD-977B-41D671C4707A}
> The browser is bound to 1 NetBt transport.
> DC discovery test. . . . . . . . . : Passed
>
> DC list test . . . . . . . . . . . : Passed
>
> Trust relationship test. . . . . . : Skipped
>
> Kerberos test. . . . . . . . . . . : Passed
>
> LDAP test. . . . . . . . . . . . . : Passed
>
> Bindings test. . . . . . . . . . . : Passed
>
> WAN configuration test . . . . . . : Skipped
> No active remote access connections.
> Modem diagnostics test . . . . . . : Passed
>
> IP Security test . . . . . . . . . : Skipped
>
> Note: run "netsh ipsec dynamic show /?" for more detailed
> information
>
> The command completed successfully
>
> C:\Documents and Settings\Administrator>
>
> "Meinolf Weber [MVP-DS]" wrote:
>
>> Hello Lee,
>>
>> AD is based on DNS, so there is no need for changing the ip to the
>> old one. If you still will do it change it and check that the record
>> in DNS zones will also update.
>>
>> Using the same name for the new DC creates additional workload for
>> you and requires a temp DC to remove the old one and free the name
>> for the new one.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> Thanks for that it will be a real help form me but i have two
>>> questions following that.
>>>
>>> 1. The old server will be removed from the network so the new server
>>> will be the DC/AD Server but i have to give that server the same ip
>>> address as the one i am removing from the system, is that ok and do
>>> i run it on a temporary address then change it once the old server
>>> is off the network?
>>>
>>> 2. Is it best practice to give the new domain controller a different
>>> name to the old one even when the old server is no longer on the
>>> network?
>>>
>>> Thanks Again
>>>
>>> "Meinolf Weber [MVP-DS]" wrote:
>>>
>>>> Hello Lee,
>>>>
>>>> - On the old server open DNS management console and check that you
>>>> are running Active directory integrated zone (easier for
>>>> replication, if you have more then one DNS server)
>>>>
>>>> - run replmon from the run line or repadmin /showrepl (only if more
>>>> then one DC exist), dcdiag and netdiag from the command prompt on
>>>> the old machine to check for errors, if you have some post the
>>>> complete output from the command here or solve them first. For this
>>>> tools you have to install the support\tools\suptools.msi from the
>>>> 2003 installation disk.
>>>>
>>>> - Install the new machine as a member server in your existing
>>>> domain
>>>>
>>>> - configure a fixed ip and set the preferred DNS server to the old
>>>> DNS server only
>>>>
>>>> - run dcpromo and follow the wizard to add the 2003 server to an
>>>> existing domain
>>>>
>>>> - if you are prompted for DNS configuration choose Yes (also
>>>> possible that no DNS preparation occur), then install DNS after the
>>>> reboot
>>>>
>>>> - for DNS give the server time for replication, at least 15
>>>> minutes. Because you use Active directory integrated zones it will
>>>> automatically replicate the zones to the new server. Open DNS
>>>> management console to check that they appear
>>>>
>>>> - if the new machine is domain controller and DNS server run again
>>>> replmon, dcdiag and netdiag on both domain controllers
>>>>
>>>> - if you have no errors, make the new server Global catalog server,
>>>> open Active directory Sites and Services and then double-click
>>>> sitename, double-click Servers, click your domain controller,
>>>> right-click NTDS Settings, and then click Properties, on the
>>>> General tab, click to select the Global catalog check box
>>>> (http://support.microsoft.com/?id=313994)
>>>>
>>>> - Transfer, NOT seize the 5 FSMO roles to the new Domain controller
>>>> (http://support.microsoft.com/kb/324801)
>>>>
>>>> - you can see in the event viewer (Directory service) that the
>>>> roles are transferred, also give it some time
>>>>
>>>> - reconfigure the DNS configuration on your NIC of the 2003 server,
>>>> preferred DNS itself, secondary the old one
>>>>
>>>> - if you use DHCP do not forget to reconfigure the scope settings
>>>> to point to the new installed DNS server
>>>>
>>>> - export and import of DHCP database (if needed)
>>>> (http://support.microsoft.com/kb/325473)
>>>> - backup WINS
>>>> (http://technet.microsoft.com/en-us/l.../cc727901.aspx)
>>>> - restore WINS
>>>> (http://technet.microsoft.com/en-us/l.../cc727960.aspx)
>>>> - in Exchange system Manger under "Recipients" reconfigure the
>>>> "Recipients update service" to the new DC/GC
>>>>
>>>> Demoting the old DC (if needed)
>>>>
>>>> - reconfigure your clients/servers that they not longer point to
>>>> the old DC/DNS server on the NIC
>>>>
>>>> - to be sure that everything runs fine, disconnect the old DC from
>>>> the network and check with clients and servers the connectivity,
>>>> logon and also with one client a restart to see that everything is
>>>> ok
>>>>
>>>> - then run dcpromo to demote the old DC, if it works fine the
>>>> machine will move from the DC's OU to the computers container,
>>>> where you can delete it by hand. Can be that you got an error
>>>> during demoting at the beginning, then uncheck the Global catalog
>>>> on that DC and try again
>>>>
>>>> - check the DNS management console, that all entries from the
>>>> machine are disappeared or delete them by hand if the machine is
>>>> off the network for ever
>>>>
>>>> - also you have to start AD sites and services and delete the old
>>>> servername under the site, this will not be done during demotion
>>>>
>>>> Best regards
>>>>
>>>> Meinolf Weber
>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
>>>> and
>>>> confers
>>>> no rights.
>>>> ** Please do NOT email, only reply to Newsgroups
>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>>>> Hello im currently running a network for a client that has three
>>>>> HP
>>>>> DL380G4 Servers running Windows Server 2003. They have 1 Domain
>>>>> Controller (DC1), 1 Exchange Server (MS1) & 1 ISA Server (ISA1).
>>>>> The DC1 Server has had many issues over the last month that are
>>>>> ongoing so the client has decided to replace ther server, upto now
>>>>> i
>>>>> have only installed new systems from the ground up, this is my
>>>>> first
>>>>> time of replacing a current server with new hardware, i need to
>>>>> know
>>>>> how much work is involved in this in regards to Active Directory,
>>>>> links to the Exchange Server etc.
>>>>> Any links to help guides would be great.
>>>>>

Thanks for that the IP you mention is as follows, the client is part of the
Ministry of Defence and are on RLI Military protected Broadband and we were
advised to point to that, do you think it is serving no purpose doing that as
we dont need internet connectivity on the servers?

"Meinolf Weber [MVP-DS]" wrote:

> Hello Lee,
>
> Open DNS management console and highlight the Forward/Reverse lookup zone,
> in the right pane you will see type.
>
> From dcdiag, for the errors displayed there under "systemlog" check the event
> viewer system log. There you should find errors, which are maybe resolved.
> To make sure you can save and delete the systemlog and wait 2 days, then
> run dcdiag again. Rest seems to be fine.
>
> From netdiag, the servers are not in the internet i hope, because you didn't
> use private ip range. Why 25.31.11.2 from a different ip range? Is it your
> ISP? For domain connectivity use only domain internal DNS servers, so point
> the server to the DC/DNS that should be removed.
>
>
> If not done i would also update to SP2 and latest patches.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>
> > Hello Meinolf please find below the test results foe netdiag and
> > dcdiag, i would be grateful if you could check them for me also how do
> > i check if im running an Active Directory Intergrated Zone?
> >
> > Also these tests were taken when the server was online but for the
> > last 3 weeks it seems to go offline every 2 hours and needs rebooting
> > to restore connectivity with the network - i have installed new
> > network card and dealt with all errors that were in event viewer -
> > this server was due to be replaced in May but as i could not seem to
> > resolve the issue we have decided to replace it now.
> >
> > DCDIAG Test Results:
> >
> > Microsoft Windows [Version 5.2.3790]
> > (C) Copyright 1985-2003 Microsoft Corp.
> > C:\Documents and Settings\Administrator>dcdiag
> >
> > Domain Controller Diagnosis
> >
> > Performing initial setup:
> > Done gathering initial info.
> > Doing initial required tests
> >
> > Testing server: Default-First-Site\DC1
> > Starting test: Connectivity
> > ......................... DC1 passed test Connectivity
> > Doing primary tests
> >
> > Testing server: Default-First-Site\DC1
> > Starting test: Replications
> > ......................... DC1 passed test Replications
> > Starting test: NCSecDesc
> > ......................... DC1 passed test NCSecDesc
> > Starting test: NetLogons
> > ......................... DC1 passed test NetLogons
> > Starting test: Advertising
> > ......................... DC1 passed test Advertising
> > Starting test: KnowsOfRoleHolders
> > ......................... DC1 passed test KnowsOfRoleHolders
> > Starting test: RidManager
> > ......................... DC1 passed test RidManager
> > Starting test: MachineAccount
> > ......................... DC1 passed test MachineAccount
> > Starting test: Services
> > ......................... DC1 passed test Services
> > Starting test: ObjectsReplicated
> > ......................... DC1 passed test ObjectsReplicated
> > Starting test: frssysvol
> > ......................... DC1 passed test frssysvol
> > Starting test: frsevent
> > ......................... DC1 passed test frsevent
> > Starting test: kccevent
> > ......................... DC1 passed test kccevent
> > Starting test: systemlog
> > An Error Event occured. EventID: 0xC0001B78
> > Time Generated: 01/20/2009 13:59:12
> > (Event String could not be retrieved)
> > An Error Event occured. EventID: 0xC0001B58
> > Time Generated: 01/20/2009 14:13:38
> > (Event String could not be retrieved)
> > An Error Event occured. EventID: 0x00000416
> > Time Generated: 01/20/2009 14:13:46
> > Event String: The DHCP/BINL service on the local machine,
> > An Error Event occured. EventID: 0xC0040007
> > Time Generated: 01/20/2009 14:35:36
> > Event String: The device, \Device\CdRom0, has a bad block.
> > An Error Event occured. EventID: 0xC0040007
> > Time Generated: 01/20/2009 14:35:45
> > Event String: The device, \Device\CdRom0, has a bad block.
> > An Error Event occured. EventID: 0xC0040007
> > Time Generated: 01/20/2009 14:35:51
> > Event String: The device, \Device\CdRom0, has a bad block.
> > An Error Event occured. EventID: 0xC0040007
> > Time Generated: 01/20/2009 14:36:01
> > Event String: The device, \Device\CdRom0, has a bad block.
> > An Error Event occured. EventID: 0xC0040007
> > Time Generated: 01/20/2009 14:36:07
> > Event String: The device, \Device\CdRom0, has a bad block.
> > An Error Event occured. EventID: 0xC0040007
> > Time Generated: 01/20/2009 14:37:38
> > Event String: The device, \Device\CdRom0, has a bad block.
> > An Error Event occured. EventID: 0xC0040007
> > Time Generated: 01/20/2009 14:37:44
> > Event String: The device, \Device\CdRom0, has a bad block.
> > An Error Event occured. EventID: 0xC0040007
> > Time Generated: 01/20/2009 14:37:50
> > Event String: The device, \Device\CdRom0, has a bad block.
> > An Error Event occured. EventID: 0xC0040007
> > Time Generated: 01/20/2009 14:37:57
> > Event String: The device, \Device\CdRom0, has a bad block.
> > An Error Event occured. EventID: 0xC0040007
> > Time Generated: 01/20/2009 14:38:04
> > Event String: The device, \Device\CdRom0, has a bad block.
> > An Error Event occured. EventID: 0xC0040007
> > Time Generated: 01/20/2009 14:38:11
> > Event String: The device, \Device\CdRom0, has a bad block.
> > An Error Event occured. EventID: 0xC0040007
> > Time Generated: 01/20/2009 14:38:21
> > Event String: The device, \Device\CdRom0, has a bad block.
> > An Error Event occured. EventID: 0xC0040007
> > Time Generated: 01/20/2009 14:38:27
> > Event String: The device, \Device\CdRom0, has a bad block.
> > An Error Event occured. EventID: 0xC0040007
> > Time Generated: 01/20/2009 14:38:34
> > Event String: The device, \Device\CdRom0, has a bad block.
> > An Error Event occured. EventID: 0xC0040007
> > Time Generated: 01/20/2009 14:38:41
> > Event String: The device, \Device\CdRom0, has a bad block.
> > An Error Event occured. EventID: 0xC0040007
> > Time Generated: 01/20/2009 14:38:48
> > Event String: The device, \Device\CdRom0, has a bad block.
> > An Error Event occured. EventID: 0xC0040007
> > Time Generated: 01/20/2009 14:38:54
> > Event String: The device, \Device\CdRom0, has a bad block.
> > An Error Event occured. EventID: 0xC0040007
> > Time Generated: 01/20/2009 14:39:06
> > Event String: The device, \Device\CdRom0, has a bad block.
> > An Error Event occured. EventID: 0xC0040007
> > Time Generated: 01/20/2009 14:39:13
> > Event String: The device, \Device\CdRom0, has a bad block.
> > An Error Event occured. EventID: 0xC0040007
> > Time Generated: 01/20/2009 14:39:22
> > Event String: The device, \Device\CdRom0, has a bad block.
> > An Error Event occured. EventID: 0xC0040007
> > Time Generated: 01/20/2009 14:39:28
> > Event String: The device, \Device\CdRom0, has a bad block.
> > An Error Event occured. EventID: 0xC0040007
> > Time Generated: 01/20/2009 14:39:35
> > Event String: The device, \Device\CdRom0, has a bad block.
> > ......................... DC1 failed test systemlog
> > Starting test: VerifyReferences
> > ......................... DC1 passed test VerifyReferences
> > Running partition tests on : TAPI3Directory
> > Starting test: CrossRefValidation
> > ......................... TAPI3Directory passed test
> > CrossRefValidation
> > Starting test: CheckSDRefDom
> > ......................... TAPI3Directory passed test
> > CheckSDRefDom
> > Running partition tests on : ForestDnsZones
> > Starting test: CrossRefValidation
> > ......................... ForestDnsZones passed test
> > CrossRefValidation
> > Starting test: CheckSDRefDom
> > ......................... ForestDnsZones passed test
> > CheckSDRefDom
> > Running partition tests on : DomainDnsZones
> > Starting test: CrossRefValidation
> > ......................... DomainDnsZones passed test
> > CrossRefValidation
> > Starting test: CheckSDRefDom
> > ......................... DomainDnsZones passed test
> > CheckSDRefDom
> > Running partition tests on : Schema
> > Starting test: CrossRefValidation
> > ......................... Schema passed test
> > CrossRefValidation
> > Starting test: CheckSDRefDom
> > ......................... Schema passed test CheckSDRefDom
> > Running partition tests on : Configuration
> > Starting test: CrossRefValidation
> > ......................... Configuration passed test
> > CrossRefValidation
> > Starting test: CheckSDRefDom
> > ......................... Configuration passed test
> > CheckSDRefDom
> > Running partition tests on : ne-rfca
> > Starting test: CrossRefValidation
> > ......................... ne-rfca passed test
> > CrossRefValidation
> > Starting test: CheckSDRefDom
> > ......................... ne-rfca passed test CheckSDRefDom
> > Running enterprise tests on : ne-rfca.local
> > Starting test: Intersite
> > ......................... ne-rfca.local passed test Intersite
> > Starting test: FsmoCheck
> > ......................... ne-rfca.local passed test FsmoCheck
> > C:\Documents and Settings\Administrator>
> >
> > NETDIAG Test Results:
> >
> > Microsoft Windows [Version 5.2.3790]
> > (C) Copyright 1985-2003 Microsoft Corp.
> > C:\Documents and Settings\Administrator>netdiag
> >
> > .....................................
> >
> > Computer Name: DC1
> > DNS Host Name: DC1.ne-rfca.local
> > System info : Microsoft Windows Server 2003 (Build 3790)
> > Processor : x86 Family 15 Model 4 Stepping 1, GenuineIntel
> > List of installed hotfixes :
> > KB890046
> > KB893756
> > KB896358
> > KB896422
> > KB896424
> > KB896428
> > KB899587
> > KB899588
> > KB899589
> > KB899591
> > KB900725
> > KB901017
> > KB901214
> > KB902400
> > KB904706
> > KB905414
> > KB907265
> > KB908519
> > KB908521
> > KB908531
> > KB910437
> > KB911280
> > KB911562
> > KB911564
> > KB911567
> > KB911927
> > KB912919
> > KB914388
> > KB914389
> > KB916281
> > KB917159
> > KB917344
> > KB917422
> > KB917537
> > KB917734
> > KB917953
> > KB918439
> > KB918899
> > KB920214
> > KB920670
> > KB920683
> > KB920685
> > KB921398
> > KB921883
> > KB922582
> > KB922616
> > Q147222
> > Netcard queries test . . . . . . . : Passed
> >
> > Per interface results:
> >
> > Adapter : Local Area Connection 5
> >
> > Netcard queries test . . . : Passed
> >
> > Host Name. . . . . . . . . : DC1
> > IP Address . . . . . . . . : 25.14.168.11
> > Subnet Mask. . . . . . . . : 255.255.255.192
> > Default Gateway. . . . . . : 25.14.168.1
> > Dns Servers. . . . . . . . : 25.14.168.11
> > 25.31.11.2
> > AutoConfiguration results. . . . . . : Passed
> >
> > Default gateway test . . . : Passed
> >
> > NetBT name test. . . . . . : Passed
> > No remote names have been found.
> > WINS service test. . . . . : Skipped
> > There are no WINS servers configured for this interface.
> > Global results:
> >
> > Domain membership test . . . . . . : Passed
> >
> > NetBT transports test. . . . . . . : Passed
> > List of NetBt transports currently configured:
> > NetBT_Tcpip_{1FE061C8-E0AE-40AD-977B-41D671C4707A}
> > 1 NetBt transport currently configured.
> > Autonet address test . . . . . . . : Passed
> >
> > IP loopback ping test. . . . . . . : Passed
> >

Hello Lee,

If your higher level orders to use that DNS server as secondary, use it.
For the new DC/DNS i would only use the existing DC/DNS 25.14.168.11 as preferred
until AD/DNS replication is done complete, after that change the ip to itself
as preferred and use the other DNS server as secondary.

Then for testing the new server from all clients, reconfigure them for the
new DNS, disconnect the old one (unplug network cable one or two days) and
check if everything is still running. Do not forget to make the DC also Global
catalog.

If all tests are ok reconnect the old server and you can start demoting it,
change the ip's etc.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Thanks for that the IP you mention is as follows, the client is part
> of the Ministry of Defence and are on RLI Military protected Broadband
> and we were advised to point to that, do you think it is serving no
> purpose doing that as we dont need internet connectivity on the
> servers?
>
> "Meinolf Weber [MVP-DS]" wrote:
>
>> Hello Lee,
>>
>> Open DNS management console and highlight the Forward/Reverse lookup
>> zone, in the right pane you will see type.
>>
>> From dcdiag, for the errors displayed there under "systemlog" check
>> the event viewer system log. There you should find errors, which are
>> maybe resolved. To make sure you can save and delete the systemlog
>> and wait 2 days, then run dcdiag again. Rest seems to be fine.
>>
>> From netdiag, the servers are not in the internet i hope, because you
>> didn't use private ip range. Why 25.31.11.2 from a different ip
>> range? Is it your ISP? For domain connectivity use only domain
>> internal DNS servers, so point the server to the DC/DNS that should
>> be removed.
>>
>> If not done i would also update to SP2 and latest patches.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> Hello Meinolf please find below the test results foe netdiag and
>>> dcdiag, i would be grateful if you could check them for me also how
>>> do i check if im running an Active Directory Intergrated Zone?
>>>
>>> Also these tests were taken when the server was online but for the
>>> last 3 weeks it seems to go offline every 2 hours and needs
>>> rebooting to restore connectivity with the network - i have
>>> installed new network card and dealt with all errors that were in
>>> event viewer - this server was due to be replaced in May but as i
>>> could not seem to resolve the issue we have decided to replace it
>>> now.
>>>
>>> DCDIAG Test Results:
>>>
>>> Microsoft Windows [Version 5.2.3790]
>>> (C) Copyright 1985-2003 Microsoft Corp.
>>> C:\Documents and Settings\Administrator>dcdiag
>>> Domain Controller Diagnosis
>>>
>>> Performing initial setup:
>>> Done gathering initial info.
>>> Doing initial required tests
>>> Testing server: Default-First-Site\DC1
>>> Starting test: Connectivity
>>> ......................... DC1 passed test Connectivity
>>> Doing primary tests
>>> Testing server: Default-First-Site\DC1
>>> Starting test: Replications
>>> ......................... DC1 passed test Replications
>>> Starting test: NCSecDesc
>>> ......................... DC1 passed test NCSecDesc
>>> Starting test: NetLogons
>>> ......................... DC1 passed test NetLogons
>>> Starting test: Advertising
>>> ......................... DC1 passed test Advertising
>>> Starting test: KnowsOfRoleHolders
>>> ......................... DC1 passed test KnowsOfRoleHolders
>>> Starting test: RidManager
>>> ......................... DC1 passed test RidManager
>>> Starting test: MachineAccount
>>> ......................... DC1 passed test MachineAccount
>>> Starting test: Services
>>> ......................... DC1 passed test Services
>>> Starting test: ObjectsReplicated
>>> ......................... DC1 passed test ObjectsReplicated
>>> Starting test: frssysvol
>>> ......................... DC1 passed test frssysvol
>>> Starting test: frsevent
>>> ......................... DC1 passed test frsevent
>>> Starting test: kccevent
>>> ......................... DC1 passed test kccevent
>>> Starting test: systemlog
>>> An Error Event occured. EventID: 0xC0001B78
>>> Time Generated: 01/20/2009 13:59:12
>>> (Event String could not be retrieved)
>>> An Error Event occured. EventID: 0xC0001B58
>>> Time Generated: 01/20/2009 14:13:38
>>> (Event String could not be retrieved)
>>> An Error Event occured. EventID: 0x00000416
>>> Time Generated: 01/20/2009 14:13:46
>>> Event String: The DHCP/BINL service on the local machine,
>>> An Error Event occured. EventID: 0xC0040007
>>> Time Generated: 01/20/2009 14:35:36
>>> Event String: The device, \Device\CdRom0, has a bad block.
>>> An Error Event occured. EventID: 0xC0040007
>>> Time Generated: 01/20/2009 14:35:45
>>> Event String: The device, \Device\CdRom0, has a bad block.
>>> An Error Event occured. EventID: 0xC0040007
>>> Time Generated: 01/20/2009 14:35:51
>>> Event String: The device, \Device\CdRom0, has a bad block.
>>> An Error Event occured. EventID: 0xC0040007
>>> Time Generated: 01/20/2009 14:36:01
>>> Event String: The device, \Device\CdRom0, has a bad block.
>>> An Error Event occured. EventID: 0xC0040007
>>> Time Generated: 01/20/2009 14:36:07
>>> Event String: The device, \Device\CdRom0, has a bad block.
>>> An Error Event occured. EventID: 0xC0040007
>>> Time Generated: 01/20/2009 14:37:38
>>> Event String: The device, \Device\CdRom0, has a bad block.
>>> An Error Event occured. EventID: 0xC0040007
>>> Time Generated: 01/20/2009 14:37:44
>>> Event String: The device, \Device\CdRom0, has a bad block.
>>> An Error Event occured. EventID: 0xC0040007
>>> Time Generated: 01/20/2009 14:37:50
>>> Event String: The device, \Device\CdRom0, has a bad block.
>>> An Error Event occured. EventID: 0xC0040007
>>> Time Generated: 01/20/2009 14:37:57
>>> Event String: The device, \Device\CdRom0, has a bad block.
>>> An Error Event occured. EventID: 0xC0040007
>>> Time Generated: 01/20/2009 14:38:04
>>> Event String: The device, \Device\CdRom0, has a bad block.
>>> An Error Event occured. EventID: 0xC0040007
>>> Time Generated: 01/20/2009 14:38:11
>>> Event String: The device, \Device\CdRom0, has a bad block.
>>> An Error Event occured. EventID: 0xC0040007
>>> Time Generated: 01/20/2009 14:38:21
>>> Event String: The device, \Device\CdRom0, has a bad block.
>>> An Error Event occured. EventID: 0xC0040007
>>> Time Generated: 01/20/2009 14:38:27
>>> Event String: The device, \Device\CdRom0, has a bad block.
>>> An Error Event occured. EventID: 0xC0040007
>>> Time Generated: 01/20/2009 14:38:34
>>> Event String: The device, \Device\CdRom0, has a bad block.
>>> An Error Event occured. EventID: 0xC0040007
>>> Time Generated: 01/20/2009 14:38:41
>>> Event String: The device, \Device\CdRom0, has a bad block.
>>> An Error Event occured. EventID: 0xC0040007
>>> Time Generated: 01/20/2009 14:38:48
>>> Event String: The device, \Device\CdRom0, has a bad block.
>>> An Error Event occured. EventID: 0xC0040007
>>> Time Generated: 01/20/2009 14:38:54
>>> Event String: The device, \Device\CdRom0, has a bad block.
>>> An Error Event occured. EventID: 0xC0040007
>>> Time Generated: 01/20/2009 14:39:06
>>> Event String: The device, \Device\CdRom0, has a bad block.
>>> An Error Event occured. EventID: 0xC0040007
>>> Time Generated: 01/20/2009 14:39:13
>>> Event String: The device, \Device\CdRom0, has a bad block.
>>> An Error Event occured. EventID: 0xC0040007
>>> Time Generated: 01/20/2009 14:39:22
>>> Event String: The device, \Device\CdRom0, has a bad block.
>>> An Error Event occured. EventID: 0xC0040007
>>> Time Generated: 01/20/2009 14:39:28
>>> Event String: The device, \Device\CdRom0, has a bad block.
>>> An Error Event occured. EventID: 0xC0040007
>>> Time Generated: 01/20/2009 14:39:35
>>> Event String: The device, \Device\CdRom0, has a bad block.
>>> ......................... DC1 failed test systemlog
>>> Starting test: VerifyReferences
>>> ......................... DC1 passed test VerifyReferences
>>> Running partition tests on : TAPI3Directory
>>> Starting test: CrossRefValidation
>>> ......................... TAPI3Directory passed test
>>> CrossRefValidation
>>> Starting test: CheckSDRefDom
>>> ......................... TAPI3Directory passed test
>>> CheckSDRefDom
>>> Running partition tests on : ForestDnsZones
>>> Starting test: CrossRefValidation
>>> ......................... ForestDnsZones passed test
>>> CrossRefValidation
>>> Starting test: CheckSDRefDom
>>> ......................... ForestDnsZones passed test
>>> CheckSDRefDom
>>> Running partition tests on : DomainDnsZones
>>> Starting test: CrossRefValidation
>>> ......................... DomainDnsZones passed test
>>> CrossRefValidation
>>> Starting test: CheckSDRefDom
>>> ......................... DomainDnsZones passed test
>>> CheckSDRefDom
>>> Running partition tests on : Schema
>>> Starting test: CrossRefValidation
>>> ......................... Schema passed test
>>> CrossRefValidation
>>> Starting test: CheckSDRefDom
>>> ......................... Schema passed test CheckSDRefDom
>>> Running partition tests on : Configuration
>>> Starting test: CrossRefValidation
>>> ......................... Configuration passed test
>>> CrossRefValidation
>>> Starting test: CheckSDRefDom
>>> ......................... Configuration passed test
>>> CheckSDRefDom
>>> Running partition tests on : ne-rfca
>>> Starting test: CrossRefValidation
>>> ......................... ne-rfca passed test
>>> CrossRefValidation
>>> Starting test: CheckSDRefDom
>>> ......................... ne-rfca passed test CheckSDRefDom
>>> Running enterprise tests on : ne-rfca.local
>>> Starting test: Intersite
>>> ......................... ne-rfca.local passed test Intersite
>>> Starting test: FsmoCheck
>>> ......................... ne-rfca.local passed test FsmoCheck
>>> C:\Documents and Settings\Administrator>
>>> NETDIAG Test Results:
>>>
>>> Microsoft Windows [Version 5.2.3790]
>>> (C) Copyright 1985-2003 Microsoft Corp.
>>> C:\Documents and Settings\Administrator>netdiag
>>> .....................................
>>>
>>> Computer Name: DC1
>>> DNS Host Name: DC1.ne-rfca.local
>>> System info : Microsoft Windows Server 2003 (Build 3790)
>>> Processor : x86 Family 15 Model 4 Stepping 1, GenuineIntel
>>> List of installed hotfixes :
>>> KB890046
>>> KB893756
>>> KB896358
>>> KB896422
>>> KB896424
>>> KB896428
>>> KB899587
>>> KB899588
>>> KB899589
>>> KB899591
>>> KB900725
>>> KB901017
>>> KB901214
>>> KB902400
>>> KB904706
>>> KB905414
>>> KB907265
>>> KB908519
>>> KB908521
>>> KB908531
>>> KB910437
>>> KB911280
>>> KB911562
>>> KB911564
>>> KB911567
>>> KB911927
>>> KB912919
>>> KB914388
>>> KB914389
>>> KB916281
>>> KB917159
>>> KB917344
>>> KB917422
>>> KB917537
>>> KB917734
>>> KB917953
>>> KB918439
>>> KB918899
>>> KB920214
>>> KB920670
>>> KB920683
>>> KB920685
>>> KB921398
>>> KB921883
>>> KB922582
>>> KB922616
>>> Q147222
>>> Netcard queries test . . . . . . . : Passed
>>> Per interface results:
>>>
>>> Adapter : Local Area Connection 5
>>>
>>> Netcard queries test . . . : Passed
>>>
>>> Host Name. . . . . . . . . : DC1
>>> IP Address . . . . . . . . : 25.14.168.11
>>> Subnet Mask. . . . . . . . : 255.255.255.192
>>> Default Gateway. . . . . . : 25.14.168.1
>>> Dns Servers. . . . . . . . : 25.14.168.11
>>> 25.31.11.2
>>> AutoConfiguration results. . . . . . : Passed
>>> Default gateway test . . . : Passed
>>>
>>> NetBT name test. . . . . . : Passed
>>> No remote names have been found.
>>> WINS service test. . . . . : Skipped
>>> There are no WINS servers configured for this interface.
>>> Global results:
>>> Domain membership test . . . . . . : Passed
>>>
>>> NetBT transports test. . . . . . . : Passed
>>> List of NetBt transports currently configured:
>>> NetBT_Tcpip_{1FE061C8-E0AE-40AD-977B-41D671C4707A}
>>> 1 NetBt transport currently configured.
>>> Autonet address test . . . . . . . : Passed
>>> IP loopback ping test. . . . . . . : Passed
>>>

Hello thanks for a brilliant guide, it helped me do the job really well but i
have a small issue after demoting the old DC, it is still on the network as a
member server but the client accounts are locking out all of the time, any
idea where the problem could be?

Thanks

Lee

"Meinolf Weber [MVP-DS]" wrote:

> Hello Lee,
>
> If your higher level orders to use that DNS server as secondary, use it.
> For the new DC/DNS i would only use the existing DC/DNS 25.14.168.11 as preferred
> until AD/DNS replication is done complete, after that change the ip to itself
> as preferred and use the other DNS server as secondary.
>
> Then for testing the new server from all clients, reconfigure them for the
> new DNS, disconnect the old one (unplug network cable one or two days) and
> check if everything is still running. Do not forget to make the DC also Global
> catalog.
>
> If all tests are ok reconnect the old server and you can start demoting it,
> change the ip's etc.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>
> > Thanks for that the IP you mention is as follows, the client is part
> > of the Ministry of Defence and are on RLI Military protected Broadband
> > and we were advised to point to that, do you think it is serving no
> > purpose doing that as we dont need internet connectivity on the
> > servers?
> >
> > "Meinolf Weber [MVP-DS]" wrote:
> >
> >> Hello Lee,
> >>
> >> Open DNS management console and highlight the Forward/Reverse lookup
> >> zone, in the right pane you will see type.
> >>
> >> From dcdiag, for the errors displayed there under "systemlog" check
> >> the event viewer system log. There you should find errors, which are
> >> maybe resolved. To make sure you can save and delete the systemlog
> >> and wait 2 days, then run dcdiag again. Rest seems to be fine.
> >>
> >> From netdiag, the servers are not in the internet i hope, because you
> >> didn't use private ip range. Why 25.31.11.2 from a different ip
> >> range? Is it your ISP? For domain connectivity use only domain
> >> internal DNS servers, so point the server to the DC/DNS that should
> >> be removed.
> >>
> >> If not done i would also update to SP2 and latest patches.
> >>
> >> Best regards
> >>
> >> Meinolf Weber
> >> Disclaimer: This posting is provided "AS IS" with no warranties, and
> >> confers
> >> no rights.
> >> ** Please do NOT email, only reply to Newsgroups
> >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
> >>> Hello Meinolf please find below the test results foe netdiag and
> >>> dcdiag, i would be grateful if you could check them for me also how
> >>> do i check if im running an Active Directory Intergrated Zone?
> >>>
> >>> Also these tests were taken when the server was online but for the
> >>> last 3 weeks it seems to go offline every 2 hours and needs
> >>> rebooting to restore connectivity with the network - i have
> >>> installed new network card and dealt with all errors that were in
> >>> event viewer - this server was due to be replaced in May but as i
> >>> could not seem to resolve the issue we have decided to replace it
> >>> now.
> >>>
> >>> DCDIAG Test Results:
> >>>
> >>> Microsoft Windows [Version 5.2.3790]
> >>> (C) Copyright 1985-2003 Microsoft Corp.
> >>> C:\Documents and Settings\Administrator>dcdiag
> >>> Domain Controller Diagnosis
> >>>
> >>> Performing initial setup:
> >>> Done gathering initial info.
> >>> Doing initial required tests
> >>> Testing server: Default-First-Site\DC1
> >>> Starting test: Connectivity
> >>> ......................... DC1 passed test Connectivity
> >>> Doing primary tests
> >>> Testing server: Default-First-Site\DC1
> >>> Starting test: Replications
> >>> ......................... DC1 passed test Replications
> >>> Starting test: NCSecDesc
> >>> ......................... DC1 passed test NCSecDesc
> >>> Starting test: NetLogons
> >>> ......................... DC1 passed test NetLogons
> >>> Starting test: Advertising
> >>> ......................... DC1 passed test Advertising
> >>> Starting test: KnowsOfRoleHolders
> >>> ......................... DC1 passed test KnowsOfRoleHolders
> >>> Starting test: RidManager
> >>> ......................... DC1 passed test RidManager
> >>> Starting test: MachineAccount
> >>> ......................... DC1 passed test MachineAccount
> >>> Starting test: Services
> >>> ......................... DC1 passed test Services
> >>> Starting test: ObjectsReplicated
> >>> ......................... DC1 passed test ObjectsReplicated
> >>> Starting test: frssysvol
> >>> ......................... DC1 passed test frssysvol
> >>> Starting test: frsevent
> >>> ......................... DC1 passed test frsevent
> >>> Starting test: kccevent
> >>> ......................... DC1 passed test kccevent
> >>> Starting test: systemlog
> >>> An Error Event occured. EventID: 0xC0001B78
> >>> Time Generated: 01/20/2009 13:59:12
> >>> (Event String could not be retrieved)
> >>> An Error Event occured. EventID: 0xC0001B58
> >>> Time Generated: 01/20/2009 14:13:38
> >>> (Event String could not be retrieved)
> >>> An Error Event occured. EventID: 0x00000416
> >>> Time Generated: 01/20/2009 14:13:46
> >>> Event String: The DHCP/BINL service on the local machine,
> >>> An Error Event occured. EventID: 0xC0040007
> >>> Time Generated: 01/20/2009 14:35:36
> >>> Event String: The device, \Device\CdRom0, has a bad block.
> >>> An Error Event occured. EventID: 0xC0040007
> >>> Time Generated: 01/20/2009 14:35:45
> >>> Event String: The device, \Device\CdRom0, has a bad block.
> >>> An Error Event occured. EventID: 0xC0040007
> >>> Time Generated: 01/20/2009 14:35:51
> >>> Event String: The device, \Device\CdRom0, has a bad block.
> >>> An Error Event occured. EventID: 0xC0040007
> >>> Time Generated: 01/20/2009 14:36:01
> >>> Event String: The device, \Device\CdRom0, has a bad block.
> >>> An Error Event occured. EventID: 0xC0040007
> >>> Time Generated: 01/20/2009 14:36:07
> >>> Event String: The device, \Device\CdRom0, has a bad block.
> >>> An Error Event occured. EventID: 0xC0040007
> >>> Time Generated: 01/20/2009 14:37:38
> >>> Event String: The device, \Device\CdRom0, has a bad block.
> >>> An Error Event occured. EventID: 0xC0040007
> >>> Time Generated: 01/20/2009 14:37:44
> >>> Event String: The device, \Device\CdRom0, has a bad block.
> >>> An Error Event occured. EventID: 0xC0040007
> >>> Time Generated: 01/20/2009 14:37:50
> >>> Event String: The device, \Device\CdRom0, has a bad block.
> >>> An Error Event occured. EventID: 0xC0040007
> >>> Time Generated: 01/20/2009 14:37:57
> >>> Event String: The device, \Device\CdRom0, has a bad block.
> >>> An Error Event occured. EventID: 0xC0040007
> >>> Time Generated: 01/20/2009 14:38:04
> >>> Event String: The device, \Device\CdRom0, has a bad block.
> >>> An Error Event occured. EventID: 0xC0040007
> >>> Time Generated: 01/20/2009 14:38:11
> >>> Event String: The device, \Device\CdRom0, has a bad block.
> >>> An Error Event occured. EventID: 0xC0040007
> >>> Time Generated: 01/20/2009 14:38:21
> >>> Event String: The device, \Device\CdRom0, has a bad block.
> >>> An Error Event occured. EventID: 0xC0040007
> >>> Time Generated: 01/20/2009 14:38:27
> >>> Event String: The device, \Device\CdRom0, has a bad block.
> >>> An Error Event occured. EventID: 0xC0040007
> >>> Time Generated: 01/20/2009 14:38:34
> >>> Event String: The device, \Device\CdRom0, has a bad block.
> >>> An Error Event occured. EventID: 0xC0040007
> >>> Time Generated: 01/20/2009 14:38:41
> >>> Event String: The device, \Device\CdRom0, has a bad block.
> >>> An Error Event occured. EventID: 0xC0040007
> >>> Time Generated: 01/20/2009 14:38:48
> >>> Event String: The device, \Device\CdRom0, has a bad block.
> >>> An Error Event occured. EventID: 0xC0040007
> >>> Time Generated: 01/20/2009 14:38:54
> >>> Event String: The device, \Device\CdRom0, has a bad block.
> >>> An Error Event occured. EventID: 0xC0040007
> >>> Time Generated: 01/20/2009 14:39:06
> >>> Event String: The device, \Device\CdRom0, has a bad block.
> >>> An Error Event occured. EventID: 0xC0040007
> >>> Time Generated: 01/20/2009 14:39:13
> >>> Event String: The device, \Device\CdRom0, has a bad block.
> >>> An Error Event occured. EventID: 0xC0040007
> >>> Time Generated: 01/20/2009 14:39:22
> >>> Event String: The device, \Device\CdRom0, has a bad block.
> >>> An Error Event occured. EventID: 0xC0040007
> >>> Time Generated: 01/20/2009 14:39:28
> >>> Event String: The device, \Device\CdRom0, has a bad block.
> >>> An Error Event occured. EventID: 0xC0040007
> >>> Time Generated: 01/20/2009 14:39:35
> >>> Event String: The device, \Device\CdRom0, has a bad block.
> >>> ......................... DC1 failed test systemlog
> >>> Starting test: VerifyReferences
> >>> ......................... DC1 passed test VerifyReferences
> >>> Running partition tests on : TAPI3Directory
> >>> Starting test: CrossRefValidation
> >>> ......................... TAPI3Directory passed test
> >>> CrossRefValidation
> >>> Starting test: CheckSDRefDom
> >>> ......................... TAPI3Directory passed test
> >>> CheckSDRefDom
> >>> Running partition tests on : ForestDnsZones
> >>> Starting test: CrossRefValidation
> >>> ......................... ForestDnsZones passed test
> >>> CrossRefValidation
> >>> Starting test: CheckSDRefDom
> >>> ......................... ForestDnsZones passed test
> >>> CheckSDRefDom
> >>> Running partition tests on : DomainDnsZones
> >>> Starting test: CrossRefValidation
> >>> ......................... DomainDnsZones passed test
> >>> CrossRefValidation
> >>> Starting test: CheckSDRefDom
> >>> ......................... DomainDnsZones passed test
> >>> CheckSDRefDom
> >>> Running partition tests on : Schema
> >>> Starting test: CrossRefValidation
> >>> ......................... Schema passed test
> >>> CrossRefValidation
> >>> Starting test: CheckSDRefDom
> >>> ......................... Schema passed test CheckSDRefDom
> >>> Running partition tests on : Configuration
> >>> Starting test: CrossRefValidation
> >>> ......................... Configuration passed test
> >>> CrossRefValidation
> >>> Starting test: CheckSDRefDom
> >>> ......................... Configuration passed test
> >>> CheckSDRefDom
> >>> Running partition tests on : ne-rfca
> >>> Starting test: CrossRefValidation
> >>> ......................... ne-rfca passed test
> >>> CrossRefValidation
> >>> Starting test: CheckSDRefDom
> >>> ......................... ne-rfca passed test CheckSDRefDom
> >>> Running enterprise tests on : ne-rfca.local
> >>> Starting test: Intersite
> >>> ......................... ne-rfca.local passed test Intersite
> >>> Starting test: FsmoCheck
> >>> ......................... ne-rfca.local passed test FsmoCheck
> >>> C:\Documents and Settings\Administrator>
> >>> NETDIAG Test Results:
> >>>
> >>> Microsoft Windows [Version 5.2.3790]
> >>> (C) Copyright 1985-2003 Microsoft Corp.
> >>> C:\Documents and Settings\Administrator>netdiag
> >>> .....................................
> >>>
> >>> Computer Name: DC1
> >>> DNS Host Name: DC1.ne-rfca.local
> >>> System info : Microsoft Windows Server 2003 (Build 3790)
> >>> Processor : x86 Family 15 Model 4 Stepping 1, GenuineIntel
> >>> List of installed hotfixes :
> >>> KB890046
> >>> KB893756
> >>> KB896358
> >>> KB896422
> >>> KB896424
> >>> KB896428
> >>> KB899587
> >>> KB899588
> >>> KB899589
> >>> KB899591
> >>> KB900725
> >>> KB901017
> >>> KB901214
> >>> KB902400
> >>> KB904706
> >>> KB905414
> >>> KB907265
> >>> KB908519
> >>> KB908521
> >>> KB908531
> >>> KB910437
> >>> KB911280
> >>> KB911562
> >>> KB911564
> >>> KB911567
> >>> KB911927
> >>> KB912919
> >>> KB914388
> >>> KB914389
> >>> KB916281
> >>> KB917159
> >>> KB917344
> >>> KB917422
> >>> KB917537
> >>> KB917734
> >>> KB917953
> >>> KB918439
> >>> KB918899
> >>> KB920214
> >>> KB920670
> >>> KB920683
> >>> KB920685
> >>> KB921398
> >>> KB921883
> >>> KB922582
> >>> KB922616
> >>> Q147222
> >>> Netcard queries test . . . . . . . : Passed
> >>> Per interface results:
> >>>
> >>> Adapter : Local Area Connection 5
> >>>
> >>> Netcard queries test . . . : Passed
> >>>

Hello Lee,

Check out Account lockout tools:
http://technet.microsoft.com/en-us/l.../cc738772.aspx

http://www.microsoft.com/downloads/d...displaylang=en

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Hello thanks for a brilliant guide, it helped me do the job really
> well but i have a small issue after demoting the old DC, it is still
> on the network as a member server but the client accounts are locking
> out all of the time, any idea where the problem could be?
>
> Thanks
>
> Lee
>
> "Meinolf Weber [MVP-DS]" wrote:
>
>> Hello Lee,
>>
>> If your higher level orders to use that DNS server as secondary, use
>> it. For the new DC/DNS i would only use the existing DC/DNS
>> 25.14.168.11 as preferred until AD/DNS replication is done complete,
>> after that change the ip to itself as preferred and use the other DNS
>> server as secondary.
>>
>> Then for testing the new server from all clients, reconfigure them
>> for the new DNS, disconnect the old one (unplug network cable one or
>> two days) and check if everything is still running. Do not forget to
>> make the DC also Global catalog.
>>
>> If all tests are ok reconnect the old server and you can start
>> demoting it, change the ip's etc.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> Thanks for that the IP you mention is as follows, the client is part
>>> of the Ministry of Defence and are on RLI Military protected
>>> Broadband and we were advised to point to that, do you think it is
>>> serving no purpose doing that as we dont need internet connectivity
>>> on the servers?
>>>
>>> "Meinolf Weber [MVP-DS]" wrote:
>>>
>>>> Hello Lee,
>>>>
>>>> Open DNS management console and highlight the Forward/Reverse
>>>> lookup zone, in the right pane you will see type.
>>>>
>>>> From dcdiag, for the errors displayed there under "systemlog" check
>>>> the event viewer system log. There you should find errors, which
>>>> are maybe resolved. To make sure you can save and delete the
>>>> systemlog and wait 2 days, then run dcdiag again. Rest seems to be
>>>> fine.
>>>>
>>>> From netdiag, the servers are not in the internet i hope, because
>>>> you didn't use private ip range. Why 25.31.11.2 from a different ip
>>>> range? Is it your ISP? For domain connectivity use only domain
>>>> internal DNS servers, so point the server to the DC/DNS that should
>>>> be removed.
>>>>
>>>> If not done i would also update to SP2 and latest patches.
>>>>
>>>> Best regards
>>>>
>>>> Meinolf Weber
>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
>>>> and
>>>> confers
>>>> no rights.
>>>> ** Please do NOT email, only reply to Newsgroups
>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>>>> Hello Meinolf please find below the test results foe netdiag and
>>>>> dcdiag, i would be grateful if you could check them for me also
>>>>> how do i check if im running an Active Directory Intergrated Zone?
>>>>>
>>>>> Also these tests were taken when the server was online but for the
>>>>> last 3 weeks it seems to go offline every 2 hours and needs
>>>>> rebooting to restore connectivity with the network - i have
>>>>> installed new network card and dealt with all errors that were in
>>>>> event viewer - this server was due to be replaced in May but as i
>>>>> could not seem to resolve the issue we have decided to replace it
>>>>> now.
>>>>>
>>>>> DCDIAG Test Results:
>>>>>
>>>>> Microsoft Windows [Version 5.2.3790]
>>>>> (C) Copyright 1985-2003 Microsoft Corp.
>>>>> C:\Documents and Settings\Administrator>dcdiag
>>>>> Domain Controller Diagnosis
>>>>> Performing initial setup:
>>>>> Done gathering initial info.
>>>>> Doing initial required tests
>>>>> Testing server: Default-First-Site\DC1
>>>>> Starting test: Connectivity
>>>>> ......................... DC1 passed test Connectivity
>>>>> Doing primary tests
>>>>> Testing server: Default-First-Site\DC1
>>>>> Starting test: Replications
>>>>> ......................... DC1 passed test Replications
>>>>> Starting test: NCSecDesc
>>>>> ......................... DC1 passed test NCSecDesc
>>>>> Starting test: NetLogons
>>>>> ......................... DC1 passed test NetLogons
>>>>> Starting test: Advertising
>>>>> ......................... DC1 passed test Advertising
>>>>> Starting test: KnowsOfRoleHolders
>>>>> ......................... DC1 passed test KnowsOfRoleHolders
>>>>> Starting test: RidManager
>>>>> ......................... DC1 passed test RidManager
>>>>> Starting test: MachineAccount
>>>>> ......................... DC1 passed test MachineAccount
>>>>> Starting test: Services
>>>>> ......................... DC1 passed test Services
>>>>> Starting test: ObjectsReplicated
>>>>> ......................... DC1 passed test ObjectsReplicated
>>>>> Starting test: frssysvol
>>>>> ......................... DC1 passed test frssysvol
>>>>> Starting test: frsevent
>>>>> ......................... DC1 passed test frsevent
>>>>> Starting test: kccevent
>>>>> ......................... DC1 passed test kccevent
>>>>> Starting test: systemlog
>>>>> An Error Event occured. EventID: 0xC0001B78
>>>>> Time Generated: 01/20/2009 13:59:12
>>>>> (Event String could not be retrieved)
>>>>> An Error Event occured. EventID: 0xC0001B58
>>>>> Time Generated: 01/20/2009 14:13:38
>>>>> (Event String could not be retrieved)
>>>>> An Error Event occured. EventID: 0x00000416
>>>>> Time Generated: 01/20/2009 14:13:46
>>>>> Event String: The DHCP/BINL service on the local machine,
>>>>> An Error Event occured. EventID: 0xC0040007
>>>>> Time Generated: 01/20/2009 14:35:36
>>>>> Event String: The device, \Device\CdRom0, has a bad block.
>>>>> An Error Event occured. EventID: 0xC0040007
>>>>> Time Generated: 01/20/2009 14:35:45
>>>>> Event String: The device, \Device\CdRom0, has a bad block.
>>>>> An Error Event occured. EventID: 0xC0040007
>>>>> Time Generated: 01/20/2009 14:35:51
>>>>> Event String: The device, \Device\CdRom0, has a bad block.
>>>>> An Error Event occured. EventID: 0xC0040007
>>>>> Time Generated: 01/20/2009 14:36:01
>>>>> Event String: The device, \Device\CdRom0, has a bad block.
>>>>> An Error Event occured. EventID: 0xC0040007
>>>>> Time Generated: 01/20/2009 14:36:07
>>>>> Event String: The device, \Device\CdRom0, has a bad block.
>>>>> An Error Event occured. EventID: 0xC0040007
>>>>> Time Generated: 01/20/2009 14:37:38
>>>>> Event String: The device, \Device\CdRom0, has a bad block.
>>>>> An Error Event occured. EventID: 0xC0040007
>>>>> Time Generated: 01/20/2009 14:37:44
>>>>> Event String: The device, \Device\CdRom0, has a bad block.
>>>>> An Error Event occured. EventID: 0xC0040007
>>>>> Time Generated: 01/20/2009 14:37:50
>>>>> Event String: The device, \Device\CdRom0, has a bad block.
>>>>> An Error Event occured. EventID: 0xC0040007
>>>>> Time Generated: 01/20/2009 14:37:57
>>>>> Event String: The device, \Device\CdRom0, has a bad block.
>>>>> An Error Event occured. EventID: 0xC0040007
>>>>> Time Generated: 01/20/2009 14:38:04
>>>>> Event String: The device, \Device\CdRom0, has a bad block.
>>>>> An Error Event occured. EventID: 0xC0040007
>>>>> Time Generated: 01/20/2009 14:38:11
>>>>> Event String: The device, \Device\CdRom0, has a bad block.
>>>>> An Error Event occured. EventID: 0xC0040007
>>>>> Time Generated: 01/20/2009 14:38:21
>>>>> Event String: The device, \Device\CdRom0, has a bad block.
>>>>> An Error Event occured. EventID: 0xC0040007
>>>>> Time Generated: 01/20/2009 14:38:27
>>>>> Event String: The device, \Device\CdRom0, has a bad block.
>>>>> An Error Event occured. EventID: 0xC0040007
>>>>> Time Generated: 01/20/2009 14:38:34
>>>>> Event String: The device, \Device\CdRom0, has a bad block.
>>>>> An Error Event occured. EventID: 0xC0040007
>>>>> Time Generated: 01/20/2009 14:38:41
>>>>> Event String: The device, \Device\CdRom0, has a bad block.
>>>>> An Error Event occured. EventID: 0xC0040007
>>>>> Time Generated: 01/20/2009 14:38:48
>>>>> Event String: The device, \Device\CdRom0, has a bad block.
>>>>> An Error Event occured. EventID: 0xC0040007
>>>>> Time Generated: 01/20/2009 14:38:54
>>>>> Event String: The device, \Device\CdRom0, has a bad block.
>>>>> An Error Event occured. EventID: 0xC0040007
>>>>> Time Generated: 01/20/2009 14:39:06
>>>>> Event String: The device, \Device\CdRom0, has a bad block.
>>>>> An Error Event occured. EventID: 0xC0040007
>>>>> Time Generated: 01/20/2009 14:39:13
>>>>> Event String: The device, \Device\CdRom0, has a bad block.
>>>>> An Error Event occured. EventID: 0xC0040007
>>>>> Time Generated: 01/20/2009 14:39:22
>>>>> Event String: The device, \Device\CdRom0, has a bad block.
>>>>> An Error Event occured. EventID: 0xC0040007
>>>>> Time Generated: 01/20/2009 14:39:28
>>>>> Event String: The device, \Device\CdRom0, has a bad block.
>>>>> An Error Event occured. EventID: 0xC0040007
>>>>> Time Generated: 01/20/2009 14:39:35
>>>>> Event String: The device, \Device\CdRom0, has a bad block.
>>>>> ......................... DC1 failed test systemlog
>>>>> Starting test: VerifyReferences
>>>>> ......................... DC1 passed test VerifyReferences
>>>>> Running partition tests on : TAPI3Directory
>>>>> Starting test: CrossRefValidation
>>>>> ......................... TAPI3Directory passed test
>>>>> CrossRefValidation
>>>>> Starting test: CheckSDRefDom
>>>>> ......................... TAPI3Directory passed test
>>>>> CheckSDRefDom
>>>>> Running partition tests on : ForestDnsZones
>>>>> Starting test: CrossRefValidation
>>>>> ......................... ForestDnsZones passed test
>>>>> CrossRefValidation
>>>>> Starting test: CheckSDRefDom
>>>>> ......................... ForestDnsZones passed test
>>>>> CheckSDRefDom
>>>>> Running partition tests on : DomainDnsZones
>>>>> Starting test: CrossRefValidation
>>>>> ......................... DomainDnsZones passed test
>>>>> CrossRefValidation
>>>>> Starting test: CheckSDRefDom
>>>>> ......................... DomainDnsZones passed test
>>>>> CheckSDRefDom
>>>>> Running partition tests on : Schema
>>>>> Starting test: CrossRefValidation
>>>>> ......................... Schema passed test
>>>>> CrossRefValidation
>>>>> Starting test: CheckSDRefDom
>>>>> ......................... Schema passed test CheckSDRefDom
>>>>> Running partition tests on : Configuration
>>>>> Starting test: CrossRefValidation
>>>>> ......................... Configuration passed test
>>>>> CrossRefValidation
>>>>> Starting test: CheckSDRefDom
>>>>> ......................... Configuration passed test
>>>>> CheckSDRefDom
>>>>> Running partition tests on : ne-rfca
>>>>> Starting test: CrossRefValidation
>>>>> ......................... ne-rfca passed test
>>>>> CrossRefValidation
>>>>> Starting test: CheckSDRefDom
>>>>> ......................... ne-rfca passed test CheckSDRefDom
>>>>> Running enterprise tests on : ne-rfca.local
>>>>> Starting test: Intersite
>>>>> ......................... ne-rfca.local passed test Intersite
>>>>> Starting test: FsmoCheck
>>>>> ......................... ne-rfca.local passed test FsmoCheck
>>>>> C:\Documents and Settings\Administrator>
>>>>> NETDIAG Test Results:
>>>>> Microsoft Windows [Version 5.2.3790]
>>>>> (C) Copyright 1985-2003 Microsoft Corp.
>>>>> C:\Documents and Settings\Administrator>netdiag
>>>>> .....................................
>>>>> Computer Name: DC1
>>>>> DNS Host Name: DC1.ne-rfca.local
>>>>> System info : Microsoft Windows Server 2003 (Build 3790)
>>>>> Processor : x86 Family 15 Model 4 Stepping 1, GenuineIntel
>>>>> List of installed hotfixes :
>>>>> KB890046
>>>>> KB893756
>>>>> KB896358
>>>>> KB896422
>>>>> KB896424
>>>>> KB896428
>>>>> KB899587
>>>>> KB899588
>>>>> KB899589
>>>>> KB899591
>>>>> KB900725
>>>>> KB901017
>>>>> KB901214
>>>>> KB902400
>>>>> KB904706
>>>>> KB905414
>>>>> KB907265
>>>>> KB908519
>>>>> KB908521
>>>>> KB908531
>>>>> KB910437
>>>>> KB911280
>>>>> KB911562
>>>>> KB911564
>>>>> KB911567
>>>>> KB911927
>>>>> KB912919
>>>>> KB914388
>>>>> KB914389
>>>>> KB916281
>>>>> KB917159
>>>>> KB917344
>>>>> KB917422
>>>>> KB917537
>>>>> KB917734
>>>>> KB917953
>>>>> KB918439
>>>>> KB918899
>>>>> KB920214
>>>>> KB920670
>>>>> KB920683
>>>>> KB920685
>>>>> KB921398
>>>>> KB921883
>>>>> KB922582
>>>>> KB922616
>>>>> Q147222
>>>>> Netcard queries test . . . . . . . : Passed
>>>>> Per interface results:
>>>>> Adapter : Local Area Connection 5
>>>>>
>>>>> Netcard queries test . . . : Passed
>>>>>