Windows Server 2019 (vNext) LTSC Preview – Build 17623 available for download

March 21, 2018 at 7:24 pm in Build 17623, Microsoft Tech Community, Windows Server 2019, Windows Server Insider, WS2019 by Wim Matthyssen

Yesterday Microsoft announced that Windows Server 2019 would be generally available in the second half of 2018, together with System Center 2019. As expected, this next-gen (vNext) Server OS is built on top of Windows Server 2016 and will focus on the following main areas: hybrid, security, application platform and hyper-converged infrastructures. Good to know is that Windows Server 2019 is a Long-Term Servicing Channel (LTSC) release, which means it will have 5 years of mainstream support and 5 years of extended support.

Whit this announcement Microsoft also released the first preview build (17623) of Windows Server 2019 LTSC to the public, which contains both the Desktop Experience as well as the Server Core edition in all 18-server languages.

To get started with the download of this Preview build, you need to be a member of Windows Server Insider program. If you are not yet registered for this Insider program, you can do so over here. Keep in mind that you can sign up with an organization or a personal account.

clip_image002

As a registered Insider, you can head over to the Windows Server Insider Preview download page. Under available Downloads you can now download the 4.2 GB ISO file. This build, which expires on 02/06/18, requires an activation key during setup. The following keys are allowed for unlimited activations:

  • Datacenter Edition 6XBNX-4JQGW-QX6QG-74P76-72V67
  • Standard Edition MFY9F-XBN2F-TYFMP-CCV49-RMYVH

clip_image004

clip_image006

clip_image008

When downloaded you can install the Windows Server 2019 OS from the ISO image on a virtual machine (VM) or on a physical server.

clip_image010

clip_image012

Have fun testing out this build and do not forget to provide your feedback to Microsoft using the Windows Feedback Hub app, or through the Windows Server space in the Microsoft Tech community.

Wim Matthyssen (@wmatthyssen)

Azure Tip: How to find your Subscription ID (GUID)

March 12, 2018 at 10:00 pm in Azure, Azure portal, Azure PowerShell, Azure Subscription ID, Azure Tip, Microsoft Azure, Subscription ID by Wim Matthyssen

 

The Subsciption ID is a 32-digit GUID, which is associated with an Azure Subscription.  Some situations require you to know this Subscription ID, such as when you open a new Azure support ticket. This post will show you how you can quickly retrieve this ID via the Azure portal or via Azure PowerShell.

 

Azure Portal

Open a New Inprivate window in Edge (or any other browser) and browse to https://portal.azure.com where you Sign in with your account.

Select All services and click on Subscriptions which you can find under the GENERAL field.

clip_image002

A new blade, the Subscriptions pane, will open showing all your subscriptions, select the appropriate one and under SUBSCRIPTION ID you will find the corresponding ID you where looking for.

2018-03-12_21-43-47

 

Azure PowerShell

Open a PowerShell window with Administrator privileges.

Type Login-AzureRmAccount and provide your Azure credentials (email address and password).

clip_image006

When you are logged in, all information of your default subscription will be shown and you can find your Subscription ID in the SubscriptionId field.

clip_image008

When you have more than one subscription you can find the Subscription ID of a specific Subscription by typing Get-AzureRmSubscription. This command will list all of your subscriptions, with details like the SubscriptionId, which are associated with the logged in account.

clip_image010

Hope it helps.

Wim Matthyssen (@wmatthyssen)

Microsoft Wireless Display Adapter won’t connect with Windows 10 laptop running Hyper-V

March 1, 2018 at 8:35 pm in Client Hyper-V, Hyper-V, Microsoft Wireless Display Adapter, Miracast, Wi-Fi, Windows 10 by Wim Matthyssen

When delivering workshops at customers most of the time I use my Microsoft Wireless Display Adapter to show my presentations or demo’s on a big screen.

clip_image002

Normally, I only just need to plug in the USB and HDMI connectors from the Wireless Display Adapter to the HDTV, monitor or projector, and click Connect on the Windows 10 Action Center. My display adapter is then listed as on option and I only need to click on it to extend or duplicate my laptop screen. It is so easy and connecting with a Windows 10 device could not be quicker.

clip_image004

However last week while preparing a new Azure workshop, making a connection to my home TV did not go that smooth as usual. When I tried to connect to my display adapter, making a connection took a long time and at the end the message “Couldn’t connect” popped up while the TV was still showing Connecting.

 

clip_image006

clip_image008

After troubleshooting for some time and checking the usual steps (check adapter’s firmware, check Windows Updates, reset the adapter …) I finally figured it out. When making a connection the Wireless Display Adapter uses Miracast, a wireless technology, which makes communication between devices possible on either the 2.4 GHz or 5 GHz wireless frequency bands. The display adapter itself, even if it looks like a sort of HDMI to USB cable, has a full Wi-Fi card and antenna on board which it uses to connect to the wireless adapter on your laptop.

