Page 1

How To fix Windows 10 (Fall Update 2017) not able to connect to SMB share with Guest account

I recently updated my Windows 10 workstation with the Fall update and after the update all seems to work fine. Except when I wanted to play some music on my system that is located on my NAS (freenas). It complained it couldnt find the file. After checking Windows Explorer (My Computer) and noticing the File Share was disconnected I tried checking the PING to the NAS. The system was up&running.

Logging in to the Freenas and checking the mount points but all showing OK and also all the disks where OK. Hmm… strange…

After searching I found that Microsoft for some reason disabled the AllowInsecureGuestAuth and also the Error message when trying to connect to the share showed me there was an Issue with the Guest account.

This is how I fixed the issue:

  1. Go to Start and run “Regedit
  2. browse to the following key “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
  3. Check if you find a DWORD value with the name “AllowInsecureGuestAuth
    1. If it is not already on your system create a DWORD (32bit)
  4. Modify the value of “0” to “1”
  5. Close Regedit

No reboot required!

Try to reconnect the drives and they should appear on your system.



SharePoint 2013 setup fails because of .NET Framework issue

While installing a new SharePoint 2013 system on a Windows Server 2012R2 I encountered an error while starting the Setup for the first time. The installation of the Prerequisites went fine and after several reboots i was ready to start the SharePoint 2013 installation itself.

After starting the Setup SharePoint is going to check if the system requirements are met. One of those requirements is the installation of the .NET Framework 4.5. If there is not .NET Framework 4.5 installed the setup will fail and you will be unable to continue the installation. This is exactly what happened to me…

First i made sure the .NET Framework 4.5 was installed by checking the Add Roles Features option, this was the case. So there should be some other error. As I didn’t install the Server itself i started looking for updates that might caused this issue. I did found the answer in: .NET 4.6.*

While installing the system, the engineer did run the Windows Updates so the system is up-to-date, this was also causing the setup to fail. Make sure you check-out what .NET Framework version is installed on your system and if needed remove the Update that is causing the system to be running 4.6 or 4.6.1

Check the registry and then the Release key to make sure what version you are running
Also you could try to trick the installer by exporting the key, modifying the Version and Release key to fake the installer, then install SharePoint and switch back to the 4.6 keys you exported.

Just for your information, Sharepoint 2013 is compatible with .NET Framework 4.6 and .NET Framework 4.6.1


Check the progress of the Shrink Database task in SQL Server

Today I had to shrink a database that was about 250GB and had 100GB free space to create some space on the disk. After running the command you are not able to see the progress of the Shrink, and as this can take some time you want to see how the action is proceeding.

To see the progress of the Shrink Database task you can run a query that will give you some information about the task. Run the following Query in a “New Query Window”

command = 'DbccFilesCompact'

This will show you the following information: “Percent_complete”, “start_time”, “cpu_time” and some more information. Keep in mind a shrink can take some time!


Microsoft Dynamics AX 2012R3 CU8 demo vm shutting down

Because we have a support case with the MSFT team I was asked to download some Microsoft DEMO vm’s for Dynamics AX 2012R3 CU8. When i downloaded the VM’s and started these everything was working fine for a few minutes. I was making some modification when suddenly the VM shuts down. Now I found out the License was Expired and then the Machine auto shuts down.

This can be tracked in the EventViewer where the VM tells you it is shutting down because of an evaluation version.

Rearm the machine to keep working

You can rearm the machine so it will stay online and you can keep testing with it. To do this follow the steps below:

  1. Login to the Virtual Machine with the Administrator credentials
  2. Start an elevated CommandPrompt (run as administrator)
  3. run the following command:
    slmgr /dlv
    Check if you can still rearm the machine (remaining number of rearm)
  4. run the following command to rearm the machine
    slmgr /rearm
  5. Reboot your server
  6. Njoy

VMware Workstation and Hyper-V on Windows 8.1

