Compellent/Hyper-V: Trying to follow best practices

Windows 2016/Hyper-V/SC4020

I'm setting up two new Windows 2016 Hyper-V hosts.  So, I am trying to follow the instructions in "Dell EMC SC Series Storage: Microsoft Multipath I/O".  Section 5.1.2 says you should associate the SC Volumes to the DSM, by doing this:

New-MSDSMSupportedHW –VendorID "COMPELNT" –ProductID "Compellent Vol"

No problem with that - this works fine.  But then it says to "claim all available SC volumes by doing this:

Update-MPIOClaimedHW –Confirm:$false 

This causes the Powershell window to hang, and all of the iSCSI connections to immediately go to Inactive.  Rebooting the server (which also seems to hang, and I have to power cycle the server) resolves the problem.

So, my two questions are, is this normal? 

Second, this paper that I refer to says it's important to claim the volumes, but doesn't seem to explain how to verify if the volumes are claimed, and how I can be sure that when later on I add a new compellent volume, how it also gets claimed.  On my system, when I run "GetMSDSMAutomaticClaimSettings" it says "false", so presumably new volumes aren't getting claimed.

Right now, I see the volumes attached to my servers, and they aren't duplicated, so it looks like MPIO is working.  I am unsure what to look for and unsure if I am still missing one of the instructions here.