I recently moved house, and as part of that a few things on my network changed. My NAS (A Synolofy DS8J) changed it’s IP Address. This caused an issue when ESXi was trying to get hold of the datastore.
So, now this needs to be removed and replaced – I came across this error:
I’m fortunate enough to have a small Intel NUC powering my labbing efforts for both home and work use. When I joined Okta, I decided to set up a separate AD/Firewall VM to keep things apart from my home lab AD I’d been using in the past.
I also decided that I didn’t need these VMs running over night so I thought I’d suspend them after ‘working hours’. So at 9am, I wanted the VMs to resume, and at around 5:30/6, have them suspend.
In this post, we will explore how to use the vCenter API called by a Python script to suspend and resume a set of VMs on a schedule.
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.
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.
Providing access to applications as easy as possible is one of the primary goals of Workspace ONE. While Workspace ONE can enable Single Sign On to Office 365, I see most setups just deploying the main portal to Office 365. One massive improvement we can make is to provide users with links directly to O365 services, such as OneDrive, Outlook and Excel Online by enabling one click links into these services.
Below is a step by step guide to get each service within Office 365 presented to end users via the Workspace ONE Catalog.