| Author |
Message |
Peter B
Guest
|
 Posted:
Wed Jan 05, 2005 7:41 pm Post subject:
Post- Migration woes part I |
|
|
Hi All,
happy new year to you all.
completed my in-place upgrade of our nt4 server over our xmas holidays, and
everything went without major issues. when the staff started getting back on
the 3rd, some strange things were happening on some of the workstations.
1. people were complaining that when they started outlook, it was a total
pig. i checked the settings on the workstations dns/wins seemed ok, but then
compared the system properties to a workstation thad had no problems.
i found on the systems with the slow response, on the Network Identification
tab, click Properties, and then click More, Primary DNS suffix of this
computer was filled with the DNS suffix "mycomp.mycity.local", the other
workstations didn't have this. i removed the suffix and rebooted, started
outlook, and it was back to normal !!. do i need this dns suffix ???
2. most of the xp/w2k workstations authenticated against my w3k DC's when i
did some testing, but there's one that i've seen that is still
authenticating to one of the NT4 BDC's, did i miss disabling something on
this workstation or is this normal ?
3. how can i tell/test if the DNS/AD is functioning correctly on the
workstation side/perspective. this dns suffix has me concerned something is
not working correctly if the field is set.
4. i have shut off the backup "BDC" in case i need to roll back to an NT4
domain again and also a temporary w2k server that was used for storage, what
is the proper way to remove these machines from the Domain. (delete in AD,
then remove wins records ???)
Notes:
- exchange 5.5 running on nt4 BDC still
- proxy server 2.0 running on nt4 BDC.
any insight or comments greatly appreciated.
Thank you all.
Peter |
|
| Back to top |
|
 |
