When I was passing this via my PHP API wrapper, this was giving me no end of heck. I spent ages looking for how to escape those “”‘s, and after testing with Postman that this worked great like this, for some reason I notice an option in Postman I’d never clicked before.
Just up there by Save on the top right.
Then like an idiot, I realised I just needed to use the ASCII code for “, and I’d have been fine. Copy and pasted this into the function call going to my API wrapper, and we have liftoff.
If you want to be even smarter, you can have Postman generate all the code needed when you have a working call in the app! This would have saved me HOURS in the past if I’d known this.
I have been recently building some new VMs for Catalina for testing, and I was having the below error:
This was frustrating the hell out of me, as Fusion was 100% running, so I uninstalled vfuse, reinstalled it from homebrew so I knew I had the right version (2.2.6). I’m running Fusion Pro 11.5.6, I could not work out WTF was going on.
I then went to the vfuse source code (as you do) to see how the script determines the Fusion application path.
** DISCLAIMER ** – This is not intended for use on a production platform, VMware does not recommend amending or touching the View ADAM database manually. You will not receive support if anything fails after amending this. This blog is a learning exercise only.
At VMware, I’m responsible for looking after the whole Workspace ONE and Horizon suite (our Digital Workspace/End User Computing solutions). Most of my work is supporting the Unified Endpoint Management (UEM) and Access solutions, but more recently I’ve been assisting with some Horizon questions.
With that, I was presented an interesting question. How can we set all existing Horizon clients to not automatically connect to a desktop pool? In cases where only 1 pool is assigned, or reset any users who have set this option manually.
Never fear, there is a way! With our good friend PowerShell we can go in and make changes to the View ADAM Database which is within ADSI.
Since the start of the the year I’ve been mulling over what upgrades to my Home Lab are in order. I’m doing a lot more VMware Horizon learning/testing and I’m prepping to take VCP-DCV, so I needed some capacity to make some cool things happen.
I was planning on buying a new NUC to get some extra capacity, but I decided to invest in a RAM upgrade instead. Considerably less cost outlay, less extra initial power consumption and theres a good possibly this extra headroom will be enough.
I’m going to do another post on my home lab setup, but for today I went successfully from 32 to 64GB RAM in my NUC7I7DNHE primary node.
WWDC 2019 brought with it a whole host of new enterprise features for Apple’s OS’s, including macOS 10.15 Catalina. One of the most importnat in my opinion is called ‘Enrolment Customisation’. This is essentially a page during the DEP process where an MDM can present any web content. In our case, this was a perfect place to put a SAML authentication page.
Today I was accepted into the VMware vExpert 2019 list! I’ve been included in this due to, in part, this blog and the blog.eucse.com site, along with talks I’ve run at conferences and events this year.
If you’ve upgraded to Workspace ONE UEM 18.10 and you have anybody enrolled with the AirWatch Agent, you wont fail to see the new Intelligent Hub app and Hub Services configuration.
Intelligent Hub is an overhaul of the AirWatch Agent to deliver a full Unified App Catalog features, allowing the Hub to be the one stop shop for users to access any app on any device. The app also allows Administrators to deliver notifications to end users.
If you are an end to end Workspace ONE user, integrating UEM (Unified Endpoint Management, powered by AirWatch) with VMware Identity Manager, you’ll probably want to deliver your SaaS Apps as well as Native applications.
I was lucky enough to find a good deal on eBay for a good NUC to help build out my Home Lab. As an EUC/VMware Mobility Specialist I’m not looking to run any massive vSphere/vSAN deployments, just a nice box to run the usual suspects (AD, ADCS, Unified Access Gateway) to give me everything I need.
Unfortunately, I started running my setup during what should be known as the end of times in the UK (June/July 2018) where temperatures hardly dropped below 27 during the day. This meant keeping my kit cool was difficult so I put it down a a bit more ambient heat than usual. When I started getting some major fan noise due to an issue with Azure AD Connect services taking more CPU, I decided to try and change some settings to resolve it.
I set up VCSA (vCenter Server Appliance) running on a vSAN datastore, then wanted to move things around. I disconnected my ESXI hosts and deleted the VCSA appliance. Proper SDDC experts are probably crying at that statement not, but you learn by doing! I then had the issue where I was unable to delete the vSAN datastore.
To resolve this, I had to run thr following:
First enable SSH on your ESXI host. SSH into it and run:
esxcli vsan cluster leave
Once this was done, I was still unable to re-claim the disks back into regular datastores. I couldn’t remove the partitions via ESXi Web Client either, so resorted back to Google.