5.4.4 Action to take when automatic notification from ID-management relay computer is delayed
If a computer changes its route while automatic notification from an ID-management relay computer is being delayed, the computer might not be deregistered from its ID group. The following describes how to work around this issue. Here, a managing server or management relay server that creates ID groups and manages ID-management relay computers is called the manager managing the ID group.
Action to take when a computer is not de-registered from ID groups
If a computer changes its route to the manager managing the ID group while an ID group deregistration notification from the ID-management relay computer is delayed, the computer will not be deregistered 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 12.2.1 Registering a managed computer in an ID group.
-
In Remote Install 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.