Home

Technology

Health

Travel

Foods

Housing

Digital Marketing

Announcing Windows Server vNext Preview Build 18917

Wednesday, June 19, 2019

Announcing Windows Server vNext Preview Build 18917

Hello Windows Insiders!

Today, we are pleased to launch a new privileged preliminary compilation of the six-monthly editions of the Windows Server VNext Channel and the 1906 Preview of the Windows Administration Center.

Content available
  • Semi-Annual Preview of Windows Server vNext
Server Core Edition is available in the 18 supported server languages ​​in ISO format and in English only in VHDX format.
  • Compatibility of the Windows Server Core application Preview of FoD
  • Windows Server Language Packages
  • Windows 1906 Administration Center
The symbols are available in the public symbol server. See Update in the Microsoft Symbol Server blog post and Use the Microsoft Symbol Server. The corresponding Windows Server container images will be available through the Docker Hub. For more information about Windows Server containers and insider constructions, click here.

The following keys allow unlimited activations of the semiannual previews of the Windows Server channel
  • Server standard: V6N4W-86M3X-J77X3-JF6XW-D9PRV
  • Server data center: B69WH-PRNHK-BXVK3-P9XF7-XD84W
This preview of Windows Server will expire on July 31, 2020.

Windows News Preview to the Administration Center 1906

Thanks for staying up to date on the Windows Administration Center tour! As our first draft version after the last version generally available in April, the 1906 preview of the Windows Administration Center includes several new preview features:

Update tool: you can now select individual Windows updates to install, a higher user request.

Windows Management Center connectivity configuration: we have listened to users who are in completely disconnected environments who prefer to have a configuration in the Windows Administration Center where they can specify that they are disconnected, so there will be no notifications about the hybrid functionality of Azure, Extensions Updates, or other actions that require public access to the Internet.

To try, enter msft.sme.shell.connectivity as an experiment key in Settings-> Development -> Advanced, then visit the new Connectivity configuration item. You can select Gateway to restrict online access, or Azure and Gateway if you want to access only Azure features, but nothing else on the public Internet. In a future version, this menu item will also provide you with a complete list of URLs so that you can configure your firewall to block all traffic by default and explicitly allow only traffic specific to known services.

Virtual machines tool:

  • Import / export virtual machine: we have added the Import / Export buttons to the Virtual Machines tool to import virtual machines and export virtual machines to a local volume or remote file share. When importing virtual machines, you have the option of creating a new virtual machine ID and copying the files from the virtual machine or using them in place.
[Known Issue] When importing a virtual machine and creating a copy of the virtual machine files, if you choose a local volume or a cluster shared volume as the destination, it will be saved in the root folder of the volume instead of in the folder " Hyper-V. " This will be repaired in the next release. For now, you can use the Browse button to manually navigate to the actual folder to which you want to import the virtual machine.

  • Virtual machine tagging: Similar to the user interface for tagging connections in the Windows Administration Center, you can now tag virtual machines on a Hyper-V server! In the Inventory tab of the virtual machines tool, an "Edit labels" button was added to manage the labels. These tags are saved on the Hyper-V host server and can be accessed by other administrators.
[Known issue] Labeling of virtual machines is not yet supported in the failover cluster or in the user interface of the hyper-converged cluster. Labels will not be displayed in the grouped VM view and administration labels in this view may overwrite or inadvertently delete existing labels.

  • Performance improvements: significant performance improvements have been made to reduce the page load time in the virtual machines tool.

Improvements in Azure integration functionality:

  • The Azure hybrid services tool now loads content from a source, so new services can be added at any time without an update of the entire tool.
  • From the Account menu in the configuration, you can now switch between multiple Azure accounts.
  • When you add a server or Windows PC to your list of connections, you have a new option to log in to Azure and explore your Azure resources for the specific server or PC.
[Known Issue] At this time, the Windows Administration Center only lists its Azure resources, but can not guarantee connectivity.

Ecosystem Developers in the Windows Management Center: You will find a new menu item: Performance Profile, in the Windows Administration Center configuration under the heading Development. This new tool will record your browsing session, tracking the times of each request and page load, so you can identify opportunities to improve performance.

How to download

Registered insiders can navigate directly to the Windows Server Insider Preview download page. See the Additional Downloads drop-down menu for the Windows Administration Center and other applications and add-on products. If you have not yet registered as an internal user, see HOW TO BEGIN WITH THE SERVER on the Windows Insiders for Business portal.

Windows team value your comments!

