?
Solved

Exchange 2010 OWA works for some not others

Posted on 2012-08-25
24
Medium Priority
?
849 Views
Last Modified: 2012-08-31
Ok.  I have installed exchange 2010 on a new server running server 2008 R2 SP1, fully patched.
The users that were in the domain before I installed exchange cannot login to OWA, I get the error message incorrect username or password.  Users I have created since then work just fine.

I have un-installed OWA and reinstalled it, I have checked event logs and error logs, nothing pops out about the error.

My question is, is there something that needs to be set on the users that may not have been updated during the AD upgrade and ADPREP's?

I have looked at both using ADSIEDIT and cannot see anything overtly different between the users.
0
Comment
Question by:Enfostrad
  • 12
  • 10
  • +1
24 Comments
 

Author Comment

by:Enfostrad
ID: 38333224
The old domain was running on 2003 and adprep /forest and /domain were performed and the new 2008 server promoted to DC.  

I cannot think of any other items to report, so please let me know.
0
 
LVL 33

Expert Comment

by:Exchange_Geek
ID: 38333227
Run the following cmdlet against the old user and verify if they can access OWA

Set-Mailbox -Identity AffectedUser -applymandatoryproperties

Regards,
Exchange_Geek
0
 

Author Comment

by:Enfostrad
ID: 38333239
Thanks for the reply.  I ran that on two of the effected employees and it came back successful but no settings changed.  I tried logging in as them anyhow, no difference in how OWA operates.  I have set the authentication on OWA to forms and added the default domain name, even tho I have tried with and without domain name for the username.
0
Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

 
LVL 33

Expert Comment

by:Exchange_Geek
ID: 38333246
OWA should only have basic authentication, please change it to basic and reset IIS.

Regards,
Exchange_Geek
0
 

Author Comment

by:Enfostrad
ID: 38333252
Ok I changed that, don't like how the login looks.  and the same users still cannot login.  I have reset their password and ensured they are unlocked in AD.
0
 
LVL 33

Expert Comment

by:Exchange_Geek
ID: 38333256
When you run the cmdlet against the mailboxes you ran "applymandatoryproperties" do you find mailbox type as legacy / linked or user mailbox?

Get-mailbox Affecteduser

Regards,
Exchange_Geek
0
 

Author Comment

by:Enfostrad
ID: 38333260
That command never showed me the type.  However, according to EMC they are all user mailboxes.
0
 
LVL 33

Expert Comment

by:Exchange_Geek
ID: 38333261
OK Can you login to their webmail using your webmail credentials, considering giving yourself full mailbox rights?

Regards,
Exchange_Geek
0
 
LVL 37

Expert Comment

by:Jamie McKillop
ID: 38333271
"OWA should only have basic authentication" What? You can use whatever authentication method you want. Why can't he use forms based authentication?

Are these users able to access their mailbox with Outlook? Is OWA enabled on thier mailboxes? Was this an upgrade from a previous version of Exchange or is this the first time Exchange has been installed in this forest?

JJ
0
 
LVL 33

Expert Comment

by:Exchange_Geek
ID: 38333274
I'm talking about what the default settings are. We can toy around with Windows Integration / Basic / anonymous - what ever we want - that's our wish.

Regards,
Exchange_Geek
0
 

Author Comment

by:Enfostrad
ID: 38333288
This is a new exchange install.  no previous install of exchange.  I have tried all types of authentication.  I logged in as admin to OWA and tried opening one affected persons mail and got "your mailbox appears to be unavailable. Try again in ten minutes."
0
 

Author Comment

by:Enfostrad
ID: 38333314
I fixed the above error,  the system attendant failed.  I have that straightened out.  I can now open their mailboxes when logged in as admin.  When they try to login, they get the error incorrect username or password.
0
 
LVL 33

Expert Comment

by:Exchange_Geek
ID: 38333315
How many mailboxes are we dealing with that are affected?

Regards,
Exchange_Geek
0
 

Author Comment

by:Enfostrad
ID: 38333316
6 or 7 (almost the entire users group... I know, small group.
0
 
LVL 33

Expert Comment

by:Exchange_Geek
ID: 38333318
How about, you disconnect one of them - and reconnect them immediately, considering if you reconnect you're basically providing them Exchange attributes of you're new box.

So, try this and provide feedback.

Regards,
Exchange_Geek
0
 

Author Comment

by:Enfostrad
ID: 38333320
disconnect the mailbox? or remove the account and recreate?
0
 
LVL 33

Expert Comment

by:Exchange_Geek
ID: 38333325
Hang on - only disable the mailbox DO NOT CLICK on Remove.

Once you're mailbox is disconnected, run the following command and then use the disconnected mailbox tab in EMC to find the mailbox and reconnect it.

Get-MailboxDatabase | Clean-MailboxDatabase.

Regards,
Exchange_Geek
0
 

Author Comment

by:Enfostrad
ID: 38333339
That gives me the same issue.  I did however, delete one account and re-created it adn the mailbox.  That person worked.
0
 
LVL 33

Expert Comment

by:Exchange_Geek
ID: 38333343
Disabling and reconnecting should do the same stuff, however if recreating does the trick - here is what you need to do

Get-Mailbox | FL >>Mbx.csv

The above cmdlet would capture all the mailbox level settings of each user

Next, export the PST of the users whom you are recreating using the cmdlet

New-MailboxExportRequest -Mailbox user -FilePath D:\PST\UserName.pst

Once the mailbox is exported - go ahead and recreate the mailbox and use the following command to import PST

New-MailboxImportRequest -Mailbox user -FilePath D:\PST\UserName.pst

Simple.

Regards,
Exchange_Geek
0
 

Author Comment

by:Enfostrad
ID: 38333348
Since no one has any mail on the server yet... Thank god.... I can avoid most of the above work.  I do not believe I will have any issues with their local profiles on their computers as long as the username is the same.

Thanks
0
 
LVL 33

Expert Comment

by:Exchange_Geek
ID: 38333350
Perfect, you're good to go. Had an interesting weekend - didnt you?

LOL

Regards,
Exchange_Geek
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 38333899
One other thing to check is that Permission Inheritance is configured correctly.
In ADUC, check that inheritance is enabled on the Security tab under Advanced Permissions.

Simon.
0
 

Accepted Solution

by:
Enfostrad earned 0 total points
ID: 38334476
I figured it out.  Previous Admin set everyone's  logon restrictions to their PC only.  I added the exchange server to their list of computers they can logon to and it works!!!

Thanks all
0
 

Author Closing Comment

by:Enfostrad
ID: 38353484
I figured it out on my own.  I was reviewing everything the admin told me and it struck me that he had mentioned the logon restrictions.  I tested it and I was right, they needed the exchange server added to their list as well.
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

High user turnover can cause old/redundant user data to consume valuable space. UserResourceCleanup was developed to address this by automatically deleting user folders when the user account is deleted.
Here in this article, you will get a step by step guidance on how to restore an Exchange database to a recovery database. Get a brief on Recovery Database and how it can be used to restore Exchange database in this section!
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…
Suggested Courses

862 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question