We use storage array features to clone LUNs and then map these "new" LUNs out again to the same or different hosts. A typical case is when we refresh between environments, so imagine cloning a LUN holding a bunch of VMs from source host TEST1 to destination host TEST2. Sometimes the destination host will assign the drive automatically, and sometimes it won't. The storage array changes the cloned LUN's serial number (but we could modify it back) but for the rest the cloned LUN contents are identical to the source. In the case of a refresh (so in this example remove the old LUN from TEST2 and then map the cloned LUN in it's place) the LUN ID also stays the same. The LUNs are accessed over a Fibre Channel SAN and are thus not seen as removable devices. Needless to say, in the situation here we are not cloning the boot LUN itself either.
I found Microsoft KB234048 describing the behavour with Windows 2000 but I suspect a lot has changed in the last 10 years.
If anyone has details, including special cases like if they are MSCS shared disks, or multiple disks with matching signatures (i.e.cloned disk is maped to same server), please share!