Exchange Issues

I am working with Exchange 2010 Enterprise running on Windows 2008 R2 standard.  Our SSL Certificate expired and I installed a new one.  We continued to have a name error because out internal domain is a .local.  The plan was to do some more research on the effect on Outlook clients if we changed the internal URL.  The next day we started to see more issues.  Currently EMC, EMS and EWS are all not working.  I get a message that WinRM client cannot process the request.  These resolutions I have found on the web have already been tried:
1. time sync is fine
2. Kerbauth modules are correct at both the default web page level and powershell
3. SSL has been on and off
4. WinRM IIS Extension has been installed

Our issues include Mac outlook clients don't work, OWA cannot delete email, calendar busy function does not work, I cannot access either the management console or the shell
LVL 1
it_medcompAsked:
Who is Participating?
 
it_medcompConnect With a Mentor Author Commented:
NetoMeter,

When I start Exchange Management Shell I get the attached
EMS.PNG
0
 
Alan HardistyCo-OwnerCommented:
You can change the internal URL's for Exchange so that Exchange looks to your Public SSL certificate name for resolution, but it sounds like the new SSL didn't install properly.

Does OWA work and do you see any cert errors?
0
 
Andy MInternal Systems ManagerCommented:
Not 100% sure if it's the same thing but we had similar problems with an Exch 2010 system a while ago - resolved by restarting IIS services (or rebooting server could work too) - think it ended up being someone tried to alter the exchange url's through IIS rather than powershell or something like that.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
NetoMeter ScreencastsCommented:
What kind of certificate did you install - a Single Domain Certificate or a UCC (Multipple Domain Certificate).

You need to start with checking your Exchange 2010 URL configuration. Could you post the result of the following commands in Exchange Management Shell:
Get-ClientAccessServer | FL *Uri
Get-EcpVirtualDirectory | FL *URL
Get-WebServicesVirtualDirectory | FL *URL
Get-ActiveSyncVirtualDirectory | FL *URL
Get-OabVirtualDirectory | FL *URL
Get-OWAVirtualDirectory | FL *ternalURL

Open in new window

If necessary, replace the real internal Domain Name with "MyCompany.local" and the public one with "MyCompany.com"
0
 
it_medcompAuthor Commented:
Alan

Yes OWA basically works, but it does not delete email.  Outlook clients basically work as well, except for the Mac client that relies on EWS which isn't working at all.
0
 
it_medcompAuthor Commented:
Morty

I have restarted the server multiple times at this point and that hasn't helped
0
 
it_medcompAuthor Commented:
NetoMeter,

When I try to run these commands I get a response that it is not a recognized cmdlet
0
 
Lee IngallsConnect With a Mentor Director of IT/TS, Quality and FinanceCommented:
Have you assigned services to the certificate? IIS selected?

The following solution worked for me....  please reference:
http://technet.microsoft.com/en-us/library/ee332322.aspx
"Use the Shell to renew an Exchange certificate" since EMC is not working.
0
 
it_medcompAuthor Commented:
Lee

When I installed the new certificate, this is the TechNet I followed.  At this point I can't get into the shell either.
0
 
NetoMeter ScreencastsCommented:
Probably you are trying to run them in PowerShell - you need to run them in Exchange Management Shell.
0
 
NetoMeter ScreencastsCommented:
We have a starting point.

Download and run  EMTshooter (Exchange Management Troubleshooter) and see what info it provides.
0
 
it_medcompAuthor Commented:
I have been able to spin up a virtual server and install Exchange on that server.  From there I am able to access Exchange Management shell and it seems to have connected to my production Exchange server.

I ran the following

Get-ClientAccessServer | FL *Uri
Get-EcpVirtualDirectory | FL *URL
Get-WebServicesVirtualDirectory | FL *URL
Get-ActiveSyncVirtualDirectory | FL *URL
Get-OabVirtualDirectory | FL *URL
Get-OWAVirtualDirectory | FL *ternalURL

They all pointed to my production server using the .local domain.  I have reset them to my external domain that matches the certificate I recently install.

This has fixed the issue with the certificate warning when opening outlook.

This has not fixed the EWS issue which I believe is the cause of the calendar, Mac connection and not being able to delete from OWA.

I also ran the EMTShooter and it did not show any problems.
0
 
Md. MojahidCommented:
0
 
it_medcompAuthor Commented:
Lots of good help. Not sure what the eventual solution was- it's almost a 2 year old question! I just have to accept it so I can use this account.
0
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.

All Courses

From novice to tech pro — start learning today.