愿得一人心,白首不相离。
技术支持

linux系统修改时间

1.手动修改

在没网的时候,可以使用这种方式


 1 # 修改系统时间

 2 date -s  "2019-11-01 17:28:00"

 3 # 修改硬件时间

 4 hwclock --set  --date  "2019-11-01 17:28:00"

 5 # 同步系统时间和硬件时间

Jack 2024-4-26 0评论

windows 2016新建额外域控没有netlogon和SYSVOL共享

公司新建域辅助域控,就新建了一台额外域控,但是该域控建好后发现组策略不生效,检查sysvol文件夹一片空白,肯定是没有从主域控复制过来,使用dcdiag检查,有下面报错

发现是没有netlogon和sysvol共享,通过微软知识库查询到问题,(先从正常的域控C:\Windows下复制文件夹SYSVOL到故障域控上S)需要更改注册表HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters中的SysvolReady键值更改为1。

Jack 2024-2-22 0评论

域控制器上的 SYSVOL 复制失败并显示 DFSR 错误 4612

症状

受影响的 DC 在 net share 命令中没有列出 SYSVOL 或 NETLOGON 共享。

受影响 DC 上的 DFS 复制事件日志包含 DFSR 错误 4612 和 5008。两个错误中指示的合作伙伴服务器是不再可用的 DC。

Error 4612:

The DFS Replication service initialized SYSVOL at local path [path] and is waiting to perform initial replication. The replicated folder will remain in the initial synchronization state until it has replicated with its partner [partner]. If the server was in the process of being promoted to a domain controller, the domain controller will not advertise and function as a domain controller until this issue is resolved. This can occur if the specified partner is also in the initial synchronization state, or if sharing violations are encountered on this server or the sync partner. If this event occurred during the migration of SYSVOL from File Replication service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. This can cause the SYSVOL folder on this server to become out of sync with other domain controllers.

Jack 2024-2-21 0评论