dth1
asked on
Changing local domain name in SBS 2003 Standard (no Exchange)
Hi,
I'm looking for information regarding changing the local domain name on Small Business Server 2003 Standard.I'm in a situation where someone configured the system with a local domain name identical to the .com domain name the company uses for internet services, which are all hosted at a service provider. I know that Microsoft has a tool for this that does not work on SBS 2003 and Ihave seen the sbsmigration.com website. I have the impression that the difficulties in SBS 2003 mostly involve Exchange. I am wondering if there is an outside chance that domianrename.exe will work on a SBS 2003 server that does not have Exchange installed, or in the case of the Standard edition does not include Exchange.
If it makes any difference this network has another server running Server 2003 R2. This server is configured as a backup AD domain controller.
I'm looking for information regarding changing the local domain name on Small Business Server 2003 Standard.I'm in a situation where someone configured the system with a local domain name identical to the .com domain name the company uses for internet services, which are all hosted at a service provider. I know that Microsoft has a tool for this that does not work on SBS 2003 and Ihave seen the sbsmigration.com website. I have the impression that the difficulties in SBS 2003 mostly involve Exchange. I am wondering if there is an outside chance that domianrename.exe will work on a SBS 2003 server that does not have Exchange installed, or in the case of the Standard edition does not include Exchange.
If it makes any difference this network has another server running Server 2003 R2. This server is configured as a backup AD domain controller.
Last Comment
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS 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 the response, that is pretty much what I figured. I have only been in this position once before and elected to reinstall the OS.
I'll expand my question to include some more details, perhaps someone out there has had to deal with this domain configuration before and can speak to the problems it might cause. This server has been in place for 3-4 years, the person who set it up realized their mistake and corrected it by making the necessary changes in the DNS server(point host names like mail, www, etc to the proper IP address). It looks to me like this has been done properly and I don't personally notice any network issues that lead me to believe it is worth the effort and expense to make this right. The problem is that the support rep at the ISP we use(a small company based in a nearby city) somehow got wind of the DNS situation here, so the first words out of his mouth when we call for support are "change your DNS." I don't have to deal with the ISP as much as the guy here who handles the web stuff, and he gets this kind of response to problems related to the web site, ftp access etc. It is a stupid situation and I think it would be much easier to change the ISP than the server configuration except for the nagging doubt I have that there are potentially more problems caused by this configuration than I realize.
Has anyone ever lived with this situation before and can you comment on the problems you had that were not addressed by manually configuring some of the DNS hosts on your server?
I'll expand my question to include some more details, perhaps someone out there has had to deal with this domain configuration before and can speak to the problems it might cause. This server has been in place for 3-4 years, the person who set it up realized their mistake and corrected it by making the necessary changes in the DNS server(point host names like mail, www, etc to the proper IP address). It looks to me like this has been done properly and I don't personally notice any network issues that lead me to believe it is worth the effort and expense to make this right. The problem is that the support rep at the ISP we use(a small company based in a nearby city) somehow got wind of the DNS situation here, so the first words out of his mouth when we call for support are "change your DNS." I don't have to deal with the ISP as much as the guy here who handles the web stuff, and he gets this kind of response to problems related to the web site, ftp access etc. It is a stupid situation and I think it would be much easier to change the ISP than the server configuration except for the nagging doubt I have that there are potentially more problems caused by this configuration than I realize.
Has anyone ever lived with this situation before and can you comment on the problems you had that were not addressed by manually configuring some of the DNS hosts on your server?
SOLUTION
THIS SOLUTION IS 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.
Windows Server 2003
Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).
129K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
You could attempt to mask the domain with other dns records. i.e. matching domain1.com with records in domain2.com.
You can also specify a Primary USN so that you log on using credentials for a different domain to the primary.
Other than this, i think you're stuck with it.