Microsoft exchange 2010 - cannot conect EMC after install

I'm having a strange problem here.  I recently setup a windows server 2012 vm and install exchange server on it in my domain.  Installation completed but when I try to open the console I get a strange error message which i attached as a file image.  I checked the WinRm and it is running.  can anyone please point me in the direction to look? i'm totally lost here.

exchange error
SLEEPYALAsked:
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.

Addy NadiaExpertCommented:
Hello,

Ensure that the user account you’re logging on with is a member of the ‘Organization Management’ Active Directory security group.


Thanks,
Andy
0
Murali ReddyExchange ExpertCommented:
Defenitely not apermission issue, I suspect a connectivity issue.

Check Win-RM and IIS are running on the exchange server you are connecting to.

If you could open exchange management shell, get-exchangeserver|test-servicehealth
0
SLEEPYALAuthor Commented:
here is what I get when I try to open exchange management shell. Now it seems that it is looking for 2 seperate servers.  Let me give a bit of history maybe it will help. I tried to setup an exchange server before 'exch01' and that never worked and i trashed the server and never really removed anything related to it from AD.  Now I installed a new on 'naturesexch01', so that is the background if it has any bearing on this at all.

shell error
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Adam FarageEnterprise ArchCommented:
try running the EMT troubleshooter against it: http://blogs.technet.com/b/exchange/archive/2010/12/07/3411644.aspx. That should give you good details on what is actually broken, but it is in fact WinRM.

From the error I see above, it seems that the WinRM (/powershell/) vDirectory on the server is not responding to the kerberos request. With that said, try the following:

1) Check out the Event Viewer: Application logs to see if any associated errors show up when you hit the server
2) Make sure the Windows Remote Management service is started, and try to restart it
3) Open IIS Manager and make sure the MSExchangePowerShellAppPool is running, and if it is try recycling it (IISRESET /NOFORCE)
4) Run NETSTAT -AN on the local CAS and make sure that TCP 443 is not bound to another service..

All else fails, reboot the server.
0
Murali ReddyExchange ExpertCommented:
Restart WindowsRemoteManagement service and check once on the local server from where you are trying to run.
0
Diwakar SharmaCommented:
Hi Sleepyal,

You can run "winrm quickconfig" and then check. it helped me to resolve this issue with Exchange 2010 SP1.
 This command analyzes and configures the WinRM service.

Diwakar
0
Adam FarageEnterprise ArchCommented:
Also check DNS - I do not think this is an issue with the WinRM configuration, but an issue with either one of the following:

DNS A record in the forward lookup zone
TCP 443 bound to a separate service
Deadlock on the MSExchangePowerShellAppPool or the pool not started
0
SLEEPYALAuthor Commented:
I tried rebooting several times but the issue persists.  how can I check these 2?

TCP 443 bound to a separate service
Deadlock on the MSExchangePowerShellAppPool or the pool not started
0
Adam FarageEnterprise ArchCommented:
Are the DNS A records within the forward lookup zone for each server? So if you run the following, what do you get:

NSLOOKUP
Set q=A
Server (internal DNS IP address)
FQDN of CAS

Does this look up?
0
SLEEPYALAuthor Commented:
yeah it all looks up correctly.
0
Adam FarageEnterprise ArchCommented:
Try the winrm quickconfig
0
SLEEPYALAuthor Commented:
I just scrapped the whole thing and started over and now i'm getting a different issue, will consider this case resolved. thank you all
0

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
SLEEPYALAuthor Commented:
decided to move on, no solution available.
0
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.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.