Wednesday, June 13, 2018

Dell TB16 Thunderbolt 3 Dock Installation Notes

I recently got a couple Dell TB16 Thunderbolt 3 docks. It was a little tricky getting everything to work correctly. These are my notes from the process.

When following these steps, start with the dock disconnected from the computer. Note that you'll need to have local admin rights on the machine. You'll also need to know the BIOS admin password if one is set.

  1. Run Dell Command Update to get the latest driver and BIOS updates. If it finds updates, continue running it again until it doesn't find any more. Sometimes it takes 2-3 runs for everything to install.
  2. Go to the TB16 driver page and download all 4 items. There should be 3 drivers and a firmware update utility.
  3. Install the 3 drivers and reboot.
  4. Connect the dock and give everything a minute to "settle down" - wait for the displays stop flashing and let the drivers for any USB peripherals connected to the dock install.
  5. Approve the Thunderbolt devices by setting the cable and the dock to "Always Connect".

  6. Go into Display Settings and set up your monitor arrangement how you want it.
  7. Run the TB16 firmware update utility and update the dock's firmware. You'll need to right-click the executable and "Run as administrator".
  8. Reboot

Friday, February 16, 2018

pcapfix - libssp-0.dll was not found

I was trying to use pcapfix on a Windows machine to fix corrupted Wireshark capture file, and I got an error that libssp-0.dll was not found.

A quick search of my C drive revealed that I had several copies of the file, so I copied one of them into the pcapfix directory and everything was happy.

If your machine doesn't already have a copy somewhere, the easiest way to get a copy is to install Git, and the file will be located in C:\Program Files\Git\mingw64\bin.

Sunday, October 30, 2016

Changing Keyboard Shortcut Behavior in PowerShell Studio

I'm a big fan of SAPIEN's PowerShell Studio. The editor is fast and PrimalSense (their equivalent of intellisense) is rock solid, unlike intellisense in the PowerShell ISE, which mostly works...sometimes...if you're lucky.

One thing that I don't like is how the behavior of the F5 shortcut key differs from the ISE - F5 runs the script in their special sandbox session rather than within the shell itself. At the time of this writing, there is no way to change this behavior within the program itself.

Enter AutoHotkey. AutoHotkey is open-source macro-creation and automation software. In this instance, I'm using its macro abilities to send Ctrl+F8 (run script in shell) whenever F5 is pressed, but only when the PowerShell Studio window is active.

I also set up Scroll Lock to send Ctrl+Shift+A (expand aliases to Cmdlets) and Ctrl+Shift+J (format script). If you're wondering about whether or not pressing Scroll Lock for this macro causes it to turn on the light on your keyboard, it doesn't.

First, download and install AutoHotkey. After that, navigate to the directory where you want to store your script and create a new AutoHotkey Script via the right-click menu.

Next, open your newly-created ahk file in your favorite text editor, paste the following code into it and save.

#IfWinActive SAPIEN PowerShell Studio 20
SetTitleMatchMode, 1 ; Title must start with the specified text to be a match

f5:: ; Run script in console
 send, ^{f8}}

Scrolllock:: ; Expand aliases to Cmdlets and format script
 send, ^+a
 send, ^+j

Double-click the file and it will run. If you want to reload the script after making changes, or exit AutoHotkey completely, this can be done by right-clicking the green tray icon.

Once you're satisfied that everything is working as desired, place a shortcut to your ahk file in the startup directory and you're done.

Monday, September 5, 2016

Notepad++ Find in Files

Several months ago, I wrote a post about some of the cool things that Notepad++ can do. Today, I'm going to share another feature that saved me a lot of headache - Find in Files.

After installing an update to an important application, I discovered that the installation path had changed. This was a problem because I had a folder full of scripts that reference this path. Thanks to Notepad++, I was able to fix this in about 3 minutes.

Using Find in Files

This should go without saying, but before you make any modifications to your files, make sure that you have good backups of everything.

When you're confident that you're ready to modify your files, go to Search > Find in Files, or press Ctrl + Shift + F

Text files prior to text replacement

When the Dialog box appears, simply specify the text that you want to replace, and the folder that you want to search in, and click Replace in Files.

After the replace runs, all the files within that folder should have the applicable text replaced.

Text files after text replacement

Monday, August 1, 2016

Sending Windows Key Shortcuts Over RDP

If you use Windows keyboard shortcuts, such as Alt-Tab, Win-R, Win-E, etc. you may have noticed that when you use use them in an RDP session that isn't full-screen, the action occurs on your local machine rather than the remote machine. Annoying, right?

To change this behavior, open the RDP client and click Show Options.

Next, go to the Local Resources tab and set change the Apply Windows key combinations: setting to On the remote computer.

Finally, go back to the General tab and click Save so that the RDP client will default to this setting in the future.

Sunday, July 24, 2016

Fixing VMware Client Mouse Issues on Scaled Displays

If you have a high-resolution display and are running DPI scaling in Windows, you may have experienced how frustrating the VMware vSphere desktop client can be. Accessing the console of a VM is a maddening experience where the mouse refuses to cooperate and makes it nearly impossible to accomplish even the simplest tasks.

A workaround for this is to disable DPI scaling for the client. Browse to the installation directory, C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher by default, and open the properties for VpxClient.exe. Under the Compatibility tab, check the box for "Disable display scaling on high DPI settings" and click OK.

The downside to this solution is that the client may appear tiny on your display because it's not being scaled like the rest of the desktop. It looks microscopic on my laptop's 15-inch 4k display, but at least it's usable. Fortunately, my laptop is docked most of the time, so I can just use the client on one of my larger external monitors.

Thursday, June 30, 2016

PowerCLI Error Updating Shortcut

I was trying to make the text bigger in the VMware PowerCLI shell. When I tried to apply the changes, an "Error Updating Shortcut" message. After clicking OK, the changes would apply, but wouldn't persist after closing re-opening.

This was happening because the program didn't have access to the shortcut, so it couldn't to modify it. To get around this error, simply run the console elevated (aka "as administrator"). The error should go away and the changes should persist.