Sunday, January 5, 2020

Run the following set of steps one by one to install and configure Docker on Windows 10:

Run the following set of steps one by one to install and configure Docker on Windows 10:
       Invoke-WebRequest "https://master.dockerproject.org/windows/
       amd64/docker-1.13.0-dev.zip" -OutFile "$env:TEMP\docker-1.13.0
       -dev.zip"
       -UseBasicParsing       Expand-Archive -Path "$env:TEMP\docker-1.13.0-dev.zip"
       -DestinationPath $env:ProgramFiles       $env:path += ";c:\program files\docker"       [Environment]::SetEnvironmentVariable("Path", $env:Path + ";
       C:\Program Files\Docker", [EnvironmentVariableTarget]::Machine)       dockerd --register-service
  1. Start the Docker Service by running the following command:
       Start-Service docker
  1. In order to develop Windows Server Containers, we need any Windows base OS image, such as windowsservercore or nanoserver. Since Windows 10 supports Nano Servers only, run the following command to download the nanoservercore base OS image (we have a dedicated chapter for learning development using Nano Server images). The following command might take some time depending on your bandwidth; it downloads and extracts the nanoserver base OS image, which is 970 MB in size, approximately:
       docker pull microsoft/nanoserver
At the time of writing, Windows 10 can only run Nano Server images. Even though the windowsservercore image gets downloaded successfully, running containers using this image will fail due to incompatibility with the OS.
  1. Ensure that the images are successfully downloaded by running the following command:
       docker images
The preceding command gives the following output:
Now you are ready to start container development on Windows 10, you can directly skip to the Windows Server Containers development section to start creating Windows Containers.

Tuesday, December 24, 2019

Software-Defined Network


The key characteristics of SDN Architecture are given in the following.

9.8.1.1 Programmable

Since the network services are separated from the forwarding layer and are deployed as software applications, they are programmable and it is easy to add and update features.

9.8.1.2 Agile

The administrator has more flexibility to manage network traffic flow to meet customer demands.

9.8.1.3 Central Management

The network intelligence is centralized and software‐based. This allows it to maintain a global view of the network, appearing to applications and policy engines as a single, logical switch.

9.8.1.4 Configurable

Network management programs are not dependent on the proprietary hardware, so network managers can write programs to manage, configure and operate network resources.
Open standard-based and vendor-neutral: SDN simplifies network design and operation because instructions are provided by SDN controllers instead of multiple, vendor‐specific devices and protocols.




Transfer and seize operations master roles

You may be familiar with seizing FSMO roles from previous versions of Windows Server. In previous versions, you would use the  ntdsutil.exe command-line utility, but in Windows Server 2016 it needs to be done in
PowerShell.

Understand offline maintenance using ntdsutil. The ntdsutil command-line tool is a primary method by which system administrators perform offline maintenance. Understand how to launch this tool by entering ntdsutil at a command prompt.






Cloning a source Domain Controller - Windows 2012 R2


Considerations for Virtualization - Time Synchronization


Downloading your social media archive