Working From Home

Covid19 has changed the world. It seems everyone is now working from home, or slowly getting back to work. Here a re a couple of things to consider, I’m sure this is behind the times, but it’s still relevant.

I'm Back! Thanks to Covid19

I am back online. I have not focused on my technology website. A couple of reasons for this, too much work and too little time. Second, it has not been a priority. My site was infected with a security vulnerability which required some code rewrites and updates. These have all been addressed and I'm back online.
In the coming weeks I'll be adding content regarding some of the last projects centering on Horizon Workspace One, Citrix Cloud, AWS, and Azure.

My Hiatus is Over

I've been busy with clients and consultants. I've let this site wallow. And I've gotten my pilot license so I can get to my clients faster and in most places.

I thought since I've been away this information on the sight might be out of date. But, I'm surprised. Many of clients are still on older hardware, older operating systems, and using older system. They aren't upgrading. I have clients still on XenApp 4.x, XenApp 6.x. And also older versions of VMware. Windows 2003 is still out there.

Why?

Powershell to Add Computers to AD

When I work with clients to assist with rapid building computers, often I will use the Wizard, but there are situations where I prefer to stage the computers in AD first. Rarely, do I want to build a group of computers one by one. So I use powershell to do this. Make sure you import the Active Directory module before you start. You may have to download the RSAT tools from Microsoft and enable them on your system. This script uses all of the native tools from Microsoft.

import-module activedirectory

Thick Disk v. Thin Disk -- "It Depends!"

It is surprising how often this scenario comes up, and I get asked the question, "Should we thin-provision or thick-provision our VM's?" My answer is almost always the same, "it depends." Today, I have the same answer, but for very different reasons from in the past. In the past, my answer was based on performance-related issues and saving expensive disk space. These are still very, valid concerns, however, now I answer based on risk. In recent days have been working with three different clients that have all experienced outages related to thin-disk provisioning.

Windows 7 x64 with VDI. Why do it?

Here is the spoiler -- don't do Windows 7 x64 for VDI.
Now let's talk about why. First, I'm going to give credit to Brian Madden's Blog, he mentions this also, and he is exactly correct. Windows 7 x64 uses around 200MB more memory than the x86 version. If you multiply this by the number of VDI users, it adds up quickly. (1000 desktops x 200MB equals 2 TB more memory). For a project I'm working on this equated to a requirement for 8 more servers because of x64.

Pages

Subscribe to vConsulting.us RSS