Lets say I have 3 remote offices A, B and C. I have an IP scope for remote office A and B, remote office C is left for special needs computers that will have all different IP addresses. I manually add computers from both remote office A and B into the remote office of C. I need different patching configs at each location but when the IP scope refreshes it is pulling the computers out of the remote office C location and placing them back into the remote offices that the IP address match. I do not want to assign static IP addresses to the special needs computers to keep them from being added back into the respective scopes. How can I set up a policy within endpoint central to allow me to have a location with mixed IP addresses from other remote offices and them not be moved back into the remote office containers with the IP scope they match?  I have went over this with the chat agent and was told it is not possible. I do not think this is uncommon and wondered if anyone has some sort of work around for this situation?

End goal is to have some random computers placed into a group that will be given the option to postpone reboot after patching is completed and have the others force reboot.