by Mike Gruner
In current virtual desktop environments the direction went since a couple of month more and more in the direction of non-persistent systems. That mean, you get every time a blank Windows 10 machine for instance. Why that is the way to go?
You ever wants to set websites in Microsoft Internet Explorer as default through your whole environment? Sure, that is one of the use cases of VMware´s Dynamic Environment Manager (DEM). But what if you use the Internet Explorer Enhanced Security Configuration? In
As mentioned before in the overview I have created a short video of the whole workflow. In that you can see how the Out of the Box (OOBE) enrolment of a fresh Microsoft Windows 10 Device works with VMware Workspace ONE (Access
Check Attribute mapping – Okta To make the whole process works if you implemented the compete scenario (Workspace ONE Access and UEM, Okta and Microsoft Azure) we have to make sure that the user attribute mapping is correct. So, you have to
Integrate Workspace ONE in Microsoft Azure AD If you want to use Microsoft Azure AD as well with Workspace ONE we have to configure some things here. First of all, we will integrate the AirWatch MDM application into Azure AD that we
If you want to use your assigned applications from Okta directly from the Workspace ONE Access console we have to integrate Okta as an application source in Workspace ONE Access. After the configuration the applications which the users were assigned to in
Integration of Microsoft Azure AD and Office 365 in Okta As next we integrate Microsoft Azure AD into Okta that we can provision users from Okta to Azure AD as well. In that case we can use two scenarios of integration, Password
Integration of Microsoft Azure AD as Directory Services in Workspace ONE UEM In case you want to integrate a Directory Service in Workspace ONE UEM for instance Microsoft Azure AD you can do this as follows. Log into Workspace ONE UEM Groups
Integration of Workspace ONE Access as 3rd party SAML iDP in Okta We can integrate Workspace ONE Access as 3rd party SAML iDP in Okta. That is necessary for the Device Trust Use Case for instance with iOS and Android mobile devices.
In case you want to use Enterprise Mobility Management or Modern management for your devices as well and additionally use the configuration as described before to let the users authenticate against Okta first before they can log into the Workspace ONE platform,