Registered mode is a capability in UEM that allows IT to deliver a secure way for Employees to access corporate data using Workspace ONE without having to manage their devices. While the core philosophy behind Registered mode is the same across different platforms, the problem it addresses on various platforms are slightly different. Understanding its origin will shed some light into how you can effectively utilize this capability and provide seamless access to your Employees Evolution of Registered Mode As a technologist that’s been following and absorbing all the progress that’s been happening this space, I wanted to start this post by covering the evolution of Registered Mode with Workspace ONE over the last 4-5 years.
Demystifying Technology for those that strive to thrive
CLOUD TEKKI® aims to explore new ideas and their implementation techniques that make Digital Transformation possible. Topics will be focussed around Cloud, Cloud Native Technologies, Automation Technologies, End User Computing and the synergy between People, Process and Product
DISCLAIMER: All opinions are Author's own. Content will evolve. Please remember to link and credit
Edge Services Observability" Edge Services Observability Unified Access Gateway (UAG) is a key component in most VMware End User Computing deployments, including Workspace ONE and Horizon. The UAG hosts various Edge Services like VMware Tunnel, Content Gateway, Secure Email Gateway, Reverse Proxy and Horizon Secure (External) Access. Additionally, the UAG can also provide DMZ Authentication and Identity Bridging. These services play a pivotal role in providing Zero Trust Network Access to corporate resources.
Having changed roles (or at least titles) almost once every year (TAM@2014➔SAM@2016➔TSM@2017➔TAM Lead@2018➔CSM@2019➔CSA@2020), I don’t usually make a huge deal about role changes but this is a major pivot ending a 7 year long chapter in my career and thus an exception. Bitter sweet moment as this minute will mark the end of a 7 year long chapter in my career. — Partheeban Kandasamy (PK) (@pkblah) July 17, 2021 Over the last 7 years, I’ve had the incredible opportunity to work with large Enterprises, form great relationships and helped several meet their digital transformation goals.
Howdy! I’m Kevin Ten Eyck, a Staff EUC Customer Success Architect at VMware. I’ve been with VMware for 4 years and greatly enjoy all things EUC! Coming from a background in Mobility and VDI, I love finding new challenges to be solved. Would love to hear your feedback or alternate ideas on how you’ve solved similar problems! What problem does this solve? This blog post is targeted at Workspace ONE UEM administrators who are being asked to prevent unmanaged devices from accessing Office 365 applications.
Hi! I’m Nagul Subramanian working on VMware End User Computing technologies for more than 7 years and have gained a lot of field experience on WS ONE and Mobility. I’ve always had a personal goal to contribute my knowledge back to the community. As I explored ways to do that, I ran into PK and Cloud Tekki. This is my first blog post(hopefully first of many) and would love to hear your feedback!
What is Workspace ONE Intelligence? Workspace ONE Intelligence is the mainstream data analytics product within the Workspace ONE product suite. It allows you to tap into a wide array of data sources (from UEM, SDK enabled apps, Access and others) to get unique Insights & Automation capabilities over your End User Computing landscape! Features Unified Visibility: Workspace ONE Intelligence aggregates and correlates device, application and user data together in one place to deliver a complete view of the entire digital workspace environment.
This is a quick post covering an exciting update to the Workspace ONE Access Migration Tool. If you are interested in learning more about the tool, please check out these resources - Why was this Migration tool built? How can you use it? Download the Migration tool Access Migration Tool - Logo" Access Migration Tool - Logo As a quick recap, the fling allows easy migration of Apps (excluding virtual apps) from one WS1 Access tenant to another (both on-prem to SaaS as well as SaaS to SaaS) by preserving the user experience as much as possible while reducing the migration effort by automating these major tasks -
Recently I had the opportunity to lead a Project where I had to define a scalable process (repeatable by nature) that streamlines a customer's product adoption experience for a particular use case. When adopting a product or a solution to any use case, a Customer would typically work with multiple teams. The journey starts from a Customer evaluating a new product and all the way to installing and managing the product.
Migration?…Migraine?… When it comes to migration scenarios, the most involved and difficult migration within the EUC lineup (that I can think of) is the WS1 Access tenant migration. It is equivalent to adopting a new IDP solution as you’ll have to re-federate all the apps in order to successfully complete a migration. And this is case regardless of where you are trying to move from - On-Premise to SaaS As Cloud is picking up steam and as features are developed with a cloud-first mentality, tt makes sense to offload the management of the Access Service to VMware This scenario is also getting more common as Access and Hub Services are FedRAMP certified as of CY Q4 2020 SaaS to SaaS This is a not very common use case but few situations demand them nonetheless predominantly due to issues arising from high customization entertained early in the product adoption lifecycle Another use case for is populating a UAT or a DEV tenant with Apps from another tenant Path to Migration First and foremost, a migration is possible as documented in @williamsmt blog which provides a detailed walk through of the entire migration approach.
In this post, I’ll be covering how you can automate the process of building a Windows 10 images on your Lab. As a part of my daily job working with Workspace ONE Unified Endpoint Management, I work with a lot of Modern Management use cases and this requires testing various use cases on various versions of Windows 10. To always start with a clean image, I use Packer to build and enroll the device for me into my lab UEM tenant thus speeding up the process and reducing the probability for errors.
I’ve talked about why everyone needs a homelab in my medium article but never had the courage to submit my homelab to the community homelab list maintained by William Lam Follow. Mainly because I wasn’t sure how my lab would stack up against everyone elses' submission. With my latest post covering my experience enabling Tanzu with vSphere in my homelab, I feel like I’ve gone through the checklist of best practices and I’m proud of my minimalist(if i can say so myself) homelab setup!
For most folks that have been involved with SDDC for some time, this is going to be a lot of basic and obvious. As a quick disclaimer, I’ve to add that when i started down this path back in April, 2020(which was around the time vSphere 7.0 was released), I was (and still am) pretty new to the world of Home Lab and SDDC. As someone who has primarily worked on the application/software layer, I have been oblivious to the underlying infrastructure that made it all possible.