To change internal AD domain name or create a new forest/domain

I have a customer who has a small AD domain (>50 users) that has a lot of problems but all problems are a result of misconfiguration and not corruption.  They are wanting to create a whole new forest and domain.  My stance is to just fix the current one since it is going to be just as much work which ever option they choose ( no migration involved).

Now they have introduced a new wrinkle requesting the internal AD domain name be changed.  

I have heard of nightmare with domain name changes and now I am not sure if creating a new forest isn't the best solution.  They have no Exchange (O365) and no SQL that I know of.

What is your option?  I want to present the best possible solution with the minimum amount of effort.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

My only comment is that renaming a domain can be done but it can be tricky and for such a small domain [relatively speaking] it's probably not worth the effort.
ENTPFAuthor Commented:
So probably the best solution would to create a new forest/domain with the new name?  Would you agree?
I think I would probably do that, yes.  I guess you could test it out and see if you can change the name on a dummy domain without any troubles [in a VM, perhaps].

You don't say exactly how it is misconfigured so that could play a roll in your decision, too.
I would say give the customer what they want.  If not, any other problem that creeps up in the future they will blame on the repaired domain controller.  Example, issues caused by patches, bad drivers etc..
I wouldn't rename the existing domain,
I would setup a new domain controller with the new name and move all the desktops over and any other servers that are not Domain controllers.
Migrate any data over
Then flatten the original DC and add it back as a backup DC
But, if you have an Exchange server then things will get difficult.

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
Active Directory

From novice to tech pro — start learning today.