Part 1 of a 2 part blog
Windows Virtual Desktop represents a transformational shift in the EUC space and will be looked back upon as an accelerator in the evolution of this industry. As a larger community, we’re still in the honeymoon phase of our relationship with WVD. We all see great opportunity, we’re excited about the potential of this new technology and many customers, CSP and MSPs are working to figure out how to leverage WVD.
WVD is a set of complex Azure services managed by APIs and PowerShell scripts. WVD Azure services are all basically run from PowerShell. Not only does this allow for incredible flexibility and agility, it enables creativity and community shared content.
We’re already seeing community PowerShell contribution from numerous thought leaders in this space, through Twitter and other outlets, that add value to WVD in a number of creative ways. Unfortunately, without professional support services, these nuggets of potential value can become business risks if you are not aware of what you are doing.
What happens if the PowerShell script you got from a blog post stops working? If you didn’t write the script or take the (large amount of) time to learn and document it, you’re stuck. That feature, function or management approach was built into your business, your standard operating procedures rely on that function but if it breaks, you better understand PowerShell, WVD and the dependent services that you built on that PowerShell — oh, and don’t forget to document what you changed to make it work.
Nuances of PowerShell scripts to perform certain tasks are not always documented adequately. If you know PowerShell, you have had the experience of trying to re-interpret your own (let alone a predecessor’s) scripts and code. What was I thinking? Why did I do it that way? Etc. The saying “up a creek without a paddle” may never have found a more appropriate use.
If you want to do it yourself, who’s dime are you learning on? Your company’s? Good, just don’t deploy a pilot or production in your ‘learning’ environment.
Disparate deployment methods, one off customizations and custom built solutions can solve complicated problems from the start, but operationally, this becomes a problem.
- Who supports it? How is it supported? What is the escalation path?
- Who documents what has been done?
- Who documents what needs to be done?
- What change control is used, if at any?
- How many PowerShell experts do you have on staff? (it better be more than 2)
- What is your timeline to deploy WVD? What is the priority for WVD deployment?
- Does your organization have and follow secure development methodologies?
This is a throwback to the build versus buy debate.
Unless you understand the implications of your configurations, you are prone to security and misconfiguration issues. This is no small consideration. Security breaches due to misconfiguration are regularly recognized in OWASP’s Top 10 Security Risk list.
If experience has taught us anything, it’s that operating in a ‘wild west scenario’ (like you are exploring a new frontier) is a security and business continuity risk.
PowerShell is a beautiful way to automate configuration changes to your WVD environment. Security automation and orchestration can reduce human error of misconfiguration and fat-fingering. Automation is essential for managing at scale. However, you can automate “bad” practices just as easy, if not easier, than “best practices” if you aren’t careful.
No PowerShell Expertise Needed for WVD with CloudJumper
WVD is complex set of Azure PaaS services that, arguably, requires, at a minimum, an intermediate level of PowerShell acumen. CWMS eliminates the requirement of PowerShell expertise. It overlays the WVD Azure environment with a simple web interface. CWMS funnels hundreds of deployment options into a few key questions, in a familiar web UI, then orchestrates a custom environment. With CloudJumper, you are just minutes away from deploying thousands of new WVD VMs – no PowerShell expertise required.
CloudJumper orchestrates and manages the delivery of virtual applications and desktop deployments through a single pane of glass — without redirection, or competing with any Azure services.
In part 2 of this blog, we’ll discuss other pros and cons of PowerShell and the BYOS (bring your own support) model.
This is Part 1 of a 2 part blog. Read the 2nd part.
CloudJumper is an automation, orchestration and workflow solution used to deploy and manage VDI and RDS workspaces. Consider us the industry’s best alternative to the big guys. CWMS is a native web service running a graphical UI for the deployment, orchestration and management of WVD, VDI and RDS workspaces – no PowerShell needed. CloudJumper is a recognized Microsoft Preferred Solution Provider for WVD. Our product team worked alongside Microsoft for two years developing a native Azure solution.
Customers and MSP Partners have been trusting CloudJumper for nearly 20 years in the managed workspace industry. We have thousands of customers running tens of thousands of applications and desktops.