Solved

Determine Outlook web address URLs from Username

Posted on 2009-05-20
15
837 Views
Last Modified: 2013-12-24
I need to guess the URL to folders in a user's Outlook Web Access given info about the user from Active Diredtory via LDAP.
This sounds simple at first, as it should be
https://(servername)/exchange/(username)/(foldername)
However, I seem to be unable to determine the really working username.
My best guess so far has been the part after "cn=" of the LDAP attribute "legacyExchangeDN".
But I do have a few users where this fails.
These seem to suggest that I should extract the username form some "proxyAdresses", but this does not work relyably for everyone, either.
There must be a "right" thing to do it, I hope!?
0
Comment
Question by:thehagman
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 7
  • 3
15 Comments
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 24430501
last part of LegacyExchangeDN is the MailNickName attribute and not proxyaddress.
0
 
LVL 20

Author Comment

by:thehagman
ID: 24431421
Sorry to correct: I *do* have entries with
mailNickname != last part of legacyExchangeDN
and more to the point, neither
https://(servername)/exchange/(mailNickname)/(foldername)
nor
https://(servername)/exchange/(last part of legacyExchangeDN)/(foldername)
are always suitable URLs for my intended purpose.
I have a user with the following anonymized output from ldapsearch:

# Wyyy Sxxxx, Bbbb, Benutzer, zzzzzzz.local
dn: CN=Wyyy Sxxxx,OU=Bbbb,OU=Benutzer,DC=zzzzzzz,DC=local
initials: WLZ
displayName: Wyyy, Sxxxx
proxyAddresses: x400:c=DE;a= ;p=ZZZZ;o=Bbbb;s=Wyyy;g=Sxxxx;
proxyAddresses: smtp:wyyy@bbbb.zzzzzzz.de
proxyAddresses: X400:c=DE;a= ;p=ZZZZ;o=Bbbb;s=Wyyy;g=Sxxxx;i=WLZ;
proxyAddresses: smtp:Sxxxx.Wyyy@zzzzzzz.de
proxyAddresses: SMTP:wyyy@zzzzzzz.de
mailNickname: wyyy
sAMAccountName: Wyyy
legacyExchangeDN: /o=ZZZZ/ou=Bbbb/cn=Recipients/cn=swyyy

For this user
https://(servername)/exchange/wyyy/(foldername)  does not work
https://(servername)/exchange/swyyy/(foldername)  does not work
https://(servername)/exchange/Sxxxx.Wyyy/(foldername)  works



0
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 24431465
for OWA we would require the Displayname after the
https://(servername)/exchange/Sxxxx.Wyyy/(foldername)
for eg Sxxxx.Wyyy is the display name
0
Edgartown IT Case Study

Learn about Edgartown's quest to ensure the safety and security of the entire town's employee and citizen data. Read the case study!

 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 24441532
If the issue is resolved can close the issue and distribute the points...... :-)
0
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 24448172
Any updates ?
0
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 24465079
Any updates on the issue ?
0
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 24480882
Any updates on the issue ?
0
 
LVL 20

Author Comment

by:thehagman
ID: 24482077
Sorry for being away for a while.
While Rancy is correct that the URL
https://(servername)/exchange/Sxxxx.Wyyy/(foldername)
works, it should be mentioned that "Sxxxx.Wyyy" is not the displayName - the displayName is "Wyyy, Sxxxx".
Also, replacing "foo, bar" with "bar.foo" seems not to work in 100% of all cases (not to mention problems with possible special chars in the parts or what to do if displayName has no comma).
Hence the riddle is still unsolved - given complete LDAP info, determine tha name üpart of the OWA URL
0
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 24482380
Could you please be more informative as to what works and what does not and ideally i havn't seen user name having "Special Characteristics" in them as it causes a lot of problems at times.
0
 
LVL 20

Author Comment

by:thehagman
ID: 24496591
The problem is that *I* cannot find *any* LDAP attribute that works 100%, but I hoped that *someone* had to know - after all I do not expect the OWA server to perform magic, but rather follow some obscure algorithm. Could there be something like a "hidden" LDAP attribute?

The example in post #24431421 essentially listed my poor attempts to guess what could work - from using OWA under a few user accounts and checking what the URLs look like: mailNickname, samAccountname and the last part of legacyExchangeDN *seemed* to be better and better approximations aof the real target. However, for that specific user only *a* (but which a priori?) proxyAddress seemes to match (as found by ldapserach | grep Sxxx.Wyyy). Unfortunately, it turned out that neither the first listed procxyaddress (of type smtp) nor the main (i.e. SMTP) address worked. In other words, I'm at a loss ...
0
 

Accepted Solution

by:
ee_auto earned 0 total points
ID: 25503101
Question PAQ'd, 500 points refunded, and stored in the solution database.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
This article describes how to import an Outlook PST file to Office 365 using a third party product to avoid Microsoft's Azure command line tool, saving you time.
Video by: Steve
Using examples as well as descriptions, step through each of the common simple join types, explaining differences in syntax, differences in expected outputs and showing how the queries run along with the actual outputs based upon a simple set of dem…
This Experts Exchange video Micro Tutorial shows how to tell Microsoft Office that a word is NOT spelled correctly. Microsoft Office has a built-in, main dictionary that is shared by Office apps, including Excel, Outlook, PowerPoint, and Word. When …

738 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