Old Servers listed in DHCP Server list

When opening a DHCP console on domain that had been in operation since 2008, and gone through a number of upgrades, migrations and repairs, a number of old servers were still listed.

To remove these, as a domain administrator, verify the data by running:

netsh dhcp show server

To remove the servers, use the command:

netsh dhcp delete server %FQDN% %IPADDRESS%


netsh dhcp delete server dc03.anonit.local

If the response is

Deleting server with dc03.anonit.local,
The specified servers are not present in the directory service.

Open adsiedit.msc and navigate to Configuration / CN=Configuration / CN=Services / CN=NetServices

In this container, depending on what you see is how you proceed:

In the example above, the DhcpRoot container DHCPServers attribute was empty, and we needed to remove one of the extra entries (the bottom one on the list).  Once deleted, the output from netsh dhcp show server was correct, and there were no more extra servers showing up in the list.



Synology exFAT support

I had a Synology DS418 NAS drive, and needed to attach a USB drive to get some data off it as a one off operation.  I found the drive formatted as a exFAT drive, and out of the box, Synology doesn’t support that.  They have an add on in their store for $3, but given the amount of money I paid for the unit, and I knew it ran linux, and this was a one off operation, I thought I’d do some digging to see if I can bypass that restriction, and learn something in the process.


A Synology NAS;

A linux PC (a Raspberry pi was used in this example);

(A Windows PC was used to download the files and transfer them via winscp).

Download the relevant exfat-fuse file for the NAS architecture from https://packages.debian.org/stretch/armel/exfat-fuse/download (In this example I used exfat-fuse_1.2.5-2_arm64.deb)

Transfer this file to the Linux PC if necessary (it can’t be extracted on the NAS itself).

Extract the files:

$ dpkg –extract exfat-fuse_1.1.0-2_armel.deb .

(Note the full stop at the end of the line)

In the control panel of the NAS web UI, enable SSH, and login via SSH.

Copy the extracted file /sbin/mount.exfat-fuse to the NAS placing in the /opt/sbin/ directory.

Without the USB drive attached to the NAS, run an ls /dev/, then connect the usb drive, and do the same.  Look for differences in the directory, this will be the USB drive.  In my case it was listed as sdq, and the partition I wanted was sdq2.

Run the commands:

$ mkdir /mnt/exfatusb
$ ./mount.exfat-fuse /dev/sdq2 /mnt/exfatusb

to mount the USB drive.  You can then copy the files to the required directory and unmount the drive:

$ cp -av /mnt/exfatusb /volume1/retroPIE
$ umount /mnt/exfatusb

From the above command you may also be able to work out a project I am currently working on!

I have attached the relevant files here:

Synology exFAT support



Opening HLP files on Windows 10 x64

I needed to open a HLP file on Windows 10 x64 v1903.

There are a number of posts and threads, and some differing advise.  I found the following:


Download the msi file.

SHA256:  CE4C0FFB97BDAE423D197EC902DB88F298B699E7279F315C0694C7F48A7BD546

SHA1: AC30060E6442CF260C63D47FB12E2DE0DE1FE661

MD5: 10BA7330EAB7DBAEC93BEE5112DF47D4

Upload to VirusTotal to check.

I then ran the MSI and installed the application.

This allows the file to be opened from within Explorer.  Native help within applications may still fail.

Get the command line of a running process via powershell

If you need to get the command line of a running process you can use powershell:

gwmi win32_process -filter "name='vmware-vmx.exe'" | where-object {$_.commandline -like "*ex02*"} | select commandline, processid | fl

The above will get the commandline and processid of the vmware-vmx.exe process that has a command line containing *ex02*

Create a temporary folder in powershell

I needed to create a temporary folder. I modified the code found here https://stackoverflow.com/questions/34559553/create-a-temporary-directory-in-powershell. One issue in the original code was the chance (albeit extremely slight) of having a name collision with an existing folder. The script below checks and tries 5 times before failing. It isn’t neat, and is somewhat of a brute force method of getting around the issue, but it gets the job done. You can see the modified code here https://pastebin.com/DPfj3iT7