On October 19, 2021, we have enabled single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
If you had already registered your account at Plesk 360 (formerly known as My Plesk) please use one for login. Otherwise please re-register it using the same email address as your existing Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account.

How to manage date and time for Plesk autoupdates?

Follow

Comments

1 comment

  • Avatar
    David Hubbard

    Probably too late to change it now, unless you enhance the directive to allow for the optional adding of a timezone offset, but implementing this feature in a manner that is only UTC time creates issues for anyone managing Plesk servers in multiple timezones.  For example, customers generally want their service-affecting updates to occur outside of business hours, such as 2am-5am local time.  Well, 2am local time depends entirely on the server's configured time zone.  If we put this in the policy or panel.ini file:

    timeFrameStart = 02
    timeFrameEnd = 05

    Our servers in Australia are going to update in the middle of the business day, Europe will get the proper time, US/EST will end up late evening, US/PST will end up early evening.

    Anyone running an operation where servers are set to the customer's timezone, and they have worldwide customers, won't be able to use this feature properly unless the panel.ini file is customized for each timezone.  We use an automated config management which enforces the contents of that file given its security risks, so now we will have to deploy custom policy on that file for every timezone we have customers in.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request