We Offer Services
It’s a Story About Our Team

Great things are done by a series of small things.

August 28, 2019

Here’s a fix I discovered for a problem when running Quickbooks 2016 and DNS on a Windows 2012 server.


  • Users get the error Error Code: H202 This company file is on another computer, and QuickBooks needs some help connecting.
  • Quickbooks server manager service on the Windows 2012 server is not running.
  • When you run the QuickBooks Database Server Manager, and click Start Scan, it scans the folders, then get an error: Quickbooks network diagnostics failed. Resolve errors and retry.
  • If you try to start the QuickBooksDB26 system service, it starts and then immediately stops, giving the message, “The QuickBooksDB26 service on Local Computer started and then stopped.  Some services stop automatically if they are not in use by other services or programs.”
  • In the Application log on the server this error appears:”The description for Event ID 1 from source SQLANY 16.0 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.


In my case, the quickbooks database server, and DNS server are both using port 55333. If DNS is running first, quickbooks doesn’t choose another available port, but rather stops completely.

Quick Solution:

Stop the DNS Server service, then start the Quickbooks service.

This works, but you will have the same problem after a reboot.


Permanent workaround:

Stop the DNS Server service, and the Quickbooks service.

Reserve the port using netsh from the command prompt

“netsh int ipv4 add excludedportrange protocol=udp startport=55368 numberofports=5” NOTE THESE PORTS ARE DIFFERENT DEPENDING ON QUICKBOOKS DATABASE VERSION.

then start both services

See more info on the netsh command related to this.

More details on the quickbooks forums related to this same problem here.


Original Post: http://www.devonstephens.com/quickbooks-database-manager-conflicting-dns-server/

June 4, 2019

Here are the steps to uninstall Windows Defender on Windows Server 2016.

  1. Login to the Windows Server 2016.
  2. First of all ensure Windows Defender is running. You can run sc query Windefend in command prompt.
  3. Run the PowerShell command to uninstall Windows Defender on Windows Server 2016.

When you run sc query Windefend, if you see the state as RUNNING, that means Windows Defender is present and service is active on the machine.

uninstall Windows Defender

To uninstall the defender, open PowerShell and run the below command. Note that a server reboot is required once you uninstall the Windows Defender.

Uninstall-WindowsFeature -Name Windows-Defender

uninstall Windows Defender

In future if you decide to use Windows Defender, you can install it using a PowerShell command. Run the PowerShell as administrator and run the below command.

Install-WindowsFeature -Name Windows-Defender

uninstall Windows DefenderA reboot is required if you install Windows Defender on a Server 2016.


Original Article: https://www.prajwaldesai.com/uninstall-windows-defender-windows-server/


August 18, 2018

Windows Checking For Updates Stuck

Operating System Affected: Windows XP, Windows Server 2003, Windows Vista, Windows 7, Windows Server 2008, Windows 8.1, Windows Server 2012
Symptoms: Windows Update stuck “Checking For Updates” for long periods of time, related process (i.e. svchost.exe) runs constantly at 10-99% CPU even during idle
Cause: Windows/Microsoft Update Failure

I’ve expanded this post to include possible solutions for all windows editions affected. The symptom to look out for is if:
1) Windows Update is enabled and svchost.exe or an equivalent process is running continuously with high RAM and CPU utilization
2) Windows Update is manually started with “Checking for Updates” and it never stops. The checking for updates stage of the process should not take longer than a couple minutes and without fixing this I’ve let it run for days with no result.

The solutions are:
1) Completely disable the Windows Update service and live with no updates, not just setting it to “Never check for updates (not recommended)” as this doesn’t fully stop it
2) Upgrade to Windows 10 (not always an option)
3) Fix the problem outlined below for your respective operating system version

Install the following patches in right order (increasing KB package value) and according to the proper operating system, bit-architecture, and IE version (when applicable) [all important!].

Windows XP and Windows 2003

Windows Vista

Windows 7 SP1 and Windows Server 2008 R2

Windows 8.1 and Windows Server 2012 R2

With Office installed
Having Office 2007, Office 2010, or Office Compatibility Pack SP3 installed will also cause the same problem even if you installed any of the above patches. You’ll have to install the below patches as well if you’re still stuck on checking for updates phase.
KB4011605KB4011607 – Office compatibility Pack SP3
KB4011657 – Word 2007
KB4011602 – Excel 2007
KB4011659 – Word 2010
KB4011660 – Excel 2010

