Using Update AD Object when AD attributes have a hyphen in the name
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-08-2022 02:14 PM
Before I write a custom PowerShell script, has any been successful in using the out of the box Update AD Object workflow activity to update an AD attribute in which the name of the AD attribute has hyphens in the name?
For example, an attribute like msRTCSIP-DeploymentLocator?
When I pass an attribute with a hyphen in the name to that workflow activity, the activity fails and the response I get back says "The specified directory service attribute or value does not exist."
I've tried many variations of the object attribute I'm passing to the workflow activity but none have succeeded.
Thanks,
Michael Domke
- Labels:
-
Orchestration (ITOM)

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-09-2022 05:54 PM
Hi
My apologies if none of my replies are helpful to you.
My first reply was to hopefully see if it'd try and work with out of box actions, etc. using square bracket notation and all that (since you didn't provide any actual examples of what you've tried thus far). Square bracket notation and double quotes is how it's also recommended for people to write it in PowerShell scripts anyway.
My second reply was to just show you that hyphenated objects don't work well/at all with out of box actions (so this would just confirm that and help you not waste time further trying to get it to work -- even though I wanted to try initially anyway -- as things can change/newer support, etc.) and then yes, the final outcome being...for more "complex" needs, hyphenated seems to count as complex here, that you'd have to script it i.e. PowerShell.
In any case, that's about it.
Take care!
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-09-2022 07:19 PM
I truly appreciate all the comments/interactions. Many thanks for that. I went the PowerShell route and all works great!
Michael