it would depend entirely on your VDI environment - if it's a full virtual machine, then it will behave just like a real machine. If it's a remote-desktop type solution, then of course not.
Do you get a BIOS start screen in your VDI environment? I imagine you do if it's a VMWare based solution - if so, then it will be just like a real machine. SSO and everything.
I have done RDP to a test session, and also connected to it via the viewer. I don't have one of the thin clients that they most often use(this is a remote site), but I've been told that the thin client simply launches the same viewer utility that I have installed.
This presents me with a list of the "desktops" that I have access. It then passes me into the VDI using my current credentials, as captured by GINA. This option allows for manually logging as well. Eitehr way, it is the Windows logon that I experience, not a bios process like a "real" PC.
By your description, I would assume that our current setup is not standard and that it is entirely possible for it to be changed to allow view of the actual boot process. I know that if I'm on my physical machine with vmware, I can easily launch a virtual session that has pre-boot enabled. I guess I thought maybe there was some unforseen issues with vmware, since you coded the ini setting into AutoDomain.
1 of 1 people found this helpful
the options in autodomain are for people who prep images in VM before deploying them to real machines - there's no problem with using EEPC on VMWare though.
I would just install EEPC on one of your VDI machines and see what happens ;-)