That is where my connection problem was situated. I do a lot of research on my laptop with the use of Client Hyper-V, which enables me to run all sorts of virtual machines (VMs) for testing purposes. For connecting some of those VMs to the Internet, I make use of an internal virtual switch, which uses a shared connection (Internet Connection Sharing) on my wireless adapter.

clip_image010

clip_image012

However, this Windows service causes some changes in the way the wireless adapter works, which in normal circumstances does not disturb anything, except when you try to connect to a Wireless Display Adapter.

So, after removing this sharing option, the Wireless Display Adapter connected as easily as before.

clip_image014

clip_image016

clip_image018

Conclusion

A Microsoft Wireless Display Adapter strongly depends on the wireless adapter in your device to setup communication. Any issues or changes to the wireless adapter in any way can cause connecting problems. If you still want to use Client Hyper-V on your Windows 10 laptop and connect your VM to the Internet with the use of your wireless adapter, I suggest to create an External virtual switch which connects to it. Do not forget to allow the management Operating System to share the wireless network adapter. This setup does not seem to disturb the connection with a Wireless Display Adapter.

Client Hyper-V: Unable to start a VM from saved state (Event ID 3326)

February 26, 2018 at 8:56 am in Client Hyper-V, Event ID 3326, Hyper-V, saved state, virtual machine by Wim Matthyssen

 

Last week while starting a virtual machine (VM) from saved state on my Windows 10 laptop with Client Hyper-V the following error popped up and the VM itself did not power on.

clip_image002

The error itself did not explain a lot why the startup from saved state was failing, but in the Hyper-V event logs (Event Viewer – Applications and Services Logs – Microsoft – Windows – Hyper-V-Worker – Admin) Event 3326 was shown which showed a lot more:

The Virtual Machine ‘VM-W8-HOME’ failed to start because there is not enough disk space. The system was unable to create the memory contents file on ‘C:\_VM\VM-W8-HOME\Virtual Machines\CB9D8995-F1FC-4349-9C35-7728F5B90245′ with the size of 7340 MB. Set the path to a disk with more storage space or delete unnecessary files from the disk and try again. (Virtual machine ID CB9D8995-F1FC-4349-9C35-7728F5B90245)

clip_image004

The error indicates that not enough free space is available on the host which causes problems to start the VM. The View in Disk Management (tap the Windows key + R to open Run, type diskmgmt.msc in the empty box and tap OK) indeed shows that the C: drive only has 2 % free, which is not sufficient to start the VM.

clip_image006

After determining that the error was caused by a lack of disk space, I cleaned up my C: drive by deleting some unnecessary and temporary files to free up some more space (at least 4096 MB which equals the amount of virtual memory of the VM). As a result, the VM started up again.

clip_image008

Conclusion

To start a VM from saved stated the amount of free disk space should at least equals the amount of virtual memory allocated to the VM. For example, if your VM has 4096 MB of virtual memory assigned, you should have at least 4096 MB available on the drive. If you do not have enough disk space available you should free up some space to be able to start the VM. As a recommendation you should always keep at least 10 – 20 % of free disk space available.

Azure Backup Server: SQL 2016 AlwaysOn protection fails with Internal error code 0x80990F75

January 23, 2018 at 3:54 pm in 0x80990F75, Azure, Azure Backup, Azure Backup Server, Microsoft Azure Backup Server, Microsoft Azure Backup Server v2, SQL Always On Availability Groups, SQL Server 2016 by Wim Matthyssen

While setting up a new backup job to protect a SQL Server 2016 AlwaysOn Availability Group (AG) using Azure Backup Server (MABS), the job failed and ended up with the Protection Status – Replica is inconsistent.

clip_image002

Because this status does not say a lot about what exactly went wrong, I looked up the Critical alert under the Monitoring tab. There the following more detailed message was shown:

The DPM job failed for SQL Server 2016 database <DBname> on <serverName > because the SQL Server instance refused a connection to the protection agent. (ID 30172 Details: Internal error code: 0x80990F75)

clip_image004

This issue occurs because when you create a new Availability Group by default, the location where backups should occur is set to Prefer Secondary and the setting Make Readable Secondary is set to No, which always results in MABS getting the above error.

clip_image006

To resolve the issue, open SQL Management Studio and connect to server instance that hosts the primary replica. Expand the Always On High Availability node and the Availability Groups node. Click the availability group whose replica you want to change and expand Availability Replicas.

clip_image008

Right-click the Availability Replica, and click Properties (be sure to repeat this steps for all Availability Replicas you want to backup with MABS).

clip_image010

In the Availability Replica Properties dialog box, set the value of the field Readable secondary to Yes. Click OK to save the new setting.

clip_image012

