Blog

I recently worked with a customer because their C: drive was out of space. He had another drive in their laptop (D: drive) that had 500GB of free space.  I decided to move all offline files from the C: drive to the D: drive. I found the following article and worked through it:

https://support.microsoft.com/en-us/kb/942960

After getting the offline files synced, I started working to clean up the old location of the offline files. I took ownership and I was able to delete most of them, but I kept getting an error that I could not delete some of the files because “the file name was too long”. I spent a long time researching and trying to figure out how to gain this space back by deleting the files. I eventually created a share to the folder, accessed it from another system, and I was able to successfully delete it from there.

Recently, a customer said they were no longer able to shadow remote desktop sessions for some new thin clients that were installed.  The error message was "Access is Denied".  It turns out that these new thin clients were dual monitor setups.

According to  https://support.microsoft.com/en-us/kb/2484290 , this is normal behavior when trying to shadow a multiple monitor session.

After installing Windows 10 and Office on a new laptop, I started getting the following error message when I tried to click on any link in any email message or click on a table of contents link in a Word doc:

"Your organization's policies are preventing us from completing this action for you. For more info, please contact your help desk"

While it's not an entirely bad thing to have email links require a copy and paste, it's a real problem with other links like the Table of Contents in a long Word document.

There is a KB article at https://support.microsoft.com/en-us/kb/310049 that discusses this issue. The solution for Windows 10 is to find a system that doesn't have the problem and export a registry key then import it into the offending system. The key it references was missing from my system.

The steps that worked for me were to find a Windows 10 system that didn't have the problem, run regedit and locate the following subkey:

HKEY_LOCAL_MACHINE\Software\Classes\htmlfile\shell\open\command

Then you export the subkey to a file, copy the file to the system having the problem and import it into that system's registry (either by double clicking the .reg file or importing it via regedit).

There is a last verification step to verify the String (Default) value of "HKEY_CLASSES_ROOT \.html" key is "htmlfile".

I was recently working on a project to migrate a customer from a physical server to new virtual servers on a new ESX host. I installed ESXi 6.0 Update 2 on the new physical server and delivered to the customer site. After the server was onsite, I began building my first virtual machine. Since it was the first virtual machines and vCenter was not installed yet, I downloaded the VI client and connected to the host.

While creating the first VM, I received the following warning:

"If you use this client to create a VM with this version, the VM will not have the new features and controllers in this hardware version. If you want this VM to have the full hardware features of this verison, use the vSphere Web Client to create it."

According to the warning message, I needed to use the vSphere Web Client to create a VM with the latest full hardware feature set. The vSphere Web Client is part of vCenter, so I didn’t see how this was possible because vCenter was not installed yet. VMware has been planning to obsolet the VI client and moving to the web client, so I figured this was just a push in that direction. Obviously, this doesn’t work well for customers who are just building their first virtual servers. I didn’t need the new hardware features, so I just picked Virtual Machine Version: 11 and continued building the VM.

A few days later I was curious as to what the warning message meant and decided to do some more investigation. It turns out that with ESXi 6.0 Update 2, VMware started embedding a new VMWare Embedded Host Client (EHC) in ESXi. This new Embedded Host Client is a HTML5-based tool to directly manage the ESXi host and is a replacement for the VI client. This is nice because nothing needs to be downloaded or installed to manage the ESXi host using the EHC.

Here's a screenshot of the new EHC:

Knowing that the EHC exists, I now understand what the warning message I received when using the VI client was saying. They were not necessarily saying I had to use the vSphere Web Client that uses vCenter, but rather that I could connect directly to the ESXi host using the Embedded Host Client.

The VMware Embedded Host Client can be access by going to http://IPAddressOfESXiHost/ui. More information on the VMWare Embedded Host Client can be found here: http://blogs.vmware.com/vsphere/2016/04/vsphere-6-0-update-2-whats-new.html

Windows 10 includes a Spotlight feature to provide random background images that appear on the lock screen. Some of these images are very nice so I found a way to save them for use on other devices like a phone or tablet.

• Navigate to C:\Users\<username>\AppData\Local\Packages\Microsoft.Windows.ContentDeliveryManager_cw5n1h2txyewy\LocalState\Assets. The <username> should match your current Windows profile. You might have to enable “show hidden operating system files” to navigate to this folder.
• The images are saved with GUID-type name without a file name extension, but they are in JPG format. I’ve found it’s easier to copy them to a different folder, then add the “.jpg” extension to preview them in your favorite picture viewer.
• The images are rotated pretty frequently so you’ll want to check right away if you see an image you like. If you’re browsing the folder use the modify date on the file to determine if it’s new.
• The same image will likely have multiple files for different resolutions and orientations (landscape or portrait).
• To make future navigation to this folder easier, you can create a shortcut or pin the location to the Quick Access section in Windows Explorer.

The traditional method of opening Windows Task Manager, going to the Users tab, right clicking the user, and clicking Remote Control is no longer and option on Windows Server 2012 R2.

To shadow a session in Windows Server 2012 R2, you must use the "mstsc" command with the /shadow switch. First, open Windows Task Manager and go to the Users tab. Find the ID of the user you wish to shadow and remember this number. Then, from RUN or a Command Prompt, type “mstsc /shadow:<session id>”. The user will be prompted to allow you to shadow their session. This will work on Remote Desktop and normal servers.

If the server is a Remote Desktop Server, you can use Server Manager to shadow the session. Go To Remote Desktop Services, then Collections, and find the Connections window. Right click the user and click Shadow. The user will be prompted to allow you to shadow their session.

This is handy if you need to quickly connect to the console of a VM and don't need any other features of the vSphere web interface. The documentation from VMware says to run this from the web interface, but it can be run standalone, like this:

"C:\Program Files (x86)\VMware\VMware Remote Console\vmrc.exe" "vmrc://DOMAIN\[email protected]/?moid=vm-VMID"

VCENTER.DOMAIN.COM should be replaced with the FQDN of your vCenter server.

The "DOMAIN\USERNAME@" can be omitted, but if you are saving this command somewhere, you might as well include your username.

Use VMware PowerCLI PowerShell command "get-vm MACHINENAME | fl id" to find the VMID.  Just use the part that starts with vm-.  You can also get these from the ESX console.  

Download VMRC from here: https://my.vmware.com/web/vmware/details?downloadGroup=VMRC90&productId=491.  There is a link to this on the vSphere web page.  This requires an account with VMware.

For some versions of the TPM chip found in the Lenovo ThinkPad T420, you will receive an Access Denied error message when attempting to encrypt the hard disk if you have a group policy enabled that restricts CD/DVD access.  Apparently, some models of TPM chip are seen by the system as a CD/DVD device, and will not function correctly if it has been disabled via Group Policy. 

The fix is to just disable the group policy until after the disk has been encrypted and the PIN has been setup.  Once it has been encrypted you can reapply the Group Policy and it will continue to function normally.