basically if you enable winrm with an Enter-PSSession you can control the host from enywhere (firewall must be setup) in powershell.

what I do not find is a central management tool to have an overview of all hosts and their loading conditions.

@Danp said in How would you build this:

Beyond the aforementioned finger pointing, what prevents you from running the VM on your current virtual infrastructure w/o purchasing an additional server?

just the hypervisor I think

@scottalanmiller said in How would you build this:

An obvious question is... does the customer have any needs beyond this that might influence it?

Wait is it to be run for your business or for a customers of yours? If it was for internal usage my previous post still hold. Otherwise I think that keeping the default witha 3rd party is better. Can they understand where a real issue is in case of finger pointing?

Ok if it is a Vm what kind of finger pointing could be there? I think about performance and special setups. Virtualization is expected to abstract hw. If the vm image format is convertible I don't see why hypervisor/hw should matter.

As first I could thick about performances, then guest agents not being available in vendor image, third strange network configs hard to be attained without kvm.

For sure centos+your hw (can you buy the same machine?) should be near 100% ok!
Other combinations should be checked for previous 3 points and if they are ok don't see any issue

Does hyper-v has any restful api as first? Otherwise you have to wrap its api into a rest one for https.

Multi-site multi-company centralized management doesn't seems main concern at MS. It is more of an in-company vlaned netscalered env.

@dbeato said in Managing Hyper-V:

@scottalanmiller You need a Windows 8.1 or Windows 10 computer, and like I said on my post before you can go to the c$ of that HyperV enter the username and password and then connect using the Hyperv console.

WHAT?!

@Tim_G said in Managing Hyper-V:

@matteo-nunziati said in Managing Hyper-V:

@Tim_G yes but @scottalanmiller was discussing the binding caused by mmc: new hypeev? New windows workstation...

I'm gonna have to go back and read all 95 posts.

Nope! 95% is @scottalanmiller just read the last one

@scottalanmiller said in Managing Hyper-V:

@matteo-nunziati said in Managing Hyper-V:

ok comany is closing. after dinner will put notes here!

For the weekend?

Yep!

@Tim_G yes but @scottalanmiller was discussing the binding caused by mmc: new hyperv? New windows workstation...

@Tim_G yes the virtual console

@scottalanmiller said in Managing Hyper-V:

@wirestyle22 said in Managing Hyper-V:

@matteo-nunziati said in Managing Hyper-V:

@JaredBusch said in Managing Hyper-V:

@matteo-nunziati said in Managing Hyper-V:

ok comany is closing. after dinner will put notes here!

it is just winrm, trusthosts and same user/password/workgroup setup. then you can fly!

This is the answer for non domain joined systems.

But most people have no need for this in the SMB as a MS AD deployment is almost always already in place.

@Dashrender opened this thread with a poor hypothetical scenario.

It is something that can apply to an ITSP or consultant, but it is completely not something that will apply to the vast majority of deployments.

They asked for non ad joined management...

Even so, Jared is right.

There ARE cases where you need or want to avoid AD joining. But I think that I agree, normally AD joining will be best and probably should happen here.

Don't know. I miss ad for my company management. But honestly I see hypervisors as a building block like vlans and so. Something before services like the AD. Don't know if I would join the hv to the ad. Word this differently: it was xen would you put it under domain via samba in dom0?

@scottalanmiller said in Sizing the SOHO, SMB, SME, Enterprise and Other Markets:

@coliver said in Sizing the SOHO, SMB, SME, Enterprise and Other Markets:

@scottalanmiller said in Sizing the SOHO, SMB, SME, Enterprise and Other Markets:

@matteo-nunziati said in Sizing the SOHO, SMB, SME, Enterprise and Other Markets:

• SME: 2,000 - 5,000 people. True business with stable finances and acts like a true business, just one that is very small.

over 250, management starts apperaing but not so much levels.

• Medium: 5000 - 10,000 people. No longer small in any way, not a sizeable company needing serious services.
• Large: 10000 - 20,000 people. A serious company but not large enough to through its weight around based on a famous name.
• Enterprise: 20,000+ people. Those on the Fortune 1000 list or just missing it. Big, well known companies with tons of resources where they are big enough to have entire IT stacks internally, you don't need to hop between companies to move up the ladder, there is total efficiency of scale opportunity, etc.

this is far from my perception.

IBM considers SMB to be 500 - 10,000 or something like that. Under 500 they don't even consider to be a "business".

Is IBM a good bench mark?

No, horrible. but it's important to understand that big portions of the industry think that we see things in the opposite skew than we tend to think that we are doing.

My limits are extracted from italian accounting and fiscal law. They fit quite well with behaviur change in organizations here.

@scottalanmiller said in Sizing the SOHO, SMB, SME, Enterprise and Other Markets:

@matteo-nunziati said in Sizing the SOHO, SMB, SME, Enterprise and Other Markets:

