Unknown - Jan 6, 2015
not sure if anyone is still looking at this but i have a question that seems simple but its puzzling me!
I am trying to follow the instructions to convert a GUID into a string. I have done this:
Which you can do with this one line of PowerShell script
Suppose I generate a GUID of 8c4ac332-975f-4717-ad7b-ba4a4e968fff by running the following PowerShell Command line
[system.guid]::newguid()
Don’t worry if your GUID is different from mine; it should be! If it isn’t let me know because I think I’ll partner with you for the lottery (aka a tax on the mathematically impaired).
Some attributes (like the attributeSecurityGUID) when edited through ADSI Edit require you to convert the GUID to octet string (for little endian systems – Intel processors are little endian): 32c34a8c5f971747ad7bba4a4e968fff
While using FIM and PowerShell to manage Exchange 2010 I was following along a wonderful article on resource mailboxes that left me wondering a few things.
Exactly how is the data stored in the msExchResourceDisplay and msExchResourceSearchProperties attributes?
How is it stored with multiple custom properties?
Is manipulating those AD attributes sufficient or is PowerShell storing something in the Exchange Data store?
Here are the answers:
msExchResourceSearchProperties at first blush appears to be a single-valued string with semi-colons, however further examination reveals it to be a multi-valued attribute
