Computers slow to a crawl after domain join
-
@espynn said in Computers slow to a crawl after domain join:
But we have had some large scale network changes recently.
What sort of changes? This may help me help you.
-
@wayne-workman mostly related to WAN changes to ensure reliability between our data centers. Nothing on the vlan in question.
-
@espynn k. So on Monday then, I’d like you to focus on network. Do pings to the DCs continously (ex.
ping 10.x.x.x -t). Ping your gateway continously too. Look for slow responses and dropped packets. Also troubleshoot DNS, make sure your domain’s DCs are in fact what’s set for dns. Also dig through group policy - see if any printers, map drives, roaming profiles, folder direction, or software is getting deployed via group policy.Also, simply things like ensuring your subnet mask is correct, and looking for duplicate IPs for your DCs.
Just gotta troubleshoot this thing to death till you find the root problem.
-
Are these the first Windows 10 computers that you’ve had? Maybe some GPO is present that just doesn’t like 10.
-
@avaryan not the case
-
@espynn said in Computers slow to a crawl after domain join:
Our GPO is a bit of a black hole and no one really knows what’s going on down there to be honest
Some GPO that doesn’t work with Win10 could very-well be the case. You can’t make statements like “Our GPO is a black hole” and also claim that GPO isn’t the problem. You need to look through all your group policies - this might be the problem.
-
@wayne-workman said in Computers slow to a crawl after domain join:
@espynn said in Computers slow to a crawl after domain join:
Our GPO is a bit of a black hole and no one really knows what’s going on down there to be honest
Some GPO that doesn’t work with Win10 could very-well be the case. You can’t make statements like “Our GPO is a black hole” and also claim that GPO isn’t the problem. You need to look through all your group policies - this might be the problem.
Windows 10 fresh install without imaging and set up exactly the same on the domain have no issues is why I make that claim. I just struggle to see what imaging would do that a GPO could even detect…
-
@espynn In such case, I’d recommend creating a fresh & clean image to try out next.
