ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Windows VM in the cloud

    Scheduled Pinned Locked Moved IT Discussion
    cloudazureawsvultr
    45 Posts 5 Posters 7.1k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • FATeknollogeeF
      FATeknollogee
      last edited by

      Unfortunately, this LOB is Windows only, hence the need for RDS.

      scottalanmillerS 1 Reply Last reply Reply Quote 0
      • scottalanmillerS
        scottalanmiller @FATeknollogee
        last edited by

        @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?

        FATeknollogeeF 1 Reply Last reply Reply Quote -1
        • CloudKnightC
          CloudKnight
          last edited by

          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?

          FATeknollogeeF scottalanmillerS 2 Replies Last reply Reply Quote 0
          • FATeknollogeeF
            FATeknollogee @scottalanmiller
            last edited by

            @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"

            scottalanmillerS 1 Reply Last reply Reply Quote 0
            • FATeknollogeeF
              FATeknollogee @CloudKnight
              last edited by

              @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"

              1 Reply Last reply Reply Quote 0
              • CloudKnightC
                CloudKnight
                last edited by

                you mentioned RDS? will you not be using Remote Desktop Services?

                scottalanmillerS 1 Reply Last reply Reply Quote 0
                • scottalanmillerS
                  scottalanmiller @CloudKnight
                  last edited by

                  @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.

                  1 Reply Last reply Reply Quote 0
                  • scottalanmillerS
                    scottalanmiller @FATeknollogee
                    last edited by

                    @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?

                    FATeknollogeeF 1 Reply Last reply Reply Quote -1
                    • scottalanmillerS
                      scottalanmiller @CloudKnight
                      last edited by

                      @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.

                      CloudKnightC 1 Reply Last reply Reply Quote 1
                      • CloudKnightC
                        CloudKnight @scottalanmiller
                        last edited by

                        @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.

                        scottalanmillerS 1 Reply Last reply Reply Quote 0
                        • scottalanmillerS
                          scottalanmiller @CloudKnight
                          last edited by

                          @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?

                          CloudKnightC 1 Reply Last reply Reply Quote 0
                          • CloudKnightC
                            CloudKnight @scottalanmiller
                            last edited by

                            @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.

                            scottalanmillerS 1 Reply Last reply Reply Quote 0
                            • CloudKnightC
                              CloudKnight
                              last edited by

                              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.

                              scottalanmillerS 1 Reply Last reply Reply Quote 0
                              • scottalanmillerS
                                scottalanmiller @CloudKnight
                                last edited by

                                @StuartJordan said in Windows VM in the cloud:

                                When installing the RDS role you can select Session Based Desktops or VDI Based Desktops.

                                True.

                                1 Reply Last reply Reply Quote 0
                                • scottalanmillerS
                                  scottalanmiller @CloudKnight
                                  last edited by

                                  @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.

                                  CloudKnightC 1 Reply Last reply Reply Quote 0
                                  • FATeknollogeeF
                                    FATeknollogee @scottalanmiller
                                    last edited by

                                    @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.

                                    scottalanmillerS 1 Reply Last reply Reply Quote 0
                                    • CloudKnightC
                                      CloudKnight @scottalanmiller
                                      last edited by

                                      @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/

                                      scottalanmillerS 1 Reply Last reply Reply Quote 0
                                      • scottalanmillerS
                                        scottalanmiller @FATeknollogee
                                        last edited by

                                        @FATeknollogee said in Windows VM in the cloud:

                                        Unfortunately, it's an EMR system & Windows is the only option.

                                        But.... is that relevant to what I said? That it IS EMR doens't mean that it is a viable, supported EMR. And the issue is not that it is Windows, but that the design is archaic and suggestive of deep rooted support problems.

                                        FATeknollogeeF 1 Reply Last reply Reply Quote 0
                                        • scottalanmillerS
                                          scottalanmiller @CloudKnight
                                          last edited by

                                          @StuartJordan said in Windows VM in the cloud:

                                          @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/

                                          "Guideline" only sort of. That's the "guidelines" of the performance team, not MS as a whole. And MS themselves provide the single VM deployment model not just as an option, but a built in and ready to go one. If you don't need the performance, then the guideline to split doesn't exist. I'd argue that that very link actually suggests, through implication, that the single server deployment is best when not needed for performance needs - which is what I said above.

                                          1 Reply Last reply Reply Quote 0
                                          • FATeknollogeeF
                                            FATeknollogee @scottalanmiller
                                            last edited by

                                            @scottalanmiller said in Windows VM in the cloud:

                                            @FATeknollogee said in Windows VM in the cloud:

                                            Unfortunately, it's an EMR system & Windows is the only option.

                                            But.... is that relevant to what I said? That it IS EMR doens't mean that it is a viable, supported EMR. And the issue is not that it is Windows, but that the design is archaic and suggestive of deep rooted support problems.

                                            I'm not disagreeing w you, I'm just stating what it is.
                                            It is viable, it is supported by the vendor but it exist's as 100% Windows only

                                            scottalanmillerS 1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 1 / 3
                                            • First post
                                              Last post