bitLife – KandZ

First, enter a PowerShell remote session:

Enter-PSSession -ComputerName nanoserv -Credential kandz\administrator

Then install Windows updates:

$update = New-CimInstance -Namespace root/Microsoft/Windows/WindowsUpdate -ClassName MSFT_WUOperationsSession

Invoke-CimMethod -InputObject $update -MethodName ApplyApplicableUpdates

Restart the server with restart-computer. Exit the session with exit and then connect again with Enter-PSSession.

Install Docker as described here. If PowerShell does not have invoke-webrequest install docker as described here

Then you have to create a firewall rule, so the nano server allows docker traffic.

new-netfirewallrule -displayname "Docker" -direction Inbound -Action Allow -Protocol TCP -LocalPort 2375

More information about new-netfirewallrule here

Create a new configuration file for the dockerd daemon:

new-item -type file c:\programdata\docker\config\daemon.json

Add the required configuration info to the file you created above

add-content 'c:\programdata\docker\config\daemon.json' '{
"hosts":["tcp://0.0.0.0:2375", "npipe://"] }'

Then restart the service

restart-service docker

Install the Docker.exe. You need this file to manage the dockerd remotely.  So on the server, you want to manage the dockerd engine you have installed at the nano server, you need to:

• Download the Docker.exe

invoke-webrequest
"https://download.docker.com/components/engine/windows-
server/cs-1.12/docker.zip" -outfile "$env:temp\docker.zip"

• Extract the zip file to program files directory

expand-archive -path "$env:temp\docker.zip" -destinationpath
$env:programfiles

• Add to Path the docker location

You can run docker from another server than the nanoserver that the docker engine is.

docker.exe -H tcp://192.168.122.74:2375

 

Windows Server 2016 – Install Docker on nano server http://bitlife.kandz.me/windows-server-2016-install-docker-on-nano-server/

On my nano server, PowerShell does not have invoke-webrequest. So I have to download the zip file to another server copy it and then install it. Follow this post to create nano server with containers installed

So, first download Docker to another server:

invoke-webrequest https://download.docker.com/win/static/stable/x86_64/docker-17.09.0-ce.zip -Outfile "c:\cocker.zip "

Then copy the zip file to the server (change computername and credential):

$s=New-PSSession -ComputerName nanoserv -Credential kandz\administrator
copy-item .\docker.zip -Destination c:\docker.zip -tosession $s

Remote access the nano server:

Enter-PSSession -computername nanoserv -credential kandz\administrator

Extract the archive to Program Files

Expand-Archive .\docker.zip -DestinationPath $Env:Programfiles -Force

Add Docker to the path

$env:path += "$env:ProgramFiles\docker;” 
setx PATH $env:path /M

Register the Docker Daemon as a service and start the service

dockerd --register-service Start-Service docker

 

Windows Server 2016 – Install Docker in Nano Server when invoke-webrequest problem http://bitlife.kandz.me/windows-server-2016-install-docker-in-nano-server-when-invoke-webrequest-problem/

If you faced a problem when you try to reach a server from the DC and you received an error message “The WinRM client cannot process the request because the server name cannot be resolved” then there is a DNS problem.

First, you need to check your DNS and see if it exists a zone record for the server. If not then follow this tutorial -> Windows Server 2016 – Problem with DNS registration

If you still have this problem, then on the DC server you need to add edit the DNS address. Before that use the get-dnsclient to get the interface index. Then :

set-dnsclientserverAddress -interfaceindex 15 -ServerAddress "127.0.0.1"

Do not forget to change the -interfaceindex

Good luck!

 

http://bitlife.kandz.me/windows-server-2016-winrm-problem-server-name-cannot-be-resolved

Windows Server 2016 – WinRM problem server name cannot be resolved http://bitlife.kandz.me/windows-server-2016-winrm-problem-server-name-cannot-be-resolved/

When I added the nano server to the domain, it didn’t add a new record to the main zone in the DNS. What I did to fix that.

First I created a new PowerShell session:

enter-pssession -computerName 192.168.122.74 -credential 192.168.122.74\administrator

then I run get-dnsclient to get the interface index for the NIC I wanted to configure

Then I configured the DNS Servers for the nano server and registered the DNS client.

set-dnsClientServerAddress -interfaceIndex 2 -Server Address "192.168.122.21"
ipconfig /all #check if the dns server updated

register-dnsclient -verbose

Then I checked the DNS server if the nano server registered and it did!!! 🙂

 

 

http://bitlife.kandz.me/windows-server-2016-problem-with-dns-registration

Windows Server 2016 – Problem with dns registration http://bitlife.kandz.me/windows-server-2016-problem-with-dns-registration/