Ediscovery using GUID

%3CLINGO-SUB%20id%3D%22lingo-sub-983349%22%20slang%3D%22en-US%22%3EEdiscovery%20using%20GUID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-983349%22%20slang%3D%22en-US%22%3E%3CP%3EI%20want%20to%20identify%20a%20user%20via%20the%20GUID.%20My%20data%20has%20duplicate%20usernames%2C%20the%20only%20thing%20I%20can%20use%20to%20separate%20them%20is%20the%20GUID.%20How%20can%20I%20use%20this%20extract%20a%20single%20mailbox%20in%20eDiscovery%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-983349%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECompliance%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-983693%22%20slang%3D%22en-US%22%3ERe%3A%20Ediscovery%20using%20GUID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-983693%22%20slang%3D%22en-US%22%3E%3CP%3EDepends%20on%20where%20you%20are%20trying%20to%20perform%20this.%20The%20old-style%20Exchange%20content%20search%2FeDiscovery%20should%20accept%20the%20Exchange%20GUID.%20The%20new-style%20(the%20one%20in%20the%20SCC)%20does%20not%20accept%20the%20GUID%20in%20the%20UI.%20And%20in%20PowerShell%2C%20it%20only%20seems%20to%20accept%20the%26nbsp%3B%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3EExternalDirectoryObjectId%20identifier%2C%20not%20the%20actual%20GUID%20from%20Exchange.%20THis%20does%20seem%20like%20a%20bug%20or%20somethng%20they%20overlooked%20to%20me%2C%20so%20I'll%20try%20pinging%20few%20folks%20while%20we're%20here%20at%20Ignite%20and%20report%20back.%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1033105%22%20slang%3D%22en-US%22%3ERe%3A%20Ediscovery%20using%20GUID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1033105%22%20slang%3D%22en-US%22%3EHi%2C%3CBR%20%2F%3EI'm%20guessing%20you%20had%20no%20favourable%20responses.%20thanks%20for%20trying%20though.%3CBR%20%2F%3EI'll%20remain%20hopeful%20that%20this%20gets%20sorted%20in%20future%20upgrades.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1039241%22%20slang%3D%22en-US%22%3ERe%3A%20Ediscovery%20using%20GUID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1039241%22%20slang%3D%22en-US%22%3E%3CP%3EI%20did%20speak%20to%20few%20folks%20about%20it%2C%20they%20promised%20to%20take%20a%20look%20and%20get%20back%20to%20me....%20and%20crickets%20%3A)%3C%2Fimg%3E%20I'll%20try%20pinging%20them%20again%2C%20in%20the%20meantime%20simply%20use%20the%20ExternalDirectoryObjectID%20instead.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

I want to identify a user via the GUID. My data has duplicate usernames, the only thing I can use to separate them is the GUID. How can I use this extract a single mailbox in eDiscovery?

3 Replies
Highlighted

Depends on where you are trying to perform this. The old-style Exchange content search/eDiscovery should accept the Exchange GUID. The new-style (the one in the SCC) does not accept the GUID in the UI. And in PowerShell, it only seems to accept the ExternalDirectoryObjectId identifier, not the actual GUID from Exchange. THis does seem like a bug or somethng they overlooked to me, so I'll try pinging few folks while we're here at Ignite and report back.

Highlighted
Hi,
I'm guessing you had no favourable responses. thanks for trying though.
I'll remain hopeful that this gets sorted in future upgrades.
Highlighted

I did speak to few folks about it, they promised to take a look and get back to me.... and crickets :) I'll try pinging them again, in the meantime simply use the ExternalDirectoryObjectID instead.