@scottalanmiller said in Sizing the SOHO, SMB, SME, Enterprise and Other Markets:

These are kind of the rough numbers I feel most comfortable with.

• SOHO: 1 - 10 people. The "too small to have AD" category.

OK 1-10 or 1-20 fits here.

There is normally a big behavioural change between 10 - 12 people.

In my experience 10 is the limit in industry but consultancy firms can grow up to 20 keeping steady behavior here.

@JaredBusch said in Managing Hyper-V:

@matteo-nunziati said in Managing Hyper-V:

ok comany is closing. after dinner will put notes here!

it is just winrm, trusthosts and same user/password/workgroup setup. then you can fly!

This is the answer for non domain joined systems.

But most people have no need for this in the SMB as a MS AD deployment is almost always already in place.

@Dashrender opened this thread with a poor hypothetical scenario.

It is something that can apply to an ITSP or consultant, but it is completely not something that will apply to the vast majority of deployments.

They asked for non ad joined management...

ok company is closing. after dinner will put notes here!

it is just winrm, trustedhosts and same user/password/workgroup setup. then you can fly!

@Dashrender said in Managing Hyper-V:

@matteo-nunziati said in Managing Hyper-V:

@Dashrender anyway. If you have to pay, a control system con be obtained buying a windows pro licence every time you deploy a newer hyper-v version, then virtualize it in your WS.

it was windows 8 with hyper-v 2012, then now it is win 10 with hyper-v 2016. what? 300$ every 4 years? feaseable probably...

unfortunately the hyper-v snap-in in windows mmc.exe is a bit poor on some edges.
I've deployed 2 hyper-v servers and setup replica on them just with my snap-in. More complex layout probably will lead to a big issue, as the snap-in has really poor management functions. anyway as @Tim_G said somewhere, you can add the free veeam one to get better overview of resource usage.

not a single pane of glass, but hell LCDs aren't even glass: all plastic

about domain: never tryed hyper-v 2012 but this is what I've done.

Has anyone tried this for Win10 and Hyper-V 2016 since HVRemote doesn't support those, and the page says there are no current plans to update it to support it?

NO wait no HVRemote here. and done the shit on win10 for hyper-v 2016.... I've just hyper-v 2016 AND win 10. and we have NO AD AT ALL HERE!

mmm... let me recheck my motes. maybe an how-to is in the makings

@scottalanmiller said in Sizing the SOHO, SMB, SME, Enterprise and Other Markets:

These are kind of the rough numbers I feel most comfortable with.

• SOHO: 1 - 10 people. The "too small to have AD" category.

OK 1-10 or 1-20 fits here.

• SMB: 10 - 2,000 people. True small business that often can't decide if it is a hobby, pasttime, tax shelter or a business.

weeeeee.....
small here is < 50
medium is from 50 to 250

reall business not hobbies but there is no management or hierarchy.

• SME: 2,000 - 5,000 people. True business with stable finances and acts like a true business, just one that is very small.

over 250, management starts apperaing but not so much levels.

• Medium: 5000 - 10,000 people. No longer small in any way, not a sizeable company needing serious services.
• Large: 10000 - 20,000 people. A serious company but not large enough to through its weight around based on a famous name.
• Enterprise: 20,000+ people. Those on the Fortune 1000 list or just missing it. Big, well known companies with tons of resources where they are big enough to have entire IT stacks internally, you don't need to hop between companies to move up the ladder, there is total efficiency of scale opportunity, etc.

this is far from my perception.

@Dashrender anyway. If you have to pay, a control system con be obtained buying a windows pro licence every time you deploy a newer hyper-v version, then virtualize it in your WS.

it was windows 8 with hyper-v 2012, then now it is win 10 with hyper-v 2016. what? 300$ every 4 years? feaseable probably...

unfortunately the hyper-v snap-in in windows mmc.exe is a bit poor on some edges.
I've deployed 2 hyper-v servers and setup replica on them just with my snap-in. More complex layout probably will lead to a big issue, as the snap-in has really poor management functions. anyway as @Tim_G said somewhere, you can add the free veeam one to get better overview of resource usage.

not a single pane of glass, but hell LCDs aren't even glass: all plastic

about domain: never tryed hyper-v 2012 but this is what I've done.

@scottalanmiller said in Managing Hyper-V:

@wirestyle22 said in Managing Hyper-V:

The issue with that is my lack of powershell knowledge

base knowledge needed to work on Windows. Just how it is.

what mostly hurts me on PS is that it seems more of a scripting language than a proper shell. you need to store a function even to open a VM console. on kvm you have virt-viewer... simple!

@DustinB3403 said in XOA Pricing Model - What might it look like from a US perspective:

@Danp that was exactly my recommendation.

Different teirs of priority, not functionality

Yes postgres here works that way: look!