Fabian Lenz is known for his practical and theoretical knowledge in the field of virtualization and datacenter technologies. Fabian holds a Master of Science in International Information Systems.
The main focus of his work is based on VMware solutions. Besides the very deep knowledge within this field (approved by several vendor certifications) Fabian has a good overall IT-Service/-Infrastructure know-how, as well as a deep level of understanding in programming, automation, project management and software-development.
Besides that, Fabian Lenz blogs on vLenzker.net and performs public speaking and moderation arrangements. Either in an entertaining role at local tech events, or, more serious, during technical presentations.
My recent blog posts:
It’s this time of the year again where a lot of us need to decide. Shall I go to this year’s VMworld? From time to time discussions come up with statements like:
“(#VMworld) is not the same any more…..When I was young, real knowledge and content was presented… . I was at #VMworld in the old days before it was cool….Virtualization is legacy, Azure and AWS is the only thing that counts”
Who am I to contradict those statements (even though the are wrong :P). I will try to give you my opinion why #VMworld is still the tech-conference highlight of the year.
If it’s your first time visiting VMware’s US event I am going to create a second article called ‘let’s visit #VMworld’ about some personal tips and tricks how to get the maximum out of this years #VMworldRead More
Two weeks ago I had the pleasure to spent 4 days on problematic Applications within an App Volumes environment of a customer. The best thing that can happen to me as an infrastructure guy is to work on building AppStack with guys who know how to package and therefore troubleshoot those applications. Bringing together the knowledge from multiple domains helped us to fix the problems that we had so far with App Volumes.Read More
Using #VMware’s Unified Access Gateway (UAG) for internal #Horizon 7 connections – Design Discussion
Over the last months I gathered more and more experience about VMware’s secure Linux appliance that allows secure access to a virtual Desktop (and more) over an unsecure network (e.g.) the Internet: Unified Access Gateway (UAG).
Keep in mind the UAG is not just a replacement for the old Windows based Security Sever, it is also offering much more functionality (Edge Services for Airwatch / Workspace One, reverse proxy, 2nd-factor authentication integration, etc.).
There might be use cases where we want to design our horizon environment in a way that we use the UAGs not just for external unsecure access, but internally as well.Read More
I love the vCenter Server Appliance. The migration works pretty well. Still from time to time I stumble across minor problems (which until now were always quite easy to workaround/fix).
One of this migration ‘issues’ I was faced with recently at a customers site.
We migrated a vCenter against an ESXi host which was using a distributed switch and the corresponding portgroup as a target network.
Since we add the virtual network adapter directly on the ESXi host to the distributed switch we need to have an ephemeral portgroup (otherwise only the vCenter could add the VMs network adapter to this portgroup).
The general process of the migration look like the following.
- Deploy a new and empty vCenter Server appliance and connect it to the network
- A temporary IP-address is given to this vCenter Server appliance
- All relevant data of the source windows based vCenter Server is exported and transferrred over the network to the new vCenter Server appliance
- When the whole data-set is transferred, shutdown the original vCenter and give the new vCSA the network identity of the original vCenter
Migration of the #Horizon View Composer to another machine (including a database migration from Oracle / Microsoft)
Within the vSphere world we have currently one goal regarding our vCenter. Migrate it from a Windows based installation to the vCenter Server Appliance (vCSA).
The doing of this migration is pretty straight forward and works pretty well (e.g. here). But since we will shutdown the original vCenter VM based on Windows afterwards we need to make sure how to deal with applications that were running besides the vCenter.
We need to migrate them as well. Especially in case of the Horizon View Composer we need to do some proper planning, otherwise our linked-clones (which require the composer) cannot be created and maintained anymore (refresh, rebalance, recompose (R-R-R) operations).
Doing that migration is quite straight-forward. But we need to do some specific and not very well known tasks before we can do all of the steps.Read More