Having been away from home a lot recently, it had been a while since my laptop had been backed up by TimeMachine. After a few attempts though it got a bit annoying as McAfee kept interrupting the process. The problem seemed to be that the backups contained infected emails: McAfee was blocking TM from writing infected emails to the backup drive. As it turns out, I recalled fixing this once before (although I never blogged about it). So how could it have come unpicked? Looking at my TM backup exclusions, the exclusion that I added was still in place: But my whole mail folder should be more than 8KB!… Then it clicked. I hadn’t done a TM backup since updating to OSX El Capitan. After clicking the “+” button to add a new rule, I navigated to my mail folder. […]
I saw a question on Twitter this morning that I thought warranted a quick post: The default timeout for the various workflow stubs is 30 minutes, but they can be changed. As always, take backup copies and be careful! The six stubs that can be changed are: Expired RegisterMachine Disposing UnprovisionMachine BuildingMachine MachineProvisioned The timeout settings for External Workflow stubs are configured on the Windows server (vRA 6.x) that hosts the Manager role. The file and path required (assuming a default installation) is:
C:\Program Files (x86)\VMware\vCAC\Server\ExternalWorkflows\xmldb\ExternalWFStubs.xml
Using your favourite text editor, simply adjust the timeout value for each workflow. Most people tend to require a longer timeout for “MachineProvisioned”, often because they require longer running post-provisioning tasks to complete before handing a Virtual Machine over to the requester. Save the file and make sure that the same changes are made on the […]
That’s the fifth UKVMUG done with, and the first one that I’ve ever presented at. I loved it, it was a great day. The highlights for me (or what I did): Joe Baguley’s opening keynote – great as ever (even though I saw some of it in TechSummit a couple of weeks ago). Joe is a very inspiring speaker, and I’m not just saying that because he’s my boss (a few times removed). Listening without a hangover this time, there were some interesting things that I took away from it. Eric Wright’s session on OpenStack and VMware. Great to meet a fellow vBrownBag guy and good content too. An idea Josh Atwell gave me for some future blog postings over lunch. Picking the brains of Andy Jenkins and Robbie Jerom about Docker and Cloud Native Apps Ricky El-Qasem and Alec […]
Before anyone gets in a huff, I’m not suggesting that a key part of VMware’s automation, orchestration and cloud functionality be consigned to the bin. This is about the name. It was Q3 / Q4 last year (2014) that VMware announced the changes to its product names. A whole year ago! Of course, it can take time for a change to take effect, particularly when any of the following are a factor: Older projects and environments using older versions of the products that contain original branding Document, diagram and presentation re-use where the older names are used Investment in any other IP or collateral Ingrained habits, especially if you’ve been using these products for years But by now “vCO” should be a thing of the past. That’s not its name anymore. I won’t be removing the tag from my blog […]
New job. New laptop. But of course it isn’t set up like the old one. It doesn’t have all of the tweaks that I made over the years on it. One annoyance, what with me being a heavy and frequent user of vRealize Orchestrator, is that client.jnlp files downloaded from the vRO web interface don’t have an application association by default. I’m writing this as a quick reference just in case I need it again anytime soon. Having downloaded and saved the client.jnlp file as normal, use the finder app to select the file, right click and select “Open with > Other…”. Browse to this path: /System/Library/CoreServices Select the executable Java-Web-Start.app Tick the “Always Open With” option. Click “Open”. Done!