Server will not shut down
-
@scottalanmiller said in Server will not shut down:
@dafyre can you follow up with all of the details
Well... You asked for it... takes deep breath
TL;DR: Don't Add iSCSI Devices in the iSCSI initiator in Windows before sysprepping.
So we did finally figure out what happened. Apparently, when you sysprep a system, it deletes device drivers, and it does something to screw up the iSCSI initiator to the point that it simply won't work.
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.
-
@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.
-
@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.
-
@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.
-
@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.
-
@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.
For him, it's not so much a distrust of VMware, as much as it is a "I've never done it this way before."
-
@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.
-
@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.
-
@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
-
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.
-
@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.
-
@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.
-
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.
-
@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?
-
@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
-
@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.
