Category: Microsoft

How to change network card priority in Windows Servers

There are occasions where the sys admins need to select the default NIC out of multiple NICs. Specially when it comes to working with NIC teaming & etc.

To solve this, you just have to tell your computer which network card you want it to use first.

Just launch the Run command and enter “ncpa.cpl“.
As you can see, you have all your network cards available in this window.

Next, if you press the “ALT” key, you will show different tabs appear in the top.
Click on the “Advanced” tab and then “Advanced Settings”

A window will appear with the different network cards and the different parameters for IPv4 and IPv6.

There, you just have to select the one you want to use in priority and click on the up arrow and put it at the top of the list.

 

Server 2012 Hang on Startup TiWorker.exe causing boot loop

The TiWorker (This is an automated scheduled task that comes pre-configured in Windows Server 2012 R2) process is related to the following services;

  • Windows Update service
  • TrustedInstaller.exe
  • Windows Modules Installer service

The symptoms for this issue that your Windows 8 or Server 2012 system runs slowly and applications lag. If you press CTRL+ALT+DEL and check the Windows 8 or Server 2012 Processes. Then you will see a process called tiworker.exe using around 80% – 90% of your CPU time. If you try and end this process the tiworker.exe automatically starts itself again.

After 30 minutes or so the issue will go as the tiworker,exe process will end. This process is used by Microsoft’s auto update services when downloading and applying updates to Windows 8 and Server 2012, it runs an applicability scan hence why the process will restart when you kill it as it will run until it has checked if there are updates for applications you are running.

To resolve the issues, 2 workarounds can be applied to the affected system (But there is not a confirmed fix for the issue)

  • Workaround 01 : Applying the hotfix from the Microsoft
  • Workaround 02 : Disabling the related services (Windows Update service / Windows Modules Installer service)