Exchange 2007 OWA - Problem access to other mailbox

Exchange 2000

    Sponsored Links

    Next

  • 1. E2K7 Why is mailboxdatabase property "Mounted" always null?
    If I use get-mailboxdatabase to retrieve the properties of a db, the "Mounted" property is alwas null. I've tried using different DCs, and running the command locally from the mailbox server and it's always the same - no value is returned for that property.
  • 2. seemingly simple question: Customized Signature in MS Outlook 2007
    Good morning, All! We have a client (SBS2003 / MS Office 2007 running on Windows XP SP3 machines) who has a request that we provide a customized signature that pulls specific information from AD (First Name, Last Name, Company, Address, Title, image) so that everyone in the office will have essentially the same signature in e-mail. Essentially, that signature would look something like this Cary Shultz MyWidgets, Inc. 123 Main Street Anytown, VA 24000 Tel: 540.555.1212 insert company .jpeg here This is becoming a bit more challenging than I thought it might be. Does anyone know of a way to accomplish this? We would like to avoid purchasing a third-party application if possible (but, can anyone recommend one - just in case?). I have included several news groups (SBS, AD, GPO, Exchange) in this same post..... Thanks everyone!
  • 3. Exchange 2003 DSACCESS
    Hi, Does some one know any utility to reset exchange 2003 DSAccess (point exchange to another GC) without rebooting the server when GC that exchange looking up to becomes unavailable? Thank you in advance.
  • 4. Can RSGs mount dbases from other Exchange servers in other ADs?
    Hello, Need some advice about reconnecting mailboxes in the Exchange 2003 RSG. Say we have the following: - Exchange server "A" in Active Directory "Black"; - Exchange server "B" in Active Directory "White". Both run Exchange 2003 SP2 in physically separate networks with no interconnection. Can we take a physical copy of the mailbox database from B, mount it to the RSG in A, and connect its mailboxes to mailbox-enabled users in Black? We need to do this for a migration. The B/White environment will only be used to migrate messages from a copy of another mailsystem; we can't migrate directly to A/Black because of performance issues on the source. We're worried that the database or user mailboxes might contain signatures or SIDs linking them to a specific AD. The alternative is to export PSTs in B and import into A but we're talking about a few thousand mailboxes, although not at once. Thanks, - Alan.

Exchange 2007 OWA - Problem access to other mailbox

Postby aGlpdHN1 » Sat, 17 Nov 2007 01:38:09 GMT

Have I any other way give access to other mailboxes via OWA than granting to 
users full access with Add-MailboxPermission cmdlet. 

We have a lot of shared mailboxes and many users read them, sometimes users 
should have to access them via OWA.

I wonder, what really mean Add-MailboxPermission cmdlet's AccessRights 
parameters? Example: Change-Permission?

Exchange 2007 is a new mailsystem for us and we decided to not use PFs.

Similar Threads:

1.OWA users able to access others mailboxes

2.Allowing others access to mailboxes in Exchange 2000

Hi there, just done the swap from SBS 4.5 to 2000 and am configuring
Exchange!  I have just one query - in Ex5.5 we had additional users for some
mailboxes, set up using exchange administrator on the Permissions tab of the
Recipient properites box.  Is there a similar way in 2000 to allow somebody
who isn't the owner of a mailbox to have full permission?


3.Upgrading to Exchange 2007, problems with accessing via OWA - from outside the network

Hello,

I have just finished installing exchange 2007 and successfully moved a
user mail box for testing purposes.  My original mail server which
still stand is a 2003 exchange.  The user mail box which has been
moved can send/receive email internally and to external sites. I can
access the mail from from the LAN, however, I cannot access this mail
box via OWA.

Could someone please let me know how I can proceed to deal with this
issue?  What I was thinking is to do the following.

1. Setup a new DNS entry eg, mail2.company.com and point it to a
public ip address which forwards the email to my internal server, new
exchange 2007

