windows server 2012,电脑系统在运行的时候，啥情况下会发生系统时间与硬件时间同步啊

Posted 2023-03-24

在系统事件日志里面对每次时间变更都有记录，提示“系统时间已从 XXX 更改为 XXX”。

请问可能是什么原因导致这种现象？有什么排查思路？

目前已经取消了与Internet时间服务器同步的选项、禁用了Windows Time服务，但仍然存在该现象。

本人也不是很懂，估计是双系统引起的时间同步问题。以下资料来源于网络。
Linux和Windows双系统会出现这种情况。这是因为Windows系统默认读取主板bios等硬件系统时间作为OS的当地时间;而MAc,Linux类的OS以主板bios等硬件系统时间作为UTC时间，然后操作系统的时间以UTC为标准按照使用者的时区设置加加减减。这就造成了中国用户会出现一个很有趣的现象：Ubuntu上的时间会比windows上的快8小时。
1.关闭UTC;所用命令：
sudo gedit etc/default/rcS

注意“rcS”，S大写;在所显示的内容中将“UTC=yes”改为"UTC=no"
2.这时时间仍旧是显示原有的“快”时间，你可以采用网络时间服务器来校正;

sudo ntpdate pool.ntp.org

3.可以考虑把矫正后的时间写入硬件系统，命令
hw clock追问

服务器电脑这边是没有网络的，快8小时，不是时区。。。。。

追答

系统是直接读取主板BIOS时间的，并不是网络同步，上面讲了，是两种系统以不同的标准读取时间导致的时间不一致

参考技术A 我也遇到这个问题，请问你那里解决没有？ 参考技术B 解决了没楼主，我这WIN10也是睡眠后与硬件时钟同步，导致系统唤醒

Upgrade Windows Server 2016 to Windows Server 2019

 

 

Pre-Upgrade

---

Upgrade path:

Windows Server 2016 can be upgraded to Windows 2019 in a single upgrade process.

Support:

In-place Upgrade is supported for Windows Server 2016 on physicaL hardware, and in Virtual Machines. Public and private cloud companies also support In-place Upgrade on Windows Server 2016 Virtual Machines to upgrade to Windows Server 2019 – check with your cloud provider.

Alternative:

Migrate (re-deploy) applications and data on a clean install of Windows Server 2019.

Limitations:

• For the smoothest upgrade experience, if you‘ve deployed software-defined datacenter (SDDC) features like Software-Defined Networking (SDN) or Storage Spaces Direct, you are encouraged to wait for validated hardware from the Windows Server Software-Defined (WSSD) program to become available. The first wave of validated hardware is expected very soon; in mid-January 2019. Until then, please evaluate Windows Server 2019 using the Windows Insider edition, or call Microsoft support for recommendations on how to proceed.

• Windows Servers configured to “Boot from VHD” cannot be upgraded using In-place Upgrade.

Planning for In-place Upgrade

---

Before proceeding with In-place Upgrade, collect the following information:

• Is there a target or goal timeframe for upgrading this server?

• Is this a production-critical server?

• Is there a maintenance window for upgrading this server?

• Is there enough time for a test upgrade on an identical or similar non-production server?

• Who uses this server? Internal users, external users, or both? Have they been informed of the upgrade or maintenance?

• Is there an inventory of what is running on the server? Check the following:

  • Windows Server Roles and Features

  • Microsoft applications: SQL Server, SharePoint Server, Exchange Server, etc.

  • 3rd-Party applications: SAP, Oracle, DB2, etc.

  • Is the server joined to an Active Directory domain?

  • Are any of the server disks BitLocker protected?

  • Is the server part of a Failover Cluster?

    Note that Cluster OS Rolling Upgrade can be used to upgrade Windows Server 2016 Failover Clusters to Windows Server 2019.

• How often is the server backed-up? Have backups ever been successfully restored (applied) to the server or applications?

• What backup software is used?

• If In-place Upgrade is not successful and the server needs to be rebuilt, are the Windows Server and application install media available?

  Although it is rare, In-place Upgrade can fail and there should be a plan in-place for this possibility, to minimize server downtime and maintain SLAs.

• Is the server fully patched? It is strongly recommended that the server is fully patched prior to In-place Upgrade.

• Run systeminfo.exe and save the output:

  

• Run ipconfig /all and save the output:

  

• Run Get-WindowsFeature and save the output:

  

• Run RegEdit and capture the value of the the HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsNTCurrentVersion hive – this will show the exact version (BuildLabEx) and edition (EditionID) of Windows Server:

  

 

 

Before proceeding with the In-place Upgrade

---

1. Backup the Operating System, Applications, and Virtual Machines.

2. Shutdown, Quick Migrate, or Live Migrate all Virtual Machines running on the server - Virtual Machines cannot be running on the server during In-place Upgrade.

 

 

Upgrade

---

1. Locate the setup media for Windows Server 2019

2. Run setup.exe by double-clicking it:

   

3. Click Yes to enable setup to proceed:

   

5. For internet-connected devices, we recommend the Download updates, drivers and optional features option. Click Next:

   

6. Setup will check the configuration of your computer – please wait:

   

7. Depending on the distribution channel that you received Windows Server media from (Retail, Volume License, OEM, ODM, etc.) and the license for the server, you may be prompted to enter a licensing key to proceed.

8. You will be prompted to select the image of the Edition to upgrade to. Then click Next:

   

9. Depending on the distribution channel that you received Windows Server media from (Retail, Volume License, OEM, ODM, etc.) you may be presented with different license agreements. Click Accept:

   

10. For In-place Upgrade, select Keep personal files and apps, and then click Next:

    

11. When the analysis phase is complete, setup will prompt you to click Back to change choices, or to proceed with the In-place Upgrade. Click Install:

    

12. Setup will proceed with the In-place Upgrade, and then the server will reboot:

    

13. Setup will complete and the server will reboot.

 

 

Post-upgrade

---

1. After Setup has completed installing and rebooted the sever, login to check that the server has been successfully upgraded. If you selected Windows Server 2019 Standard or Datacenter Desktop Edition, you should see the Server Manager window:

 

2. Run RegEdit and check the value of the HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsNTCurrentVersion hive – the version should be successfully updated to Windows Server 2019.

   

 

3. Check that applications are running and that client connections to the applications succeed.

4. If you believe that there has been an issue upgrading you server, you should copy and Zip the %SystemRoot%Panther (usually C:WindowsPanther) directory and contact support.