When you now run the Perform consistency check … job on the failed Protected member in the MABS console, the status should end up in OK.

If not, and the status still ends up in Replica is inconsistent, be sure to check out my previous blog post http://scug.be/wim/2017/06/19/microsoft-azure-backup-server-unable-to-configure-protection-for-a-sql-database-id-3170-and-33424/ to see if the user NT Authority\SYSTEM has sysadmin rights on the SQL Server instance(s).

If on the other hand the status ends up in Online recovery point creation failed, just right-click the Protected member again and select Resume azure backups…

I hope this helps and if you have any questions feel free to contact my through my Twitter handle.

Wim Matthyssen (@wmatthyssen)

Azure Backup Server: Remove Unprotected computers with protection agent installed

January 4, 2018 at 8:36 am in Azure Backup Server, MABS, MABS v2, Microsoft Azure Backup Server, Microsoft Azure Backup Server v2, PowerShell by Wim Matthyssen

While doing maintenance on a customer’s Azure Backup Server (MABS), I was unable to remove some unprotected computers in the MABS console. The Remove resulted in a fail and the error page didn’t show a direct reason why this occurred.

clip_image002

clip_image004

clip_image006

clip_image008

But no worries, this is where PowerShell came into the rescue to force the removal of the broken agent from the DPMDB database. Take notice that this solution will not uninstall the protection agent from the (un)protected computer. When required, you still need to uninstall that agent manually.

Open the DPM Management Shell and run the following command, it will prompt you for the rest of the parameters one at a time (always use the FQDN name for both parameters).

You can also run this command with all paramaters already filled in. Just replace [DPMServerName] with the name of the MABS server and [ProtectedComputerName] with the name of the (un)protected computer that must be removed.

image

Like you can see the agent(s) are now removed from the MABS console.

clip_image012

Hope it helps.

Wim Matthyssen (@wmatthyssen)

Azure Interactives

December 27, 2017 at 10:46 am in Azure, Azure Interactives, Cloud by Wim Matthyssen

 
Azure is a growing collection of integrated services that IT professionals and developers can use to build, deploy or manage applications in the cloud. With so many services now available, most of the time it is somewhat of a challenge to find the right information. To help you have a clear overview, Microsoft has released a new beta webpage, the Azure Interactives, which will guide and introduce you to all the various services that are available on Azure.

clip_image002

From this interactive page, you can easily navigate to the three experiences listed below, to display and find all information you want.
 

Azure Products

From here, you can easily select a specific Azure product and find all information, documentation and pricing links about it.

clip_image004

Cloud design patterns

This page will give you architecture guidance and lists common problems and patterns for your cloud applications.

clip_image006

Azure security + operations management

This page will give you a guide on how to efficiently manage and protect your Azure and on-premises resources.

clip_image008

Have fun checking this all out.

Wim Matthyssen (@wmatthyssen)

MABS v2: Unable to install DPM Remote Administration console on a W2K8 R2 SP1 server because mi.dll is missing

December 12, 2017 at 9:32 am in Azure, Azure Backup, Azure Backup Server, DPM Remote Administration, mi.dll, Microsoft Azure Backup Server, Microsoft Azure Backup Server v2, PowerShell, WMF 5.1 by Wim Matthyssen

While installing the DPM Remote Administrator console on a Windows Server 2008 R2 SP1 (W2K8 R2 SP1) for remote administration of a customers Microsoft Azure Backup Server (MABS) v2, I stumbled upon the below error message, which resulted in the setup being aborted:

The Program can’t start because mi.dll is missing from your computer. Try reinstalling the program to fix this problem.

clip_image002

This error shows up because one of the following requirements is not installed: Windows Management Framework 4.0, .NET Framework 4.0 or Visual C++ Redistributable for Visual Studio 2012 Update 4

needs to be installed to be able to deploy the DPM Remote Administration console on a W2K8 R2 server.

To fix the issue, I checked if all latest Windows Updates were installed. Afterwards I installed the Windows Management Framework 5.1 (WMF 5.1), .NET Framework 4.0 and the Visual C++ Redistributable for Visual Studio 2012 Update 4 on the W2K8 R2 SP1 server, which can be downloaded from the link above. To ease up and to automate the installation, you can use the below PowerShell script (copy and/or save as .ps1) to get things downloaded somewhat faster.

clip_image004

When the C:\Temp folder opens after the downloads, run Install-WMF5.1.ps1. (PowerShell window with Administrator privileges) to install WMF 5.1

clip_image006

clip_image008

clip_image010

clip_image012

Before rebooting, also run the two other packages, dotNetFx40_Full_setup.exe and vcredist_x64.exe (if required). When done reboot the server.

clip_image014

When the server is rebooted, check if mi.dll exists under C:\Windows\System32.

clip_image016

You can now start Setup.exe (Microsoft Azure Backup Server folder) and start the DPM Remote Administration installation.