2.set up the router to accept an incoming request on a diff port eg,
10000 and forward that port to the new exchange server.

I believe there should be an easier way to deal with this issue.
Please advise.

4.2007 OWA - some users can connect, others can't

we have exchange 2007 sp1

i can login to OWA as can 1 other user.  other users with OWA enabled can 
not.  they get 'user name and password that you entered in not valid.'.  i 
know the passwords are correct.  i've been trying on the same computer so the 
environment is the same.

i have confirmed that OWA is enabled for those users in EMS.

any ideas?
thanks in advance

5.Exchange 2007 - Migrated Mailboxes Cannot Access OWA

I'm rolling out a new Exchange 2007 in the same domain as one where my
Exchange 2003 server exists.  One problem I'm having with my pilot
migration group is that the users moved from Exchange 2003 to Exchange
2007 cannot use OWA.  They get the following error:

---

Exception
Exception type:
Microsoft.Exchange.Data.Storage.StoragePermanentException
Exception message: There was a problem accessing Active Directory.

Call stack

Microsoft.Exchange.Data.Storage.ExchangePrincipal.Save()
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchLanguagePostLocally(OwaContext
owaContext, OwaIdentity logonIdentity, CultureInfo culture, String
timeZoneKeyName, Boolean isOptimized)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchLanguagePostRequest(OwaContext
owaContext)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.PrepareRequestWithoutSession(OwaContext
owaContext, UserContextCookie userContextCookie)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.InternalDispatchRequest(OwaContext
owaContext)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchRequest(OwaContext
owaContext)
System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
completedSynchronously)

Inner Exception
Exception type: Microsoft.Exchange.Data.Directory.ADOperationException
Exception message: Active Directory operation failed on (domain
controller) This error is not retriable. Additional information:
Insufficient access rights to perform the operation. Active directory
response: 00002098: SecErr: DSID-03150A45, problem 4003
(INSUFF_ACCESS_RIGHTS), data 0

Call stack

Microsoft.Exchange.Data.Directory.ADSession.AnalyzeDirectoryError(PooledLdapConnection
connection, DirectoryRequest request, DirectoryException de, Int32&
retries, Int32 maxRetries)
Microsoft.Exchange.Data.Directory.ADSession.ExecuteModificationRequest(ADRawEntry
entry, DirectoryRequest request, ADObjectId originalId)
Microsoft.Exchange.Data.Directory.ADSession.Save(ADObject
instanceToSave, IEnumerable`1 properties)
Microsoft.Exchange.Data.Storage.ExchangePrincipal.Save()

Inner Exception
Exception type:
System.DirectoryServices.Protocols.DirectoryOperationException
Exception message: The user has insufficient access rights.

Call stack

System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32
messageId, LdapOperation operation, ResultAll resultType, TimeSpan
requestTimeOut, Boolean exceptionOnTimeOut)
System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest
request, TimeSpan requestTimeout)
Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest
request, LdapOperation ldapOperation)
Microsoft.Exchange.Data.Directory.ADSession.ExecuteModificationRequest(ADRawEntry
entry, DirectoryRequest request, ADObjectId originalId)

----

A mailbox created on the Exchange 2007 server has no problem at all.
I compared the permissions of both mailboxes, and there are no
differences at all.  Both are user mailboxes, in the same ou, etc.  I
imagine the problem may be buried deeper in AD in a not-so-obvious
place.  Some of the users I've migrated are seen as "Linked
Mailboxes", but I suppose that is from having an "Associated External
Account" as a legacy setting from when we had another domain.  Still,
the behavior is consistent between both mailbox types.

It'd be nice to be able to migrate users and have them access OWA.

Pete

6. Can't access Exchange 2003 BE mailboxes from OWA 2007 on CAS s

7. Can't access Exchange 2003 BE mailboxes from OWA 2007 on CAS serve

8. Log access to others mailboxes



Return to Exchange 2000

 

Who is online

Users browsing this forum: No registered users and 19 guest