Although power consumption may not scale linearly compared to CPU utilization, a constant increase in CPU utilization is bound to result in higher power consumption and heat generation anyways, neither of which are great. Think about it, you have an office of computers running at 100% CPU 24/7 cause they’re searching for those updates, and for the longest time I had no idea this was happening. The computer just felt a bit sluggish, as once you start using it the OS will intelligently reallocate resources to what you’re doing, and we had computer components dying prematurely from being constantly used by Windows Update. Planned obsolescence at its finest.

Note: For Windows Vista, you’re wondering if you have to install all of them and really in that order? Yes, I’ve tried installing just the last two, just the first couple, any combination and this is the only way that worked for me. This solution was compiled for many sources, too many to list, but mainly bleepingcomputer and mydigitallife. Also, just updated from Vista because it’s truly terrible.

ARTICLE CREDIT GOES TO: http://blog.jonmwang.com/2017/04/19/windows-checking-for-updates-stuck/

July 30, 2018

I have been moving my environment to Windows 2012 R2 from Windows 2003 network recently. One of server roles I was moving was domain controllers. I had two of them, both running Windows 2003 SP2. After a fresh installation of Windows 2012 and adding 2 new VMs to domain I installed Adtive Directory Domain Services and promoted them to be domain controllers. All forest and domain preparations are made by the wizard, so only thing you do is to raise forest and domain functional level to be equal to 2003. Then I waited a bit (1 hour?) and moved all FSMO roles to new servers.  And that was the time I saw these warnings coming up on both Win 2012 machines:

Warning 13508 with NtFrs source on Windows 2012 R2

So I did some digging and I found out there is neither SYSVOL nor NETLOGON share on these servers, so they weren’t actually acting as domain controllers.. Further more dcdiag /q showed me a couple of failed tests on new machines and on old ones!

So after a day of research I found the solution, so here is what you need to do in this kind of situation:

  1. Perform a backup of your SYSVOL and NETLOGON shares.
  2. Get you PDC emulator back to old machine (in my case: Windows 2003 SP2). Open Active Directory Users and Computers console on your old PDC emulator, right-cklick on your domain and choose operations masters, then switch to PDC tab and click change. Check if it is propagated to all your DCs by typing netdom query fsmo on each of your DCs.
  3. Stop File Replication Service on all of your DCs. Use services.msc or type net stop ntfrs in a console.
  4. Go to your current PDC emulator (should be old machine now), open regedit and go to registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Paramaters\Backup/Restore\Process at Startup
  5. Change BurFlags value to “D4” using hex format.
  6. On all other controllers change the same value to “D2”. Please don’t make a mistake by typing wrong values on wrong DCs.. D4 on PDC, D2 on other DCs.
  7. Now start File Replication Service on your PDC emulator machine by typing net start ntfrs or through services.msc. Do it on all other DCs of your environment.
  8. Now you should get Warning 13565 which means your DC is trying to establish FRS connections. After a while check if there are NETLOGON and SYSVOL shares on DCs by typing net share. It should be now fine,

Remember that you are doing it on your own risk. And if you are not completely sure what you are doing I suggest to do some more reading:



ALL CREDIT GOES TO http://przemekflorek.pl/



June 4, 2018

What do you do if you want to activate the 2 (or more) Hyper-V VMs that come with your respected licensing? You don’t actually need to use the original Server key. Instead, use these keys:

Windows Server 2016 Edition AVMA key
Standard C3RCX-M6NRP-6CXC9-TW2F2-4RHYD
Essentials B4YNW-62DX9-W8V6M-82649-MHBKQ
Windows Server 2012 R2 Edition AVMA key
Datacenter Y4TGP-NPTV9-HTC2H-7MGQ3-DV4TW
Essentials K2XGM-NMBT3-2R6Q8-WF2FK-P36R2

In order for this to work you need to have the Data Exchange integration enabled on the VM via Hyper-V Management.

If you want to enter a Product Key using PowerShell use the following command:

slmgr –ipk

for example: slmgr –ipk TMJ3Y-NTRTM-FJYXT-T22BY-CWG3J