Burned by Eschewing Best Practices
-
I would think having to pay someone to pull it out of the rack, package and pay for return shipping, and then to re-return ship it would be way more expensive.
-
@DustinB3403 said in Burned by Eschewing Best Practices:
I would think having to pay someone to pull it out of the rack, package and pay for return shipping, and then to re-return ship it would be way more expensive.
Not likely more, but it's all a waste whereas the update is at least a fresh license.
-
@scottalanmiller but it's also a hard cost (measured in a PO to outright purchase the license) where as someone's time might just be a "Salary tasks for today".
When I worked for a local sheet metal facility we had our own site to site truck driver which we regularly shipped material (daily between facilities) to and from this facility. So it could be near free for the business.
But in terms of the system not being accessible for however long it takes to address this issue. That I see as being a big cost. He also probably doesn't want to approach the management team and claim he made a mistake.
-
@DustinB3403 said in Burned by Eschewing Best Practices:
But in terms of the system not being accessible for however long it takes to address this issue. That I see as being a big cost. He also probably doesn't want to approach the management team and claim he made a mistake.
Another violation of best practice, if that is the case. Trying to hide this will just cost more money.
-
@scottalanmiller said in Burned by Eschewing Best Practices:
@DustinB3403 said in Burned by Eschewing Best Practices:
But in terms of the system not being accessible for however long it takes to address this issue. That I see as being a big cost. He also probably doesn't want to approach the management team and claim he made a mistake.
Another violation of best practice, if that is the case. Trying to hide this will just cost more money.
Of course, best practice being "I made a mistake, we can do x or z to fix it."
Rather than it coming back around in 180 days (or when someone notices)
-
Just poking fun at @jospoortvliet for not using a VM for this.
-
The thing @scottalanmiller and @DustinB3403 are missing on this last one is that the OP on the SW thread has a 100% valid hypervisor in place now.
There is zero lack of virtualization if the OP so chooses.
The OP could very simply reallocate one of their Server 2012 R2 DC licenses to that box and be perfectly licensed for anything he needs.
Now that is quite expensive if that remote office will not be running the 8+ Server 2012 VMs needed to make it cost effective.
So shipping it back and redoing it can easily be the most cost effective.
At that point yes, the best thing would be to use Hyper-V Server 2012 R2 on the bare metal, but do not miss the forest for the trees. Server 2012 R2 (DC or Standard) is a perfectly viable hypervisor itself once the role is installed.
-
@JaredBusch said in Burned by Eschewing Best Practices:
The thing @scottalanmiller and @DustinB3403 are missing on this last one is that the OP on the SW thread has a 100% valid hypervisor in place now.
There is zero lack of virtualization if the OP so chooses.
The OP could very simply reallocate one of their Server 2012 R2 DC licenses to that box and be perfectly licensed for anything he needs.
Not missed at all. That he has the ability to install Hyper-V there wasn't missed, that he doesn't have a license to do so because he installed Windows Server first is the issue. He can relocate a license, but isn't willing to, and that's the entire crux of the thread.
No one is saying that Hyper-V installed via a role isn't valid, only that because he didn't virtualize first he created a license problem.
He lacks the licensing or licensing permissions to do what you are suggesting.
Yes, we know that he could do it, but if he could do that, he wouldn't have this issue in the first place because he's just reassign the license.
-
@JaredBusch said in Burned by Eschewing Best Practices:
So shipping it back and redoing it can easily be the most cost effective.
But totally unnecessary to fix this problem had he virtualized in the first place.
Unless, of course, he virtulaized with something for which he was not licensed. That would have recreated the problem.
-
@scottalanmiller said in Burned by Eschewing Best Practices:
@JaredBusch said in Burned by Eschewing Best Practices:
The thing @scottalanmiller and @DustinB3403 are missing on this last one is that the OP on the SW thread has a 100% valid hypervisor in place now.
There is zero lack of virtualization if the OP so chooses.
The OP could very simply reallocate one of their Server 2012 R2 DC licenses to that box and be perfectly licensed for anything he needs.
Not missed at all. That he has the ability to install Hyper-V there wasn't missed, that he doesn't have a license to do so because he installed Windows Server first is the issue. He can relocate a license, but isn't willing to, and that's the entire crux of the thread.
No one is saying that Hyper-V installed via a role isn't valid, only that because he didn't virtualize first he created a license problem.
He lacks the licensing or licensing permissions to do what you are suggesting.
Yes, we know that he could do it, but if he could do that, he wouldn't have this issue in the first place because he's just reassign the license.
No Scott. That has nothing to do with the licensing. When you install Server 2012 R2 + Hyper-V role, you still license the server. There is not a damned thing wrong with that model technically. With a Standard license you get 2 (Windows) VMs and with DC you get unlimited.
Let me say it again, he did not miss any virtualizaiton. You may not like it, but that is a fact.
-
@scottalanmiller said in Burned by Eschewing Best Practices:
@JaredBusch said in Burned by Eschewing Best Practices:
So shipping it back and redoing it can easily be the most cost effective.
But totally unnecessary to fix this problem had he virtualized in the first place.
Incorrect. If the cost of the license is still valid for the use on that site, he need do nothing else except enable the Hyper-V role.
You are mixing two separate things.
-
@JaredBusch said in Burned by Eschewing Best Practices:
Let me say it again, he did not miss any virtualizaiton. You may not like it, but that is a fact.
He is NOT currently virtualized. He did NOT virtualize his initial install. Say what you want, but my understanding of that thread is that these are the facts. You are arguing that he "could" virtualize yet, but not in a way possible due to his license.
But unless I missed something in the thread, there is no virtualization in place whatsoever currently. And regardless of that, the issue is that he didn't follow best practice and virtualize always hence the problem he is in.
What am I missing?
-
@JaredBusch said in Burned by Eschewing Best Practices:
@scottalanmiller said in Burned by Eschewing Best Practices:
@JaredBusch said in Burned by Eschewing Best Practices:
So shipping it back and redoing it can easily be the most cost effective.
But totally unnecessary to fix this problem had he virtualized in the first place.
Incorrect. If the cost of the license is still valid for the use on that site, he need do nothing else except enable the Hyper-V role.
You are mixing two separate things.
I'm not. The cost of the license is NOT valid for the use on that site. THat's the entire point of hte thread. No license.
-
@scottalanmiller said in Burned by Eschewing Best Practices:
@JaredBusch said in Burned by Eschewing Best Practices:
Let me say it again, he did not miss any virtualizaiton. You may not like it, but that is a fact.
He is NOT currently virtualized. He did NOT virtualize his initial install. Say what you want, but my understanding of that thread is that these are the facts. You are arguing that he "could" virtualize yet, but not in a way possible due to his license.
But unless I missed something in the thread, there is no virtualization in place whatsoever currently. And regardless of that, the issue is that he didn't follow best practice and virtualize always hence the problem he is in.
What am I missing?
What part of a Server 2012 R2 DC licvense tells you that he cannot virtualize?
-
@JaredBusch said in Burned by Eschewing Best Practices:
@scottalanmiller said in Burned by Eschewing Best Practices:
@JaredBusch said in Burned by Eschewing Best Practices:
Let me say it again, he did not miss any virtualizaiton. You may not like it, but that is a fact.
He is NOT currently virtualized. He did NOT virtualize his initial install. Say what you want, but my understanding of that thread is that these are the facts. You are arguing that he "could" virtualize yet, but not in a way possible due to his license.
But unless I missed something in the thread, there is no virtualization in place whatsoever currently. And regardless of that, the issue is that he didn't follow best practice and virtualize always hence the problem he is in.
What am I missing?
What part of a Server 2012 R2 DC licvense tells you that he cannot virtualize?
What part of "he doesn't have that license" did you miss? The whole thread is about how he has to get around lacking that license.
-
@scottalanmiller said in Burned by Eschewing Best Practices:
@JaredBusch said in Burned by Eschewing Best Practices:
@scottalanmiller said in Burned by Eschewing Best Practices:
@JaredBusch said in Burned by Eschewing Best Practices:
Let me say it again, he did not miss any virtualizaiton. You may not like it, but that is a fact.
He is NOT currently virtualized. He did NOT virtualize his initial install. Say what you want, but my understanding of that thread is that these are the facts. You are arguing that he "could" virtualize yet, but not in a way possible due to his license.
But unless I missed something in the thread, there is no virtualization in place whatsoever currently. And regardless of that, the issue is that he didn't follow best practice and virtualize always hence the problem he is in.
What am I missing?
What part of a Server 2012 R2 DC licvense tells you that he cannot virtualize?
What part of "he doesn't have that license" did you miss? The whole thread is about how he has to get around lacking that license.
Wrong. He has the license. He does not want to allocate it to the site. That is different.
-
What am I missing here? He can't use anything 2012 R2 unless it is the free Hyper-V 2012 R2 which he has no means of installing now because he skipped the best practice step. Now he can't use Server 2012 R2 at all. That's teh point of the thread. How does he fix the system now that he has no license for it?
-
@JaredBusch said in Burned by Eschewing Best Practices:
@scottalanmiller said in Burned by Eschewing Best Practices:
@JaredBusch said in Burned by Eschewing Best Practices:
@scottalanmiller said in Burned by Eschewing Best Practices:
@JaredBusch said in Burned by Eschewing Best Practices:
Let me say it again, he did not miss any virtualizaiton. You may not like it, but that is a fact.
He is NOT currently virtualized. He did NOT virtualize his initial install. Say what you want, but my understanding of that thread is that these are the facts. You are arguing that he "could" virtualize yet, but not in a way possible due to his license.
But unless I missed something in the thread, there is no virtualization in place whatsoever currently. And regardless of that, the issue is that he didn't follow best practice and virtualize always hence the problem he is in.
What am I missing?
What part of a Server 2012 R2 DC licvense tells you that he cannot virtualize?
What part of "he doesn't have that license" did you miss? The whole thread is about how he has to get around lacking that license.
Wrong. He has the license. He does not want to allocate it to the site. That is different.
Not really. Someone has a license, he's not supposed to use it there. The point of the thread is to not use that license. If your answer is "just pay for a license*, that's fine. But that's totally different and, as I said, would not require any virtualization if he was willing to relocate the license to fix this. The entire discussion is predicated on that license not being available.
-
@scottalanmiller said in Burned by Eschewing Best Practices:
What am I missing here?
This is what you are missing..
He can't use anything 2012 R2 unless it is the free Hyper-V 2012 R2
Yes he can. Who the hell said you cannot use Server 2012 R2 as a Hypervisor?
You can most certainly 100% use Server 2012 R2 with the Hyper-V role as a hypervisor. You are NOT required to use Hyper-V Server 2012 R2. -
That if the core of the request was ignored and violated that he could then pay to have a hypervisor there is true is a red herring, I think. The thread is about avoiding using that license. That is the one and only point ot the OP's request.
