none
processing folder id is not giving correct owner name RRS feed

  • Question

  • I have addin developed for outlook 2010. on some event i get the store id of the folder, which I believe addin is getting from exchange as exchange store folders information,Now from folder id I try to convert the user information by converting hexadecimal string into a string, as expected its giving me information in the format.

    from here i can grab the user name and can do my operation, this works well in out environment and some of the clients as well.  for one of the client the user name is coming differently. 

    the actual user name who is having this issue is Pawan Gupta, but processing folder id is giving UKPGC as user name, to investigate it further they have given this reply.

    globally we have a concept of Concern Wide ID – you are assigned this on joining and it stays with you forever. This includes it being the most distinguished part of the CN of your AD account (which is where Exchange will be pulling info from eventually) and your ‘pre Windows 2000 Login’ ..  Most of our users  will login in DOMAIN\CWID manner, NTLM style login so if there is a local query on an env variable, or if the LDAP query is something other than ‘email address’ field of the AD it’ll likely get the 5 char accout name rather than the email address. ‘User Logon name’ should also return pl.gi@xyz.com in this instance.

    I am not a exchange expert, so do not know what exactly they are doing and what information is missing in AD account of above specified user and wht they should put instead. Please let me know if this is some limitation of using folder id to get the owner/displayname of the folder.

    Thanks

    Nitin

    Wednesday, July 16, 2014 12:05 PM

Answers

  • It should work fine as the X500 address will be resolved to the user object, you can think of it as just another unique alias for the user. You need to use whole string the UKPGC part won't work by itself that's just the common name given to the user.

    Cheers
    Glen

    • Marked as answer by Nitrup Friday, July 18, 2014 9:11 AM
    Friday, July 18, 2014 6:17 AM

All replies

  • There is nothing missing from the AD Account and the method that particular company is using is completely valid. The problem is the method your using would never be guaranteed to give you the username, what it will give you is the X500/legacyexchangedn address of the account. Usually by default the CN of AD object would be the username but its doesn't have to be and for many reasons companies will choose to configure it differently (eg even simple things like somebody getting married and changing there surname can result in things being different).

    In the Outlook OOM you should just be able to resolve the legacyexchangedn with the AddressEntry interface http://msdn.microsoft.com/en-us/library/office/microsoft.office.interop.outlook.addressentry(v=office.15).aspx and then grab the username with http://msdn.microsoft.com/en-us/library/office/ff184599(v=office.15).aspx

    Cheers
    Glen

    Thursday, July 17, 2014 5:08 AM
  • Thanks for the help Glen, so you mean to say if instead of user name , I give X500/legacyexchangedn address as it is (like i am getting in my scenario) and then create a address entry object from it and then try to resolve it and i will get the user name or smtp address from it and it will not matter whether i am greeting exact user name in X500/legacyexchangedn or not

    what I tried already is that I tried to create a recipient object from the the  X500/legacyexchangedn address string I am getting and then tried to resolve it, it worked for me i mean in our environment,

    but i am not sure if using this string will work

    As I already explained UKPGC is not user name.

    Thanks once again :)

    Thursday, July 17, 2014 9:19 AM
  • It should work fine as the X500 address will be resolved to the user object, you can think of it as just another unique alias for the user. You need to use whole string the UKPGC part won't work by itself that's just the common name given to the user.

    Cheers
    Glen

    • Marked as answer by Nitrup Friday, July 18, 2014 9:11 AM
    Friday, July 18, 2014 6:17 AM
  • Many thanks for confirming, i will try if i got a chance to test this on client machine. 
    Friday, July 18, 2014 9:11 AM