none
Identity of "Containing" Public Folder in SearchServer 2010 RRS feed

All replies

  • I think this is actually a SearchServer question. It connects to the URL of the PFs, yes? I dont think there is anything that can be changed on the Exchange side.

     

    Tuesday, August 16, 2011 7:16 PM
    Moderator
  • It may well be.  I am just trying to find a solution that will allow us to view the "containing" folder identity that we are able to view previously.

    I am leaning to an Exchange question as the index in SSE is provided with the unintelligible (after the /OWA/ at least) URL by Exchange.


    Regards, BIFF
    Tuesday, August 16, 2011 8:16 PM
  • It may well be.  I am just trying to find a solution that will allow us to view the "containing" folder identity that we are able to view previously.

    I am leaning to an Exchange question as the index in SSE is provided with the unintelligible (after the /OWA/ at least) URL by Exchange.


    Regards, BIFF


    If In theory, you should be able to access it with that URL.

    If you go to an item in a pf via OWA and check the properties for the URL, you'll see what is being returned to the SearchServer.

     

    Wednesday, August 17, 2011 12:22 AM
    Moderator
  • AndyD 

    You are likely right and I have not clearly stated what I am trying to accomplish.

    The old SSE2008/Exchange2003 setup provided a URL that the SSE2008 user could use to separately navigate to the containing folder; i.e. the containing folder was denoted in plain english.

    Under the SSE2010/Exchange2010 setup, the URL will take you to the found item but cannot be used to identify the containing folder.

    What I am trying to accomplish is to provide a way for the SSE2010 user to obtain the containing folder path in plain english.  This is important when trying to find lost or misfiled emails or just the folder containing an email conversation.

     


    Regards, BIFF
    Wednesday, August 17, 2011 2:31 PM
  • Hi BIFF,

    In my opinion, it is a SSE2010 issue, per my know, there is no direct way achieve the purpose what you want.
    Or, you could open a ticket from MS to get more help.


    Regards!
    Gavin

    Monday, August 22, 2011 5:28 AM
    Moderator
  • Gavin,

    We have consulted with others who advise that SSE2010 IS returning the URL of THE EMAIL; however, because of the way that Exchange 2010 operates, the URL gives no "containing folder" path information (that is readable by ordinary humans) and hence can not be used to go to the "containing folder".

    Again, the issue is that if are searching for information in Exchange 2010 Public Folders, it is likely that the "containing folder" of the "found" email will contain other relevant emails.  Since we can only read the "found" email and are not provided with a path to navigate to the "containing folder" as was the case in Exchange 2003/SSE2008, we are at a loss.

    If you can advise whether or not the database index for Exchange 2010 stores containing folder information in a file path format, it would be helpful.  Any other direction relative to Exchange 2010 would be welcome also.

    In the alternative, since "found" emails are opened in OWA, if you can advise how the "containing folder" of a "found" email can be identified while viewing the "found" email in OWA, that would solve our problem for the time being.


    Regards, BIFF
    Thursday, September 1, 2011 2:55 AM
  • From the item URL the folder path can be decoded this way. 

    This is an URL that can be a search result: 
    https://exch.contoso.com/OWA/?a=Open&id=PSI.LgAAAAAaRHOQqmYRzZvIAKoAL8RaAwCqHG9DL6%2bpRb4OkIMvHa6YAAAAAAAOAAAB.RgAAAAAaRHOQqmYRzZvIAKoAL8RaCQCqHG9DL6%2bpRb4OkIMvHa6YAAAAAAAOAACqHG9DL6%2bpRb4OkIMvHa6YAAAAAAAdAAAA

    Should separate the first part between the dot (.) characters. 
    LgAAAAAaRHOQqmYRzZvIAKoAL8RaAwCqHG9DL6%2bpRb4OkIMvHa6YAAAAAAAOAAAB

    This is a base64 coded entryID for a folder. Decode it and you will get this: 
    (it may happen you must replace the %2b with a + sign to get this) 
    2E000000001A447390AA6611CD9BC800AA002FC45A0300AA1C6F432FAFA945BE0E90832F1DAE9800000000000E000001

    Should remove the 2E from the beginning and the 01 from the end. 
    Now you get the PR_ENTRYID for the specific Public Folder in hex. 
    000000001A447390AA6611CD9BC800AA002FC45A0300AA1C6F432FAFA945BE0E90832F1DAE9800000000000E0000

    You can list the EntryID for the public folders with this command: 

    Get-PublicFolder –Recurse | Ft –EntryID,Identity –AutoSize

    In this output list should find a match for the above entry ID and then you got the folder path under Identity. 


    MCSE:M 2003, MCITP:EA, SA, EMA, EMA:2010

    Thursday, February 14, 2013 6:31 AM