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

    Managing Hyper-V

    IT Discussion
    24
    328
    59.9k
    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.
    • B
      black3dynamite @Obsolesce
      last edited by

      @Tim_G My annoyance with Proxmox is the need to change the repo from enterprise to the no subscription repo.

      I don't really have an issue with them using Debian because majority of time is spent on the
      webui.

      I do wonder why they don't use Fedora unless they are more familiar with Debian.

      1 Reply Last reply Reply Quote 0
      • B
        bigbear @JaredBusch
        last edited by

        @JaredBusch in the case of the domain being down can you still log in locally?

        M O 2 Replies Last reply Reply Quote 0
        • M
          matteo nunziati @bigbear
          last edited by

          @bigbear ad credentials cached afaik

          1 Reply Last reply Reply Quote 0
          • O
            Obsolesce @bigbear
            last edited by Obsolesce

            @bigbear said in Managing Hyper-V:

            @JaredBusch in the case of the domain being down can you still log in locally?

            Same as any Windows server. There's domain logon and local user logon. Also, as matteo said, cached credentials.

            Not to mention "other" ways if you have physical access to the server, or remote with iDrac/ilo.

            S 1 Reply Last reply Reply Quote 1
            • S
              StorageNinja Vendor @Obsolesce
              last edited by

              @Tim_G said in Managing Hyper-V:

              @bigbear said in Managing Hyper-V:

              @JaredBusch in the case of the domain being down can you still log in locally?

              Same as any Windows server. There's domain logon and local user logon. Also, as matteo said, cached credentials.

              Not to mention "other" ways if you have physical access to the server, or remote with iDrac/ilo.

              Ransomware. I've seen cryto attack that encrypted all the VMs

              D O 2 Replies Last reply Reply Quote 0
              • D
                Dashrender @StorageNinja
                last edited by

                @John-Nicholson said in Managing Hyper-V:

                @Tim_G said in Managing Hyper-V:

                @bigbear said in Managing Hyper-V:

                @JaredBusch in the case of the domain being down can you still log in locally?

                Same as any Windows server. There's domain logon and local user logon. Also, as matteo said, cached credentials.

                Not to mention "other" ways if you have physical access to the server, or remote with iDrac/ilo.

                Ransomware. I've seen cryto attack that encrypted all the VMs

                I'm not sure how much more likely this is in a domain joined situation that non domained joined. If a computer that's used by an admin of VMs gets infected, it can possibly be used as an attack vector to the rest.

                Hopefully you don't have anything open you don't need, like fileshares.

                If you're talking about vulnerabilities in SMB, then domain joined or not didn't matter to those.

                1 Reply Last reply Reply Quote 0
                • O
                  Obsolesce @StorageNinja
                  last edited by Obsolesce

                  @John-Nicholson said in Managing Hyper-V:

                  @Tim_G said in Managing Hyper-V:

                  @bigbear said in Managing Hyper-V:

                  @JaredBusch in the case of the domain being down can you still log in locally?

                  Same as any Windows server. There's domain logon and local user logon. Also, as matteo said, cached credentials.

                  Not to mention "other" ways if you have physical access to the server, or remote with iDrac/ilo.

                  Ransomware. I've seen cryto attack that encrypted all the VMs

                  That's not an issue of being on a domain. That's an issue caused by bad IT administration.

                  I have hypervisors on the domain and they haven't been encrypted.

                  Other companies had ransomware with hypervisors on the domain, and the VMs themself haven't been encrypted... maybe files inside the VM, but that part is hypervisor agnostic.

                  1 Reply Last reply Reply Quote 2
                  • C
                    coliver
                    last edited by

                    @Tim_G While you're investigating have you taken a look at xCat? Seems like it may be something that can manage KVM.

                    W 1 Reply Last reply Reply Quote 0
                    • W
                      wirestyle22 @coliver
                      last edited by

                      @coliver said in Managing Hyper-V:

                      @Tim_G While you're investigating have you taken a look at xCat? Seems like it may be something that can manage KVM.

                      Seems like no console access but might be convenient for provisioning VM's and maintenance

                      1 Reply Last reply Reply Quote 0
                      • D
                        dbeato
                        last edited by

                        Has anyone tested this?
                        http://hv-manager.org/#home

                        S 1 Reply Last reply Reply Quote 0
                        • S
                          scottalanmiller @dbeato
                          last edited by

                          @dbeato said in Managing Hyper-V:

                          Has anyone tested this?
                          http://hv-manager.org/#home

                          No, is it free? Any idea how active it is? Maybe make a thread for testing it?

                          D 1 Reply Last reply Reply Quote 1
                          • D
                            dbeato @scottalanmiller
                            last edited by

                            @scottalanmiller YEah, it is free. I will start the testing.

                            S M 2 Replies Last reply Reply Quote 0
                            • S
                              scottalanmiller @dbeato
                              last edited by

                              @dbeato said in Managing Hyper-V:

                              @scottalanmiller YEah, it is free. I will start the testing.

                              Cool, make a thread for it. And lots of screen shots 🙂

                              1 Reply Last reply Reply Quote 0
                              • M
                                manxam @dbeato
                                last edited by

                                @dbeato said in Managing Hyper-V:

                                @scottalanmiller YEah, it is free. I will start the testing.

                                In my crude testing it appears that one can start, stop, pause, reset a VM.
                                One cannot modify its settings, access the console, nor create/destroy.

                                It does provide some basic guest details such as cpu, memory, network configuration, replication status, etc.

                                It is a little slower than I'd like.

                                S 1 Reply Last reply Reply Quote 0
                                • S
                                  scottalanmiller @manxam
                                  last edited by

                                  @manxam said in Managing Hyper-V:

                                  @dbeato said in Managing Hyper-V:

                                  @scottalanmiller YEah, it is free. I will start the testing.

                                  In my crude testing it appears that one can start, stop, pause, reset a VM.
                                  One cannot modify its settings, access the console, nor create/destroy.

                                  It does provide some basic guest details such as cpu, memory, network configuration, replication status, etc.

                                  It is a little slower than I'd like.

                                  Limited, but not completely useless.

                                  1 Reply Last reply Reply Quote 0
                                  • D
                                    dbeato
                                    last edited by

                                    @scottalanmiller Another thing that can be done is PowerShell Web Access
                                    https://technet.microsoft.com/en-us/library/hh831611(v=ws.11).aspx
                                    Found about that today 🙂

                                    1 Reply Last reply Reply Quote 0
                                    • R3dPand4R
                                      R3dPand4
                                      last edited by

                                      Late to the party....but just my two cents...haven't found a situation in which I'd want to join my hosts to a domain. The only consideration I could see here is if you're configuring failover clustering, but I'm fairly certain that applies to pre-2016. Generally when we're talking about Hyper-V Hosts and management pc's I have a dedicated workstation/laptop that's off domain and then create a mirrored Administrator account on the Hyper-V Hosts that's also off domain.

                                      JaredBuschJ 1 Reply Last reply Reply Quote 0
                                      • JaredBuschJ
                                        JaredBusch @R3dPand4
                                        last edited by

                                        @r3dpand4 said in Managing Hyper-V:

                                        Late to the party....but just my two cents...haven't found a situation in which I'd want to join my hosts to a domain. The only consideration I could see here is if you're configuring failover clustering, but I'm fairly certain that applies to pre-2016. Generally when we're talking about Hyper-V Hosts and management pc's I have a dedicated workstation/laptop that's off domain and then create a mirrored Administrator account on the Hyper-V Hosts that's also off domain.

                                        Why go through all this work if you have a domain already? Just join it and be done.

                                        It certainly does not have to be, but if you have a domain already it also certainly does not hurt.

                                        R3dPand4R 1 Reply Last reply Reply Quote 3
                                        • R3dPand4R
                                          R3dPand4 @JaredBusch
                                          last edited by R3dPand4

                                          @jaredbusch Because I have never needed the very thing supporting my infrastructure to be dependent on one of the vms inside of it. Also I'm not sure why you're saying this like it's a lot of work, it's literally no more or less work than creating a user account for management in AD and joining members to a domain. I wasn't arguing that it would hurt anything, it's just personal preference in all honesty, wasn't trying to be confrontational I just like having my management separated from the rest of the environment. I can imagine the headache that would come from a Host dropping Trust.

                                          D JaredBuschJ 2 Replies Last reply Reply Quote 0
                                          • D
                                            Dashrender @R3dPand4
                                            last edited by

                                            @r3dpand4 said in Managing Hyper-V:

                                            @jaredbusch Because I have never needed the very thing supporting my infrastructure to be dependent on one of the vms inside of it. Also I'm not sure why you're saying this like it's a lot of work, it's literally no more or less work than creating a user account for management in AD and joining members to a domain. I wasn't arguing that it would hurt anything, it's just personal preference in all honesty, wasn't trying to be confrontational I just like having my management separated from the rest of the environment. I can imagine the headache that would come from a Host dropping Trust.

                                            I thought this whole thread was about how much of a PITA non domain joined Hyper-V and control stations where to use? That would be the reason to join everything to a domain.

                                            Have you some way that makes passing authentication from your non domain joined PC to the non domain joined Hyper-V work easily? Though many would probably argue that you having to maintain yet another PC that is soley for this use, it's pretty expensive.

                                            R3dPand4R 1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 12
                                            • 13
                                            • 14
                                            • 15
                                            • 16
                                            • 17
                                            • 14 / 17
                                            • First post
                                              Last post