Skip to content
BranchesTags

Latest commit

History

3 Commits

Folders and files

NameName
Last commit message
Last commit date
Custom
Custom
README.md
README.md

Repository files navigation

VMware vRealize Orchestrator Server Workflows

Workflows Developed by:Gary Coburn

Optimized and Customized by: Adrian Pekar

Tested Product Versions: vRA 7.3 with built-in vRO

Disclaimer:

These workflows have been created entirely for educational and informational purpose. They do not come with any warranty or support but will provide a good base understanding of how you can accomplish your goals. These are not intended for production. Use at your own risk.

Description

This workflows in the repositories are a modified versions of the original workflows posted by Gary Coburn.

The workflows provide two functionalities:

  • Change the default passwords configured on the VM Golden Images (Debian-based Linux Destop and Server, Windows Server and Destop).
  • Send custom notification emails to the users including the generated new passwords.

The password change is necessary for improved security. The Golden Image has a master login and password that is set during its creation. If the password is not changee, cloud users can potentially log in to VMs that are not provisioned for them. The IP addresses are usually assigned to the VMs from a pool. It is not complex to find other VMs within the same IP range.

The custom notification emails are required for sending the users the generated passwords.

Note: The workflows are configured in a way that the passwords are stored in a local file (on the vRO server). This is not an optimal and secure way. It is the user's responsibility to change the generated passwords as soon as possible.

Instructions

  1. Import the workflows into the appropriate folders (there have been a standardization for directory sturcture and naming in 2016).
  2. Customise the workflows.

The worklflows here are provided in an 'as is basis'. You should know how to install and configure VMware vRO.

For configuring the Event Broker follow part-1 and part-2 of the tutorials.

For custom email notifications follow this tutorial and follow the discussion in the Comments section.

For an example how to provide the users with an option to change their password follow this tutorial and follow the discussion in the Comments section.

Windows 10 password change problems:

In W10 the NET command requires elevated command prompt mode, ie., you have to run it as an Administrator. However, in W10, admin account is deactivated by default. In addition, even if you activate it in your reference machine (template), the Sysprep procedure resets it to the default deactivated mode (when you are cloning it in vRA (actually vCenter)). So when the vRO workflow tries to change the password, it will fail (a standard user account with administrator privileges is not suitable for password change).

To resolve the issue:

  • First, you have to force W10 to activate the administrator account when finishing Sysprep. For this task, you can use the procedure in KB2034622 (do not forget to set a password and check your Customization Specification (CS) in vCenter as well - by mistake, I kept overwriting this password with the one I forget to change in the CS).
  • Then, in the workflow, you will connect to the VM using the Administrator account instead of the standard user account.
  • At last, in the workflow, you first set the user password using the administrator account and then deactivate it (the admin account).

How to configure the AD with your workflow

Prerequisites:

  1. Configure AD
  2. Set Default AD (“Configure AD plug-in options” – workflow name is a bit misleading) – needed for the way how I query AD.

Code for AD query:

AllUserData=ActiveDirectory.searchExactMatch(“User”,machine.get(“owner”));username=AllUserData[0].getAttribute(“displayName”);System.log(“Username: ”+username);login=AllUserData[0].getAttribute(“sAMAccountName”);System.log(“Login: ”+login);email=AllUserData[0].getAttribute(“mail”);System.log(“Email: ”+email);

About

VMware vRealize Orchestrator Server Workflows

Resources

Readme
Activity

Stars

1 star

Watchers

1 watching

Forks

2 forks
Report repository

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
GitHub - drnpkr/vro-workflows: VMware vRealize Orchestrator Server Workflows · GitHub
Skip to content
BranchesTags
Latest commit
History
3 Commits
Folders and files
NameName
Last commit message
Last commit date
Custom
Custom
README.md
README.md
Repository files navigation
VMware vRealize Orchestrator Server Workflows
Workflows Developed by:Gary Coburn
Optimized and Customized by: Adrian Pekar
Tested Product Versions: vRA 7.3 with built-in vRO
Disclaimer:
These workflows have been created entirely for educational and informational purpose. They do not come with any warranty or support but will provide a good base understanding of how you can accomplish your goals. These are not intended for production. Use at your own risk.
Description
This workflows in the repositories are a modified versions of the original workflows posted by Gary Coburn.
The workflows provide two functionalities:
  • Change the default passwords configured on the VM Golden Images (Debian-based Linux Destop and Server, Windows Server and Destop).
  • Send custom notification emails to the users including the generated new passwords.
