2003 to 2012 migration and Standalone DNS Migration

Thank you for viewing my post.

Current Environment

Domain Windows 2003

DNS server in DMZ (Standalone DNS server?)

File and Exchange (2003) servers in separate network

Users - 100

Near Term Plan Upgrade all servers (including Exchange) to Windows 2012

Issue:

Im not sure of the correct upgrade path but I see a couple possibilities but I dont know which is the best approach:

-       Option 1- Install Fresh 2012 Domain Configure Accounts Security and then add PC`s / users to domain and deal with all the data/email migration. Taking DNS server out of DMZ and install with AD Server / Services

or

-       Option 2a - Migrate/Transition/Upgrade to Server 2008 R2 Domain and to Exchange 2010 - keeping DNS in DMZ

-       Option 2b then further transition/migrate to Windows Server 2012 and Exchange 2013 (plan to do is Option 1 is not viable)

Current Consideration / thinking - Keeping DNS server in DMZ

Im considering doing option 2a first in order to stabilize / add capacity (to) the Network in general and to buy time to better plan Option 1 (preferred-for too many reasons to explain here).

Im not sure the best way to ask my question(s) but I will try (it will be a bit clunky):

In System properties, the computer name is showing as ex. ComputerName.DomainName.local  Up until working on this network, I have always seen ex. ComputerName.DomainName so Im a bit unfamiliar with this scenario

What is the best thing to do?

Keep the DNS in the DMZ configuration? Or as part of the upgrade have AD and DNS on the same server? (Option 1)

If I configure AD and DNS on the same server how will this affect the users PC and the user Profile? By this I mean ex. Prior to upgrade `John` has a pc named HappyPC.DomainName.local . Can John logon the upgraded Network without any problems or will his PC need to be removed from the domain (HappyPC.domainname.local) before upgrading and then re-added (to the domain. HappyPC.domain) after the upgrade and then have his profile reconfigured? 

The truth is I dont understand what happen or what will happen when taking the DNS out the DMZ. I have always worked with DNS and ADS being on the same server.

Can anyone provide some insight or advice on the best upgrade/integration approach? Or maybe some general information on what to expect when in terms with the Users profile (and email for that matter) in this scenario.  I want to make the upgrade/migration as smooth and painless as possible for the end users.

Any assistance would be appreciated.

Thank you for taking the time to read my questions.

Arlo

May 28th, 2015 7:45am

Hello,

"DNS server in DMZ (Standalone DNS server?)"

What is the reason for this, security? Normally you should run DNS on the DCs direct and open the firewalls for DNS forwarding so the clients can access the internet via your domain DNS server.

"File and Exchange (2003) servers in separate network"

Does this mean in another subnet or in another forest/domain where you have a trust with?

You can not install Exchange 2003 on Windows Server 2012 and you can not migrate to Exchange 2013 directly.

In your case I would install a new OS DC to the existing domain, then install a new Exchange 2010 on domain member server, YES 2010, as coexistence is NOT working with Exchange 2003 for Exchange 2013.

http://blogs.technet.com/b/mconeill/archive/2013/04/03/migration-from-exchange-2003-to-2013-a-no-go.aspx

https://social.technet.microsoft.com/Forums/exchange/en-US/22636a3c-3550-4cbd-86b4-88c078468df3/migrating-from-exchange-2003-to-2013?forum=exchangesvrdeploy

https://technet.microsoft.com/en-us/library/dd638130%28v=exchg.141%29.aspx?f=255&MSPPError=-2147217396

For the Exchange part I suggest that you ask the experts in https://social.technet.microsoft.com/Forums/exchange/en-US/22636a3c-3550-4cbd-86b4-88c078468df3/migrating-from-exchange-2003-to-2013?forum=exchangesvrdeploy

The domain upgrade to 2012 you can do as described in http://blogs.msmvps.com/mweber/2012/07/30/upgrading-an-active-directory-domain-from-windows-server-2003-or-windows-server-2003-r2-to-windows-server-2012/ but check BEFORE with the Exchange experts about problems that may occur. Also adding the new OS DC to the existing domain has the advantage that you can keep accounts, GPOs, etc.

If you install new file servers "robocopy" could be used to copy data including permissions and then just the GPOs must be adjusted for the new server.

Free Windows Admin Tool Kit Click here and download it now
May 28th, 2015 1:51pm

Hi,

I just want to confirm what is the current situation.

Please feel free to let us know if you need further assistance.

Regards.

May 30th, 2015 12:56am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics