• State Verified Answer
  • Locked Locked
  • Replies 13 replies
  • Subscribers 63 subscribers
  • Views 23111 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Get-QADUser -IncludedProperties 'attribute' returning a different value than if using -IncludeAllProperties

Jacob R
over 6 years ago

Hello all,

 

I am having some trouble returning a value using Get-QADUser and the -IncludedProperties switch. It seems that there is a difference in the value returned if using the -IncludeAllProperties switch.

In my example this is my difference:

Get-QADUser "domain\user123" -IncludedProperties "edsva-msexch-protocolsettings-owa-enable"

And return:

edsva-msexch-protocolsettings-owa-enable                   : True

 

However, if I run this:

Get-QADUser "domain\user123" -IncludeAllProperties

I return: 

edsva-msexch-protocolsettings-owa-enable                         : False

 

The IncludeAllProperties switch returns the correct value that is stored in ARS while the IncludedProperties returns the incorrect value. Does anyone know why this may be happening? I would like to be able to query an account without using the IncludeAllProperties switch as it takes much longer to gather all of the information.

 

Any help is greatly appreciated!

Jacob

  • +1 over 6 years ago

    In my test lab the output works as expected with the PowerShell Commandlet, unlike how it works in your environment the values always match in mine.

    Have you tried using the ADSI Object to see if the Calculation comes up with a different result.

    $objUser = [adsi]"EDMS://DNofUser"

    $objUser.RefreshCache('edsva-msexch-protocolsettings-owa-enable')

    $objUser.'edsva-msexch-protocolsettings-owa-enable'

  • 0 over 6 years ago

    That is very strange that the output is different in your test lab however ADSI did work!
    When I use the code below all of the values output as intended:

    $UserInfo = (Get-QADUser domain\user123)
    $userpath = (Get-QADUser domain\user123).path

    $objUser = [adsi]"$userpath"
    $objUser.RefreshCache('edsva-msexch-protocolsettings-owa-enable')
    $objUser.'edsva-msexch-protocolsettings-owa-enable'

    $objUser.RefreshCache('edsva-msexch-protocolsettings-imap4-enable')
    $objUser.'edsva-msexch-protocolsettings-imap4-enable'

    $objUser.RefreshCache('edsva-msexch-protocolsettings-mapi-enable')
    $objUser.'edsva-msexch-protocolsettings-mapi-enable'

    $objUser.RefreshCache('edsva-msexch-protocolsettings-uptodatenotifications-enable')
    $objUser.'edsva-msexch-protocolsettings-uptodatenotifications-enable'

    $objUser.RefreshCache('edsva-msexch-protocolsettings-oma-enable')
    $objUser.'edsva-msexch-protocolsettings-oma-enable'

    $objUser.RefreshCache('edsva-msexch-protocolsettings-pop3-enable')
    $objUser.'edsva-msexch-protocolsettings-pop3-enable'

    $objUser.RefreshCache('edsva-msexch-protocolsettings-activesync-enable')
    $objUser.'edsva-msexch-protocolsettings-activesync-enable'


    Thank you all very much for your assistance!

  • 0 over 5 years ago

    I know it's already solved with a workaround but I guess the issue itself is related to the behaviour descriped here: support.oneidentity.com/.../activesync-attribute-always-shows-as-true