As I’m working a lot with Dynamics AX and the Microsoft Demo VM’s, i was in need of VMware and Hyper-V on my notebook so I could run my VM’s for VPN and run Hyper-V for the Microsoft DEMO machines.

Now you can install both of them in Windows 8.1, but when you try to start VMware you get an error message:

VMware Workstation and Hyper-V are not compatible. Remove the Hyper-V role from the system before running VMware Workstation.

This message is because the Hyper-V role is installed on your workstation and it is not compatible with VMware. To work around this issue you can modify the Hypervisorlaunchtype for Hyper-V. I made 2 CMD files with the following content. Run them as Administrator and you can enable or disable Hyper-V so you can work with either VMware or Hyper-V.

You must reboot your system after running the CMD files

Disable Hyper-V (to work with VMware) save this file as CMD file
@echo off
echo Turning off Hyper-V services
bcdedit /set hypervisorlaunchtype off
echo Modified the BootFile, please reboot...

Enable Hyper-V (to work with Hyper-V) save this file as CMD file
@echo off
echo Turning ON Hyper-V services
bcdedit /set hypervisorlaunchtype auto
echo Modified the BootFile, please reboot...

You need to run both the files as Administrator


Perflib (WmiApRpl and BITS) on Server2012 and SharePoint 2013

I have been searching for a way to get rid of some performance counter errors (WmiApRpl and BITS) on my SharePoint 2013 installation for a while but couldn’t find the answer. Today I decided to have a look with Process Monitor and finally found a solution.

The w3wp process tries to access to registry keys but does not have the permissions.

After granting the WSS_WPG group full control(you probable can get away with a little less) to the following registry keys, the errors went away.



Missing Private Key on IIS

Yesterday I was working on a new Sharepoint setup for a customer, and this website needed to be SSL only. So only on HTTPS instead of both HTTP and HTTPS. The customer did help us by already buying the Certificate.

When I got at the point I wanted to install, I did just finish the wizard in IIS, and installed the p7b certificates. So all the certificates were installed in the proper location and in the Computer MMC and not the USER mmc (when starting MMC open the Certification Snap in as Computer and not User!).

I noticed i was missing the private key, while the certificate was installed properly. This way i was not able to select the SSL certificate for the Website in IIS. Asking the customer they told me they generated the CSR on a different machine.

WIth the DIGICERT TOOL we could export the whole pfx and then we did an import on the IIS machine using the same tool again. We could then repair the SSL Certificate.

So To move an SSL certificate without the PrivateKey you can use the DIGICERT Tool to Export the current certificate and key and then import it. Keep in mind you MUST have access to the machine where the CSR was generated.


Auto Update on SharePoint servers

Somewhere in October Microsoft decided to add a SharePoint update to the Windows Update system. This caused some Sharepoint servers that had enabled Auto Update to stop working and throwing errors all around the place.

Now on most servers we have disabled the following function:
Give me updates for other Microsoft products when I update Windows


This should disallow Windows Update to update Office applications like SharePoint, except it didnt do this for the update that Microsoft did sneak into a Windows update!

This resulted in a new Best Practice for our SharePoint servers to not Auto Update the SharePoint servers, we know this could be a possible Security risk, but it also could lead to a non working SharePoint Farm!


Let Windows only download the updates and manually install them so you can check for hidden updates. You can change this in the Control Panel –> System Security –> Windows Update, and just change the settings there.


Dynamics AX Batch Jobs in waiting status after Upgrade and CU updates

Today i was testing the new CU8 for Microsoft Dynamics AX 2012 R3, and after the full Compile and full CIL compile I got stuck upon the data upgrade list. The DataUpgrade job was in “Waiting” status and couldnt get it to start. After some digging and modifying the partitions to make sure the permissions were correct, it still didnt work.

With some google magic I stumbled upon the link below with a great check list for verifying if the BatchServer is configured correctly. Check it out below!