How to deploy DHCP Failover On Windows 2016

Step by step introduction with screenshots how to deploy DHCP Failover On Windows 2016.


Sources:

Comments

Post a Comment

Popular posts from this blog

SQL Server Setup: Windows Firewall warning (Ports)

Image
What was it again SQL server setup throws out, when you have your Windows Firewall on?! Rule "Windows Firewall" generated a warning. The Windows Firewall is enabled. Make sure the appropriate ports are open to enable remote access. See the rules documentation at http://go.microsoft.com/fwlink/?LinkId=94001 for information about ports to open for each feature. Keywords: Setup, Firewall, Ports, SQL Server, Microsoft
Read more

Camtasia 7 and Full HD (1920x1080 / 1080p resolution)

As the post implies that is not something that works out of the box. But the following steps proved to work to create a video recorded on full HD. Out of the box Camtasia 7.1.1 was always producing videos with missing lower right hand-side; Like it was not taking the whole screen, but only 1/2-2/3 of the top-left-most area. Once I figured out a way to force the full HD resolution it would give me an out of memory exception: Camtasia Studio Error: E_OUT_OF_MEMORY has been returned when trying to write the file. This may be caused by the videos with large dimensions on the timeline. Please verify that all videos on ... When selecting screen or manually highlighting the screen area the recording would correctly put the green boxes around the full screen space. Yet, the recording dimension were something around 1500x800, not 1920x1080. So, this needs to be manually edited. After the recording finished, for whatever reason, the resulting capture-1.camrec would have a zomm ...
Read more

Read-only Domain Controllers

By default a domain controller is a read/write domain controller. So, it can be used to authenticate against it, but also to e.g. set a new password. That password will then be replicated out to other domain controllers on your network. Why would you need a read-only domain controller now? In short: for security reasons (not performance, availability, ...). The assumption is that remote offices will be less secured than the company headquarters for many reasons (e.g. reducing IT costs on security). As such it is handy to have a local domain controller that clients can use to authenticate on-site. Yet, those should not be allowed to replicate data back to the central system, as they are assumed to be more vulnerable to attacks and breaches than the (hopefully) fortified HQ. Sources: Introduction to Active Directory Infrastructure in Windows Server 2012 @ ~20:00
Read more