Windows server 2016
67 TopicsStorage Spaces Direct using Windows Server 2016 virtual machines
First published on MSDN on May 27, 2015 Windows Server 2016 introduces Storage Spaces Direct (S2D), which enables building highly available storage systems which is virtual shared storage across the servers using local disks.16KViews3likes0CommentsExchange 2016 / 2019 demands to install a prerequisite on an OS not supported by the prerequisite
Hi there, I would like to get some feedback and raise awareness about an issue I have encountered at a customer which lead me to question the prerequisite UCMA 4.0 as part of Exchange 2016 / 2019 mail role on Server 2016 / 2019. by fact UCMA is not supported on either of these Windows Server OS (refer download prerequisites) The one that is supported is UCMA 6.0 The docs appear like nothing changed since Exchange Server 2013, which is not the case as there have been 2 subsequent major releases of UCMA since. "The UCMA 4.0 runtime is specifically required. If you’ve installed any other version of UCMA, you are in a non-supported state. The Exchange team is responsible for supporting their pre-requisites." Is this statement bonkers or would the Exchange Server seriously argue against your own mesh of supportability which seem to exclude your prerequisites? I would like to plea: change docs, change version checks of UCMA in setup / CUs. Update to UCMA 6.0 when Exchange is running on Server 2016 / 2019 (for Ex2019 no question as only 2019 is supported at the moment) Fix the UCMA 6.0 setup to no demanding the outdated C++ Redist 2015-2019 x64 14.12. but also accepting the currently secured version 14.28. Dear Exchange Team, thank you for your time and feedback.1.1KViews2likes1CommentWindows Server 2016: Settings -> Accounts crashes
On a Windows server 2016 we recently installed, whenever ANY user goes to Settings -> Accounts, it starts loading and crashes. The event log shows an error every time (see below). All users are local and the system is not in a domain. We have tried several things to resolve it, but the issue persists. Some things we have tried: creating a new user and testing it on there system file check (sfc /scannow) Windows trouble shooter (as well as the downloadable Windows update troubleshooter) reinstalling the Settings app (Get-AppXPackage | foreach {Add-AppxPackage -DisableDevelopmentMode - Register "$($_.InstallLocation) \AppXManifest.xml"}) Event viewer error log: Faulting application name: SystemSettings.exe, version: 10.0.14393.82, time stamp: 0x57a55dc6 Faulting module name: usercpl.dll, version: 10.0.14393.2608, time stamp: 0x5bd1347f Exception code: 0xc0000005 Fault offset: 0x000000000000d297 Faulting process id: 0xb80 Faulting application start time: 0x01d5a36c63ad0ee2 Faulting application path: C:\Windows\ImmersiveControlPanel\SystemSettings.exe Faulting module path: C:\Windows\System32\usercpl.dll Report Id: dbe77bad-e235-499e-b0c2-13956fa9c637 Faulting package full name: windows.immersivecontrolpanel_6.2.0.0_neutral_neutral_cw5n1h2txyewy Faulting package-relative application ID: microsoft.windows.immersivecontrolpanel6.7KViews2likes9Comments