Exchange Server 2013 Migration issues

Dear Experts,

I have successfully migrated user mailboxes from exchange 2010 to exchange 2013. I am explaining the scenario below.

VM1 - Windows 2008R2  DC with Exchange 2010 installed  
Domain - Testking.local
VM2- Windows 2012 member server. I have added this machine to Testking.local domain then after I have installed AD DS, AD LDS,DNS etc. and all the prerequisites that are needed to Install Exchange 2013.I Installed Exchange 2013 on VM2 machine and it was successful and Migrated user mail boxes from exch2010 to Exch2013. But when I opened Exchange management Shell in exch2013 I am getting this error. Please find the attached image and suggest ....IMG_20150928_215502.jpgIMG_20150928_215606.jpg
LVL 1
JJ KRWindows System administratorAsked:
Who is Participating?

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

x
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.

Will SzymkowskiSenior Solution ArchitectCommented:
The message is pretty self explainitory. It is basically stating that it cannot make a connection to the server using Windows Remote Management due to the account that is being used.

Try some of the suggestions it lists and see if that corrects the issue.

Also try a different account with the proper permissions.

Will.

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
ET SupportCommented:
1. Confirm the logged in user has Domain admin, Organization management privilages.

2.  Run setspn -l "servername" and get the lists of SPNs

3. Confirm the IIS port binds are defaults and there is no binding with blank port informations
JJ KRWindows System administratorAuthor Commented:
Thanks a lot tried different account and issues resolved..
Will SzymkowskiSenior Solution ArchitectCommented:
Not sure why you graded this a C grade?

Will.
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
Exchange

From novice to tech pro — start learning today.