Resolving VMware vRealize Orchestrator DST Issues with a Custom Script

One of my customers encountered issues with VMware vRealize Orchestrator (vRO) after the Daylight Saving Time (DST) transition. Scheduled workflows failed or were triggered incorrectly, disrupting their automated processes. The root cause was incorrect system time zone settings after the DST change.

The Solution: To fix the issue, we created a custom VMware Prelude profile using a script that:

  1. Created the necessary directories for custom profiles.
  2. Added a check script to validate system time zone settings.
  3. Ensured proper Helm chart configuration for correct time handling.

1.

1.                1. Please use the following java property in the section serverJavaOpts: "user.timezone":"Australia/Victoria".

  1. This time zone Australia/Victoria corresponds to AEST-10AEDT according to https://en.wikipedia.org/wiki/Time_in_Australia
  2. With the above applied, Orchestrator will run in the AEST-10AEDT timezone, and this setting will not be changed by the upgrade (custom profiles are preserved) or daylight-saving time (Java handles daylight-saving time).

The Result: Deploying this script corrected the time zone settings, and vRO resumed executing workflows on schedule, restoring the customer’s automation without further DST issues.

Takeaway: A simple script to adjust system time zones can resolve DST disruptions and ensure smooth operation for VMware solutions like vRealize Orchestrator.



 








1P

Comments

Post a Comment

Popular posts from this blog

My Journey to Becoming a VMware vExpert: Persistence, Passion & People

Image
  I’m thrilled to share that I’ve been recognized as a VMware vExpert in 2025 —a milestone that means a lot to me both personally and professionally. But this wasn’t an overnight success. In fact, it took a few tries, a lot of reflection, and a solid support system to get here. If you're someone working toward this goal, I hope my journey helps you stay motivated. 🚧 The Early Attempts Like many, I applied to the vExpert program a few times in the past—each time with hope, and each time facing the sting of not making the cut. It was disheartening, but also humbling. I realized that passion alone isn’t enough —you need strategy, mentorship, and impact-driven contributions. 🔁 What I Did Differently This Time This year, I changed my approach: Mentorship was key. I reached out to two incredibly generous vExpert Pros & old friends, Arun Nukula and Ravneet Arora , who not only agreed to mentor me but also set up standing meetings to check in on my progress. Their feedba...
Read more

Understanding and Customizing ESXi Password Requirements

VMware ESXi enforces strict password policies for access via the Direct Console User Interface (DCUI) , ESXi Shell , SSH , and the VMware Host Client . These rules are designed to improve security by requiring strong, complex passwords. Default ESXi Password Requirements: Character Classes : Passwords must include at least three of the following four character classes: Lowercase letters Uppercase letters Numbers Special characters (e.g., underscore or dash) Password Length : Must be at least seven characters long and no more than 40 characters . Restrictions : Passwords cannot contain dictionary words or parts of them. Passwords cannot include the username or parts of the username. Customizing ESXi Password Restrictions: You can modify the password rules if the default password policy doesn't meet your organisation's needs. VMware allows you to configure custom password policies to match specific s...
Read more

How do you request an NSX 4.2.1.1 download?

How do you request an NSX 4.2.1.1 download? Background: You will notice no downloadable links for this version if you have seen a recent NSX 4.2.1.1 release. This is something we followed to get the download. Step 1: File an SR with VMware Support. Step 2: Request the downloadable link for the NSX 4.2.1.1 release. Please mention your customer's use case and why they need this release.  Please read the below to see if your infra use case needs NSX 4.2.1.1. Release Notes: VMware NSX 4.2.1.1 Release Notes While NSX 4.2.1  brought several improvements, NSX 4.2.1.1  takes things further with targeted fixes and enhancements. Here's a breakdown of what’s worth noting: 1. Security Patches for Critical Vulnerabilities The most significant difference between NSX 4.2.1  and NSX 4.2.1.1  is the resolution of several critical security vulnerabilities . Specifically, NSX 4.2.1.1  addresses: CVE-2024-38818 CVE-2024-38817 CVE-2024-38815 These vulnerabilities were recently...
Read more