Exchange 2010 EMC connection issue

I have introduced a new Server 2012 into an existing domain.
Primary DC SBS2008 with Exchange 2007.
Update Rollup 8-v2 and 10 to 15 for Exchange Server 2007 SP3.

Server1 (new) Server 2012 R2 Standard installed and joined the server to the existing domain.
Web Server IIS
.NET Framework 3.5 & 4.5 Features
WinRM IIS Extension
Media Features
Exchange 2010.

The existing Backup server runs Server 2008 R2 SP1
Update Rollup 7-v2 Exchange Server 2010 SP1
Update Rollup 8 Exchange Server 2010 SP1
Update Rollup Office Communications Server 2007 R2 Unified Communications Manager API 2.0

No antivirus yet
The backup server can see Server1 in the EMC all seems works ok there.
On Server 2012 (Server1) when I open EMC and try to connect to BackupServer I see the following.

Initialization failed
The following error occurred when retrieving user information for domainname\admin
The term "Get-LinkedRoleGroupForLogonUser" is not recognized as the name of a cmdlet, function, script file, or operable program.
Check spelling of the name, or if a path was included, verify that the path is correct and try again.

Maybe admin is not recognized as an account on Server2012?
I was reading a post where I guy had the same error and he said both Exchange 2010 versions need to be the same.
Backupserver Version 14.1 (Build 218.15)
Server1 Version 14.2 (Build 247.5)
If so how do I bring BackupServer up to same as Server1 version and build?  
tauro2Company DirectorAsked:
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.

StuartTechnical Architect - CloudCommented:
Backupserver Version 14.1 (Build 218.15) = Exchange 2010 SP1
Server1 Version 14.2 (Build 247.5) = Exchange 2010 SP2

Therefore to bring the backup server to the same version you need to update it with SP2

You should also look at and plan a upgrade to the latest release to make the most of the product features and bug fixes introduced in later versions (currently SP3 rollup 10)

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
StuartTechnical Architect - CloudCommented:
This article shows the version numbers inc added features/bug fixes with links to the download ;)
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

tauro2Company DirectorAuthor Commented:
Thanks for the quick reply. So you think it is a version issue?  I thought I had them both running SP2 but I have obviously missed it.  I have planned on bringing them both up to SP3. Thanks for the advice I will be working on it this weekend will keep you posted with progress.
StuartTechnical Architect - CloudCommented:
Possibly, I personally would  get all the Exchange servers to the same patch level then start troubleshooting again if this doesn't resolve the issue
tauro2Company DirectorAuthor Commented:
Thanks again Stuart. One question. Can I go straight to SP3 or do all the SP need to be installed incrementally?
Shreedhar EtteCommented:
You need to install latest SP directly.
StuartTechnical Architect - CloudCommented:
You need to install SP3 then install roll up 10, the SP install will need to modify the schema so make sure the account has the correct permissions, also run the roll up as administrator or it will fail
tauro2Company DirectorAuthor Commented:
Ok thank you to Stuart and thank you Sheedhar. I plan to seize the FISMO roles from SBS2008. Would it be advisable to leave this task until until last?
StuartTechnical Architect - CloudCommented:
Yes because you will be rebooting, make sure replication is good before you moves roles
tauro2Company DirectorAuthor Commented:
Success both systems now have same build and I can open the EMC on the new server. Only thing is there is no data. Nothing in the left column such as organization and server configuration?
Also on the outgoing DC when I open the 2007 EMC I get a warning.

The server administrator 'longwallhaul.local/Microsoft Exchange Security Groups/Delegated Setup' is not a member of the Exchange View-Only Administrators.
StuartTechnical Architect - CloudCommented:
Add your ad account to organisation administrators
tauro2Company DirectorAuthor Commented:
Already is a member of that group. Was not a member of the exchange view-only admins group though but I have since added it. Also the main Administrator account is disabled. Should I enable for this process?
tauro2Company DirectorAuthor Commented:
Update. The original EMC message I was seeing is gone and it opens. But there is no data in the left column. Under organisational Summary and Servers Summary every line displays Unavailable.
If I click on manage databases or manage server nothing happens.
When I click on Data is unavailable. "Click here to access the latest data" the snap-in crashes and want to report the error to Microsoft. I think I might need to reinstall Exchange 2010 on Server1. Or load SP3 on both that may resolve issues. There is some sort of connection or network issue between the 2 2010 Exchange servers.
tauro2Company DirectorAuthor Commented:
Update 3. Success. Removed Clustering Tools and management role service from Backup server. Installing SP3 it complained of a transient communications issue and there was a hotfix for it but I  we don't need this as it is not possible to setup a failover cluster on this domain. Installed SP3 on server1. Restarted and now EMC loads with all the content and data in the left column. I can now confidently move all the mailboxes and manage them from the new server.
To summaries.
Looks like there may be a bug or a compatibility issue with .NET 3.5 and reinstalling solved the EMC MMC crashing. Thus I could then change servers from the console.
Installing SP3 resolved the management view issue in the management column.
Thank you Stuart for your advice it really helped me get there.
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 Server 2012

From novice to tech pro — start learning today.