Solved

Determine Outlook web address URLs from Username

Posted on 2009-05-20
15
841 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
Get proactive database performance tuning online

At Percona’s web store you can order full Percona Database Performance Audit in minutes. Find out the health of your database, and how to improve it. Pay online with a credit card. Improve your database performance now!

 
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

Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

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

This post contains step-by-step instructions for setting up alerting in Percona Monitoring and Management (PMM) using Grafana.
A couple of months ago we ran into an issue that necessitated re-creating our Edge Subscriptions. However, when we attempted to execute the command: New-EdgeSubscription -filename C:\NewEdgeSub_01.xml we received an error indicating that the LDAP se…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…
This is a high-level webinar that covers the history of enterprise open source database use. It addresses both the advantages companies see in using open source database technologies, as well as the fears and reservations they might have. In this…

627 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