Search This Blog

Friday, October 26, 2018

Live Demo Webinar: Windows Server 2019 in Action

So you’ve heard all about Windows Server 2019 - now you can see it in action in a live demo
webinar on November 8th!

The last WS2019 webinar by Altaro was hugely popular with over 4,500 IT pros registering for
the event. Feedback gathered from that webinar and the most popular features will now be
discussed and tested live by Microsoft MVP Andy Syrewicze. And you’re invited!

This deep-dive webinar will focus on:
• Windows Admin Center
• Containers on Windows Server
• Storage Migration Service
• Windows Subsystem for Linux
• And more!

Demo webinars are a really great way to see a product in action before you decide to take the
plunge yourself. It enables you to see the strengths and weaknesses first-hand and also ask
questions that might relate specifically to your own environment.

With the demand so high, the webinar is presented live twice on November 8th to help as
many people benefit as possible. The first session is at 2pm CET/8am EST/5am PST and the
second is at 7pm CET/1pm EST/10am PST.

With the record number of attendees for the last webinar, some people were unable to attend
the sessions which were maxed out. It is advised you save your seat early for this webinar to
keep informed and ensure you don’t miss the live event.

Save your seat:

Saturday, October 20, 2018

Create Self Signed Certicate to Use For Minio

By default minio is using http. To configure minio to use TLS, you need to create a self signed certificate. Original post is taken from here:-

But it take me a while to figure out. Therefore, i come out a guide with screenshot.

In our lab scenario, we are using Windows based system.

Let start the configuration
1. Use GnuTLS. Download GNUTLS for Windows from here.
2. Set the system variable to include the path.[Under environment variable] Example my GNUTLS has extracted to C:\Backup\gnutls-MinGW64.DLLs-gnutls_3_6_4\win64-build\bin

3.Use command line to execute:-
certtool.exe --generate-privkey --outfile private.key
Generating a 3072 bit RSA private key...

private.key is generated.

4. Create a cert.cnf file and put this entry:

# X.509 Certificate options
# DN options

# The organization of the subject.
organization = "Example Inc."

# The organizational unit of the subject.
#unit = "sleeping dept."

# The state of the certificate owner.
state = "Example"

# The country of the subject. Two letter code.
country = "MY"

# The common name of the certificate owner.
cn = "Lai"

# In how many days, counting from today, this certificate will expire.
expiration_days = 365

# X.509 v3 extensions

# DNS name(s) of the server
dns_name = "localhost"

# (Optional) Server IP address
ip_address = ""

# Whether this certificate will be used for a TLS server

# Whether this certificate will be used to encrypt data (needed
# in TLS RSA cipher suites). Note that it is preferred to use different
# keys for encryption and signing.
5. Run

certtool.exe --generate-self-signed --load-privkey private.key --template cert.cnf --outfile public.crt
It will create public.crt
Generating a self signed certificate...
X.509 Certificate Information:
        Version: 3
        Serial Number (hex): 59d89416fe9279c1e7967dd8c1ed165cc7a42587
                Not Before: Sat Oct 20 11:15:46 UTC 2018
                Not After: Sun Oct 20 11:15:46 UTC 2019
        Subject: C=MY,ST=Example,O=Example Inc.,CN=Lai
        Subject Public Key Algorithm: RSA
        Algorithm Security Level: High (3072 bits)
                Modulus (bits 3072):
                Exponent (bits 24):
                Basic Constraints (critical):
                        Certificate Authority (CA): FALSE
                Subject Alternative Name (not critical):
                        DNSname: localhost
                Key Purpose (not critical):
                        TLS WWW Server.
                Key Usage (critical):
                        Key encipherment.
                Subject Key Identifier (not critical):
Other Information:
        Public Key ID:
        Public Key PIN:

Signing certificate...

6. Copy private.key and public.crt and put into C:\Users\UserProfileName\.minio\certs

7. Final verification, execute "minio sever C:\Backup\Minio [depend on your folder]

use Minio Client to verify:

Hope this help!

Install NFS Server Roles on Windows Server 2016

In this post, we are going to install NFS Server roles on Windows Server 2016. NFS share is different from SMB share.

  • SMB is the standard for Windows
  • NFS is perfect for UNIX

Both are good for file sharing purpose.

It is a simple step. Just go to Server Manager | Add Roles & Features

NFS Server roles are located under "File and Storage Services"

If you fail to install the role, do refer to this post.

Once role installed, proceed to create an NFS share.

1. Create a new directory called "NFSRepo". Right click | Properties. Select Manage NFS Sharing

Tick share this folder. Leave the setting default. Click on permission to set security right

Add a new permission. Enter
  • Unix Server IP
  • Read-Write permission
  • Allow root access

Below is how it look like:-

The NFS share path will be "Servername:/NFSShare format

We're all done on the NFS Server side configuration.

Unable to Install NFS Server Roles on Windows Server 2016

When you try to install NFS Server Roles on Windows Server 2016 by using server manager, you were not able to. The system keeps requesting you to restart the server. [Pending restart]

But restart the server still does not allow you to install NFS Server roles.

Next step:-
This may be due to other application is using same port 111. Example:- Veeam vPower NFS Service

[ Resolution ]
1. Temporary disable the Veeam vPower NFS Service services
2. Install NFS Server Roles using Server Manager
3. Restart Veeam vPower NFS Service

That should do the trick!