Today, I’d like to share a very simple function I wrote some years ago, I would even say many years :). This is a simple powershell function, without any error handling and parameters checking. I needed at some point to have proper logging of my scripts and I wanted to have it displayed on screen and logged to the file as well for some later usage. I wrote this function to achieve my need.
There are situations when one need to add a new port group to the existing standard vSwitch in vCenter. This is easily configurable in the vCenter in the host configuration. This can be done manually on the small number of hosts, however on bigger number it can be really annoying. What offers vRO as basis. In the built in workflow list under the “Library->vCenter->Networking->Standard Virtual Switch“, one can find a workflow “Add port group in the standard virtual switch“. It’s good for the start, so let’s see what it needs Continue reading
Today, let me post my friend’s post, which is I find really amazing/magnificent. If you’re looking for the manual/guide how to replace self-signed certificates in vCenter 5.5 with PKI one, please go to the following link [How to] Replace self-signed certificates on VCSA 5.5.
The only thing I can say : THANK YOU Waldemar for posting that !!!!
And of course NOT thank you VMWARE for NOT posting that. I can imagine that all VMWARE engineers are too busy or too skilled to write such manual to fulfil Customer needs. Or just simply they are NOT skilled enough. Really poor support from vendor!!!!!!!!!!
I’m a great PowerShell fan, I think it’s the second best (or maybe first one) thing Microsoft bring to IT world – for me still the one and best is MS Exchange.
Some time ago MS introduced a thing called Desired State Configuration, as I’m correct it was with PS 3.0, for sure with PS 4.0.
You can read a lot of DSC just to google it or go to MS site. I won’t explain how DSC works and what is the pull server, how to enforce configuration compliance, etc …
For my compliance I’m using SCCM, however I found Powershell DSC really useful for my initial server configuration, so I’d like to share how easy and handy is to build some initial server configurations – “Make it smart, make it simpe” – from this starting point one can go wherever … sky is the limit 🙂 Continue reading
As system engineer I’m providing a 3rd level support in IT areas I work on. So one day a strange case came to me. An issue was reported that on multi-homed Windows 2012 R2 server – this case was : 2 network interfaces on Windows 2012 R2 (I can imagine it can happen on 2+ network interfaces Windows 2008 or newer). So on mutlihomed Windows Server 2012 R2, when try to ping internally FQDN wrong IP is returned. Continue reading
In this post I’ll focus mostly on code for creating simple vRO action to find a virtual machine network card by its MAC address. A use case for me was to set and IP address on VM with multiple network cards or delete a network card with specific MAC address. So instead of creating a new workflow I decided to create an action. Continue reading
Recently when I tried to add some features in Windows 2012 R2 using server manager I received this error : Failed to open the runspace pool. The Server Manager WinRM plug-in might be corrupted or missing.
I started to search for help and one of the posts I found was http://www.lukebrowning.com/sysadmin/windows/windows-server-2012-winrm-corrupt-or-missing/ – so maybe solution presented there is working – I don’t know for me it’s not. Continue reading
In the post vRealize Orchestrator – Workflow to change DRS setting to default on single VM I presented the workflow to change DRS to manual on single VM. Now it’s the time to change this setting back to the default one, as it was. So to do this it’s quite easy to make a copy of previously create workflow.
And just edit the code of “Scriptable task”, because input parameter and attributes remain the same as in workflow described in previous post. Continue reading
Multiple times in multiple workflows, I needed to have VM not being migrated during the workflow run. Easiest way is to disable DRS on the VM. Well, it seems that DRS setting does not belong to VirtualMachine object, DRS settings is part of the ESX Cluster object. We’re still able to to set setting individually per VM, however it has to be set on ESX Cluster level not on the VM itself. I was pretty sure, that there built-in vRO workflows for such simple setting … However, it’s not. That’s what VMWare offers by default
- Add DRS virtual machine
- Add virtual machines to DRS group
- Create cluster
- Delete cluster
- Disable DRS on cluster
- Disable HA on cluster
- Enable DRS on cluster
- Enable HA on cluster
- Remove virtual machine DRS group from cluster
- Remove virtual machines from DRS group
- Rename cluster
If there is a need and there is no solution – it has to be created.