In the previous topics, we have installed and updated Veeam B&R 9.5. Then we have connected Veeam to vCenter 6.5 to get visibility on VMware VM and backup them. To finish, we have added a backup repository to store backup files. Now we can backup a virtual machine. Once we have some restore points, we can also recover the VM.
Last year I have written a topic on Starwind to create VMs from PowerShell. That enables to automate the creation process without using a GUI, either from Virtual Machine Manager or Hyper-V Manager. But a VM deployment is not finished when the VM is created but when the application is deployed. Before deploying the application, the OS must also be installed and specialized. This topic shows you the method I use to deploy and specialize a VM without a single click.
If you read this documentation (Implicit Answer File Search Order section), you can see that we can specialize the OS from unattended file. This unattended.xml file will be placed in C:\Windows\Panther\Unattend. To prepare the unattended file, I use ADK (Assessment Deployment Kit). When you install the ADK, select Deployment Tools. Then you can open Windows System Image Manager.
On October 1st, Microsoft Exchange Team released the new Exchange Server 2016. Microsoft has been testing and improving on millions of mailboxes in their Office365 environment before releasing the product on-premises. I will describe in this article a step-by-step guide for the installation of Microsoft Exchange Server 2016. The installation considers:
Because Windows PowerShell is a powerful tool that every sysadmin would know, I will use PowerShell to perform the installation. But If you prefer the graphical interface, you can use it!
Microsoft releases a new version of Azure AD Connect (previous was called DirSync) that help you to synchronize your on-premises Active Directory to Azure AD. 2 new functionalities appear with this new version:
What works for 100 users very often doesn’t work for 10,000, and vice versa. Few vendors worry about making software created for the enterprise meet the needs of the SMB. Those who try to fit both worlds, rarely succeed.
Extend Active Directory to Microsoft Azure is a common scenario when you implement hybrid cloud. For example, protected VM with Azure Site Recovery may need access to Active Directory even if On-Premise datacenter is unreachable. You can also extend your Active Directory to Azure when you use production workloads in Azure VMs to avoid to implement a new forest or to avoid to use the VPN connection for all Active Directory workloads. In this topic, we will see how to extend the Active Directory to Microsoft Azure.