Rebecca Chen [MSFT]
Guest
|
| Posted:
Thu Jan 06, 2005 2:11 pm Post subject:
RE: Post- Migration woes part I |
|
|
Hi Peter,
See inline answers:
1. people were complaining that when they started outlook, it was a total
pig. i checked the settings on the workstations dns/wins seemed ok, but then
compared the system properties to a workstation thad had no problems.
i found on the systems with the slow response, on the Network Identification
tab, click Properties, and then click More, Primary DNS suffix of this
computer was filled with the DNS suffix "mycomp.mycity.local", the other
workstations didn't have this. i removed the suffix and rebooted, started
outlook, and it was back to normal !!. do i need this dns suffix ???
A: Do you mean Outlook cannot contact Exchange? Normally, DNS suffix is not
necessary. I believe "mycomp.mycity.local" is not the correct DNS suffix,
therefore the DNS server cannot resolve the Exchange FQDN. You can just
leave it blank.
2. most of the xp/w2k workstations authenticated against my w3k DC's when I
did some testing, but there's one that i've seen that is still
authenticating to one of the NT4 BDC's, did i miss disabling something on
this workstation or is this normal ?
A: It is normal. When XP and 2k detects that is win2k3 DC, them will
authenticate with win2k3. However, this will cause a known issue which is
described in the following article:
How to Prevent Overloading on the First Domain Controller During Domain
http://support.microsoft.com/?id=298713
3. how can i tell/test if the DNS/AD is functioning correctly on the
workstation side/perspective. this dns suffix has me concerned something is
not working correctly if the field is set.
A: you can use NSLookup on the client to see if DNS server can resolve the
client FQDN name. fox example, your client name is C1, you can then issue
the command "nslookup C1", can C1 be successfully resolved to FQDN name
such as "C1. mycomp.mycity.local "? For more details about NSLookup,
please issue the command "nslookup /?" in CMD.
On server side, you can see is there any error logged in DNS event log? If
there is no error, we can say the DNS is running OK. You can also check if
the correct SRV recorders are created on the DC:
241515 How to Verify the Creation of SRV Records for a Domain Controller
http://support.microsoft.com/?id=241515
816587 How to verify that SRV DNS records have been created for a domain
http://support.microsoft.com/?id=816587
More information£º
Troubleshoot DNS using command tools
http://www.microsoft.com/windows2000/en/advanced/help/default.asp?url=/windo
ws2000/en/advanced/help/sag_DNS_pro_TroubleshootNode.htm
Troubleshooting DNS clients
http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/p
roddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/stan
dard/proddocs/en-us/sag_dns_tro_clientsnode.asp
4. i have shut off the backup "BDC" in case i need to roll back to an NT4
domain again and also a temporary w2k server that was used for storage, what
is the proper way to remove these machines from the Domain. (delete in AD,
then remove wins records ???)
A: Since you have upgraded NT to win2k3, you can then safely take other BDC
offline if those BDC do not hold other roles in the network. However, if
BDC hosts WINS in the network and you want to win2k3 take control of WINS,
you can backup and restore WINS database to win2k3 before you talk BDC
offline. Please refer to the following article:
193820 How to Move a WINS Database to Another Server
http://support.microsoft.com/?id=193820
Notes:
- exchange 5.5 running on nt4 BDC still
- proxy server 2.0 running on nt4 BDC.
A: If you want to keep the original Exchange information, you need to
migrate Exchange mailbox. For more information about how to migrate
Exchange, please post all Exchange related questions to
microsoft.public.exchange.setup newsgroup.
About proxy 2.0, I suggest you upgrade to ISA since ISA has greatly
enhanced the firewall and proxy function, on other hand Proxy is out of its
product lifecycle and can be retired. :)
Any update, let us get in touch!
Best regards,
Rebecca Chen
MCSE2000 MCDBA CCNA
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights. |
|
| Back to top |
|
|
Peter B
Guest
|
| Posted:
Thu Jan 06, 2005 7:49 pm Post subject:
Re: Post- Migration woes part I |
|
|
Hi Rebecca
thanks for the info, here's more info on one of your questions:
A: Do you mean Outlook cannot contact Exchange? Normally, DNS suffix is not
necessary. I believe "mycomp.mycity.local" is not the correct DNS suffix,
therefore the DNS server cannot resolve the Exchange FQDN. You can just
leave it blank.
=> yes/no. it will connect after a minute or so (maybe timeout then hit
retry and it would connect) and will function very slow. what i noticed was
all my w2k systems had the dns suffix filled in for some reason, one i
removed it, the machines started working normally. this machine is not on
the net so we named it "mycomp.mycity.local" which = companyname.city.local
(i read somewhere for ms to use ".local' if the machine is not on the net or
something like that)
yes, proxy 2.0 is the next server to go away. i will also run those tests
today and get back to you
thanks for all your help, informative
Thanks
Peter
"Rebecca Chen [MSFT]" <v-rebc@online.microsoft.com> wrote in message
news:HBAy$c88EHA.3152@cpmsftngxa10.phx.gbl...
| Quote: | Hi Peter,
See inline answers:
1. people were complaining that when they started outlook, it was a total
pig. i checked the settings on the workstations dns/wins seemed ok, but
then
compared the system properties to a workstation thad had no problems.
i found on the systems with the slow response, on the Network
Identification
tab, click Properties, and then click More, Primary DNS suffix of this
computer was filled with the DNS suffix "mycomp.mycity.local", the other
workstations didn't have this. i removed the suffix and rebooted, started
outlook, and it was back to normal !!. do i need this dns suffix ???
A: Do you mean Outlook cannot contact Exchange? Normally, DNS suffix is
not
necessary. I believe "mycomp.mycity.local" is not the correct DNS suffix,
therefore the DNS server cannot resolve the Exchange FQDN. You can just
leave it blank.
2. most of the xp/w2k workstations authenticated against my w3k DC's when
I
did some testing, but there's one that i've seen that is still
authenticating to one of the NT4 BDC's, did i miss disabling something on
this workstation or is this normal ?
A: It is normal. When XP and 2k detects that is win2k3 DC, them will
authenticate with win2k3. However, this will cause a known issue which is
described in the following article:
How to Prevent Overloading on the First Domain Controller During Domain
http://support.microsoft.com/?id=298713
3. how can i tell/test if the DNS/AD is functioning correctly on the
workstation side/perspective. this dns suffix has me concerned something
is
not working correctly if the field is set.
A: you can use NSLookup on the client to see if DNS server can resolve the
client FQDN name. fox example, your client name is C1, you can then issue
the command "nslookup C1", can C1 be successfully resolved to FQDN name
such as "C1. mycomp.mycity.local "? For more details about NSLookup,
please issue the command "nslookup /?" in CMD.
On server side, you can see is there any error logged in DNS event log? If
there is no error, we can say the DNS is running OK. You can also check if
the correct SRV recorders are created on the DC:
241515 How to Verify the Creation of SRV Records for a Domain Controller
http://support.microsoft.com/?id=241515
816587 How to verify that SRV DNS records have been created for a domain
http://support.microsoft.com/?id=816587
More information£º
Troubleshoot DNS using command tools
http://www.microsoft.com/windows2000/en/advanced/help/default.asp?url=/windo
ws2000/en/advanced/help/sag_DNS_pro_TroubleshootNode.htm
Troubleshooting DNS clients
http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/p
roddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/stan
dard/proddocs/en-us/sag_dns_tro_clientsnode.asp
4. i have shut off the backup "BDC" in case i need to roll back to an NT4
domain again and also a temporary w2k server that was used for storage,
what
is the proper way to remove these machines from the Domain. (delete in AD,
then remove wins records ???)
A: Since you have upgraded NT to win2k3, you can then safely take other
BDC
offline if those BDC do not hold other roles in the network. However, if
BDC hosts WINS in the network and you want to win2k3 take control of WINS,
you can backup and restore WINS database to win2k3 before you talk BDC
offline. Please refer to the following article:
193820 How to Move a WINS Database to Another Server
http://support.microsoft.com/?id=193820
Notes:
- exchange 5.5 running on nt4 BDC still
- proxy server 2.0 running on nt4 BDC.
A: If you want to keep the original Exchange information, you need to
migrate Exchange mailbox. For more information about how to migrate
Exchange, please post all Exchange related questions to
microsoft.public.exchange.setup newsgroup.
About proxy 2.0, I suggest you upgrade to ISA since ISA has greatly
enhanced the firewall and proxy function, on other hand Proxy is out of
its
product lifecycle and can be retired. :)
Any update, let us get in touch!
Best regards,
Rebecca Chen
MCSE2000 MCDBA CCNA
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.
|
|
|
| Back to top |
|
|
Rebecca Chen [MSFT]
Guest
|
| Posted:
Mon Jan 10, 2005 6:19 pm Post subject:
Re: Post- Migration woes part I |
|
|
Hi Peter,
I have not found the root cause of outlook issue since I am not a outlook
guy. Please post this question to microsoft.public.exchange.clients since
the Exchange guy will provide more accurate suggestions on this question.
With regards to the proxy 2.0, please know it is end of its lifecycle. I
suggest you upgrade it to ISA 2000 or above or get more advantages.
Any udpate, let us get in touch!
Best regards,
Rebecca Chen
MCSE2000 MCDBA CCNA
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights. |
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in