Last week, Veeam released the new Veeam Service Provider Console v4, the latest version of what was previously called Veeam Availability Console. I run my own VAC (now VSPC) environment, so I decided to take the opportunity to upgrade my lab to the latest version to learn the upgrade process.
Last week, I explained how to manually connect standalone computers to Veeam Availability Console. This time we will try to automate this process as much as possible.
Veeam Availability Console has been designed for multiple use cases, and one of them is to manage large fleets of computers. But what about those standalone machines we have lying around? It could be the last physical server we have in the datacenter, or a laptop of a consultant that is always travelling around. How can we deal with those? I involved my family’s computers to find out.
In a previous post I explained how to publish VAC (Veeam Availability Console) web service over Internet, to allow administrators and tenants to consume it. This time, we’ll complete the publishing by adding a proper SSL certificate to the Web Interface.
Veeam Availability Console is completely web-based. For this reason, it’s extremely easy to consume it, and the idea behind the product is that the console can be used directly by users. To do so, the Console itself has to be published over Internet, following a few but important steps.
In the previous posts of this series, we completed the configuration of Veeam Availability Console, and onboarded our first customer. The customer logged into his own account and configured the different services. Now in this fourth part, we are going to connect a remote Veeam Backup server in order to monitor it.
In the previous posts of this series, we completed the configuration of Veeam Availability Console and on-boarded our first customer. In this third part, we are going to access the Console as a new customer, to so learn what we can do there.
In the previous post of this series, we installed and started the configuration of Veeam Availability Console. In this second part, we are going to look at the rest of the initial configuration, and plan for the first customer onboarding.