Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 379
  • Last Modified:

SBS 2003 to SBS 2011 migration issue?

I have a Dell OEM SBS 2003 server and am installing a new Dell OEM SBS 2011 server.  I've read the migration process is the preferred method, but the existing domain is domain.local.

The new server will have SSL certificates for remote email and VPN access and I understand many CAs won't issue a cert if there is a .local.

Will the migration process copy the FQDN (including the .local) to the new server? (I'm assuming it will)

If so, is there any way to either prevent that from happening or rename post migration?  (I'm assuming it would require a re-install to rename)

I'm ready to pull the trigger whether it's a migration or new installation, so any help would be greatly appreciated!
0
tj-a
Asked:
tj-a
1 Solution
 
Cliff GaliherCommented:
Active Directory domain names have no impact on public facing services, and never have.

so yes, a migration will keep your domain.local name.


and no, you should not purchase public certificates with .local names.

but it won't matter because you can configure your public services to use a public name, including VPN and exchange service, purchase a public cert, and it will all work...EVEN with the AD name being .local.

so...migrate away. It all works.
0
 
tj-aAuthor Commented:
Thanks for the info cgaliher!

I'm using Demazter's SBS2003 to SBS2011 guide for the migration process.

I had an issue with the server hanging on 'Applying computer settings...' for about an hour and found it was some sort of DNS issue even though I could ping the destination server by name. Simply rebooting the source server allowed the destination to finally boot.

I'm migrating data now and will update if any other issues arise.
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now