XP and Virtual Machine Hardware Versions
-
@scottalanmiller said:
@alexntg said:
@scottalanmiller said:
@alexntg said:
@scottalanmiller said:
@alexntg said:
@scottalanmiller said:
Put it on VirtualBox and you'll get RDP back.
The hypervisor isn't preventing RDP.
Didn't imply that it was. But it isn't providing it either. VirtualBox provides RDP directly from the hypervisors so no OS level lock out will do anything. Console redirect to RDP!!
Ok. How does one do that without nesting VMs?
Just select the RDP option instead of the VNC option when downloading VirtualBox. Remote console redirection is native to VirtualBox and Xen. There is nothing special to know.
Let me rephrase; you're suggesting running VirtualBox inside of ESXI?
No. Why would want to do that?
You're making something incredibly simple into something really complicated.
Just install CentOS. Toss on VBox with RDP. Done. VBox handles everything. No weird nesting. No reading in something odd. Just a normal VBox install.
That's insane. No one should be running their production environment on VirtualBox. Replacing ESXi with that would result in a drop in performance, and it's not a Veeam-supported hypervisor.
-
@alexntg we are talking about running one XP desktop here. Keep some perspective.
-
@scottalanmiller said:
@alexntg we are talking about running one XP desktop here. Keep some perspective.
It's currently a VM running in an otherwise fine server architecture. You're suggesting adding another piece of hardware and a different virtualization platform for a minor video issue.
-
@alexntg said:
@scottalanmiller said:
@alexntg we are talking about running one XP desktop here. Keep some perspective.
It's currently a VM running in an otherwise fine server architecture. You're suggesting adding another piece of hardware and a different virtualization platform for a minor video issue.
And a major licensing issue.
-
@scottalanmiller said:
@alexntg said:
@scottalanmiller said:
@alexntg we are talking about running one XP desktop here. Keep some perspective.
It's currently a VM running in an otherwise fine server architecture. You're suggesting adding another piece of hardware and a different virtualization platform for a minor video issue.
And a major licensing issue.
All it takes is a single SA subscription or VDA license to fix. That's not major. The issue would still exist on VirtualBox.
-
@alexntg Is VDA still needed on a 1:1 scenario?
-
@scottalanmiller said:
@alexntg Is VDA still needed on a 1:1 scenario?
To start with, yes. The accessing device must be covered by either SA or VDA. If a Companion Subscription License (CSL) is added on to the VDA or SA for a user's primary device, they're able to use up to 4 additional devices to access the virtual OSE.
-
@alexntg said:
@scottalanmiller said:
@alexntg Is VDA still needed on a 1:1 scenario?
To start with, yes. The accessing device must be covered by either SA or VDA. If a Companion Subscription License (CSL) is added on to the VDA or SA for a user's primary device, they're able to use up to 4 additional devices to access the virtual OSE.
So you can't remote into a VM on your own desktop?
-
@scottalanmiller said:
@alexntg said:
@scottalanmiller said:
@alexntg Is VDA still needed on a 1:1 scenario?
To start with, yes. The accessing device must be covered by either SA or VDA. If a Companion Subscription License (CSL) is added on to the VDA or SA for a user's primary device, they're able to use up to 4 additional devices to access the virtual OSE.
So you can't remote into a VM on your own desktop?
Without SA or VDA licensing, there's no licensed usage of a Windows desktop OS on a VM, even if on your local machine. This is the reason I have SA on my home computer.
-
@alexntg said:
@scottalanmiller said:
@alexntg said:
@scottalanmiller said:
@alexntg Is VDA still needed on a 1:1 scenario?
To start with, yes. The accessing device must be covered by either SA or VDA. If a Companion Subscription License (CSL) is added on to the VDA or SA for a user's primary device, they're able to use up to 4 additional devices to access the virtual OSE.
So you can't remote into a VM on your own desktop?
Without SA or VDA licensing, there's no licensed usage of a Windows desktop OS on a VM, even if on your local machine. This is the reason I have SA on my home computer.
But they sell Ultimate explicitly with that option. 4 VMs on your desktop, no SA.
-
It's like watching a tennis match. Seriously this is good information for those of us looking at keeping an XP pc alive using VM.
-
@scottalanmiller said:
@alexntg said:
@scottalanmiller said:
@alexntg said:
@scottalanmiller said:
@alexntg Is VDA still needed on a 1:1 scenario?
To start with, yes. The accessing device must be covered by either SA or VDA. If a Companion Subscription License (CSL) is added on to the VDA or SA for a user's primary device, they're able to use up to 4 additional devices to access the virtual OSE.
So you can't remote into a VM on your own desktop?
Without SA or VDA licensing, there's no licensed usage of a Windows desktop OS on a VM, even if on your local machine. This is the reason I have SA on my home computer.
But they sell Ultimate explicitly with that option. 4 VMs on your desktop, no SA.
Windows 8.1 is not available in Ultimate. It's available in RT, Basic, Pro, and Enterprise. Windows 7 Ultimate included XP mode, which was a single-instance more desktop-integrated VM designed specifically to assist with application compatibility issues. It did not include normal virtualization rights.
-
@alexntg said:
Windows 8.1 is not available in Ultimate. It's available in RT, Basic, Pro, and Enterprise. Windows 7 Ultimate included XP mode, which was a single-instance more desktop-integrated VM designed specifically to assist with application compatibility issues. It did not include normal virtualization rights.
In the Microsoft official material it stated that Ultimate was a non-SA version of Enterprise that was identical in every way.
According to this chart the VDI licensing was the same between the two...
-
@scottalanmiller said:
@alexntg said:
Windows 8.1 is not available in Ultimate. It's available in RT, Basic, Pro, and Enterprise. Windows 7 Ultimate included XP mode, which was a single-instance more desktop-integrated VM designed specifically to assist with application compatibility issues. It did not include normal virtualization rights.
In the Microsoft official material it stated that Ultimate was a non-SA version of Enterprise that was identical in every way.
According to this chart the VDI licensing was the same between the two...
Can you link the MS official material? I'm getting my info from http://download.microsoft.com/download/3/d/4/3d42bdc2-6725-4b29-b75a-a5b04179958b/licensing_windows7_with_VM_technologies.docx
