[
https://issues.apache.org/jira/browse/VCL-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16120679#comment-16120679
]
ASF subversion and git services commented on VCL-1069:
------------------------------------------------------
Commit 1804610 from [email protected] in branch 'vcl/trunk'
[ https://svn.apache.org/r1804610 ]
VCL-1069
Added check to make sure the optional $message argument is defined before
attempting to print it in Windows.pm::get_current_computer_time. It was
generating an uninitialized concatenation warning in vcld.log if called without
the optional argument.
In Version_6.pm::activate, added $message argument to call to
Windows.pm::get_current_computer_time.
> Allow Windows to update time regardless of skew
> -----------------------------------------------
>
> Key: VCL-1069
> URL: https://issues.apache.org/jira/browse/VCL-1069
> Project: VCL
> Issue Type: Improvement
> Components: vcld (backend)
> Reporter: Andy Kurth
> Assignee: Andy Kurth
> Fix For: 2.5
>
>
> By default, Windows will only automatically update its time from an NTP
> server if the Windows computer's time is within 15 hours of the correct time.
> It's possible for an image to load and the computer's time be off by more
> than this value. Registry settings can be adjusted to allow the time to
> update regardless of skew:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\ConfigMaxPosPhaseCorrection
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\MaxNegPhaseCorrection
> Improving the chances that the time is correct will increase the chances that
> KMS activation will succeed, a step which occurs later on in the post-load
> stage. Activation fails if the computer's time is incorrect.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)