asked on Currently setting up test environment for exchange 5.5 upgrade and windows 2000 upgrade
Okay everyone here is what i have done so far with my test environment for exchange 5.5 to 2007 upgrade and windows 2000 dc to windows 2003 dc. I used acronis enterprise software and took full backups of each machine currently running the environment and then used acronis universal restore and restored the backups on to test machines in my cube area that are not on the domain. Both machines are the the exact identical to the live machines currently running. So I am confused on what to do next since I cannot add it to the domain because it gets a windows duplicate name and of course is setup for the ip as the live environment. I am wondering the best way now to make the exchange 5.5 server communicate with the windows 2000 dc for the test environment which is in my cube. Then once i get them both communicating would it be okay to go ahead and upgrade the 2000 dc to 2003 dc and then start migrating the exchange 5.5 to exchange 2003. So heres a list of the machines setup in my cube for now for testing purposes.
1 Duplicate Windows 2000 DC with Active Directory
1 Duplicate Windows 2000 exchange 5.5
1 Windows 2003 64 bit for exchange 2007
1 Windows 2003 standard for exchange 2003
2 Windows XP test machines
thanks
Josh
1 Duplicate Windows 2000 DC with Active Directory
1 Duplicate Windows 2000 exchange 5.5
1 Windows 2003 64 bit for exchange 2007
1 Windows 2003 standard for exchange 2003
2 Windows XP test machines
thanks
Josh
ExchangeActive DirectoryAcronis
Last Comment
Erik Bjers
ASKER
Yeah i know that i would have to isolate from the network but here we dont use any vlans and every switch i plug it into would give it full access to the network. I guess would be a way to go into the switch and modify the settings of the port of my cube area but then i wont have full access to the network. I have a switch in my cube now but its cheap so i cant even modify any settings on it so thats why im not sure what to do.
switch i plug it into would give it full access to the network <- don't plug it in to the network... the test environment should be a 100% isolated network.
eb
eb
ASKER
now if i add a router from the port in my cube to the switch and then plug all the test machines in the switch i am wondering if that will work.
That will work
eb
eb
ASKER
Well would i need to change anything in the router settings though or just leave it all default. I went home yesterday for lunch and plugged the router in. From the wall to the router i plugged it into the wan port which is correct and then i plugged my computer into the router and i can still ping everything. Now i just believe i need to run a straight through cable from the router to switch and then plug all the test machines into the switch and then i hope it will work. I am sick this week and coughing badly so i cant even think straight so thats why im just moving slow otherwise i would of tested all this yesterday. What do you think.
I think it should work, let me know once you try
Hope you feel better
eb
Hope you feel better
eb
ASKER
ebjers,
So i ended up plugging in the router yesterday and then running a cable from the router to switch and then plugging all the test machines in the switch. The weird thing is when i booted up the domain controller i did not get a error for a duplicate name or anything but i hurried and disconnected the cable and booted up just the windows 2003 with nothing else on it yet. Then i just started pinging servers and could ping everyone so i am not sure what is going on. I am wondering if i need to modify the settings in the router. I ended up leaving work early yesterday due to not feeling well so that is as far as i got. What do you think?
So i ended up plugging in the router yesterday and then running a cable from the router to switch and then plugging all the test machines in the switch. The weird thing is when i booted up the domain controller i did not get a error for a duplicate name or anything but i hurried and disconnected the cable and booted up just the windows 2003 with nothing else on it yet. Then i just started pinging servers and could ping everyone so i am not sure what is going on. I am wondering if i need to modify the settings in the router. I ended up leaving work early yesterday due to not feeling well so that is as far as i got. What do you think?
"The weird thing is when i booted up the domain controller i did not get a error for a duplicate name or anything" this is because you are behind a router and therefore a different network. If your test network is the same subnet as your main network on the other side of the router then you will get no traffic routed between the networks (so no name conflict).
eb
eb
ASKER
But since there is no conflict i want to make sure this wont be a problem then with all the users logging into the domain and the exchange server. I want to make sure there not logging in to the test machines setup. Should i be changing the ip address and stuff though on the test environment because its still the same ip, dns, subnet, etc as the Real test environment.
Yes, to be safe you should change the IP addressing. However, since you have the two networks joined by a router traffic will not flow between because all traffic will be recognized as local traffic and not get routed.
ASKER
Ebjers,
Sorry for the late response but i have been swamped at work. Here are the ip addresses.
Here are the ip address for the current servers setup in the environment.
Real Domain:
IP 192.168.27.108
SUB 255.255.255.0
GATE 192.168.27.112
DNS 192.168.27.27
192.168.27.108
WINS 192.168.27.27
SECONDARY WINS 192.168.27.108
TEST Domain:
ip 192.168.15.105
sub 255.255.255.0
gate 192.168.15.1
dhcp 192.168.15.1
dns 192.168.27.27
192.168.27.108
So let me knwo what you think of this?
Sorry for the late response but i have been swamped at work. Here are the ip addresses.
Here are the ip address for the current servers setup in the environment.
Real Domain:
IP 192.168.27.108
SUB 255.255.255.0
GATE 192.168.27.112
DNS 192.168.27.27
192.168.27.108
WINS 192.168.27.27
SECONDARY WINS 192.168.27.108
TEST Domain:
ip 192.168.15.105
sub 255.255.255.0
gate 192.168.15.1
dhcp 192.168.15.1
dns 192.168.27.27
192.168.27.108
So let me knwo what you think of this?
You should have no problems as they are on separate networks and since your real network clients are going to use your main router as a gateway they should never be routed to your test LAN. I don't see any problems with this setup.
eb
eb
ASKER
Ebjers,
So now i should beable to hookup a test machine and install office on it and try to test any of the email accounts to make sure its working then i can go ahead and start the migrating process once i know its working. I just need to make sure exchange and domain controller are communicating since the ip on the test environment are different so the domain might not be communicating with exchange now. You have any thought for me on this.
thanks,
So now i should beable to hookup a test machine and install office on it and try to test any of the email accounts to make sure its working then i can go ahead and start the migrating process once i know its working. I just need to make sure exchange and domain controller are communicating since the ip on the test environment are different so the domain might not be communicating with exchange now. You have any thought for me on this.
thanks,
No not with out being there...
You should relay have a completely separate test environment. Set up a new DC to mimic your main domain, setup an exchange server to mimic your existing exchange server. Setup a workstation, then create some accounts and generate some mail. Then try the migration. You relay should not have this test environment connected/ dependent on your production environment at all. If you don't have the resources to setup multiple servers you can look at VMWare server (free) to virtualize your test lab.
eb
You should relay have a completely separate test environment. Set up a new DC to mimic your main domain, setup an exchange server to mimic your existing exchange server. Setup a workstation, then create some accounts and generate some mail. Then try the migration. You relay should not have this test environment connected/ dependent on your production environment at all. If you don't have the resources to setup multiple servers you can look at VMWare server (free) to virtualize your test lab.
eb
ASKER
No ebjers,
You are getting confused. Remember my test environment is seperate. I have all the machines connected in my cube to the switch that is connected to the router. I am just asking now that i need to make sure in the test environment that the 2000 DC with active directory is communicating with the 2000 exchange 5.5 server. I should just beable to reset any of those accounts setup in the DC and then login to the test environment with there username/password and shouldnt even have to create any new accounts. I dont need to use vmware.
Josh
You are getting confused. Remember my test environment is seperate. I have all the machines connected in my cube to the switch that is connected to the router. I am just asking now that i need to make sure in the test environment that the 2000 DC with active directory is communicating with the 2000 exchange 5.5 server. I should just beable to reset any of those accounts setup in the DC and then login to the test environment with there username/password and shouldnt even have to create any new accounts. I dont need to use vmware.
Josh
Yes, as long as both the DC and the Exchange server are in your test lab then you should be OK.
eb
eb
ASKER
eb,
Yes i have stated this above and have all these machines in my test environment.
1 Duplicate Windows 2000 DC with Active Directory
1 Duplicate Windows 2000 exchange 5.5
1 Windows 2003 64 bit for exchange 2007
1 Windows 2003 standard for exchange 2003
2 Windows XP test machines
Yes i have stated this above and have all these machines in my test environment.
1 Duplicate Windows 2000 DC with Active Directory
1 Duplicate Windows 2000 exchange 5.5
1 Windows 2003 64 bit for exchange 2007
1 Windows 2003 standard for exchange 2003
2 Windows XP test machines
Then as far as I can tell your test environment is good to go and you should have no problems.
eb
eb
ASKER
Ebjers,
Sorry i got swamped at work with setting up new pcs and a meeting but i will work on this toimmorow when i get time if i do and i will let you know if its working correctly. I just wish i had more time to work on this project but being a fulltime network admin and managing the 65 servers, domain, exchange, new pc setups, phone systems, backups, etc is just all my time really. I will let you know though.
Josh
Sorry i got swamped at work with setting up new pcs and a meeting but i will work on this toimmorow when i get time if i do and i will let you know if its working correctly. I just wish i had more time to work on this project but being a fulltime network admin and managing the 65 servers, domain, exchange, new pc setups, phone systems, backups, etc is just all my time really. I will let you know though.
Josh
ASKER
sorry ebjers, i didnt have no time at all to check on this today because i had alot of other stuff to do so tommorow hopefully i can get to it and then i will let you know if its working or not.
no problems, take your time...
ASKER
Ebjers,
Seems there is a issue with the test domain because when i add a new user and then i go check on the real domain the name appears there also so i unplugged all the network cables on the test environment for now. When i go in site and services on the domain, how do i remove all the real servers that show there because when i try and right click and choose delete it says the DSA object cannot be deleted. I believe i need to remove all those and then add the test DC which is the same name as the real domain so that might be where the problem is. What do you think?
Josh
Seems there is a issue with the test domain because when i add a new user and then i go check on the real domain the name appears there also so i unplugged all the network cables on the test environment for now. When i go in site and services on the domain, how do i remove all the real servers that show there because when i try and right click and choose delete it says the DSA object cannot be deleted. I believe i need to remove all those and then add the test DC which is the same name as the real domain so that might be where the problem is. What do you think?
Josh
I think you need to completely isolate the two networks. Remove the router and let your test network stand alone.
Other than than I can't give any other advice with out actually seeing the network.
eb
Other than than I can't give any other advice with out actually seeing the network.
eb
ASKER
Ebjers,
Could we maybe use teamviewer remote control which is free to use and you could connect in to the test machines and then you might beable to help me out more. Maybe do this tommorow or something.
Josh
Could we maybe use teamviewer remote control which is free to use and you could connect in to the test machines and then you might beable to help me out more. Maybe do this tommorow or something.
Josh
Unfortunately the network's I have access to during the day will not allow the traffic.
I think your setup is good except you need to completely isolate the 2 networks. You can either do this by removing the router or by placing a firewall between them that prevents traffic from one to the other.
eb
I think your setup is good except you need to completely isolate the 2 networks. You can either do this by removing the router or by placing a firewall between them that prevents traffic from one to the other.
eb
ASKER
Ebjers,
If i remove the router and just plug them into the switch in my cube then when i boot them up though, I will get an error saying theres a duplicate name on the network. I thought i needed the router to the switch and then all the test machines plugged into the switch. I guess i am confused now.
Josh
If i remove the router and just plug them into the switch in my cube then when i boot them up though, I will get an error saying theres a duplicate name on the network. I thought i needed the router to the switch and then all the test machines plugged into the switch. I guess i am confused now.
Josh
Is the switch connected to your main network?
You need to have no connection between the main network and your test network.
eb
You need to have no connection between the main network and your test network.
eb
ASKER
The switch is connected to the main network. So if i unplug it from the main network and then just have all the test machines plugged into it then i wont get any errors at all but i wont beable to get online either. Is that what i need to do then to start this upgrade.
Correct, but you shouldn't need to get online to work your test environment.
eb
eb
ASKER
Ok i removed it from the network and now everything is just running from the switch alone. I booted up the domain controller and it gets a service manager error because its not connected to the internet which is no biggie. Same thing happened when i booted up the exchange server too it says service controller manager error, some files didnt start and thats because its not connected to the internet. When i logged in and went and did a ipconfig /all i got a 169 ip address but have now manually added the ip address, subnet, gateway, dns on both machines. Now how can i see though that they are communicating with each other. Should i check in sites and services and just make sure its there with the correct ip address.
ASKER
Ebjers,
Ok they are both pinging each other now. So now what should i do.
Josh
Ok they are both pinging each other now. So now what should i do.
Josh
Yes check sites and services and DNS to make sure the correct IP information is reflected.
eb
eb
ASKER
I have manually added both the same ip, gateway, dns, wins, etc as the real environment so everything should be okay with that. Now i have created a new account on the domain controller called test10 and then when i go over to the exchange server 5.5 and i try to add a new acccount called test10 then i click add the primary windows NT account, i get access denied.
Also get this error when trying to delete an account in exchange administrator.
The trust relationship between this workstation and the primary domain fialed. Microsoft Windows NT.
ID NO: 0xc00206fd
Here i am posted screenshots of what im talking about.
Josh
error1.jpeg
error2.jpeg
error3.jpeg
Also get this error when trying to delete an account in exchange administrator.
The trust relationship between this workstation and the primary domain fialed. Microsoft Windows NT.
ID NO: 0xc00206fd
Here i am posted screenshots of what im talking about.
Josh
error1.jpeg
error2.jpeg
error3.jpeg
http://support.microsoft.com/kb/q162797
Will tell you why and it says you need to remove the computer from the domain and add it again.
Will tell you why and it says you need to remove the computer from the domain and add it again.
ASKER
Ebjers,
I figured it out already by resync the time and rebooting each of the servers at the same time and then they each booted up with error message. So on the domain i added a new account called test10 and then on the exchange server i created a new email address called test10 and the primary nt account i connected with test10 and that works. Now i have added another test machine to the switch with windows xp and outlook on it and readded it to the domain and that worked but it was also getting a syncing issue so i ran the command w32tm /config /update and w32tm /resync. I am now rebooting the machine and seeing if that will work. We are moving along iwth this project and i appreciate it all yoru help with it so far. Thanks so so much.
I figured it out already by resync the time and rebooting each of the servers at the same time and then they each booted up with error message. So on the domain i added a new account called test10 and then on the exchange server i created a new email address called test10 and the primary nt account i connected with test10 and that works. Now i have added another test machine to the switch with windows xp and outlook on it and readded it to the domain and that worked but it was also getting a syncing issue so i ran the command w32tm /config /update and w32tm /resync. I am now rebooting the machine and seeing if that will work. We are moving along iwth this project and i appreciate it all yoru help with it so far. Thanks so so much.
ASKER
Ebjers,
I have fixed the time issue with the new pc i added to the test environment that has outlook 2003 and the new test10 email account is setup now with exchange on the test environment. I even removed it form the domain and readded it with it plugged in to the switch and its working. It seems to be everything is working now and i should take acronis backups now of all the machines just in case of power outage now. Now i am going to add one more account to the test environment and 1 more test machine iwth outlook and i will send emails back and forth and just make sure it works then i will be 100% ready for the upgrade and migration.
I have fixed the time issue with the new pc i added to the test environment that has outlook 2003 and the new test10 email account is setup now with exchange on the test environment. I even removed it form the domain and readded it with it plugged in to the switch and its working. It seems to be everything is working now and i should take acronis backups now of all the machines just in case of power outage now. Now i am going to add one more account to the test environment and 1 more test machine iwth outlook and i will send emails back and forth and just make sure it works then i will be 100% ready for the upgrade and migration.
good luck
ASKER
Ebjers,
Well everything is working 100% now. I can send and receive emails from the 2 new accounts i setup in AD and exchange. Should i know just do the inhouse upgrade on the 2000 dc to 2003 dc in my test environment. I am going to accept this solution and give you the 250 points for helping me all the way out with this and i really really appreciate it so much.
Josh
Well everything is working 100% now. I can send and receive emails from the 2 new accounts i setup in AD and exchange. Should i know just do the inhouse upgrade on the 2000 dc to 2003 dc in my test environment. I am going to accept this solution and give you the 250 points for helping me all the way out with this and i really really appreciate it so much.
Josh
OK good luck with the upgrade test...
And remember things will always go right in the test, but they rarely go perfect when it comes to the real thing... In other words back everything up before you attempt this upgrade on the production network
eb
And remember things will always go right in the test, but they rarely go perfect when it comes to the real thing... In other words back everything up before you attempt this upgrade on the production network
eb
ASKER
Ebjers,
Thanks. So should i first upgrade to 2003 dc in the test environment and then start the migration.
Josh
Thanks. So should i first upgrade to 2003 dc in the test environment and then start the migration.
Josh
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
thanks for all your help so far with this and im moving along just fine now.
Good luck, and thanks for the points.,
eb
eb
> You don't want to add these to the domain. Either create a separate VLAN or just use a separate switch.
"I am wondering the best way now to make the exchange 5.5 server communicate with the windows 2000 dc for the test environment which is in my cube"
> Either use the VLAN or switch as described above, or if these are the only 2 servers you can use a crossover cable.
" Then once i get them both communicating would it be okay to go ahead and upgrade the 2000 dc to 2003 dc and then start migrating the exchange 5.5 to exchange 2003"
> Yes
Basically you want to take all the systems in your cube that you plan on using for this migration and put them on their own network that is isolated from the rest of the LAN.
eb