The password change is necessary for improved security. The Golden Image has a master login and password that is set during its creation. If the password is not changee, cloud users can potentially log in to VMs that are not provisioned for them. The IP addresses are usually assigned to the VMs from a pool. It is not complex to find other VMs within the same IP range.
The custom notification emails are required for sending the users the generated passwords.
Note: The workflows are configured in a way that the passwords are stored in a local file (on the vRO server). This is not an optimal and secure way. It is the user's responsibility to change the generated passwords as soon as possible.
Instructions
  1. Import the workflows into the appropriate folders (there have been a standardization for directory sturcture and naming in 2016).
  2. Customise the workflows.
The worklflows here are provided in an 'as is basis'. You should know how to install and configure VMware vRO.
For configuring the Event Broker follow part-1 and part-2 of the tutorials.
For custom email notifications follow this tutorial and follow the discussion in the Comments section.
For an example how to provide the users with an option to change their password follow this tutorial and follow the discussion in the Comments section.
Windows 10 password change problems:
In W10 the NET command requires elevated command prompt mode, ie., you have to run it as an Administrator. However, in W10, admin account is deactivated by default. In addition, even if you activate it in your reference machine (template), the Sysprep procedure resets it to the default deactivated mode (when you are cloning it in vRA (actually vCenter)). So when the vRO workflow tries to change the password, it will fail (a standard user account with administrator privileges is not suitable for password change).
To resolve the issue:
  • First, you have to force W10 to activate the administrator account when finishing Sysprep. For this task, you can use the procedure in KB2034622 (do not forget to set a password and check your Customization Specification (CS) in vCenter as well - by mistake, I kept overwriting this password with the one I forget to change in the CS).
  • Then, in the workflow, you will connect to the VM using the Administrator account instead of the standard user account.
  • At last, in the workflow, you first set the user password using the administrator account and then deactivate it (the admin account).
How to configure the AD with your workflow
Prerequisites:
  1. Configure AD
  2. Set Default AD (“Configure AD plug-in options” – workflow name is a bit misleading) – needed for the way how I query AD.
