Just users in the primary site are hitting netlogon shares in the secondary, and it’s taking 15-20 mins for their changes to show (sometimes a bit more, TBH)
They’re testing some stuff and I get the impression they’re reporting a lot of issues that are related to the lag in replication more than anything wrong with the things I’m working on. Mention Active Directory to anyone and you get a shrug and a shudder ☺ From: [email protected] [mailto:[email protected]] On Behalf Of Kennedy, Jim Sent: 07 January 2016 14:18 To: [email protected] Subject: RE: [NTSysADM] AD question Makes no difference. Is the real issue here that there are ‘big’ delays in replication? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of James Rankin Sent: Thursday, January 7, 2016 9:17 AM To: [email protected]<mailto:[email protected]> Subject: RE: [NTSysADM] AD question I’m just using the short domain name rather than FQDN – does that make a difference? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Andrew S. Baker Sent: 07 January 2016 14:13 To: ntsysadm <[email protected]<mailto:[email protected]>> Subject: Re: [NTSysADM] AD question If you browse to \\fqdn\someshare<file://fqdn/someshare>, where you end up is determined by DNS resolution. \\contoso.com<http://contoso.com>\NetLogon will be resolved to \\some.contoso.dc.ip\NetLogon<file://some.contoso.dc.ip/NetLogon> and then your system will go there. ASB http://XeeMe.com/AndrewBaker<http://xeeme.com/AndrewBaker> Providing Virtual CIO Services (IT Operations & Information Security) for the SMB market… GPG: 1AF3 EEC3 7C3C E88E B0EF 4319 8F28 A483 A182 EF3A On Thu, Jan 7, 2016 at 7:32 AM, James Rankin <[email protected]<mailto:[email protected]>> wrote: A question for the AD masters out there… If I browse to the \\DOMAIN\netlogon<file://DOMAIN/netlogon> share, how is the DC I browse to in this instance defined? I’m fairly sure it isn’t the server specified in the %LOGONSERVER% variable. Got users who are changing things in the NETLOGON share and they’re finding big delays in seeing these updates because they’re hitting servers in different physical sites. Am I right in thinking it depends in how subnets are configured in Sites and Services? Or way off base? Cheers, James Rankin EUC Director | HTG TaloSys | 07809 668579 | [email protected]<mailto:[email protected]> One Trinity Green, Eldon Street, South Shields, Tyne & Wear, NE33 1SA Tel: 0191 481 3489 Email address: [email protected]<mailto:[email protected]> Website: www.talosys.co.uk<http://www.talosys.co.uk> [phpy9YoGNAM]
