<div>
You would end up doing a domain rename, which is &quot;fun.&quot; You're better off using a .lan or .local or something for your company anyway.
</div>


<div>
You probably should not be naming the SBS domain the same as your public domain in the first place. &nbsp;See this article on MS view of domain naming. <a href="http://support.microsoft.com/kb/296250" rel="ugc nofollow">http://support.microsoft.com/kb/296250</a>&nbsp; If you name it with a .local, then you would not need to renam it. &nbsp;All you would need to do is rerun the CEICW to give Exchange the real external domain name and you will be all set.
</div>


<div>
<div class="content wysiwyg-content">
Hi Everyone,<br />
<br />
I'm installing SBS 2003 on a test network. &nbsp;Thing is, I need to install it as a different DNS Domain on the test network (it's set up that way with the ISP). &nbsp;The test network is compnay.biz, and when we switch it to production, it's going to be company.com.<br />
<br />
Can the DNS Domain be changed once the SBS is installed? &nbsp;Recall that The SBS server function as the primary (and only) DC.<br />
<br />
Thanks,<br />
<br />
Theo
</div>
</div>


Hi Everyone,

I'm installing SBS 2003 on a test network.  Thing is, I need to install it as a different DNS Domain on the test network (it's set up that way with the ISP).  The test network is compnay.biz, and when we switch it to production, it's going to be company.com.

Can the DNS Domain be changed once the SBS is installed?  Recall that The SBS server function as the primary (and only) DC.

Thanks,

Theo

SBS 2003 DNS question

Small Business Server (SBS) is a line of server operating systems targeted at small businesses by bundling the operating system with a number of other Microsoft products that would normally need to be purchased or licensed separately. The most notable inclusions are Exchange, SQL Server, SharePoint and ISA/TMG (Microsoft's firewall and proxy server).

Network Management involves issues that are independent of specific hardware or software, including email policies, upgrade planning, backup scheduling and working with managed service providers for Desktop-As-A-Service (DaaS), Software-As-A-Service (SaaS) and the like through the use of tools, coupled with manufacturer standards, best practice guidelines, policies and procedures plus all other relevant documentation. Network management also includes monitoring, alerting and reporting, management reporting, planning for device or service updates, the backup of configurations, the setting of key performance indicators and measures (KPIs/KPMs), associated service level agreements and problem records as part of the IT Service Management (ITSM) framework.

Network Management

Servers are computing devices that are similar to desktop computers in that they have the same basic components, but are significantly different in size, configuration and purpose. Servers are usually accessed over a network, and many run unattended, without a computer monitor, input device, audio hardware or USB interfaces. Many servers do not have a graphical user interface (GUI), and are configured and managed remotely. Servers typically include hardware redundancy such as dual power supplies, RAID disk systems, and ECC memory, along with extensive pre-boot memory testing and verification. Critical components might be hot swappable, and to guard against overheating, servers might have more powerful fans or use water cooling.