@scottalanmiller said in How Do You Use USB HD for Veeam on Hyper-V:
@JaredBusch said in How Do You Use USB HD for Veeam on Hyper-V:
Don"t use USB disks.
If you want a USB disk that can be removed, use a NAS with a USB port that can replicate data in a certain folder to the USB.
Or use a NAS with Starwind VTL so that you get the behaviour of tapes. And the protection of RAID.
I'm going to have to look at that
@scottalanmiller said in DID Block Puchases:
@Danp said in DID Block Puchases:
@scottalanmiller said in DID Block Puchases:
That's just weird.
How so? Each DID is independent of the B channel, so I can have a multitude of DIDs and only a few B channels if so desired.
Except it's a weird pairing. If you wanted flexibility to sell one at a time. Not "almost every channel."
But it is a did not a number assigned to a channel.
@scottalanmiller said in XOA Pricing Model - What might it look like from a US perspective:
@DustinB3403 said in XOA Pricing Model - What might it look like from a US perspective:
@Dashrender said in XOA Pricing Model - What might it look like from a US perspective:
OK - in another thread, we're talking about IT generalist, and how they often aren't specialists in any one thing. How does that play into the use of support?
They get to learn the tools you have in house, and become the in house expert.
How many SMBs have things to become experts on? Some, but how many?
Assuming you inhouse accounting software - does that count? I mean the support of installing/configuring/backing up/restoring, etc.
how about backups in general? Even if hosted, there are hopefully backups going on.
the main thing I can think of - is general desktop support - but really, if it's more than a 10 min fix (which I would think would be IT stuff - assuming not hardware), then you should probably be wiping and reloading, right?
MS admits there's a problem, but no fix for any version of Windows 10 yet.
MS has released a patch for Windows 7 for this problem.
I was able to buy one from VOIP.ms.
My main voice vendor sells them in blocks of 5.
@JaredBusch said in Managing Hyper-V:
@Dashrender said in Managing Hyper-V:
@JaredBusch said in Managing Hyper-V:
@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.
Not hypothetical at all - It's Wired's setup.
@wirestyle22 works for a MSP correct? This MSP manages disparate city equipment.
This is ok different than any other MSP scenario.
Nothing on his machine should have always access to disparate networks.
So the thing you are proposing should not exist.
Now if these disparate networks, with various AD domains, are all city networks, then just pick a domain to join all the hypervirors to and move one.
Wired's machine that he is using to manage the Hyper-V for the City, all belong to the city. So for the sake of this conversation, ignore that he actually works for an MSP. Instead consider him an internal IT resource.
Which then moves to you agreeing with the idea of putting all Hyper-V hosts into a single domain for ease of management.
OK - in another thread, we're talking about IT generalist, and how they often aren't specialists in any one thing. How does that play into the use of support?
@scottalanmiller said in XOA Pricing Model - What might it look like from a US perspective:
@Dashrender said in XOA Pricing Model - What might it look like from a US perspective:
@scottalanmiller said in XOA Pricing Model - What might it look like from a US perspective:
@Dashrender said in XOA Pricing Model - What might it look like from a US perspective:
I'm not saying that the IT person doesn't scour forums, read whitepapers, error reports, etc. Not saying that. I'm saying that calling Support is just one more tool in the box.
I agree... once you are in that position of having bought support.
thanks - I think.
You are questioning what to do "given where you are." I'm questioning "why get into that situation."
I was questioning that I think you finally agreed that if it's a tool in your box, that you can and maybe should use it.
As for why get into the situation - well you said you don't buy support when you can avoid it (other than hardware). OK - But can you buy Veeam and keep current with the updates and not buy support? Veeam is just an example.
I know, as you pointed out, that you can buy Windows, and it does not come with support, so sure, don't buy it, use your IT pants to get the job done.
@Mike-Davis said in Managing Hyper-V:
@JaredBusch said in Managing Hyper-V:
@Mike-Davis said in Managing Hyper-V:
In part of my strategy to prevent CryptoLocker or a bad actor from taking out my backups if a computer/server gets infected, I'm not domain joining my hosts now. I realized that even with a share on the network that used a service account, if a hacker elevates privileges and gets domain admin, they can reset the password on the backup service account and then wipe out my backups. If the backup target is not domain joined, they can't do that. Same idea with the host.
I'm curious as to what others are thinking. We love disk to disk backups, but it's really hard to air gap them with out physical interaction.
This is just stupid.
There is not any type of realistic risk for this kind of scenario that does not involve a ton of prior failures.
Within a single organization, there is zero reason to not have the hypervisors domain joined.
There will be no possible way to lose anything because there should be no possible way that a privileged account like domain admin can be compromised without ignoring other best practices.
There are zero day exploits out there. Networks get hacked. I'm trying to limit risk.
I agree with JB, if you are compromised this badly, why care more about your hypervisor than the VMs? I'm assuming the VMs are all part of the domain. Sure with control over the hypervisor, they could kill a whole box faster - but we really don't see that being the case, they aren't killing boxes, they are stealing data, or encrypting it.