This is part one of a three part series "Protecting Your Unidesk VDI Environment" from Unidesk Solution Architect Greg Deuscher.
An important part of any VDI deployment is planning for disasters. What would you do if you had a catastrophic storage failure to a Datastore where you would not be able to recover your data? If it were just a Datastore that held a secondary Cachepoint you could use the built-in Unidesk desktop repair functionality to restore the desktops from the failed Cachepoint to one of your other Cachepoints using the most recent backup of the personalization layer. The built-in Unidesk personalization backup function gives you the ability to recover from the loss of a secondary checkpoint, right through the web GUI.How To | Read this post >
So if you are an avid user of Google Chrome as your default web browser, like to stay up to date with current versions, and manage an Unidesk environment, you will want to keep reading.How To | Read this post >
If you have followed my work at Unidesk you know I am a big proponent of scripting to help manage large VDI infrastructures. Back in the day, this meant using vbscript, cmd script or even things like kix which provided very easy and powerful log-on scripting. However now Microsoft PowerShell scripting for Windows Desktops has taken on a new level of power. You can do almost anything in Windows via PowerShell. That said you can do a lot by including PowerShell scripts when a machine boots or when a user logs in. But sometimes you really need to be able to make changes directly over the network.How To | Read this post >
This post is part of the series "Understanding Your Desktop Use Case" by Unidesk solution Architect John Le. Part one of this series is here.How To | Read this post >
This post is part of the series "Understanding Your Desktop Use Case" by Unidesk solution Architect John Le.
While Unidesk is connection broker and remote protocol agnostic, I get asked a lot about which remote protocol is best or better to use with Unidesk. People have natural preferences towards things that we know or have done in the past, so it’s only natural anyone new to VDI would phrase general inquiries like this. Determining what is “best” is really a matter of defining what would constitute the ideal situation based on your specific business objectives.How To | Read this post >
One thing that is certain about managing a large group of desktops is that you can’t have enough information about how your service is utilized. As VDI Admins we make many decisions based on what our users tell us. As an example, I have a customer with a very large VDI deployment of more than 4,000 desktops. This is a school district, and they are set up where every school has its own VMware View Pool. When they set up the environment they created the number of desktops in the pool to match what the school administrators told them would be the number of desktops required for the school.How To | Read this post >
By default, when VMware or Microsoft create a virtual machine it is created with a floppy drive. Many VDI administrators do not want their users to see the floppy drive considering floppy drives are not used in VDI and really not used anymore for physical computers either.How To | Read this post >
The other day I was following a thread in our forums. It involved a customer that was following our Microsoft Office recipe and was trying to enable Windows Update so that it would install updates for Office in Windows 7. In the recipe we recommend that you do not start any Office application due to the fact that it will try to activate. If it activates, it will generate a unique activation ID that you then have to go out and rearm the installation so it gets rid of the ID. The reason they needed to start an application, like Word, is because Office will detect that automatic updates for other Microsoft applications is turned off. It will prompt you to turn them on and then automatically do that for you.How To | Read this post >
This topic comes up every so often, for some reason last week I was asked this by three separate customers so I thought I would do a blog about it.
How can I make the user of a desktop a local Administrator of that desktop? There are several ways to allow a group of users to be local administrators on all desktops. You can handle this through a startup script or a Group Policy Preference. So for example you add the Domain group "Domain Users" to the local Administrators group via a startup script or in Group Policy Preferences. I have blogged on this in the past and developed scripts to help out if you want to take this approach see www.virtualdesktopmanagement.net.How To | Read this post >
I was working with a potential customer the other day and they had mentioned they wanted to customize the performance of Visual Effects for the Windows Explorer in Windows 7. After some quick investigation, we realized that there was no dedicated GPO to control that feature. In order to get the customizations pushed out to all the Unidesk desktops in their environment I came up with the following procedure to create a registry script that will make these changes for you.How To | Read this post >
Back a few years ago, I wrote an article about Group Policy Objects (GPO) and how to apply them to Terminal Services. I was reviewing that article the other day, and realized that it is still relevant today in relation to VDI. So I figured I would do some updating, and go over that as well as how to do some basic work with profiles.How To | Read this post >