15 posts tagged with "jnorman"

Scenario: As a company, you are not allowed to make changes directly to any production environment. As such, you must implement a pilot testing methodology that allows a progression of testing environments for different groups to approve changes before those changes are promoted to production. How do you accomplish this with Frame?

This blog series centers around Frame Image Management. Image Management is “How do I set up my environment in the most optimal way, to minimize the number of images I have to manage?” Part 1 of this series covered how to onboard and configure SaaS applications. Part 2 covered how to install persistent applications into a non-persistent workload. Part 3 covered how to preconfigure user-specific settings for all users from the Sandbox. This blog post will cover another common virtual desktop use case, how to implement a pilot testing methodology using Frame. Due to the nature of persistent vs non-persistent Frame accounts, this post will cover this process from a non-persistent perspective.

In previous blog posts, we talked about optimizations as they related to the Windows Operating System, including Active Setup, the Microsoft Store, Services & Scheduled Tasks, and more.

The focus of this blog series will be Application Optimizations. We started this series with our Introduction to Application Optimization, which showcases common items to look for when it comes to Application Optimization. We followed up with Application Optimization Essentials: Google Chrome, then soldiered on with Application Optimization Essentials: Microsoft Edge, before rounding out the most common browsers with Application Optimization Essentials: Mozilla Firefox. We then switched to a different type of application next, Adobe Acrobat Reader. This blog will deep dive into a common application, and one that is generally forced on you whether you like it or not, Microsoft OneDrive.

Scenario: As an administrator, you are providing applications to your users through Frame’s desktop experience, application experience or any hybrid of both. Some of these applications are client-server applications and have input requirements on a per-user basis, such as server name, etc. You want to remove the extra complexity of manually entering this information from your end users experience. With Frame, how can you accomplish this?

This blog series centers around Frame Image Management. Image Management is “How do I set up my environment in the most optimal way, to minimize the number of images I have to manage?”. Part 1 of this series covered how to onboard and configure SaaS applications, while Part 2 covered how to install persistent applications in a non-persistent environment. This blog will cover another common virtual desktop use case: how to preconfigure user-specific settings for all users from the Sandbox.

In previous blog posts, we talked about optimizations as they related to the Windows Operating System, including Active Setup, the Microsoft Store, Services & Scheduled Tasks, and more.

The focus of this blog series will be Application Optimizations. We started this series with our Introduction to Application Optimization, which showcases common items to look for when it comes to Application Optimization. We followed up with Application Optimization Essentials: Google Chrome, then soldiered on with Application Optimization Essentials: Microsoft Edge, before rounding out the most common browsers with Application Optimization Essentials: Mozilla Firefox. This blog will deep dive into another common application Adobe Acrobat Reader.

Scenario: As a customer, you want to simplify your image management overhead by providing non-persistent Desktop Experience workloads to your users, but some users require access to non-standard applications that you don’t want to put into the base non-persistent image, nor provide via an Application Experience from another Frame Account, nor provide via a persistent workload. How do you accomplish this with Frame?

In previous blog posts, we talked about optimizations as they related to the Windows Operating System, including Active Setup, the Microsoft Store, Services and Scheduled Tasks, and more.

The focus of this blog series will be Application Optimizations. We started this series with our Introduction to Application Optimization, which showcases common items to look for when it comes to Application Optimization. We followed up with Application Optimization Essentials: Google Chrome, then soldiered on with Application Optimization Essentials: Microsoft Edge. This blog will deep dive into another one of the most commonly used browsers: Mozilla Firefox.

Operating systems can end up being a lot of work for administrators: work to configure the image, work to install the applications, and work to provide the best user experience possible. As with any software, what is provided to you is what the developer intended, but not necessarily what you want or need for your end users.

This blog series introduces you to Windows Operating System (OS) optimizations, starting with version 21H2. I will attempt to keep these optimizations as environment agnostic as possible. Hopefully, these optimizations will be just as good to administrators of physical machines as to a virtual environment utilizing Nutanix Frame, Citrix Virtual Apps and Desktops, or VMware Horizon.

This series aims to share the seemingly infinite number of ways you can optimize a Windows environment, with something for beginners as well as administrators familiar with optimizations but looking to deliver an even better experience within their environment.

Of course, the optimizations provided in this blog series are intended only as a guide. Be sure to vet any optimizations carefully and test the optimizations described in this series internally before pushing the changes to your production environment.

The first entry covered Active Setup. The second entry covered the Microsoft Store. The third entry covered Services and Scheduled Tasks. The fourth entry covered Startup Items. In each case, we discussed what each piece is, how it works, and how to optimize it.

This blog addresses three smaller aspects of your Windows Operating System: Autologgers, Features On-Demand, and Optional Features. While these three items are smaller than any of the previous blog posts individually, there are some definite optimization efforts to be considered here.

Scenario: As a customer, you want to use Frame to provide access to Software-as-a-Service (SaaS) applications. SaaS applications are also known as web-based software applications, meaning your main form of access to the application is through a web browser, such as Google Chrome or Microsoft Edge. You want to utilize the Application Experience to provide these applications to your users. With Frame, how do you accomplish this?

In previous blog posts, we talked about optimizations as they related to the Windows Operating System, including Active Setup, the Microsoft Store, Services & Scheduled Tasks, and more.

This blog series will focus on application optimizations. We started this series with our Introduction to Application Optimization, which showcases common items to look for when it comes to application optimization. We followed up with Application Optimization Essentials: Google Chrome. This blog will deep dive into one of the most commonly used browsers: Microsoft Edge of the Chromium variety.

In previous blog posts, we talked about optimizations as they related to the Windows Operating System, including Active Setup, the Microsoft Store, Services & Scheduled Tasks, and more.

The focus of this blog series will be Application Optimizations. We started this series with our Introduction to Application Optimization, which showcases common items to look for when it comes to Application Optimization. This blog will deep dive into one of the most commonly used browsers Google Chrome.