clip_image018

clip_image020

Hope this post helps whenever you face the same problem.

Wim Matthyssen (@wmatthyssen)

MABS v2: Error [0x8007007b] when performing a System State Backup on a DC running on a VMware VM

November 23, 2017 at 8:33 am in Azure, Azure Backup, Azure Backup Server, Cloud, Error [0x8007007b], MABS, MABS v2, Power, PowerShell, VMware by Wim Matthyssen

While configuring a Microsoft Azure Backup Server (MABS) v2 at a customer site, I encountered a problem while performing a System State Backup of their domain controllers (DC’s). The Protection Status showed Replica is inconsistent.

clip_image002

When looking in the Monitoring tab, following detailed message is show:

DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 517, WSB Error Code: 0x605A140).(ID 30229 Details: Internal error code: 0x8099ED0)

clip_image002[6]

Because the first part of making a System State Backup is done by the local Windows Server Backup (WSB) feature, logon to the protected server and open Windows Server Backup (Server Manager – Tools – Windows Server Backup). There a message was shown indicating that the last backup has Failed.

clip_image006

To view the error message a bit more in detail, open the Windows Server backup log file (with the exact date and timestamp) located in C:\Windows\Logs\WindowsServerBackup.

clip_image008

In the log file the following error message was shown:

Error in backup of C:\windows\\systemroot\ during enumerate: Error [0x8007007b] The filename, directory name, or volume label syntax is incorrect.

clip_image010

When looking in the Event Viewer (Application log) I could also find the following errors (CAPI2 – 513, Backup – 517):

Event ID 513

Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.

Details:

AddLegacyDriverFiles: Unable to back up image of binary Microsoft Link-Layer Discovery Protocol.

System Error:

Access is denied.

Event ID 517

The backup operation that started at ‘‎2017‎-‎11‎-‎16T15:16:22.000076700Z’ has failed with following error code ‘0x80780049′ (None of the items included in backup were backed up.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

clip_image012

clip_image014

Because all those errors descriptions do not really tell you what exactly is going wrong causing the backup to fail, you need to use the Diskshadow command-line tool to determine if there is an issue with the functionality of the VSS service or any of the application independent VSS writers.

To open the Diskshadow tool interface start PowerShell with elevated privileges and enter the below commands to write the output to a logfile.

clip_image016

When the logfile (c:\out.txt) is created open it with notepad and search for \\.

clip_image018

clip_image020

In my case, I found out there was an issue with the vsock.sys driver, which is part of the VMware vSockets Service and which is usually located in the C:\Windows\system32\drivers folder.

To fix the issue open the Registry Editor and go to the following location, HKLM\system\controlset001\services\vsock and changed the Start value to 1.

clip_image022

clip_image024

clip_image026

Also change the ImagePath entry from \SystemRoot\system32\DRIVERS\vsock.sys to system32\DRIVERS\vsock.sys.

clip_image028

clip_image030

When you have changed all those registry keys, logon to your MABS server and right click the failed System State backup and Perform a consistency check… (be aware that this could take a while). If the fix also solved your issue it would show OK when completed.

clip_image032

clip_image034

Hope this helps whenever you face the same error in your MABS environment. If you have any questions feel free to contact me trough my Twitter handle.

Wim Matthyssen (@wmatthyssen)

How to run the Hyper-V role on a VMware VM

November 21, 2017 at 10:16 am in Hyper-V, MABS v2, Nested Virtualization, PowerShell, VMware, Windows Server 2016 by Wim Matthyssen

When you install Microsoft Azure Backup Server (MABS) v2 on a Windows Server 2016, one of the prerequisites (MABS v2 prerequisites installation script) is that you install the Hyper-V role and the Hyper-V PowerShell feature.

However, while I was installing a new MABS v2 for a customer on a VMware VM (vSphere 6.5), I encountered following errors in the Hyper-V event log (41, 15350, 15340) after the Hyper-V role was installed.

Event 41 showed the following error message:

Hypervisor launch failed, Either VMX not present or not enabled in BIOS.

clip_image002

When I ran the Get-WindowsFeature in PowerShell it seemed Hyper-V was installed correctly. But this was not the case.

clip_image004

To fix the errors and get Hyper-V running like it should you need to enable Nested Virtualization for the VMware VM. To do so, shut down the VM and open the Virtual Machine Settings. Then go the Virtual Hardware tab and open the CPU options. There you need to check the box Expose hardware assisted virtualization to the guest OS. Also set CPU/MMU Virtualization to Hardware CPU and MMU.

clip_image006

When you now start the VM all Hyper-V related errors should be gone and all necessary Hyper-V services should be running.

clip_image008

clip_image010

Hope this blog post will help you whenever you need to setup Hyper-V on a VMware VM.

Wim Matthyssen (@wmatthyssen)