5.4.4 Action to take when automatic notification from relays managing IDs is delayed
If automatic notification from relays managing IDs is delayed, a computer might not be automatically de-registered from its ID groups when a change is made to its route. The following describes how to work around this issue. Here, the managing server that creates the ID group and manages the relay managing the ID is called the manager managing the ID group.
Action to take when a computer is not de-registered from ID groups
The notification de-registering a computer from an ID group might not have arrived from the relay managing the ID by the time the computer changes its route to the manager managing the ID group. In this case, the computer will not be de-registered from the ID group. You can use one of the following approaches to work around this problem:
-
Perform de-registration again from the computer that was not de-registered from the ID group
For details about how to de-register a computer from an ID group, see 11.2.1 Registering a managed computer in an ID group.
-
In Remote Installation Manager on the manager managing the ID group, delete the ID group registration information for the computer
For details about how to delete a computer from an ID group, see 5.3.4(3) Removing computers from ID groups.
- Note:
-
You can prevent this issue altogether by not de-registering computers from ID groups immediately before changing routes. After changing the route, make sure that the computer has been successfully de-registered from the ID groups.