The most important part of a frequent publication cycle is to listen to what works and what needs to be improved, so your comments are highly valued. For Windows Server, use your Windows 10 registered Insider device and use the Feedback Hub app. In the application, choose the Windows Server category and then the appropriate subcategory for your comments. In the Comment title, indicate the build number you are providing as shown below:

[Server #####] Title of my comments

See Share comments in Windows Server through Feedback Hub for specific information. We also encourage you to visit the Windows Server Insiders space in the Microsoft Tech Communities forum to collaborate, share and learn from the experts.

For the Windows Administration Center, send us your comments through UserVoice. We also encourage you to visit the Windows Administration Center space in the Microsoft technology communities.

Terms of use

This is a preliminary version software; It is provided for use "as is" and is not supported in production environments. Users are responsible for installing any update available from Windows Update. All preliminary version software made available through the Windows Server Insider program is governed by the Insider Terms of Use.

Known issues: Preview of the Windows 1906 Administration Center

  • Network: If you have configured an Azure network adapter, the address value of the Microsoft Azure virtual network gateway will be formatted as a hyperlink but will result in an invalid address. [20420185]
  • Incorporating Azure Update Management: If you have already installed the MMA agent, or if you install the agent with the new Azure Monitor integration, you can not integrate the server with Azure Update Management through the user interface in the Windows Administration Center . If Azure Update Management is already configured (either through the Administration Center or otherwise), you can still integrate the server into the Azure Monitor virtual machine information solution through the user interface of the Azure Monitor. Windows administration.
  • Chrome users can see 403 forbidden responses from WAC after the update. The solution is to close * all * the open tabs of Chrome (make sure there are no running chrome.exe processes). After restarting Chrome, everything will work normally. We have an error message that clarifies it, but Chrome users with multiple Windows administration center tabs open during the update will not see the message.

Correction of Windows server errors

  • Fixed a problem whereby the last login time of a local user of "net user name" may not register even when the user has accessed the server's shared network.
  • Fixed a problem when trying to update the Server Standard to the Server Data Center, which results in an error "Error: 1168. An error occurred while applying the configuration of the target editing component." The update can not continue. "
  • An issue was solved when the trust of the domain was broken when the recycle bin configured in the domains that carry the trust.
  • Fixed an issue where the user's access record created an invalid file in% Systemroot% \ System32 \ LogFiles \ Sum.

Windows Server Known Issues

  • The use of ntdsutil.exe to move the files in the Active Directory database may fail with the error: "Failed to move the file with the source <original_full_db_path> and Destination <new_full_db_path> with error 5 (Access Denied). "
  • The automatic logon configured by logon scripts may not work correctly
  • The icon status of the online / offline files and the status bar may not show a precise status. OfflineFiles event manager records will show the actual status of the files.
  • PowerShell may report an incorrect NdisPhysicalMedium result on the IPoIB adapter
  • It applies only to App Compat FOD MMC.exe: Multiple add-ons of Active Directory Users and Computers added to the same instance of MMC.exe may display inconsistent or null data in part of the add-ins after adding additional columns to the view of the user interface. Wokaround: for managing UI users, use a separate MMC for each ADUC add-in (DSA.MSC).
  • Scheduled startup tasks may not run. An event is logged, ID 101 with error code ERROR_LOGON_FAILURE when the error occurs.
  • DCPromo fails if the physical NIC interface metric is larger than the Loopback interface
  • Renaming a domain controller can update the incorrect attributes in Active Directory (msDS-AdditionalDnsHostName, msDS-AdditionalSamAccountName, and servicePrincipalName) leaving the orphan data behind (ValidateSPNsAndDNSHostNameActual)
  • The domain controller renames the properties of the incorrect attributes in AD leaving behind the orphaned data (ValidateSPNsAndDNSHostNameActual). This can be reproduced by adding a new FQDN, configuring it as a primary, restarting the domain controller and then deleting the current FQDN. Checking the attributes msDS-AdditionalDnsHostName, msDS-AdditionalSamAccountName, and servicePrincipalName will have incorrect values.
  • Self-service users can not install on-demand feature packets (FOD) and language packs for the Windows Server Update Service (WSUS), the System Center Configuration Manager (SCCM), and the autopilot scenarios .
  • After disabling and re-enabling the SR-IOV capability in a NIC on Linux VM, Windows may report "Failed to apply changes to the Network Adapter". The details will show "The Hyper-V virtual machine management service encountered an unexpected error: the call was canceled by the message filter. (0x80010002)." A side effect of this failure is that the VM will remain in a state of Stop when shutting down the VM and can not be restarted without a power reset
  • When implementing a controller VM, after the last restart in the deployment process, the controller VM is not visible.

No downtime for Hustle-As-A-Service,
Lady <3

No comments: