We at comdivision like to share some insights with you. Discover our blog posts on a variety of technical and non-technical topics.
This Monday morning we got an early call from our VMware partner manager Sabine Maier: "Congratulations… comdivision did it again…", what happened? As you know comdivision is always on the early adopters circle for new VMware technologies, it's not necessarily always that public as we evaluate the market, feature set, but also provide a lot of feedback towards VMware. Which is why sometimes we might not be seen for what we do on a specific product range. VMware Cloud on AWS is a bit different, as we were early in the game and also have already presented at events like the AWS transformation day in Munich earlier this year with lot's of great feedback from the AWS community.
So why did Sabine call? We first thought it was related to something else we were to launch in the next few days, but then we learned that we already completed necessary steps for the VMware Cloud on AWS Master Services Competency.
When I was first introduced to the VMware Cloud on AWS (or short VMC) model about 6 months before the launch my first reaction was: „Is this going to be market relevant?“, then I thought „who is the winner? VMware or Amazon?“ and then „Are our more conservative european users going to adopt this?“. And I will come back to some of these points later in this post. Many of you may know my clear position on all the new cloud-native parts: „It‘s nice, but especially in EMEA we have more legacy apps than cloud native. When I even drill deeper into medium or larger enterprises or public customers it‘s getting worse as we even have lot‘s of applications no longer supported, or sometimes vendors don‘t exist anymore.“. And then there is my favorite, which people who said this don‘t admit this anymore: „Everything is moving into the cloud in X years.“.Read More
Over the past few weeks I had to update quite a few instances of vRealize Orchestrator to version 7.6, where I experienced that upgraded instances do not show any workflow logs, or values anymore. My first thought was that the workflow was no longer executed, but actually it proofed to be a display problem in the vRealize Orchestrator Client. While talking to a few friends working near the product I got some guidance on how to potentially solve the issue...Read More
This article focuses on the basics of automating NSX via the API and vRealize Orchestrator. Those two are a very powerful combination, automating NSX for certain use cases and workloads. Of course, you could use the provided workflows by the NSX plugin, but what if you would like to implement a use case not covered by the provided workflows. Furthermore, the built-in workflows are using the scripting objects instead of the native REST API. Thus, intended me to write this article.
Aside of vRO, Postman is a great tool to test single API calls. In many cases I use Postman to test the API call and transfer the body, used in Postman, into the API call structure in vRO.Read More
Today a non VMware topic... My workplace needed some more screen estate and while colleagues go for multiple screens I personally prefer the one screen solution, which naturally pushed towards one of the new 49" SuperWide screens which you can find from Philips like the 499P9H which I use, or Dell U4919DW has one as well. Be careful that you check the screen resolution, there are models on 49" which are 3840x1080, which would be too low for me, only some have 5120 x 1440 pixel LCDs.Read More
I just got engaged in a customer project for Workspace ONE. This European customer wants to lower his TCO on mobile devices, as they currently hand out many Notebooks to their employees and Windows Notebook require a lot of management from the customer side. So they raised the question if it is possible to include Chromebooks in their environment and to fully manage them with their MDM solution – VMware Workspace ONE UEM.
With the use of VMware Workspace ONE UEM we have two options of management:
- Container management (We are only able to manage Settings and Content within a protected Container)
- Full system management (We are managing the whole System and all Content and Settings on it)
The customer decided to have the full system management so we have to incorporate Google Chrome Enterprise, as this solution combines the management capabilities of Google and VMware to easy and fully manage a Chrome Device.Read More
One of the new features in vCloud Director since version 9.1 is the ability to execute vRealize Orchestrator workflows direct from within the vCloud Director User Interface for both tenant and service provider usage. With the constant addition of other extensibility features this becomes a very attractive solutions for service providers to expand from standard vCloud Director based IaaS to some more advanced service offerings.
But how do you get started?Read More
This article explains how to use the “Add connection” workflow from the vCD 9.7 vRO plugin, because it’s not obvious in first place.
After installing the vCD 9.7 plugin into vRO (installation is not part of this article), there are additional workflows in the library, including a folder called “Plug-in Configuration”. This contains the workflows to add, delete, and update the plugin connection to vCloud Director.
Two months ago, I got engaged in a customer project for Workspace ONE. On Key Requirement was the installation of the Workspace ONE UEM Agent (aka. AWAgent) on Windows 10 Devices (Notebooks and Clients) which were already handed over to the End users. The IT of the Customer does not have any kind of software deployment tools like Microsoft’s SCCM or Symantec Altiris and so on. So, it was necessary to find a solution for deploying the agent without any additional tools, only GPO should be utilized.
So, what we need to do is strip our "problem" into two parts. First part installing the AWAgent without Local Admin Rights (LAR) and the second part stage the Windows 10 Device and automatically reassign the user.
Let us start with the first Part. First of all, we need our staging User. So, inside the Workspace UEM Console, we create a new User (Local user not an LDAP User) and give him the staging Permission.Read More