Computers slow to a crawl after domain join
-
@george1421
Yes, removing from the domain and the issues go awayYes, without ever connecting to domain, issues do not happen (computers fresh installed from ISO of windows, and added to domain also do not experience issues)
Disconnecting from the network seems to have no effect
I’m failing too, that’s why I’m here!
This issue is replicated across different windows install versions, different unattend.xml’s, different computer models and makes, different images and even different computers the images were taken from. I’m scratching my head here, the ONLY connection between computers that have the issue is that they were imaged from fog. We are going to be testing SCCM in the coming months, so I might be able to test if a different imaging solution entirely, resolves the issue.
…There isn’t a GPO template for “make imaged computers run slowly” is there? [/s]
-
@espynn said in Computers slow to a crawl after domain join:
There isn’t a GPO template for “make imaged computers run slowly"
This is my thought too. Instead of turbo mode, you found snail mode.
If you have the capabilities, move that computer to an OU where you are blocking all GPO policies. So the computer will be connected to AD, but no gpo policies will be applied.
It could be something silly like if you had AV installed in the golden image and when connected to AD its trying to do something and timing out causing the delay. AV is typically installed post imaging because (depending on the AV solution) a guid is created which needs to be system unique.
It would be also interesting to know if the slowness is observed when disconnected from the network.
SCCM is a good solution if you can support the infrastructure requirements. It is more than just imaging so not really in the same class as fog.
-
@george1421 No AV and network disconnect does not seem to matter. I will try another OU with GPO blocked though. Our GPO is a bit of a black hole and no one really knows what’s going on down there to be honest
Thanks for your help, if anyone stumbles into this thread, the issue is not resolved but I will report back with findings .
-
@espynn said in Computers slow to a crawl after domain join:
The windows 10 settings app will take 2-5 minutes to load, pressing the start button and starting to type for a search is also delayed. Even things as simple as right clicking the desktop and going to display settings is delayed by several minutes.
These statements would cause me to check out task manager to see what program is Taking the resources. That will lead you to the answer after a couple Google searches.
-
@wayne-workman I agree, first thing I did. No tasks were using more than normal baseline amounts of resources.
-
@espynn did you Check the network tab in task manager?
-
@wayne-workman yes. As I said below, network connected or not didn’t matter, and normal baseline resources.
-
@espynn are these desktops or laptops? any map drives getting mounted automatically? Any printers installed automatically?
-
@wayne-workman either or, no and no.
-
@espynn any software being installed automatically?
-
@wayne-workman nope, just (seemingly) normal default GPO policy. Not even moved from default computers OU.
-
@espynn is roaming profiles turned on for users? Is folder redirection being used?
-
@wayne-workman neither, and again, normal resource activity, including network activity.
-
@espynn what’s dns primary and secondary set to? Do these match the domain controller addresses?
Get the domain controller addresses by using nslookup. Example, my domain is fogproject.org, I’d do
nslookup fogproject.organd all DC addresses will be returned. -
@wayne-workman I’ll check after the weekend, I would suspect we would have wider issues across the entire domain if this were mixed up. But we have had some large scale network changes recently.
Anything else to check?
-
@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
