• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 877
  • Last Modified:

Cannot open Microsoft Exchange Managment Console Exchange 2010

Access Denied- Discover -Excahgen Server UseWia$ true Suppress Error $ true is the message I am getting- anyone have a clue what this mean or how I can resolve this issue- can't add or delete users right now or anything else for that matter
exchange.jpg
0
funkyone60
Asked:
funkyone60
  • 4
  • 4
  • 2
1 Solution
 
Glen KnightCommented:
Can you try deleting the EMC template as per my blog post here: http://demazter.wordpress.com/2010/07/02/exchange-2010-emc-error-2/
0
 
manav08Commented:
This issue is described here (http://msexchangeteam.com/archive/2010/02/04/453946.aspx) and it happens because of http binding settings for default website is changed in IIS.
To fix it follow these steps -

1. Open up Administrative Tools -> IIS Manager
2. On the left hand pane select - Sites -> Default Web Site.
3. Now on the Right hand pane click on Bindings
3. Edit the http binding(or create a new one if none exists) and make sure that hostname field is blank and port reads 80. Refer to picture below


snapshot.png
0
 
manav08Commented:
Rest of the steps -
4. After doing the above REBOOT Server.
5. If still the issue occurs again look at the following causes -

a). The ExchangeInstallPath variable may be missing. To check this, go to the System Properties, Environment variables, and look under the System variables. You should see a variable of ExchangeInstallPath with a value pointing to C:\Program Files\Microsoft\Exchange Server\V14\.

b). The Path of the Powershell virtual directory has been modified. The PowerShell virtual directory must point to the \Program Files\Microsoft\Exchange Server\v14\ClientAccess\PowerShell directory or you will encounter problems.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
Glen KnightCommented:
Would you mind sharing your solution with us instead of deleting the question without responding to any of the expert posts.
0
 
manav08Commented:
I totall agree with demazter. If the author doesn't respond, the points should be split between us.
0
 
manav08Commented:
I object because of same reasons given by demazter above. I suggest a point split
0
 
funkyone60Author Commented:
Sorry guys- I thought I had responded to this earlier.  Even though both solutions were informative- and helpful- neither of them resolved the issue.  The issue was the exchange server clock was off my 10 minutes from the AD Server.  Once i resolved the time the problem went away.
0
 
Glen KnightCommented:
thank you for getting back to us.
Now please except your last post as the solution.

By sharing your solution with us, we have all learned something :)
0
 
funkyone60Author Commented:
How do I do that?  I am new to this obviously- still learning the protocols
0
 
Glen KnightCommented:
There should be an Accept as solution link in the comment where you gave the solution?
Just click this link and follow the instructions.

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.

Join & Write a Comment

Featured Post

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

  • 4
  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now