Disabling SMBv1 broke Network Login

As per the Microsoft recommendation, SMBv1 should be disabled on all servers of a domain. We made this change on our all servers. After some days, we found that we are not able to RDP into the servers and we are not able to resolve their DNS hostname as well.

After digging into the problem, I found that "NetLogon" Server was stopped. When I tried to run it, it gave me error that one of its dependency service is stopped or disabled. Later I found that it is because of "Workstation" service because it was also in stopped mode. In event log I found that it is not able to run because SMBv1 is disabled. Below are the screenshots which will show you what I am talking about.

Configure NTP Service in your enterprise domain

Applies to : Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016

I was asked to help a client who recently created new domain controllers and removed the old ones. It included transfer of FSMO roles too. They were few issues which they were facing.

1. All clients were getting different time zones.

2. Event IDs 50 on PDC [The time service detected a time difference of greater than…]

3. Authentication was stopped for some sites.

When I looked events on PDC, then I found that root cause. NTP settings was not defined properly due to which all these issues were there. It happened because they transferred PDC role from old DCT to new DCT. Here are the steps which I followed and it was fixed after that.

SVCHOST.exe is utilizing 100% CPU

Sometimes we notice all of sudden 100% hike in CPU utilization on a server and finds "Svchost.exe" as a culprit. But this executable doesn't give much information what is it running or what is it using. There are few tricks to troubleshoot the problem but before i would like to tell you about "Svchost.exe" in brief.
"Svchost" stands for "Service Host". It is an executable for those services and applications which has only .dll files. Like, W32Time, Dhcp, Dnscache, EventLog, Themes, etc,. It means that it is very important executable to run these critical services.

Microsoft removes 260 character limit for NTFS Path in new Windows 10

The maximum length for a path (file name and its directory route) — also known as MAX_PATH — has been defined by 260 characters. But with the latest Windows 10, Microsoft is giving users the ability to increase the limit.

Restore file from VSS (Previous Version) by powershell

Sometimes it really gets too much frustrating when you restore any folder or files from VSS (Previous Version) and you get an error prompt about Source path too long / large destination path / long file name issue. Error screenshot below.

In this situation, we lost our all hope to get the files restored. But with the help of power shell we can do that and we can restore files without any issue.