Move network from Class C space to Class A space

Right now I am currently running my network using a class c space (192.168.0.0/24).  I'm looking to move it to a class A space (10.20.0.0/24).  

Here's how I have my network setup currently:

ASUS RT-N16 router w/ DD-WRT acting as firewall/gateway/AP/DHCP Server
1 VMWARE vSphere 5.x hypervisor running Domain Controller, Exchange 2010, Application Server, File Server, vCenter
1 Synology NAS acting as backup
1 Wired Workstation
Bunch of wireless laptops, phones, tablets, media streamers, etc.

What's the best way to do the move without screwing up AD and my Exchange 2010 organization?
LVL 9
MikeIT ManagerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MiftaulCommented:
What difference will it makes moving from 192.168.0.0/24 to 10.20.0.0/24. You will remain on /24 aka 254 usable IP limit.
MikeIT ManagerAuthor Commented:
Me using /24 isn't set in stone, I just did it for posting purposes.  I want to move to a less used space so I have less issues dialing into my VPN from the outside.  I'm encountering too many places using the same Class C space as me lately so I want to move to a Class A space which also gives me the ability of expanding my usable IPs.
MaheshArchitectCommented:
Since your AD and exchange remains in VMware, means you can logon to console of exchange and AD server
So I don't see very tuff challenges

You can just dismount all exchange databases, disable CAS NLB if any prior to start IP switching activity
Then once IP switching activity completes on router \ switch, just connect to DCs one by one with console and change its IP segments, check DC to DC replication
Then change exchange IP addresses on exchange server, DAG virtual IPs,NLB virtual  IPs manually in Exchange and DNS as well
If storage is mapped with Exchange for mailboxes, ensure that its IPs also get changed prior to mounting Exchange database to avoid errors

Also you need to make changes to SMTP gateways as well if any

Mahesh

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.