We assign/link snapins to hosts and once they are deployed they no longer appear to be assigned. Is that the expected behavior?
We had hoped that they would stay assigned for future use.
The snapin was saved a week ago. After the rename it appears to have become unassigned from the machines. The snapin is still there.
renaming a snapin should not break it’s association. more likely, an invalid setting was in a field and the snapin didn’t save.
Helpdesk team reported the issue wrong.
They renamed the snapin, and that caused it to disappear. Ideally, that would not break the association. They had thought a guid or something like that was used, but that might not be the case.
We are looking at each host. They assign fine, but disappear once they are applied.
This is based on the claims of my helpdesk team. I am looking into it.
that is not the expected behavior. are you looking for snapins on a per host or group basis? groups do not show what snapins are assigned to the members of the group, but individual hosts do.
Wayne Workman last edited by