Networks

Would be hopefull is u list some information about the server:

OS:
Any SP:
ISA Server software:
etc


Anyhow for starter I have link:

http://technet2.microsoft.com/WindowsServer/en/library/b6b29ec7-8f87-4761-9e9f-fd85ffed76601033.mspx?mfr=true

May help for DNS & domain controller.

Thank you for the link really helpfull...
To answer your questions:

- OS: Window 2000 Server SP4
- ISA: Microsoft ISA Server 2000
- All Clients are Windows XP SP2

But actually im not trying to move the domain controller or dns to a different site or location... im trying to move it to other servers...

Generally speaking the answer is "yes." However, there could be a few catches. First of all, if your server is a DC, then you have to have DNS running on it anyway. So, I wouldn't bother moving DNS; if you're worried about load on the server, you could set up another DNS server on the domain as a secondary or additional DNS server.

As far as ISA goes, unless you are using any programs that require the ISA client to be installed, moving ISA should not affect workstations at all. They should be set to auto-detect the proxy server through IE, and that will find the new server. The only problem might be if the workstations have their default gateway set statically; that setting would have to be changed if so. If you are using DHCP to set a default gateway on the clients, you would change that setting and refresh the IP addresses on the workstations to ensure they don't fail to detect the new proxy server.

Hope this helps!

ok, what if i promote another member server to Domain Controller, wait untill the two DCs replicate information, demote the old DC and keep the DNS service on it... is that possible... so now i will have the DNS and ISA on one Server & DC on another... so later on i can move the ISA and have 3 servers instead of 1... what do you think

It would be easyer to move DNS to another machine, let that replicate, then taked DNS off the DC. You do not have to have DNS running on a DC, but there has to be a DNS server for AD to function. As for ISA server, moving it will only effect the VPN users I would think. Is the ISA server acting as you firewall and/or gateway? When moving the DNS server, remember to change that setting in DHCP or you will hear a lot of complaints.

thanks for the reply issakd,
the isa server is acting as a firewall...
also i guess i want to move the domain controller to another location because now i have another problem with AD... http://techrepublic.com.com/5208-11184-0.html?forumID=39&threadID=200622&start=0

and i've installed DNS on another server and the replication is great...

now what do you suggest

First, check to see if the server you have now is a GC or not. AD Sites and Services --> Local Site --> Local DC --> NTDS Settings -->Right click properties. Look for the Global Catalog check box. Also, can client computers log into and out of the domain correctly?
Global Catalog is used to do forest wide searches, exchange contact lists, and universal group information. Give DNS time to fully replicate, and then switch all computers to the new DNS server using DHCP server configs. Manually set the DNS options on the DC. Dont forget to copy any forwarder information over to the new DNS server as it will become the new primary server. Also when you move the ISA server you will have to update your gateway information in DHCP as well as on static servers. I would save moving the DC for last, but adding a new DC and weighting it to be prefered is a good idea.

This question was closed by the author