You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I added a tag for ADUGroup to my edge device in the Device Twin and in the IoTHubDeviceUpdate module Twin (because it was not clear to me to which I had to):
'tags': {
'ADUGroup': 'gerryTest'
}
When I try to create a Group in Device Updates - Groups the tag is not present, in fact NO TAGS are available in the drop down at all.
UPDATE:
I tried using the "Deploy to Azure" Button and it worked!!, after I checked what was the difference, I noticed that the template used for creating the VM has these commands:
I believe the trick is done by restart adu-agent before tag the device! that instruction is not referenced in the manually procedure, please confirm, if it is the case please add to the documentation
The text was updated successfully, but these errors were encountered:
Using 0.8.0 release and connecting as module from my host, can't for the life of me get the ADUGroup tag to trigger any changes in the "Create Group" dropdown in IoTHub portal.....
This just in, the IoTHub portal just received an update! I see some new user interface and tags!
Yes, the agent needs to connect before setting the ADUGroup tag.
Can set ADUGroup to null in the twin and then restart via sudo systemctl restart adu-agent to resolve it.
Once you see it is connected in the twin, then add the ADUGroup tag.
Then you should be able to see the group available when adding a group.
@esha0611 Could you include this in relevant ms docs? I'll update the .md
I followed this procedure I manually prepared my VM
I added a tag for ADUGroup to my edge device in the Device Twin and in the IoTHubDeviceUpdate module Twin (because it was not clear to me to which I had to):
'tags': {
'ADUGroup': 'gerryTest'
}
When I try to create a Group in Device Updates - Groups the tag is not present, in fact NO TAGS are available in the drop down at all.
UPDATE:
I tried using the "Deploy to Azure" Button and it worked!!, after I checked what was the difference, I noticed that the template used for creating the VM has these commands:
I believe the trick is done by restart adu-agent before tag the device! that instruction is not referenced in the manually procedure, please confirm, if it is the case please add to the documentation
The text was updated successfully, but these errors were encountered: