# Slow AD Login for 7.9 Gateway? **URL:** \ **Category:** Ignition\ **Tags:** ignition79\ **Created:** [September 13, 2022, 3:57pm UTC](https://forum.inductiveautomation.com/t/slow-ad-login-for-7-9-gateway/64018 "2022-09-13T15:57:44Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![bkarabinchak.psi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bkarabinchak.psi/32/83567_2.png) [@bkarabinchak.psi](https://forum.inductiveautomation.com/u/bkarabinchak.psi)\ **Post date:** [September 13, 2022, 4:54pm UTC](https://forum.inductiveautomation.com/t/slow-ad-login-for-7-9-gateway/64018/3 "2022-09-13T16:54:03Z")
Ok so OU, the orgizational unit, refers to the Folder, in my case, Production. DC=MyCompanyDomain - presuming that is the top level folder that I blacked out? And DC=com remains that way. Basically the two DC's combined make up `MyCompanyDomain.com` is that the point? Edit: From an answer in another thread and what I am seeing online I think it may need to be OU=Production, OU=Users. Additional Relevant Information: > [@Active Directory LDAP User Search Filter - Filter out memberOf specific group(s)](https://forum.inductiveautomation.com/t/active-directory-ldap-user-search-filter-filter-out-memberof-specific-group-s/29228/3): > > Yes, hopefully this helps you and others. The method that we needed to use was the User List Filter along with the User Listing Base and User Search Filter. It’s helps to get the DistinguishedName of the path to the OU you want to use (Like Sysinternals AD Explorer). I will describe the filters strings below. #Use to narrow down which Organizational Units to search for. The more you use, the faster the audit roles will be. Being too broad can make it slower. To do this you combine your OU’s… --- _[View the full topic](https://forum.inductiveautomation.com/t/slow-ad-login-for-7-9-gateway/64018)._