[NTSysADM] DHCP failover

2016-05-18 Thread Melvin Backus
Anyone using DHCP failover on 2012r2? I'm seeing some unexpected things. The one that particularly surprised me was that server filters don't appear to be replicated even though all scopes are replicated between the servers. Is that normal? Melvin Backus | Sr. Systems En

[NTSysADM] RE: badPwdCount clarification

2016-05-18 Thread Brian Desmond
Is this correct so far? And if so, at the next attempt the account enters a valid password, again to DC2, the new values will be: PDCe1=0 DC2=0 DC3=0 DC4=0 I’d expect the new values to be PDCe1=2 DC2=0 DC3=1 DC4=1 I can’t think of why the successful login with chain to the PDCe, which is what

[NTSysADM] RE: DHCP failover

2016-05-18 Thread Stephen Gestwicki
DHCP failover is missing a very needed feature of automatic replication. I created a PowerShell script that I ran from a scheduled task to handle it. This is the main line in the script that did the work: Invoke-DhcpServerv4FailoverReplication -ComputerName $PrimaryDHCP -Force - Stephen From: l

[NTSysADM] RE: DHCP failover

2016-05-18 Thread Melvin Backus
So pardon my apparent blindness, but what critical function would that be? It appears that once the configuration is setup it constantly replicates as part of the normal operation. -- There are 10 kinds of people in the world... those who understand binary and those who don't. From:

[NTSysADM] RE: DHCP failover

2016-05-18 Thread Dave Lum
IIRC things like DHCP reservations do not replicate to the failover server without help from powershell scripts like the below From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Melvin Backus Sent: Wednesday, May 18, 2016 9:09 AM To: ntsysadm@lists.myitforu

RE: [NTSysADM] Windows7/10 mapped drive disconnects

2016-05-18 Thread Poppy Lochridge
That we have. To answer some of the other suggestions – there *might* be Offline files involved – I’ll check that out today. They started with a pretty default SBS server setup, and Offline Files is, I think, a default. And if that doesn’t give us any results, we will try a logon script. --Popp

[NTSysADM] RE: DHCP failover

2016-05-18 Thread Ken Cornetet
IMHO, if you need failover, the correct answer is almost always ESX or Hyper-V. In the many years that I've been dealing with computers, trying to do failover at the application level is usually an exercise in frustration. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.c

Re: [NTSysADM] RE: DHCP failover

2016-05-18 Thread Sean Martin
I tend to disagree with this statement. While server virtualization provides great HA and Failover capabilities, I've always found that leveraging an application's built-in HA/Redundancy/Replication capabilities (i.e. SQL, Exchange, etc.) generally provides better performance, easier supportabil

Re: [NTSysADM] RE: DHCP failover

2016-05-18 Thread Andrew S. Baker
I have to agree with Sean. The overhead of server virtualization for something like redundancy of DHCP is overkill in many ways. The HA now available for DHCP service is nice, and only really missing two-way sync. At present, one-way full replication is currently available via GUI or script. Autom

RE: [NTSysADM] RE: DHCP failover

2016-05-18 Thread Dave Lum
I use 2012 R2 DHCP redundancy at two businesses and I like it. One client has a small single /24 network (two sites, DHCP at each so I’m covered for IP if the link breaks). Another business - %dayjob% actually – is far more diverse and getting DCHP helpers on the managed switches took a bit of e