Databases
StackOverflow2013
Postsdbo
POConvert GUID string to octetBytes using PowerShell
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POConvert GUID string to octetBytes using PowerShell
    primarykey
    data
    text
    <p>I have a powershell script which outputs all Exchange 2003 mailboxes by size.</p> <pre><code>$computers = "vexch01","vexch02" foreach ($computer in $computers) { Get-Wmiobject -namespace root\MicrosoftExchangeV2 -class Exchange_Mailbox -computer $computer | sort-object -desc Size | select-object MailboxDisplayName,StoreName,@{Name="Size/Mb";Expression={[math]::round(($_.Size / 1024),2)}}, MailboxGUID | Export-Csv -notype -Path $computer.csv } </code></pre> <p>Currently this outputs the MailboxGUID as a string type GUID (e.g. {21EC2020-3AEA-1069-A2DD-08002B30309D}). I want to look up users in AD by this, but AD stores them in octetBytes format.</p> <p>I have found some <a href="http://www.leadfollowmove.com/archives/powershell/converting-a-guid-string-to-octet-string" rel="nofollow">powershell functions</a> which will do the conversion but only when the curly braces are removed. The <a href="http://msdn.microsoft.com/en-us/library/560tzess.aspx" rel="nofollow">Guid.ToString</a> method should supply this, but I can't get it to work in the above. </p> <p>However, if I could figure out how to do that, the <a href="http://msdn.microsoft.com/en-us/library/system.guid.tobytearray.aspx" rel="nofollow">Guid.ToByteArray</a> method might get me even closer.</p> <p>Has anyone cracked this?</p> <p>Update: the answers so far helped me write a function that converts the mailboxguid into the correct format for searching via LDAP. However, I now cannot get this working in the script. This is my updated script:</p> <pre><code>function ConvertGuidToLdapSearchString( [parameter(mandatory=$true, position=0)]$Guid ) { $guid_object = [System.Guid]$Guid ($guid_object.ToByteArray() | foreach { '\' + $_.ToString('x2') }) -join '' } # Gets data through WMI from specified Exchange mailbox servers $servers = "vexch01","vexch02" foreach ($server in $servers) { Get-Wmiobject -namespace root\MicrosoftExchangeV2 -class Exchange_Mailbox -computer $computer | sort-object -desc Size | select-object MailboxDisplayName,StoreName,@{Name="Size/Mb";Expression={[math]::round(($_.Size / 1024),2)}}, @{Name="LDAP Guid";Expression={ConvertGuidToLdapSearchString(MailboxGUID)}} | Export-Csv -notype -Path $server.csv } </code></pre> <p>I'm not sure why using the function in the <code>select-object</code> with <code>@{Name="LDAP Guid";Expression={ConvertGuidToLdapSearchString(MailboxGUID)}}</code> doesn't work.</p> <p>Is there another way of using this function in <code>select-object</code> that will give the string?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USdunxd
    1. USdunxd
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POConvert GUID string to octetBytes using PowerShell
      1. USdunxd
      1. VTFavorite
    2. VO
      singulars
      1. POConvert GUID string to octetBytes using PowerShell
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI updated my answer with more information.
      singulars
      1. POConvert GUID string to octetBytes using PowerShell
      1. USOldFart
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload