I got Veeam One 9 Update 1 installing right now, thanks to a minor issue with random flapping on an esxi host. Next will be Veeam Endpoint. Any chance you can hook me up with B&R 9 Update 1 and make my Veeam suite fully up to date?

@JaredBusch said:

With a Windows guest, you can restore directly from the backup, without needing to mount an FLR appliance.

Is this with Hyper-V, VMware hypervisors or both?

@scottalanmiller I would also say people have the same view of MS Windows updates. There have been several over the past couple of years that have really screwed some people. Just like a hosted outage can affect a large number of users, so can these updates. The main difference, for many, is they have a degree of control over when/if the updates are applied but is not necessarily true of hosted services. So when something breaks it tends to be more surprising because they weren't expecting a change.

@Carnival-Boy I agree. Nothing is 100% certain except failures will happen. Systems and services are much more reliable than they used to be but no matter where the system or service resides there can be a problem. Ideally, hosted services provide economies of scale that you can't get without huge expenditures, in-house, which usually mitigate a lot more risk and generate more reward.

@scottalanmiller I agree we are seeing it differently. I still can't see your side after rereading it. LOL - Oh well, agree to disagree as some say.

@scottalanmiller I can only go by what the OP said in his summary, which did indicate a change on the 365 side they claimed MS told them was the root cause and then was further borked by a tech that was in over his head.

@scottalanmiller It's OK. I can't say that there is enough "evidence" that points exclusively to the on-premise side of things but I guess it doesn't matter. I am still planning on migrating to hosted Exchange.

@scottalanmiller Ha! But first MS updated something on O365 Exchange that was incompatible with Exchange 2010. It was then followed by the tech running the wizard, which broke the on-premise side. Insult to injury performed by MS.

@DustinB3403 said:

Summary,** MS updated something on O365 Exchange **that is no longer compatible with Exchange 2010 on premise, using the wizard broke our mail flow connector. I not being an exchange admin (nor office 365 admin) would have known where this issue was or how to fix it.

@scottalanmiller If he didn't have 365, the problem wouldn't have existed because MS introduced a change to the 365 side that broke his hybrid setup. Either, full hosted or full on-premise would not have been impacted.

@scottalanmiller You could also look at it as 365 was the problem too

That being said, I will be migrating from on-premise to 365 within the next year.

@wirestyle22 Hit me up if you need more info. Also, I think only certain plans let you use click to run. I can't think of how they would prevent you from using it, as I don't think you put any identifying info in until after everything has been installed and the user logs in to activate the license.

Can it be that I have some 2016 and some 2013 installs as to why it allows me 10 standard (non mobile) devices?

The way it works is that it uses a script and an xml file with settings to download the file. You can run it as a startup script via GPO so they don't need to be admins. None of my users are either.

@Dashrender You deploy using the Click to Run tool. Which sounds easier than it is to setup.

@JaredBusch I saw that same screen but didn't post the whole thing.

I will try adding another laptop and see.

I activated office from an existing instance that comes sort of pre-loaded on a Dell and it told me I was using 5 of 10. Now I am using 6.

@wirestyle22 Nope. desktop and laptops running windows 7-10 Pro or enterprise.