you can also get into engineering mode, go to storage group properties, Hosts , Advanced and put a check mark next to the new path.
Hello everyone,  I am working on migrating some ESX clusters connected to a VNX5700 (Unified), to a new VSAN on our Cisco switches.  So, when I move the ESX paths to a new VSAN they automatically pop up and auto register in the VNX. That is all fine and dandy, but the problem is that they join the "~management" storage group, instead of the storage group that the host is in.  So for clarification, lets say we have host esx_host_01p that is joined to storage group named esx_host_01p_sg. When I move the path to a new VSAN, we get a new initiator, and that initiator auto registers with the same host (esx_host_01p), but it does not join the storage group (esx_host_01p_sg), instead it appears in ~management.  Our current solution to fix this is to put the ESX host into maintenance mode, remove the host from the storage group, apply the change, then rejoin the host to the storage group and reboot the ESX host. Then the new initiator works as expected.  Is there any way to get these new initiators to be recognized by the host/storage group, without having to reboot the ESX host and remove/rejoin the host to the SG?  Any help would be appreciated. 
New ESX host initiators do not join the hosts storage group?