We've got Win2K3 SBS SP2 and Exchange 2003 SP2 with a single server...
So,
1) should we put our Exchange 2003 SP2 on a new server and rename then
2) rename with Exchange 2003 SP2 on our same server
3) something else?
Our domain was setup with .net rather than .local, so our rename is on the
..net to .local.
What if we rename the domain from abc.net to xyz.local? Single step rename?
What are the implications if we mess things up? Or is it possible to mess
things up?
TIA

We've got Win2K3 SBS SP2 and Exchange 2003 SP2 with a single server...
So,
1) should we put our Exchange 2003 SP2 on a new server and rename then
2) rename with Exchange 2003 SP2 on our same server
3) something else?
Our domain was setup with .net rather than .local, so our rename is on the
..net to .local.
What if we rename the domain from abc.net to xyz.local? Single step rename?
What are the implications if we mess things up? Or is it possible to mess
things up?
TIA

With SBS? Then you can't do it at all, I'm afraid, outside of a complete
flatten/reinstall. Note that SBS does a lot of things differently and
you're always best off asking SBS2003 questions in m.p.windows.server.sbs.

> So,
> 1) should we put our Exchange 2003 SP2 on a new server and rename then
> 2) rename with Exchange 2003 SP2 on our same server
> 3) something else?
> Our domain was setup with .net rather than .local, so our rename is
> on the .net to .local.

Why do you need to do this? It's true, using the same DNS namespace
internally as externally can cause a few problems, but most of the time you
can deal with it -if your users can't access the publicly hostedwww.mydomain.com because your AD-integrated DNS thinks itself authoritative
for mydomain.com, just create a host called www in your forward lookup zone
(in your SBS DNS console) and put in the appropriate public IP. Etc.
>
> What if we rename the domain from abc.net to xyz.local? Single step
> rename? What are the implications if we mess things up? Or is it
> possible to mess things up?

With SBS? Then you can't do it at all, I'm afraid, outside of a complete
flatten/reinstall. Note that SBS does a lot of things differently and
you're always best off asking SBS2003 questions in m.p.windows.server.sbs.

> So,
> 1) should we put our Exchange 2003 SP2 on a new server and rename then
> 2) rename with Exchange 2003 SP2 on our same server
> 3) something else?
> Our domain was setup with .net rather than .local, so our rename is
> on the .net to .local.

Why do you need to do this? It's true, using the same DNS namespace
internally as externally can cause a few problems, but most of the time you
can deal with it -if your users can't access the publicly hostedwww.mydomain.com because your AD-integrated DNS thinks itself authoritative
for mydomain.com, just create a host called www in your forward lookup zone
(in your SBS DNS console) and put in the appropriate public IP. Etc.
>
> What if we rename the domain from abc.net to xyz.local? Single step
> rename? What are the implications if we mess things up? Or is it
> possible to mess things up?