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

    Server will not shut down

    IT Discussion
    windows server 2012 r2 multiple nics
    8
    58
    5.8k
    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.
    • scottalanmillerS
      scottalanmiller @Dashrender
      last edited by

      @Dashrender said in Server will not shut down:

      @scottalanmiller said in Server will not shut down:

      @dafyre said in Server will not shut down:

      @Dashrender said in Server will not shut down:

      @dafyre said in Server will not shut down:

      Workaround is to set up the VM the way you want it, and then sysprep it.... then add iSCSI settings after the machine has been cloned successfully.

      Workaround, yes, industry best practice - yeah not so much. 😉

      Preaching to the choir, man. VMware is my boss's baby. I go in and start making changes, and I'd find myself neck deep in... well, you get the idea.

      She needs to trust her baby more. The issue here, kinda, is that there was a distrust for VMware and the best practice approach and instead trust was put on Microsoft and the anti-pattern approach.

      I'm guessing it's not a lack of trust toward VMware but instead an inappropriate trusted windows.

      Strange that they run VMware and not Hyper-V in either case.

      dafyreD 1 Reply Last reply Reply Quote 0
      • dafyreD
        dafyre @scottalanmiller
        last edited by

        @scottalanmiller said in Server will not shut down:

        @Dashrender said in Server will not shut down:

        @scottalanmiller said in Server will not shut down:

        @dafyre said in Server will not shut down:

        @Dashrender said in Server will not shut down:

        @dafyre said in Server will not shut down:

        Workaround is to set up the VM the way you want it, and then sysprep it.... then add iSCSI settings after the machine has been cloned successfully.

        Workaround, yes, industry best practice - yeah not so much. 😉

        Preaching to the choir, man. VMware is my boss's baby. I go in and start making changes, and I'd find myself neck deep in... well, you get the idea.

        She needs to trust her baby more. The issue here, kinda, is that there was a distrust for VMware and the best practice approach and instead trust was put on Microsoft and the anti-pattern approach.

        I'm guessing it's not a lack of trust toward VMware but instead an inappropriate trusted windows.

        Strange that they run VMware and not Hyper-V in either case.

        State contract... I suspect that gears have been greased.

        DashrenderD scottalanmillerS 2 Replies Last reply Reply Quote 0
        • DashrenderD
          Dashrender @dafyre
          last edited by

          @dafyre said in Server will not shut down:

          @scottalanmiller said in Server will not shut down:

          @Dashrender said in Server will not shut down:

          @scottalanmiller said in Server will not shut down:

          @dafyre said in Server will not shut down:

          @Dashrender said in Server will not shut down:

          @dafyre said in Server will not shut down:

          Workaround is to set up the VM the way you want it, and then sysprep it.... then add iSCSI settings after the machine has been cloned successfully.

          Workaround, yes, industry best practice - yeah not so much. 😉

          Preaching to the choir, man. VMware is my boss's baby. I go in and start making changes, and I'd find myself neck deep in... well, you get the idea.

          She needs to trust her baby more. The issue here, kinda, is that there was a distrust for VMware and the best practice approach and instead trust was put on Microsoft and the anti-pattern approach.

          I'm guessing it's not a lack of trust toward VMware but instead an inappropriate trusted windows.

          Strange that they run VMware and not Hyper-V in either case.

          State contract... I suspect that gears have been greased.

          I understand Scott comment about trusting hyper-v vs. VMware but the reality of that situation bro I was down at the hyper-v is so young in comparison to VMware

          scottalanmillerS 1 Reply Last reply Reply Quote 0
          • dafyreD
            dafyre
            last edited by

            The irony here is that we actually do have a Hyper-V install. We're using that to build out our VDI platform. If they like the way it works, I suspect we'll be moving more and more stuff over to Hyper-V.

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

              @dafyre said in Server will not shut down:

              @scottalanmiller said in Server will not shut down:

              @Dashrender said in Server will not shut down:

              @scottalanmiller said in Server will not shut down:

              @dafyre said in Server will not shut down:

              @Dashrender said in Server will not shut down:

              @dafyre said in Server will not shut down:

              Workaround is to set up the VM the way you want it, and then sysprep it.... then add iSCSI settings after the machine has been cloned successfully.

              Workaround, yes, industry best practice - yeah not so much. 😉

              Preaching to the choir, man. VMware is my boss's baby. I go in and start making changes, and I'd find myself neck deep in... well, you get the idea.

              She needs to trust her baby more. The issue here, kinda, is that there was a distrust for VMware and the best practice approach and instead trust was put on Microsoft and the anti-pattern approach.

              I'm guessing it's not a lack of trust toward VMware but instead an inappropriate trusted windows.

              Strange that they run VMware and not Hyper-V in either case.

              State contract... I suspect that gears have been greased.

              But they are using Microsoft products too, would be odd for Hyper-V to not be allowed given that, even with the state contract, that Hyper-V and its vendors are already acquired.

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

                @Dashrender said in Server will not shut down:

                I understand Scott comment about trusting hyper-v vs. VMware but the reality of that situation bro I was down at the hyper-v is so young in comparison to VMware

                I'm not recommending it here, only stating that it is a weird emotional thing for the manager to dis VMware for Microsoft in a place where it is a pretty obvious technical problem but not do it where it would make sense.

                DashrenderD 1 Reply Last reply Reply Quote 0
                • dafyreD
                  dafyre
                  last edited by

                  The VMware thing is done higher up the food chain. From what I gather, all of our "critical systems" -- namely our student information systems (SIS) -- have to be physical (ugh!) or Virtualized with VMware.

                  Fortunatley, our SIS is Virtualized.

                  DustinB3403D 1 Reply Last reply Reply Quote 0
                  • DashrenderD
                    Dashrender @scottalanmiller
                    last edited by

                    @scottalanmiller said in Server will not shut down:

                    @Dashrender said in Server will not shut down:

                    I understand Scott comment about trusting hyper-v vs. VMware but the reality of that situation bro I was down at the hyper-v is so young in comparison to VMware

                    I'm not recommending it here, only stating that it is a weird emotional thing for the manager to dis VMware for Microsoft in a place where it is a pretty obvious technical problem but not do it where it would make sense.

                    LOl is it really weird? or is it normal even though it probably shouldn't be?

                    scottalanmillerS 1 Reply Last reply Reply Quote 1
                    • DustinB3403D
                      DustinB3403 @dafyre
                      last edited by

                      @dafyre said in Server will not shut down:

                      The VMware thing is done higher up the food chain. From what I gather, all of our "critical systems" -- namely our student information systems (SIS) -- have to be physical (ugh!) or Virtualized with VMware.

                      Fortunatley, our SIS is Virtualized.

                      I think you should just migrate that over to XS and see if anyone notices. lol

                      1 Reply Last reply Reply Quote 2
                      • scottalanmillerS
                        scottalanmiller @Dashrender
                        last edited by

                        @Dashrender said in Server will not shut down:

                        @scottalanmiller said in Server will not shut down:

                        @Dashrender said in Server will not shut down:

                        I understand Scott comment about trusting hyper-v vs. VMware but the reality of that situation bro I was down at the hyper-v is so young in comparison to VMware

                        I'm not recommending it here, only stating that it is a weird emotional thing for the manager to dis VMware for Microsoft in a place where it is a pretty obvious technical problem but not do it where it would make sense.

                        LOl is it really weird? or is it normal even though it probably shouldn't be?

                        This makes me very sad.

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