I had a server that was recently put into a subnet, and I think as a result, since it had some LDAP query jobs, it was bogging down a particular domain controller.
However the job was not configured to specifically connect to the bogged down Domain Controller, so I'm trying to figure out why it was bogging it down.
The DC is in another physical connection that I do not want it being connected to from the physical site that the job server is in.
What's the best way to prevent that?
I created a new subnet in AD sites and services that the job server is in, and associated it to the same physical site.
Would this be the fix?
Also do I need to create an Inter-Site Transport between the site A and site B?
Right now I only have one called "DEFAULTIPSITELINK" in Inter-Site Transports, and it contains every site.
Do I need to create a new site link between site A and site B with a higher cost?