Being an “open” company does not just mean embrace open-source solutions. It’s also meant to be open and listen to our partners with VMware being one of them. Recently, we joined arms on the NSX space which is kinda exciting!
You are not wrong, this title is very much accurate. This year is going to be a very special VMworld for me as this will be the first time Microsoft will host a booth in the Solutions Expo as well as a couple of sessions.
So it’s been quite a while since I blogged, the longest “dry season” for me since starting. Why is that?! Well, I kinda flipped my life with moving to the US and becoming a program manager in Azure Compute R&D.
There are some announcements that make you feel like a kid again! about two hours ago, Microsoft announced the “Transforming your VMware environment with Microsoft Azure” program. This is our way to show VMware customers that there is another way, there are more options and that Azure is that cool!
During the last weekend, I took the time to start with some home lab upgrades. I wanted to start checking all the new vSphere 6.5 goodies and some of the cool new Windows Server 2016 features, Docker integration being one of them. The new integrated Update Manager is finally here and but unfortunately, my first interaction with it was around VIB conflict.
It’s been almost a year since I’ve started working for Microsoft. You know, when I got my VCDX a few months back, few people from the vCommunity asked me how is that helping me with my day to day Azure life. If you will add to that the fact that no one (well, almost no one) at Microsoft knows what it’s all about, you will get some brain processing.
The day of the remote defense has arrived. After all the mocks, Quizlets and mental prep, it all boils down to two hours of the most important WebEx session I had in my career so far.
As some of you may already know, VMware has started to offer VCDX remote defense for “returning players”. Being able to pass it, few questions came at my direction regarding the process and the experience so I thought why not to share.