Code for AD query:
AllUserData=ActiveDirectory.searchExactMatch(“User”,machine.get(“owner”));username=AllUserData[0].getAttribute(“displayName”);System.log(“Username: ”+username);login=AllUserData[0].getAttribute(“sAMAccountName”);System.log(“Login: ”+login);email=AllUserData[0].getAttribute(“mail”);System.log(“Email: ”+email);
About
VMware vRealize Orchestrator Server Workflows
Resources
Readme
Activity
Stars
1 star
Watchers
1 watching
Forks
2 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Force GitHub README to respect dark mode
(function() {
var style = document.createElement('style');
style.textContent = '
.markdown-body {
color-scheme: dark light;
}
.markdown-body pre { background: #161b22 !important; }
.markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }
.markdown-body table th, .markdown-body table td { border-color: #30363d !important; }
.markdown-body img { background: #0d1117; }
.markdown-body blockquote { border-left-color: #8b949e; }
.markdown-body hr { border-color: #30363d; }
';
document.head.appendChild(style);
})();
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - drnpkr/vro-workflows: VMware vRealize Orchestrator Server Workflows · GitHub
Skip to content
BranchesTags
Latest commit
History
3 Commits
Folders and files
NameName
Last commit message
Last commit date
Custom
Custom
README.md
README.md
Repository files navigation
VMware vRealize Orchestrator Server Workflows
Workflows Developed by:Gary Coburn
Optimized and Customized by: Adrian Pekar
Tested Product Versions: vRA 7.3 with built-in vRO
Disclaimer:
These workflows have been created entirely for educational and informational purpose. They do not come with any warranty or support but will provide a good base understanding of how you can accomplish your goals. These are not intended for production. Use at your own risk.
Description
This workflows in the repositories are a modified versions of the original workflows posted by Gary Coburn.
The workflows provide two functionalities:
  • Change the default passwords configured on the VM Golden Images (Debian-based Linux Destop and Server, Windows Server and Destop).
  • Send custom notification emails to the users including the generated new passwords.
The password change is necessary for improved security. The Golden Image has a master login and password that is set during its creation. If the password is not changee, cloud users can potentially log in to VMs that are not provisioned for them. The IP addresses are usually assigned to the VMs from a pool. It is not complex to find other VMs within the same IP range.
The custom notification emails are required for sending the users the generated passwords.
Note: The workflows are configured in a way that the passwords are stored in a local file (on the vRO server). This is not an optimal and secure way. It is the user's responsibility to change the generated passwords as soon as possible.
Instructions
  1. Import the workflows into the appropriate folders (there have been a standardization for directory sturcture and naming in 2016).
  2. Customise the workflows.
The worklflows here are provided in an 'as is basis'. You should know how to install and configure VMware vRO.
For configuring the Event Broker follow part-1 and part-2 of the tutorials.
For custom email notifications follow this tutorial and follow the discussion in the Comments section.
For an example how to provide the users with an option to change their password follow this tutorial and follow the discussion in the Comments section.
Windows 10 password change problems:
In W10 the NET command requires elevated command prompt mode, ie., you have to run it as an Administrator. However, in W10, admin account is deactivated by default. In addition, even if you activate it in your reference machine (template), the Sysprep procedure resets it to the default deactivated mode (when you are cloning it in vRA (actually vCenter)). So when the vRO workflow tries to change the password, it will fail (a standard user account with administrator privileges is not suitable for password change).
To resolve the issue:
  • First, you have to force W10 to activate the administrator account when finishing Sysprep. For this task, you can use the procedure in KB2034622 (do not forget to set a password and check your Customization Specification (CS) in vCenter as well - by mistake, I kept overwriting this password with the one I forget to change in the CS).
  • Then, in the workflow, you will connect to the VM using the Administrator account instead of the standard user account.
  • At last, in the workflow, you first set the user password using the administrator account and then deactivate it (the admin account).
How to configure the AD with your workflow
Prerequisites:
  1. Configure AD
  2. Set Default AD (“Configure AD plug-in options” – workflow name is a bit misleading) – needed for the way how I query AD.
Code for AD query:
AllUserData=ActiveDirectory.searchExactMatch(“User”,machine.get(“owner”));username=AllUserData[0].getAttribute(“displayName”);System.log(“Username: ”+username);login=AllUserData[0].getAttribute(“sAMAccountName”);System.log(“Login: ”+login);email=AllUserData[0].getAttribute(“mail”);System.log(“Email: ”+email);
About
VMware vRealize Orchestrator Server Workflows
Resources
Readme
Activity
Stars
1 star
Watchers
1 watching
Forks
2 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Highlight search terms from Google/DuckDuckGo/Bing referrer
(function() {
var ref = document.referrer;
var terms = [];
if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {
var url = new URL(ref);
var q = url.searchParams.get('q') || url.searchParams.get('p');
if (q) {
terms = q.split(/\s+/).filter(function(t) { return t.length > 2; });
}
}
if (terms.length === 0) return;
var style = document.createElement('style');
style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';
document.head.appendChild(style);
function highlight(node) {
if (node.nodeType === 3) { // text node
var text = node.textContent;
var found = false;
terms.forEach(function(term) {
var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi');
if (regex.test(text)) {
found = true;
var frag = document.createDocumentFragment();
var parts = text.split(regex);
parts.forEach(function(part, i) {
if (i % 2 === 0) {
frag.appendChild(document.createTextNode(part));
} else {
var span = document.createElement('span');
span.className = 'userscript-highlight';
span.textContent = part;
frag.appendChild(span);
}
});
node.parentNode.replaceChild(frag, node);
}
});
} else if (node.nodeType === 1 && node.childNodes) { // element
var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];
if (!skipTags.includes(node.tagName)) {
Array.from(node.childNodes).forEach(highlight);
}
}
}
highlight(document.body);
// Re-highlight on dynamic content
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1 || node.nodeType === 3) highlight(node);
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - drnpkr/vro-workflows: VMware vRealize Orchestrator Server Workflows · GitHub
Skip to content
BranchesTags
Latest commit
History
3 Commits
Folders and files
NameName
Last commit message
Last commit date
Custom
Custom
README.md
README.md
Repository files navigation
VMware vRealize Orchestrator Server Workflows
Workflows Developed by:Gary Coburn
Optimized and Customized by: Adrian Pekar
Tested Product Versions: vRA 7.3 with built-in vRO
Disclaimer:
These workflows have been created entirely for educational and informational purpose. They do not come with any warranty or support but will provide a good base understanding of how you can accomplish your goals. These are not intended for production. Use at your own risk.
Description
This workflows in the repositories are a modified versions of the original workflows posted by Gary Coburn.
The workflows provide two functionalities:
  • Change the default passwords configured on the VM Golden Images (Debian-based Linux Destop and Server, Windows Server and Destop).
  • Send custom notification emails to the users including the generated new passwords.
The password change is necessary for improved security. The Golden Image has a master login and password that is set during its creation. If the password is not changee, cloud users can potentially log in to VMs that are not provisioned for them. The IP addresses are usually assigned to the VMs from a pool. It is not complex to find other VMs within the same IP range.
The custom notification emails are required for sending the users the generated passwords.
Note: The workflows are configured in a way that the passwords are stored in a local file (on the vRO server). This is not an optimal and secure way. It is the user's responsibility to change the generated passwords as soon as possible.
Instructions
  1. Import the workflows into the appropriate folders (there have been a standardization for directory sturcture and naming in 2016).
  2. Customise the workflows.
The worklflows here are provided in an 'as is basis'. You should know how to install and configure VMware vRO.
For configuring the Event Broker follow part-1 and part-2 of the tutorials.
For custom email notifications follow this tutorial and follow the discussion in the Comments section.
For an example how to provide the users with an option to change their password follow this tutorial and follow the discussion in the Comments section.
Windows 10 password change problems:
In W10 the NET command requires elevated command prompt mode, ie., you have to run it as an Administrator. However, in W10, admin account is deactivated by default. In addition, even if you activate it in your reference machine (template), the Sysprep procedure resets it to the default deactivated mode (when you are cloning it in vRA (actually vCenter)). So when the vRO workflow tries to change the password, it will fail (a standard user account with administrator privileges is not suitable for password change).
To resolve the issue:
  • First, you have to force W10 to activate the administrator account when finishing Sysprep. For this task, you can use the procedure in KB2034622 (do not forget to set a password and check your Customization Specification (CS) in vCenter as well - by mistake, I kept overwriting this password with the one I forget to change in the CS).
  • Then, in the workflow, you will connect to the VM using the Administrator account instead of the standard user account.
  • At last, in the workflow, you first set the user password using the administrator account and then deactivate it (the admin account).
How to configure the AD with your workflow
Prerequisites:
  1. Configure AD
  2. Set Default AD (“Configure AD plug-in options” – workflow name is a bit misleading) – needed for the way how I query AD.
Code for AD query:
AllUserData=ActiveDirectory.searchExactMatch(“User”,machine.get(“owner”));username=AllUserData[0].getAttribute(“displayName”);System.log(“Username: ”+username);login=AllUserData[0].getAttribute(“sAMAccountName”);System.log(“Login: ”+login);email=AllUserData[0].getAttribute(“mail”);System.log(“Email: ”+email);
About
VMware vRealize Orchestrator Server Workflows
Resources
Readme
Activity
Stars
1 star
Watchers
1 watching
Forks
2 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '
GitHub - drnpkr/vro-workflows: VMware vRealize Orchestrator Server Workflows · GitHub
Skip to content
BranchesTags
Latest commit
History
3 Commits
Folders and files
NameName
Last commit message
Last commit date
Custom
Custom
README.md
README.md
Repository files navigation
VMware vRealize Orchestrator Server Workflows
Workflows Developed by:Gary Coburn
Optimized and Customized by: Adrian Pekar
Tested Product Versions: vRA 7.3 with built-in vRO
Disclaimer:
These workflows have been created entirely for educational and informational purpose. They do not come with any warranty or support but will provide a good base understanding of how you can accomplish your goals. These are not intended for production. Use at your own risk.
Description
This workflows in the repositories are a modified versions of the original workflows posted by Gary Coburn.
The workflows provide two functionalities:
  • Change the default passwords configured on the VM Golden Images (Debian-based Linux Destop and Server, Windows Server and Destop).
  • Send custom notification emails to the users including the generated new passwords.
The password change is necessary for improved security. The Golden Image has a master login and password that is set during its creation. If the password is not changee, cloud users can potentially log in to VMs that are not provisioned for them. The IP addresses are usually assigned to the VMs from a pool. It is not complex to find other VMs within the same IP range.
The custom notification emails are required for sending the users the generated passwords.
Note: The workflows are configured in a way that the passwords are stored in a local file (on the vRO server). This is not an optimal and secure way. It is the user's responsibility to change the generated passwords as soon as possible.
Instructions
  1. Import the workflows into the appropriate folders (there have been a standardization for directory sturcture and naming in 2016).
  2. Customise the workflows.
The worklflows here are provided in an 'as is basis'. You should know how to install and configure VMware vRO.
For configuring the Event Broker follow part-1 and part-2 of the tutorials.
For custom email notifications follow this tutorial and follow the discussion in the Comments section.
For an example how to provide the users with an option to change their password follow this tutorial and follow the discussion in the Comments section.
Windows 10 password change problems:
In W10 the NET command requires elevated command prompt mode, ie., you have to run it as an Administrator. However, in W10, admin account is deactivated by default. In addition, even if you activate it in your reference machine (template), the Sysprep procedure resets it to the default deactivated mode (when you are cloning it in vRA (actually vCenter)). So when the vRO workflow tries to change the password, it will fail (a standard user account with administrator privileges is not suitable for password change).
To resolve the issue:
  • First, you have to force W10 to activate the administrator account when finishing Sysprep. For this task, you can use the procedure in KB2034622 (do not forget to set a password and check your Customization Specification (CS) in vCenter as well - by mistake, I kept overwriting this password with the one I forget to change in the CS).
  • Then, in the workflow, you will connect to the VM using the Administrator account instead of the standard user account.
  • At last, in the workflow, you first set the user password using the administrator account and then deactivate it (the admin account).
How to configure the AD with your workflow
Prerequisites:
  1. Configure AD
  2. Set Default AD (“Configure AD plug-in options” – workflow name is a bit misleading) – needed for the way how I query AD.
Code for AD query:
AllUserData=ActiveDirectory.searchExactMatch(“User”,machine.get(“owner”));username=AllUserData[0].getAttribute(“displayName”);System.log(“Username: ”+username);login=AllUserData[0].getAttribute(“sAMAccountName”);System.log(“Login: ”+login);email=AllUserData[0].getAttribute(“mail”);System.log(“Email: ”+email);
About
VMware vRealize Orchestrator Server Workflows
Resources
Readme
Activity
Stars
1 star
Watchers
1 watching
Forks
2 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Auto-enable theater mode on YouTube
(function() {
function tryTheater() {
var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]');
if (btn && !btn.classList.contains('activated')) {
btn.click();
}
}
// Try immediately
tryTheater();
// Try after navigation (SPA)
var lastUrl = location.href;
setInterval(function() {
if (location.href !== lastUrl) {
lastUrl = location.href;
setTimeout(tryTheater, 500);
}
}, 1000);
// Also try on player load
var observer = new MutationObserver(tryTheater);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - drnpkr/vro-workflows: VMware vRealize Orchestrator Server Workflows · GitHub
Skip to content
BranchesTags
Latest commit
History
3 Commits
Folders and files
NameName
Last commit message
Last commit date
Custom
Custom
README.md
README.md
Repository files navigation
VMware vRealize Orchestrator Server Workflows
Workflows Developed by:Gary Coburn
Optimized and Customized by: Adrian Pekar
Tested Product Versions: vRA 7.3 with built-in vRO
Disclaimer:
These workflows have been created entirely for educational and informational purpose. They do not come with any warranty or support but will provide a good base understanding of how you can accomplish your goals. These are not intended for production. Use at your own risk.
Description
This workflows in the repositories are a modified versions of the original workflows posted by Gary Coburn.
The workflows provide two functionalities:
  • Change the default passwords configured on the VM Golden Images (Debian-based Linux Destop and Server, Windows Server and Destop).
  • Send custom notification emails to the users including the generated new passwords.
The password change is necessary for improved security. The Golden Image has a master login and password that is set during its creation. If the password is not changee, cloud users can potentially log in to VMs that are not provisioned for them. The IP addresses are usually assigned to the VMs from a pool. It is not complex to find other VMs within the same IP range.
The custom notification emails are required for sending the users the generated passwords.
Note: The workflows are configured in a way that the passwords are stored in a local file (on the vRO server). This is not an optimal and secure way. It is the user's responsibility to change the generated passwords as soon as possible.
Instructions
  1. Import the workflows into the appropriate folders (there have been a standardization for directory sturcture and naming in 2016).
  2. Customise the workflows.
The worklflows here are provided in an 'as is basis'. You should know how to install and configure VMware vRO.
For configuring the Event Broker follow part-1 and part-2 of the tutorials.
For custom email notifications follow this tutorial and follow the discussion in the Comments section.
For an example how to provide the users with an option to change their password follow this tutorial and follow the discussion in the Comments section.
Windows 10 password change problems:
In W10 the NET command requires elevated command prompt mode, ie., you have to run it as an Administrator. However, in W10, admin account is deactivated by default. In addition, even if you activate it in your reference machine (template), the Sysprep procedure resets it to the default deactivated mode (when you are cloning it in vRA (actually vCenter)). So when the vRO workflow tries to change the password, it will fail (a standard user account with administrator privileges is not suitable for password change).
To resolve the issue:
  • First, you have to force W10 to activate the administrator account when finishing Sysprep. For this task, you can use the procedure in KB2034622 (do not forget to set a password and check your Customization Specification (CS) in vCenter as well - by mistake, I kept overwriting this password with the one I forget to change in the CS).
  • Then, in the workflow, you will connect to the VM using the Administrator account instead of the standard user account.
  • At last, in the workflow, you first set the user password using the administrator account and then deactivate it (the admin account).
How to configure the AD with your workflow
Prerequisites:
  1. Configure AD
  2. Set Default AD (“Configure AD plug-in options” – workflow name is a bit misleading) – needed for the way how I query AD.
Code for AD query:
AllUserData=ActiveDirectory.searchExactMatch(“User”,machine.get(“owner”));username=AllUserData[0].getAttribute(“displayName”);System.log(“Username: ”+username);login=AllUserData[0].getAttribute(“sAMAccountName”);System.log(“Login: ”+login);email=AllUserData[0].getAttribute(“mail”);System.log(“Email: ”+email);
About
VMware vRealize Orchestrator Server Workflows
Resources
Readme
Activity
Stars
1 star
Watchers
1 watching
Forks
2 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Remove or un-stick sticky/fixed headers that block content
(function() {
function unstick() {
document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) {
if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {
el.style.position = 'static';
el.style.top = 'auto';
el.style.zIndex = 'auto';
}
});
}
unstick();
var observer = new MutationObserver(unstick);
observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });
})();
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - drnpkr/vro-workflows: VMware vRealize Orchestrator Server Workflows · GitHub
Skip to content
BranchesTags
Latest commit
History
3 Commits
Folders and files
NameName
Last commit message
Last commit date
Custom
Custom
README.md
README.md
Repository files navigation
VMware vRealize Orchestrator Server Workflows
Workflows Developed by:Gary Coburn
Optimized and Customized by: Adrian Pekar
Tested Product Versions: vRA 7.3 with built-in vRO
Disclaimer:
These workflows have been created entirely for educational and informational purpose. They do not come with any warranty or support but will provide a good base understanding of how you can accomplish your goals. These are not intended for production. Use at your own risk.
Description
This workflows in the repositories are a modified versions of the original workflows posted by Gary Coburn.
The workflows provide two functionalities:
  • Change the default passwords configured on the VM Golden Images (Debian-based Linux Destop and Server, Windows Server and Destop).
  • Send custom notification emails to the users including the generated new passwords.
The password change is necessary for improved security. The Golden Image has a master login and password that is set during its creation. If the password is not changee, cloud users can potentially log in to VMs that are not provisioned for them. The IP addresses are usually assigned to the VMs from a pool. It is not complex to find other VMs within the same IP range.
The custom notification emails are required for sending the users the generated passwords.
Note: The workflows are configured in a way that the passwords are stored in a local file (on the vRO server). This is not an optimal and secure way. It is the user's responsibility to change the generated passwords as soon as possible.
Instructions
  1. Import the workflows into the appropriate folders (there have been a standardization for directory sturcture and naming in 2016).
  2. Customise the workflows.
The worklflows here are provided in an 'as is basis'. You should know how to install and configure VMware vRO.
For configuring the Event Broker follow part-1 and part-2 of the tutorials.
For custom email notifications follow this tutorial and follow the discussion in the Comments section.
For an example how to provide the users with an option to change their password follow this tutorial and follow the discussion in the Comments section.
Windows 10 password change problems:
In W10 the NET command requires elevated command prompt mode, ie., you have to run it as an Administrator. However, in W10, admin account is deactivated by default. In addition, even if you activate it in your reference machine (template), the Sysprep procedure resets it to the default deactivated mode (when you are cloning it in vRA (actually vCenter)). So when the vRO workflow tries to change the password, it will fail (a standard user account with administrator privileges is not suitable for password change).
To resolve the issue:
  • First, you have to force W10 to activate the administrator account when finishing Sysprep. For this task, you can use the procedure in KB2034622 (do not forget to set a password and check your Customization Specification (CS) in vCenter as well - by mistake, I kept overwriting this password with the one I forget to change in the CS).
  • Then, in the workflow, you will connect to the VM using the Administrator account instead of the standard user account.
  • At last, in the workflow, you first set the user password using the administrator account and then deactivate it (the admin account).
How to configure the AD with your workflow
Prerequisites:
  1. Configure AD
  2. Set Default AD (“Configure AD plug-in options” – workflow name is a bit misleading) – needed for the way how I query AD.
Code for AD query:
AllUserData=ActiveDirectory.searchExactMatch(“User”,machine.get(“owner”));username=AllUserData[0].getAttribute(“displayName”);System.log(“Username: ”+username);login=AllUserData[0].getAttribute(“sAMAccountName”);System.log(“Login: ”+login);email=AllUserData[0].getAttribute(“mail”);System.log(“Email: ”+email);
About
VMware vRealize Orchestrator Server Workflows
Resources
Readme
Activity
Stars
1 star
Watchers
1 watching
Forks
2 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Universal Dark Mode - works on any site
(function() {
var enabled = true;
function applyDarkMode() {
if (!enabled) return;
// Create style element if it doesn't exist
var style = document.getElementById('universal-dark-mode-style');
if (!style) {
style = document.createElement('style');
style.id = 'universal-dark-mode-style';
document.head.appendChild(style);
}
// Dark mode CSS - inverts colors but preserves images/video
style.textContent = '
/* Invert everything except media */
html {
filter: invert(1) hue-rotate(180deg) !important;
background: #1a1a2e !important;
}
/* Restore images, videos, iframes, canvas */
img, video, iframe, canvas, svg, picture, [style*="background-image"] {
filter: invert(1) hue-rotate(180deg) !important;
}
/* Preserve specific elements that should not be inverted */
.no-dark-mode, .no-dark-mode *,
[data-theme="light"], [data-theme="light"],
.ace_editor, .ace_editor *,
.CodeMirror, .CodeMirror *,
.monaco-editor, .monaco-editor *,
.markdown-body pre, .markdown-body pre *,
.highlight, .highlight *,
pre code, pre code * {
filter: none !important;
}
/* Fix common UI elements */
.modal, .popup, .dropdown-menu, .tooltip, .popover {
filter: invert(1) hue-rotate(180deg) !important;
background: #2d2d44 !important;
border-color: #444 !important;
}
/* Scrollbars */
::-webkit-scrollbar { background: #1a1a2e !important; }
::-webkit-scrollbar-thumb { background: #444 !important; }
::-webkit-scrollbar-thumb:hover { background: #555 !important; }
/* Selection */
::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
';
}
function removeDarkMode() {
var style = document.getElementById('universal-dark-mode-style');
if (style) style.remove();
}
// Toggle with Alt+Shift+D
document.addEventListener('keydown', function(e) {
if (e.altKey && e.shiftKey && e.key === 'D') {
e.preventDefault();
enabled = !enabled;
if (enabled) {
applyDarkMode();
console.log('[Universal Dark Mode] Enabled');
} else {
removeDarkMode();
console.log('[Universal Dark Mode] Disabled');
}
}
});
// Apply on load
applyDarkMode();
// Re-apply on dynamic content
var observer = new MutationObserver(function(mutations) {
if (enabled && !document.getElementById('universal-dark-mode-style')) {
applyDarkMode();
}
});
observer.observe(document.head, { childList: true });
console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');
})();
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();
GitHub - drnpkr/vro-workflows: VMware vRealize Orchestrator Server Workflows · GitHub
Skip to content
BranchesTags
Latest commit
History
3 Commits
Folders and files
NameName
Last commit message
Last commit date
Custom
Custom
README.md
README.md
Repository files navigation
VMware vRealize Orchestrator Server Workflows
Workflows Developed by:Gary Coburn
Optimized and Customized by: Adrian Pekar
Tested Product Versions: vRA 7.3 with built-in vRO
Disclaimer:
These workflows have been created entirely for educational and informational purpose. They do not come with any warranty or support but will provide a good base understanding of how you can accomplish your goals. These are not intended for production. Use at your own risk.
Description
This workflows in the repositories are a modified versions of the original workflows posted by Gary Coburn.
The workflows provide two functionalities:
  • Change the default passwords configured on the VM Golden Images (Debian-based Linux Destop and Server, Windows Server and Destop).
  • Send custom notification emails to the users including the generated new passwords.
The password change is necessary for improved security. The Golden Image has a master login and password that is set during its creation. If the password is not changee, cloud users can potentially log in to VMs that are not provisioned for them. The IP addresses are usually assigned to the VMs from a pool. It is not complex to find other VMs within the same IP range.
The custom notification emails are required for sending the users the generated passwords.
Note: The workflows are configured in a way that the passwords are stored in a local file (on the vRO server). This is not an optimal and secure way. It is the user's responsibility to change the generated passwords as soon as possible.
Instructions
  1. Import the workflows into the appropriate folders (there have been a standardization for directory sturcture and naming in 2016).
  2. Customise the workflows.
The worklflows here are provided in an 'as is basis'. You should know how to install and configure VMware vRO.
For configuring the Event Broker follow part-1 and part-2 of the tutorials.
For custom email notifications follow this tutorial and follow the discussion in the Comments section.
For an example how to provide the users with an option to change their password follow this tutorial and follow the discussion in the Comments section.
Windows 10 password change problems:
In W10 the NET command requires elevated command prompt mode, ie., you have to run it as an Administrator. However, in W10, admin account is deactivated by default. In addition, even if you activate it in your reference machine (template), the Sysprep procedure resets it to the default deactivated mode (when you are cloning it in vRA (actually vCenter)). So when the vRO workflow tries to change the password, it will fail (a standard user account with administrator privileges is not suitable for password change).
To resolve the issue:
  • First, you have to force W10 to activate the administrator account when finishing Sysprep. For this task, you can use the procedure in KB2034622 (do not forget to set a password and check your Customization Specification (CS) in vCenter as well - by mistake, I kept overwriting this password with the one I forget to change in the CS).
  • Then, in the workflow, you will connect to the VM using the Administrator account instead of the standard user account.
  • At last, in the workflow, you first set the user password using the administrator account and then deactivate it (the admin account).
How to configure the AD with your workflow
Prerequisites:
  1. Configure AD
  2. Set Default AD (“Configure AD plug-in options” – workflow name is a bit misleading) – needed for the way how I query AD.
Code for AD query:
AllUserData=ActiveDirectory.searchExactMatch(“User”,machine.get(“owner”));username=AllUserData[0].getAttribute(“displayName”);System.log(“Username: ”+username);login=AllUserData[0].getAttribute(“sAMAccountName”);System.log(“Login: ”+login);email=AllUserData[0].getAttribute(“mail”);System.log(“Email: ”+email);
About
VMware vRealize Orchestrator Server Workflows
Resources
Readme
Activity
Stars
1 star
Watchers
1 watching
Forks
2 forks
Report repository
Releases
Packages
Contributors
Languages