So Virtual Desktop Infrastructure (VDI) - Windows 10 Fun!

[Melbosa]

NAIT is heavily into VDI deployments now with our class load, and we've been at it since Windows 7 SP1 release days.  But something happened today in a Computer Engineering course that I didn't think a person would do, and something I have to now correct to stop from every happening again.

Check out the screen shot and see what you think they did.

[Mr. Analog]

OMG that's frickin' HILARIOUS

Of course they are a Lab User aka L'ABUSER

[Lazybones]

On one hand it is cool that windows knows the device is hot swappable on the other hand that is really funny.

[Darren Dirt]

Did they add a virtual NIC or something to get past network restrictions?

[Melbosa]

Did they add a virtual NIC or something to get past network restrictions?

Ejected C

[Tom]

I wonder why vmware says to windows that the primary disk is removable? I mean sure, addin drives can be, but you almost never want to eject C lol.

[Melbosa]

I wonder why vmware says to windows that the primary disk is removable? I mean sure, addin drives can be, but you almost never want to eject C lol.

Its an all or nothing to allow Hot Plug of Drives.  VMware presents the SCSI controller as allowing Hot Plug of drives, so therefore any drive attached can be hot removed as well.  You can turn this off either on the VMware side or on the Windows side to prevent this, but then you loose the ability to add drives on the fly.  Actually this isn't limited to Windows OSs, as you could do the same thing on Linux as well.

So on a VDI where you won't do this very often you probably want to follow the suggestions to disable this for the HD and NICs.  On a server where this might be more prudent and also have more experienced people working on them you may not want to implement those changes.

[Tom]

I wonder why vmware says to windows that the primary disk is removable? I mean sure, addin drives can be, but you almost never want to eject C lol.

Its an all or nothing to allow Hot Plug of Drives.  VMware presents the SCSI controller as allowing Hot Plug of drives, so therefore any drive attached can be hot removed as well.  You can turn this off either on the VMware side or on the Windows side to prevent this, but then you loose the ability to add drives on the fly.  Actually this isn't limited to Windows OSs, as you could do the same thing on Linux as well.

So on a VDI where you won't do this very often you probably want to follow the suggestions to disable this for the HD and NICs.  On a server where this might be more prudent and also have more experienced people working on them you may not want to implement those changes.

Sure you can't just add more than one SCSI bus? I'm not to experienced with vmware (anymore). It seems as if kvm has support for a removable flag per block device. Whether it locks a device from being removable, or gives each one its own virtual bus is another story.

[Melbosa]

I wonder why vmware says to windows that the primary disk is removable? I mean sure, addin drives can be, but you almost never want to eject C lol.

Its an all or nothing to allow Hot Plug of Drives.  VMware presents the SCSI controller as allowing Hot Plug of drives, so therefore any drive attached can be hot removed as well.  You can turn this off either on the VMware side or on the Windows side to prevent this, but then you loose the ability to add drives on the fly.  Actually this isn't limited to Windows OSs, as you could do the same thing on Linux as well.

So on a VDI where you won't do this very often you probably want to follow the suggestions to disable this for the HD and NICs.  On a server where this might be more prudent and also have more experienced people working on them you may not want to implement those changes.

Sure you can't just add more than one SCSI bus? I'm not to experienced with vmware (anymore). It seems as if kvm has support for a removable flag per block device. Whether it locks a device from being removable, or gives each one its own virtual bus is another story.

Yep you sure can, but then you have to have multiple per VM config, which adds small amount of overhead per VM in terms of resource management.  Not a big deal at 100 VMs.  But at 1000 that can be significant resources in play for limited use.