– [DISCUSSION] Windows 10 Enterprise (N) LTSC | Page 93 | My Digital Life Forums
This document does not provide you with any legal rights to any intellectual property in any Microsoft product.
You may copy and use this document for your internal, reference purposes. All rights reserved. This product contains graphics filter software; this software is based in part on the work of the Independent JPEG Group. Some new features work best on a Windows Server physical host running Hyper-V. Microsoft server management and application workloads – Application upgrades should include migration to Windows Server See the compatibility list. Follow migration guides as applicable.
ISV application workloads – Upgrades to Windows Server should use application-specific guidance. Complete options for moving servers running custom or “in-house” applications on older versions of Windows Server to Windows Server There are more options than ever before to help you and your customers take advantage of features in Windows Server , with minimal impact to your current services and workloads.
Try out the latest operating system with your application by downloading the evaluation version of Windows Server for testing on your premises. Once testing is complete and quality confirmed, you can perform a simple license conversion with a retail license key requires restarting. Microsoft Azure can also be used on a trial basis for testing to ensure your custom application will work on the latest server operating system.
Once testing is complete and quality confirmed, migrate to the latest Windows Server version on your premises. Or alternatively, once testing is complete and quality confirmed, Microsoft Azure can be used as the permanent location for your custom application or service.
This allows the old server to remain available until you are ready to switch over to the new server in Azure. In most cases, Microsoft Azure can be used to host the same application on the older version of Windows Server that it is running on today. Migrate the application and workload to a virtual machine with the operating system of your choice by using Azure Marketplace images.
The Software Assurance program for Windows Server provides new version rights benefits. Along with a list of other benefits, servers with Software Assurance can be upgraded to the latest version of Window Server when the time is right, without having to purchase a new license. Additional resources Features removed or deprecated in Windows Server For general server upgrade and migration options, visit Upgrade and conversion options for Windows Server The process of moving to Windows Server might vary greatly depending on which operating system you are starting with and the pathway you take.
We use the following terms to distinguish among different actions, any of which could be involved in a new Windows Server deployment. Installation is the basic concept of getting the new operating system on your hardware. Specifically, a clean installation requires deleting the previous operating system. Migration means moving from your existing operating system to Windows Server by transferring to a different set of hardware or virtual machine.
Migration, which might vary considerably depending on the server roles you have installed, is discussed in detail at Windows Server Installation, Upgrade, and Migration. License conversion In some operating system releases, you can convert a particular edition of the release to another edition of the same release in a single step with a simple command and the appropriate license key.
Upgrade means moving from your existing operating system release to a more recent release while staying on the same hardware. This is sometimes called “in-place” upgrade. Starting with version Upgrading previous retail versions of Windows Server to Windows Server The table below briefly summarizes which already licensed that is, not evaluation Windows operating systems can be upgraded to which editions of Windows Server Note the following general guidelines for supported paths: Upgrades from bit to bit architectures are not supported.
All editions of Windows Server are bit only. Upgrades from one language to another are not supported. Upgrades from pre-release versions previews of Windows Server are not supported. Perform a clean installation to Windows Server Upgrades that switch from a Server Core installation to a Server with a Desktop installation or vice versa are not supported. Upgrades from a previous Windows Server installation to an evaluation copy of Windows Server are not supported.
Evaluation versions should be installed as a clean installation. If you do not see your current version in the left column, upgrading to this release of Windows Server is not supported. If you see more than one edition in the right column, upgrading to either edition from the same starting version is supported.
Consult the specific TechNet Library topics for each server role you intend to upgrade for details of additional steps that might be required.
Converting a current evaluation version to a current retail version You can convert the evaluation version of Windows Server Standard to either Windows Server Standard retail or Datacenter retail. Similarly, you can convert the evaluation version of Windows Server Datacenter to the retail version. Before you attempt to convert from evaluation to retail, verify that your server is actually running an evaluation version. To do this, do either of the following: From an elevated command prompt, run slmgr.
From the Start screen, open Control Panel. Open System and Security, and then System. View Windows activation status in the Windows activation area of the System page. Click View details in Windows activation for more information about your Windows activation status.
If you have already activated Windows, the Desktop shows the time remaining in the evaluation period. For Windows Server Essentials: You can convert to the full retail version by entering a retail, volume license, or OEM key in the command slmgr. If the server is running an evaluation version of Windows Server Standard or Windows Server Datacenter, you can convert it to a retail version as follows: 1.
If the server is a domain controller, you cannot convert it to a retail version. In this case, install an additional domain controller on a server that runs a retail version and remove AD DS from the domain controller that runs on the evaluation version. Read the license terms. Make note of the edition ID, an abbreviated form of the edition name.
The server will restart twice. For the evaluation version of Windows Server Standard, you can also convert to the retail version of Windows Server Datacenter in one step using this same command and the appropriate product key.
Tip For more information about Dism. Make note of this edition ID, an abbreviated form of the edition name. Converting a current retail version to a current volume-licensed version At any time after installing Windows Server , you can freely convert it between a retail version, a volumelicensed version, or an OEM version. The edition remains the same during this conversion. If you are starting with an evaluation version, convert it to the retail version first, and then you can inter-convert as described here.
For more information about installation and upgrades, see Windows Server Installation, Upgrade, and Migration. Yes, when the server is removed by the cluster for upgrade and then added to a different cluster. Not while the server is part of a cluster. Hyper-V Yes. This information is for quick reference and is not intended to replace the individual product specifications, requirements, announcements, or general communications of each individual server application. Refer to official documentation for each product to fully understand compatibility and options.
For customers and software vendor partners looking for more information on Windows Server compatibility with non-Microsoft applications, visit the Commercial App Certification portal. Here are the details about the features and functionalities that we removed in Windows Server, version TIP You can get early access to Windows Server builds by joining the Windows Insider program – this is a great way to test feature changes.
Have questions about other releases? Check out the information for Windows Server , and Windows Server, version The list is subject to change and might not include every affected feature or functionality. Features we removed in this release We’ve removed the following features and functionalities from the installed product image in Windows Server, version Applications or code that depend on these features won’t function in this release unless you use an alternate method.
Some features have been replaced with other features or functionality, while others are now available from different sources. NOTE Please note that some of the features and roles described below are not included in the Server Core installation option, which is provided in Windows Server, version They are present in the Server with Desktop Experience installation option, which we last released with Windows Server and will release again in Windows Server If you have feedback about the proposed replacement of any of these features, you can use the Feedback Hub app.
We’re no longer investing in this feature, and there are no devices available that support it. Please use native IPv6 support instead. Instead, the Microsoft Symbol Server is moving to be an Azure-based symbol store.
If you need the Windows symbols, connect to the Microsoft Symbol Server to cache your symbols locally or use a manifest file with SymChk.
If you need to deploy these roles as part of your Remote Desktop infrastructure, you can install them on Windows Server with Desktop Experience. These roles are also included in the Desktop Experience installation option of Windows Server If you need an easy-to-use server solution for small-tomedium businesses, check out our new Microsoft for business solution, or use Windows Server Essentials. It is intended for IT professionals who are updating operating systems in a commercial environment.
This list is subject to change in subsequent releases and might not include every affected feature or functionality. Features removed from Windows Server, version Windows Server, version contains the same features present in Windows Server However, this release does offer different installation options than Windows Server does: As a Semi-Annual Channel release, Windows Server, version offers only the Server Core installation option.
Starting with this release, Nano Server is not available as an installable host operating system. Instead, Nano Server is available as a container operating system. Features being considered for replacement starting with subsequent releases The following features and functionalities are being considered for replacement starting with releases after Windows Server, version Eventually, they may be completely removed from the installed product image and replaced by other features or functionality or installable from other sources , but they are still available in this release, sometimes with certain functionality removed.
You should begin planning now to employ alternate methods or the future replacement for any applications, code, or usage that depend on these features. If you have feedback to share about the proposed replacement of any of these features, you can use the Feedback Hub app. Even though this app runs on Windows 10, you can use it to send us feedback about the Windows Server product and documentation as well. Administration namespace. You should also start migration from IIS 6. See Server Message Block Overview for background information on this feature.
Windows PowerShell 2. For the best features and performance, migrate to Windows PowerShell 5. See PowerShell Documentation for plenty of information. This list is subject to change in subsequent releases and may not include every deprecated feature or functionality. For more details about a particular feature or functionality and its replacement, see the documentation for that feature.
Features removed from Windows Server The following features and functionalities have been removed from this release of Windows Server Applications, code, or usage that depend on these features will not function in this release unless you employ an alternate method. Instead, do any of the following: If the computer you want to manage is running an operating system older than Windows Server , connect to it with Remote Desktop and use the local version of the Share and Storage Management snap-in.
On a computer running Windows 8. Use Hyper-V on a client computer to run a virtual machine running Windows 7, Windows 8, or Windows 8. There is no replacement. Instead, features are secured by default. If you need to control specific security settings, you can use either Group Policy or Microsoft Security Compliance Manager.
Windows Update The wuauclt. AutoUpdate” automaticUpdates. DetectNow Features deprecated starting with Windows Server The following features and functionalities are deprecated starting with this release. Eventually, they will be completely removed from the product, but they are still available in this release, sometimes with certain functionality removed.
You should begin planning now to employ alternate methods for any applications, code, or usage that depend on these features. Configuration tools Scregedit. If you have scripts that depend on Scregedit. Use Windows PowerShell instead. Remote management WinRM. NET Framework 3.
NET Framework 4. With this benefit, customers need to only pay for the infrastructure costs of the virtual machine because the licensing for Windows Server is covered by the Software Assurance benefit. The benefit is applicable to both Standard and Datacenter editions of Windows Server for the R2, , R2 and releases. This benefit is available across all regions and sovereign clouds. Savings examples Below you can find a reference table to assist you with understanding the benefit rules with more granularity.
The green column shows the quantity of same-type VMs and the blue row shows the core density of each VM. The yellow cells show the number of 2-proc licenses or sets of 16 cores one must have to deploy a certain number of VMs of a certain core density.
Example configurations for several licensing positions: If you want to learn more about the Azure Hybrid Benefit for Windows Server, please go to the Azure Hybrid Benefit website. If you already have VMs running with the Azure Hybrid Benefit, you will need to perform an inventory of how many units you are running, and check against the active SA licenses you have. Please contact your Microsoft Enterprise Agreement licensing specialist to validate your SA licensing position.
To see and count all virtual machines deployed with Azure Hybrid Benefit for Windows Server in a subscription, you can do one of the below: 1. Be sure to perform an inventory in each subscription that you own to generate a comprehensive view of your licensing position.
If you discovered you can cover incremental VMs with the benefit, you may want to optimize your costs further by switching to running instances with the benefit vs full cost.
If you do not have enough eligible Windows Server licenses for the number of VMs already deployed, you either need to purchase additional Windows Server on-premises licenses covered with Software Assurance through one of the channels listed below, purchase Windows Server VMs at regular hourly rates or turn off the Hybrid Benefit functionality for some VMs.
Please note that you may buy core licenses in the increment of 8 cores, to qualify for each additional Azure Hybrid Benefit VM. Please find the instructions for all available deployment options here, including: Detailed video highlighting the new deployment experience utilizing pre-built gallery images Detailed instructions on uploading a custom-built VM Detailed instructions on migrating existing virtual machines using Azure Site recovery using PowerShell.
KMS uses a client-server model to active clients. The KMS host must reside on your local network. The following table summarizes KMS host and client requirements for networks that include Windows Server and Windows 10 clients.
If you receive activation errors, check that you have the appropriate updates listed below this table. Installations of KMS on Windows Server must be updated in order to support activation of clients running Windows 10 and Windows Server , or newer client or server operating systems. For more information, see July update rollup for Windows Server Installations of KMS on Windows 8. For more information, see July update rollup for Windows 8. Windows Server R2 cannot be updated to support activation of clients running Windows Server , or newer operating systems.
If you have more than 50 clients, we recommend that you have at least two KMS hosts in case one of your KMS hosts becomes unavailable. Most organizations can operate with as few as two KMS hosts for their entire infrastructure. Addressing KMS operational requirements KMS can activate physical and virtual computers, but to qualify for KMS activation, a network must have a minimum number of computers called the activation threshold.
KMS clients activate only after this threshold is met. To ensure that the activation threshold is met, a KMS host counts the number of computers that are requesting activation on the network. KMS hosts count the most recent connections.
When a client or server contacts the KMS host, the host adds the machine ID to its count and then returns the current count value in its response.
The client or server will activate if the count is high enough. Clients will activate if the count is 25 or higher. Servers and volume editions of Microsoft Office products will activate if the count is five or greater.
The KMS only counts unique connections from the past 30 days, and only stores the 50 most recent contacts. KMS activations are valid for days, a period known as the activation validity interval.
KMS clients must renew their activation by connecting to the KMS host at least once every days to stay activated. By default, KMS client computers attempt to renew their activation every seven days. You can accept these default settings, or if you have special network and security configuration requirements, you can manually configure KMS hosts and clients. After a KMS host is activated, administrators can reactivate the same host up to nine times with the same key.
For more information, see Microsoft Volume Licensing. Computers that are running volume licensing editions of Windows 10, Windows Server , Windows 8. Use these links for retail versions of Windows: Fix this error that you get when you try to activate a Windows 8. If you’re looking for more information about Windows activation error messages, go to the following Microsoft websites: Get help with Windows activation errors When you try to use a Multiple Activation Key MAK or the Key Management Service KMS to perform Volume Activation on one or more Windows-based computers, you receive error messages that contain specific error codes.
This article discusses how to troubleshoot these errors. Verify that the key is the MAK provided by Microsoft. KMS host keys will activate up to 10 times on six different computers. If more activations are necessary, contact the Microsoft Licensing Activation Centers. MAKs by design have a limited number of activations. Contact the Microsoft Licensing Activation Centers.
MAK The grace period expired before the system was activated. Now, the system is in the Notifications state. KMS: Restart, or run slmgr. Verify that the CID is correctly entered. This error indicates that the computer is missing a Windows marker in the BIOS — provided on OEM systems to indicate computers shipping with qualifying editions of Windows, which is a requirement for KMS client activation.
You must have a qualifying operating system license AND a Volume license Windows 7 upgrade license, or a full license for Windows 7 from a retail source. Installing a Volume operating system on a computer that does not have a qualifying operating system installed is not supported. Install a qualifying version of a Microsoft operating system, and then activate by using a MAK.
Please contact your system administrator. Run Slmgr. Troubleshoot the network connection between the KMS host and the client. Make sure that TCP port default is not blocked by a firewall or otherwise filtered. KMS needs to be activated. Activate the KMS host with either online or phone activation. This can be common in mixed environments that contain application and operating system-specific KMS hosts, for example.
Install the appropriate KMS key on the corresponding version of Windows. Check the spelling. If the key is being copied and pasted, make sure that em-dashes have not been substituted for the dashes in the key. See the Volume Activation Operations Guide. The system will continue to run during the NonGenuine grace period. Obtain and install a genuine product key, and activate the system during the grace period. Otherwise, the system will go into the Notifications state at the end of the grace period.
Time sync is important to system and network security for a variety of reasons. Fix this issue by changing the system time on the client to sync with the KMS. The requested action requires elevated privileges.
Run slmgr. Right-click cmd. Troubleshoot network and DNS. O ptionally, obtain and install a MAK; then, activate the system. Finally, troubleshoot DNS. Troubleshoot network connections. Troubleshoot network connections and DNS. Please see the Application Event Log for additional information.
Troubleshoot errors from each event ID associated with the activation attempt. The most likely reason is that language packs MUI have been installed on computers that are running Windows editions that are not licensed for additional language packs. Note This is not necessarily an indication of tampering.
Some applications can install multi-lingual support even when that edition of Windows is not licensed for those language packs. This issue may also occur if Windows has been modified by malware to allow additional features to be installed. This issue may also occur if certain system files are corrupted. To resolve this issue, you must reinstall the operating system. To work around this issue, follow the steps in the following Microsoft Knowledge Base article: Error message when you try to activate Windows Vista Enterprise, Windows Vista Business, Windows 7, or Windows Server “Code 0xb” 0x The product key you entered didn’t work.
Check the product key and try again, or enter a different one. Check out Changes to Nano Server to learn what this means. Windows Server offers a new installation option: Nano Server. Nano Server is a remotely administered server operating system optimized for private clouds and datacenters.
It is similar to Windows Server in Server Core mode, but significantly smaller, has no local logon capability, and only supports bit applications, tools, and agents.
It takes up far less disk space, sets up significantly faster, and requires far fewer updates and restarts than Windows Server.
When it does restart, it restarts much faster. Nano Server is ideal for a number of scenarios: As a “compute” host for Hyper-V virtual machines, either in clusters or not As a storage host for Scale-Out File Server. Only bit applications, tools, and agents are supported. Nano Server cannot serve as an Active Directory domain controller. Group Policy is not supported.
However, you can use Desired State Configuration to apply settings at scale. Nano Server cannot be configured to use a proxy server to access the internet. Switch-embedded teaming SET is supported instead. Nano Server does not support virtual host bus adapters HBAs. Nano Server does not need to be activated with a product key. For details, see PowerShell on Nano Server. See the following subsection for more information. In this model, feature update releases of Nano Server are expected two to three times per year.
This model requires Software Assurance for Nano Servers deployed and operated in production. To maintain support, administrators must stay no more than two CBB releases behind.
However, these releases do not auto-update existing deployments; administrators perform manual installation of a new CBB release at their convenience. For some additional information, see Windows Server new Current Branch for Business servicing option.
Clean installation Because you install Nano Server by configuring a VHD, a clean installation is the quickest and simplest deployment method. To get started quickly with a basic deployment of Nano Server using DHCP to obtain an IP address, see the Nano Server Quick Start If you’re already familiar with the basics of Nano Server, the more detailed topics starting with Deploy Nano Server offer a full set of instructions for customizing images, working with domains, installing packages for server roles and other features both online and offline, and much more.
Upgrade Since Nano Server is new for Windows Server , there isn’t an upgrade path from older operating system versions to Nano Server. Migration Since Nano Server is new for Windows Server , there isn’t migration path from older operating system versions to Nano Server. If you’re already running Nano Server, this servicing model will be familiar, since it was formerly serviced by the Current Branch for Business CBB model.
Windows Server’s new Semi-Annual Channel is just a new name for the same model. However, with this release of Windows Server, version , Nano Server is available only as a container base OS image.
You must run it as a container in a container host, such as a Server Core installation of Windows Server. Running a container based on Nano Server in this release differs from earlier releases in these ways: Nano Server has been optimized for.
NET Core applications. Nano Server is even smaller than the Windows Server version. PowerShell Core,. NET Core container packages when building your container. There is no longer a servicing stack included in Nano Server. Microsoft publishes an updated Nano container to Docker Hub that you redeploy. You troubleshoot the new Nano Container by using Docker. You can now run Nano containers on IoT Core. You can run a Nano Server VHD either in a virtual machine or boot to it on a physical computer; the steps are slightly different.
Once you’ve tried out the basics with these quick-start steps, you can find details of creating your own custom images, package management by several methods, domain operations, and much more in Deploy Nano Server. To quickly deploy Nano Server in a virtual machine 1.
Start Windows PowerShell as an administrator, change directory to the folder where you have placed the NanoServerImageGenerator folder and then import the module with Import-Module.
Set-ExecutionPolicy RemoteSigned should 3. The computer name will be Nano1. If you want a Generation 1 virtual machine, create a VHD image by specifying a. You can also directly generate a WIM file by specifying a. Boot the virtual machine and in Hyper-V Manager connect to the virtual machine.
Log on to the Recovery Console see the “Nano Server Recovery Console” section in this guide , using the administrator and password you supplied while running the script in Step 3. Keyboard lights, key sections, and keyboard layout switching such as caps lock and number lock are not supported. Obtain the IP address of the Nano Server virtual machine and use Windows PowerShell remoting or other remote management tool to connect to and remotely manage the virtual machine.
Nano Server on a physical computer You can also create a VHD that will run Nano Server on a physical computer, using the pre-installed device drivers. If your hardware requires a driver that is not already provided in order to boot or connect to a network, follow the steps in the “Adding Additional Drivers” section of this guide. To quickly deploy Nano Server on a physical computer 1. Set-ExecutionPolicy RemoteSigned should work well.
This parameter is optional. The computer name will be Nano-srv1 and will have OEM drivers installed for most common hardware and has the Hyper-V role and clustering feature enabled. The Standard Nano edition is used. To do that, follow these steps: a. Mount the generated VHD. Unmount the VHD. Obtain the IP address of the Nano Server computer and use Windows PowerShell remoting or other remote management tool to connect to and remotely manage the virtual machine.
This topic covers information you need to deploy Nano Server images that are more customized to your needs compared to the simple examples in the Nano Server Quick Start topic.
You’ll find information about making a custom Nano Server image with exactly the features you want, installing Nano Server images from VHD or WIM, editing files, working with domains, dealing with packages by several methods, and working with server roles.
Based on the inputs you provide, it generates reusable PowerShell scripts that allow you easily automate consistent installations of Nano Server running either Windows Server Datacenter or Standard editions.
Obtain the tool from the Download Center. The detection process will also list all of the volumes on the system and the devices that do not have a driver included in the Server Core drivers package. If any of these are unfamiliar to you, review the remainder of this topic and the other Nano Server topics so that you’ll be prepared to provide the tool with the information it will need. Creating a custom Nano Server image For Windows Server , Nano Server is distributed on the physical media, where you will find a NanoServer folder; this contains a.
It is these package files that you use to add server roles and features to the VHD image, which you then boot to. See the “Installing roles and features online” section of this topic.
This table shows the roles and features that are available in this release of Nano Server, along with the Windows PowerShell options that will install the packages for them. As far as Windows 10 version is concerned, could this become the buggiest version of Windows ever? Everything seems to work fine here: imgur. I installed the language packs from Settings, after doing the updates.
Microsoft is mismanaged and tries to do too much in too many markets. A bug in one thing breaks another thing, then the dev teams blame each other. On top of that MS management keeps changing plans because of failures like Windows mobile, Cortana, and Edge. I had win 8, total sh! Removed it and put win7 on my laptop with NO updates.
That was several years ago. Seuss interface was introduced. A friend tried to dis me by claiming it was just like a Mac. And so on…. Windows update stays disabled. Most of the garbage Home users put up with can be disabled. I imagine that is a complicated thing to manage. Each 6 months, gives the feature upgrade. The other 6 months focus on bug fixing only. One feature upgrade per year and one bug fixing. No, there not a chance. Save my name, email, and website in this browser for the next time I comment.
Please click on the following link to open the newsletter signup page: Ghacks Newsletter Sign up. Ghacks is a technology news blog that was founded in by Martin Brinkmann.
It has since then become one of the most popular tech news sites on the Internet with five authors and regular contributions from freelance writers. The taskbar has a task view icon that allows you to easily switch to different open apps, or create a new virtual desktop. Windows 10 includes two user interface UI modes, one is optimized for devices with keyboard and mouse, and the other is for a touch screen device. Windows 10 is available in many different editions, for home PCs, you can download a Home or Pro version, and for business computers you can install the Enterprise Edition, and in academic institutions you can use the Education edition of the operating system.
Brief information about each PC edition of Windows 10 is given below:. Home – The Home Edition is the basic version of the operating system, designed for home PC users, and available for PC and tablet devices. It is available for Microsoft Volume Licensing customers, and is designed for the use in small and large organizations. Education – Education Edition is designed for educational institutions for example, schools, colleges, etc. Brief information about each PC edition of Windows 10 is given below: Home – The Home Edition is the basic version of the operating system, designed for home PC users, and available for PC and tablet devices.
Windows 10 Version history PC contain year of release. Windows 10 Features Snap applications on the screen and work together.
Windows 10 Language Pack Issue, Microsoft recommends Reset of PC – gHacks Tech News
Paint 3D app.
Windows 10 life cycle.
Oct 22, 2, 3, You need to login to view this posts content. Jul 16, 49 I tried some tweaks found here and there, and no one is able to block or remove everything from Cortana without getting a bunch of errors in event viewer. Mar 17, Sep 21, 96 Jan 4, 8 3 0. NTlite was in free mode. I confirm, there is no sub-menu “Rechercher” inside “Composants Windows”. Apr 14, 41 72 0. Feb 19, 84 25 0.
Oct 17, 12 1 0. As far as i know, that tool activates Windows for only days, so you have to reactivate every 6 months. Is there any way to activate Windows permanently with this tool? What happens if you forget to reactivate Windows after days? Aug 12, 4, 1, You must log in or sign up to post here. Show Ignored Content. Share This Page. But i was curious how Windows 10 updates were handled in the recent months.
In the image above you can see all versions Fall Update currently available. It shows that separate x64 packages were released on November 27th. So it took Microsoft almost 2 months to do this. By that time i would usually already have all my PCs updated to the latest version.
Ideally i would like to have separate packages be available at the same release date. Anyway, turned out was a mess, so nobody hurried to install it. You can see that there was another build release in March B , which probably had fixes for all nasty issues included. Interestingly, this time they released just separate packages for x86 and x64 at the same time and no combined one.
Maybe they will keep this procedure. Will keep this VM around to check later. Obviously, there is no packages yet in the general Windows 10 product category it is still in testing and wide release is planned for a second half of May. This can be handy though. Just pick the and later category and get only relevant ones. Read More. Microsoft is planning to stop using SHA-1 algorithm when signing their updates to prove they were not tampered with.
Based on support article though it seems it only affects older, stand alone version of WSUS 3. Anyway, there is still time before the switch. Microsoft should release SHA-2 support for 3. So, you should install all security and critical updates for affected OSes, install that WSUS update and hope that everything works past that date.
Now the April Update is out. Nothing has changed about the issues with Cumulative Update after the upgrade. I have searched on this topic and read at some site, that it was a known bug for version. I guess it will never be fixed..
Last time i have explained how i was going to work with feature updates for Windows 10 further, which would involve lots of manual checking and fixing. I was also hesitant to do scripting, as it was hard to make a good and error prone script. But i have finally decided to try it with scripting, because it would just be very time consuming to do the old way for hundreds of PCs twice a year.
Short post this time. After all the mess that happened after the Spectre and Meltdown vulnerabilities disclosure and a frenzy of patching i think Microsoft has released updates times in January a few machines in our network have stopped updating their status in WSUS. Although, they were still able to check for updates. It happened after a failed installation of KB update. Which then installed correctly, but since then no status updates were sent. It will involve manual checking and fixing, so if one has thousands of clients — tough luck.
It is possible to make a script to do everything. A complex, error prone and hard to test. If someone can come up with a sophisticated script for this possible to do everything on a single run during a startup, with pauses, etc. What other options there are? Not to mention it costs a lot. It is just a set of policies you apply to your PCs.
Just like Windows Update for Business. You set how and what updates should it get and hope it is working.
In the world of WannaCry outbreaks it is crucial to have a tool to make sure your network is updated. WSUS is outdated and has its own flaws, but it was working fine until Windows 10 came.
Microsoft needs to do something about it. Well, not exactly. There are some issues and quirks i had to deal with. So i went and declined an upgrade for Windows 7 and 8. Then i have added a few testing PCs to that group. When doing Check for updates it pulled the update from WSUS and started preparing it for installation.
After the update installation it still shows Needed status for some time, until it gets new info from PCs.