- Getting Started with Nano Server
- Charbel Nemnom
- 233字
- 2021-07-02 21:11:05
Servicing improvements
The numbers shown in Figure 4 are based on analysis done by Microsoft for all Windows patches that were released in 2014. These numbers fall under three categories as the following:
- Important bulletins
- Critical bulletins
- Reboots required
If you had Nano Server installation options available in 2014, Nano Server had nine important bulletins versus Server Core which had 23 and Server with Desktop Experience that had 26. The interesting one is critical bulletins; Nano Server had two versus Server Core that had eight and Server with Desktop Experience 23. The critical bulletin is a security fix for something that Microsoft has found that people are trying to exploit. This is rated as critical and must be deployed as quickly as possible. So, for the entire year, Nano Server had only two of those critical updates. However, the important bulletins help in overall quality of the system. For Nano Server, there were three reboots required for the entire year, Microsoft is working hard to bring the reboot number from three to only two; Server Core had six and Server with Desktop Experience had 11. Thus for 11 months, you had to reboot your servers because of patches that were applicable to them, whereas for Nano Server, you had to reboot only thrice. Here you can see the uptime benefits of deploying Nano Server:

- C語言程序設計(第3版)
- HTML5 移動Web開發從入門到精通(微課精編版)
- Python高級編程
- Java虛擬機字節碼:從入門到實戰
- 概率成形編碼調制技術理論及應用
- MongoDB,Express,Angular,and Node.js Fundamentals
- C/C++數據結構與算法速學速用大辭典
- Fast Data Processing with Spark(Second Edition)
- Zabbix Performance Tuning
- Python Machine Learning Blueprints:Intuitive data projects you can relate to
- Go語言入門經典
- Python數據預處理技術與實踐
- Python高性能編程(第2版)
- 大話代碼架構:項目實戰版
- Ubuntu Server Cookbook