Windows VM in the cloud
-
You CAN load your own Windows ISO and Vultr has no way to know what you are running. But Microsoft offers no license that you can use in this case, so that would always be unlicensed no matter how you tried to do it. So while it is physically possible, it's never allowed. But Vultr doesn't care because the violation is between you and Microsoft.
-
@scottalanmiller said in Windows VM in the cloud:
You CAN load your own Windows ISO and Vultr has no way to know what you are running. But Microsoft offers no license that you can use in this case, so that would always be unlicensed no matter how you tried to do it. So while it is physically possible, it's never allowed. But Vultr doesn't care because the violation is between you and Microsoft.
My bad, I was thinking of the load your own ISO option.
-
@FATeknollogee said in Windows VM in the cloud:
@scottalanmiller said in Windows VM in the cloud:
You CAN load your own Windows ISO and Vultr has no way to know what you are running. But Microsoft offers no license that you can use in this case, so that would always be unlicensed no matter how you tried to do it. So while it is physically possible, it's never allowed. But Vultr doesn't care because the violation is between you and Microsoft.
My bad, I was thinking of the load your own ISO option.
The obvious thing to try to do is to move away from Windows. We do that for basically every workload, the cost of Windows is staggering when you look at cloud because you have the "double" cost of the VM because you need so much more CPU, RAM and storage for the simplest tasks and then you have the $16/mo or whatever Windows tax on top of that. It adds up really quickly. But if you are doing RDS, I'm guessing you have no options?
-
Unfortunately, this LOB is Windows only, hence the need for RDS.
-
@FATeknollogee said in Windows VM in the cloud:
Unfortunately, this LOB is Windows only, hence the need for RDS.
Why would it require RDS for a Windows LOB software solution? Is it from the 1990s and doesn't have a web interface or some other way to access it without RDS?
-
surely If you want to use Remote Desktop Services, then you are going to need more then 1 VM?, if you want to setup a session based RDS desktop solution you will need a connection broker,RD web Access,licence server and session host that your users will use? also have you thought about licencing etc?
-
@scottalanmiller said in Windows VM in the cloud:
@FATeknollogee said in Windows VM in the cloud:
Unfortunately, this LOB is Windows only, hence the need for RDS.
Why would it require RDS for a Windows LOB software solution? Is it from the 1990s and doesn't have a web interface or some other way to access it without RDS?
Unfortunately, the only options are "Fat client" or "Thin client aka RDS"
-
@StuartJordan said in Windows VM in the cloud:
surely If you want to use Remote Desktop Services, then you are going to need more then 1 VM?, if you want to setup a session based RDS desktop solution you will need a connection broker,RD web Access,licence server and session host that your users will use? also have you thought about licencing etc?
This VM is just for offshore workers to connect back "home"
-
you mentioned RDS? will you not be using Remote Desktop Services?
-
@StuartJordan said in Windows VM in the cloud:
surely If you want to use Remote Desktop Services, then you are going to need more then 1 VM?, if you want to setup a session based RDS desktop solution you will need a connection broker,RD web Access,licence server and session host that your users will use? also have you thought about licencing etc?
Only one is needed, all those services run on a single VM.
-
@FATeknollogee said in Windows VM in the cloud:
@scottalanmiller said in Windows VM in the cloud:
@FATeknollogee said in Windows VM in the cloud:
Unfortunately, this LOB is Windows only, hence the need for RDS.
Why would it require RDS for a Windows LOB software solution? Is it from the 1990s and doesn't have a web interface or some other way to access it without RDS?
Unfortunately, the only options are "Fat client" or "Thin client aka RDS"
I, personally, use that as a reason to heavily question why the business is depending on an application that has such a limitation. What possible reason would their be for important software to require a fat client on a Windows desktop (or any desktop.) There can be reasons, but they are rare. Sounds, most likely, that it is bad software that is not fully maintained for the last decade or so? That's the stuff I worry about. If they don't have a post-1990s interface and haven't freed themselves of desktop entanglements, do they have any support left?
-
@StuartJordan said in Windows VM in the cloud:
you mentioned RDS? will you not be using Remote Desktop Services?
RDS = Remote Desktop Services. One is just the initials of the other.
-
@scottalanmiller - I understand the abbreviation, what I was meaning is, if he is using RDS session based desktops he will probably want more then 1 VM. if he is not using RDS then fair enough.
-
@StuartJordan said in Windows VM in the cloud:
@scottalanmiller - I understand the abbreviation, what I was meaning is, if he is using RDS session based desktops he will probably want more then 1 VM. if he is not using RDS then fair enough.
RDS is always session based desktops, that's what RDS is. Why would you want more than one VM for that, though? I mean... large scale, sure. But assuming under 40 users and no need for failover, why have more than one?
-
@scottalanmiller I would personally like to keep the session host VM separate from the other roles, but I'm aware you can install all roles on same machine.
When installing the RDS role you can select Session Based Desktops or VDI Based Desktops. -
In a lab Environment I don't see any issue with installing all roles on same VM but I've seen many people say they also wouldn't in production.
-
@StuartJordan said in Windows VM in the cloud:
When installing the RDS role you can select Session Based Desktops or VDI Based Desktops.
True.
-
@StuartJordan said in Windows VM in the cloud:
In a lab Environment I don't see any issue with installing all roles on same VM but I've seen many people say they also wouldn't in production.
But why not? What's the benefit to splitting out the roles as they are all versioned together and all interdependent? Keeping them together means that the fail together, which makes more sense, are more performant and easier to maintain. Until you scale past one most, which is a lot of RDS, I don't really know of a benefit to splitting the roles but a fair number of negatives.
-
@scottalanmiller said in Windows VM in the cloud:
I, personally, use that as a reason to heavily question why the business is depending on an application that has such a limitation. What possible reason would their be for important software to require a fat client on a Windows desktop (or any desktop.) There can be reasons, but they are rare. Sounds, most likely, that it is bad software that is not fully maintained for the last decade or so? That's the stuff I worry about. If they don't have a post-1990s interface and haven't freed themselves of desktop entanglements, do they have any support left?
Unfortunately, it's an EMR system & Windows is the only option.
-
@scottalanmiller said in Windows VM in the cloud:
@StuartJordan said in Windows VM in the cloud:
In a lab Environment I don't see any issue with installing all roles on same VM but I've seen many people say they also wouldn't in production.
But why not? What's the benefit to splitting out the roles as they are all versioned together and all interdependent? Keeping them together means that the fail together, which makes more sense, are more performant and easier to maintain. Until you scale past one most, which is a lot of RDS, I don't really know of a benefit to splitting the roles but a fair number of negatives.
I'm not saying you cant, it's kind of Microsoft Guidelines though?
https://blogs.technet.microsoft.com/askperf/2015/04/09/remote-desktop-services-rds-2012-session-deployment-scenarios-quick-start/
