Submitting Nominations: If you know someone who is deserving of this Award, please send an email to email@example.com and please cover the following criteria in your message:
- Active MCT or MCT Alumni
- Is the person actively teaching Microsoft technologies? How often?
- Active in the MCT community
- Demonstrates enthusiasm and a positive attitude with regards to the program and the community
- Demonstrates passion for mentoring new and existing MCTs as well as others in the technical community
- Willingness to volunteer within and outside of the MCT community. Examples could include the following:
- Volunteering at a school for Hour of Code
- Local code camps, user groups
- Regional events
- Large events, like Ignite and Build, Envision and WPC
- Online engagements (blogs, forums, etc.)
About the Award:
The Enrique Lima Award is designed to recognize and celebrate the outstanding work of Microsoft Certified Trainers in the MCT Community, being awarded to only those who show knowledge, passion, and commitment to the Microsoft community as a whole, and specifically to the MCT program. This Award was established in memory of Enrique Lima; a husband, a father of two, a Microsoft Certified Trainer (MCT) and Regional Lead, Microsoft Valued Professional (MVP), Krewe member , SharePoint Community leader, and member of the Learn on Demand Systems (LODS) team. Enrique always went above and beyond what was expected, building up both local, regional and international communities and everyday showed us all what the spirit of the MCT community was all about
I would prefer to have access from my local vlan and wireless vlan to the servers.
But didn’t want to all dns traffic into the VM’s (and depend on a testing environment)
Basically I want host resolution, and being able to utilizing the domain services in the testing environment, without interruption of my other services.
This is the solution in went for was using Conditional Forwarders
First the Hyper-V host:
I Installed the DNS Server role within Windows Server 2016.
Setup forwarders to google dns:
After that i will add the Conditional Forwards for my testing domain
I in my previous post I created 2 Domain controllers, both hosting DNS.
I will then add my Hyper-V hosts IP to the DNS server of my router/dhcp on the needed vlans.
When clients send requests for the testing domain, they will get forwarded to the Hyper-V guests (DCs) and all other requests will go to the Google DNS (126.96.36.199, 188.8.131.52) – more info: Getting started with Google Public DNS
I did want a backup as well, so I installed Synology DNS on my Synology DS1511+
Synology DNS supports forwarding zones, with up to 2 forwarders per zone.
That’s perfect for my setup, added the 2 Hyper-V guest DC’s.
The Synology DNS would of course also need Resolution services enabled, so we can forward requests to the Google DNS (184.108.40.206, 220.127.116.11)
Then I will go ahead an update the DNS servers handed out by my DHCP on my normal client network and wireless clients.
This configuration offers failover/backup, because both the Hyper-V hosts and the Synology will be able to handle DNS requests and forwarding.
Now to the good stuff
Usually when working with Hyper-V I use reference disks, mainly to save space on rather expensive disks. But is there much to gain when using deduplication? I was on sure, so asked in Tech Konnect
The response from Tech Konnect confirmed, when using deduplication, it out wages the other issues with reference disks, rather than saving disk space.
Since it’s not possible to create folders or groups within the Hyper-V Management Console, I will be using a naming standard: <Group> – <Generation> – <OS> – <hostname>
The first Virtual Machine will be a Domain Controller, what better way to start?
Virtual Machine Configuration:
Startup memory: 4096
Dynamic Memory: Enabled
Network Connection: External
Disk size: 60 GB
Boot from the ISO File – Windows Server 2016 Standard (Desktop Experience)
The quick wins for a Generation 2 Virtual Machine
- PXE Boot by using a standard network adapter
- Boot from a SCSI virtual hard disk
- Boot from SCSI virtual DVD
- Secure Boot (enabled by default
- UEFI firmware support
- Shielded Virtual Machines
- Storage spaces direct
- Hot add/removal of virtual network adapters
Note: IDE drives and legacy network adapter support has been removed.
For more info: Generation 2 Virtual Machine Overview and Hyper-V feature compatibility by Generation and Guest
The memory assigned might be a bit overkill, but for now it will be OK.
When configuring the second DC i will only assign: 2048.
The complete installation time to logon was 3 minutes and 9 seconds
Both DCs can actually live with 2048 mb ram, so it can always be cut down, but keep in mind we are using Dynamic Memory allocation.
I will of course be setting up MDT and ConfigMgr at a later point, to streamline and gain a bit of speed.
The host was installed with Windows Server 2016.
This means Hyper-V is a feature that we just need to enable – yay!
- Open a elevated PowerShell prompt
- Run the command: Install-WindowsFeature -Name Hyper-v -IncludeManagementTools -Restart
The command will automatically reboot once installed
NOTE: In some cases you will have to enable Intel-VT in BIOS.
You can read more about the system requirements here: Systems Requirements for Hyper-V on Windows Server 2016
For the actual setup of guests machines, I will be running mostly Windows Server 2016, Windows 10 and maybe a Linux guest or two.
Don’t forget to review: Supported Windows guest operating systems
Now to the Hyper-V Switch configuration:
I am going to add an external switch, as my client is already connected to the network on the correct vlan.
Keep in mind I got a seperat USB NIC with 2 Ports (USB 3.0 to Dual Port Gigabit Ethernet Adapter NIC w/ USB Port)
This means i will be able to have my on-board primary NIC only for management and use one of the other free ports only for VMs.
- Open Hyper-V Manger
- Mark your server
- Click Virtual Switch Manager in the actions pane
- Mark External
- Click Create Virtual Switch
- Name your switch – Example: External – 254 (254 indicating the vlan)
- Remove the checkbox in Allow management operating system to share this network adapter
- Mark: Enable single-root I/O virtualization (SR-IOV)
Not familiar with SR-IOV? Read this blog post by John Howard: Everything you wanted to know about SR-IOV
- Click Ok
You might get a warning that pending network configuration will prevent remote access to this computer – If your connected to the server using another NIC, you will not be disconnected.
This concludes the basic configuration of the Hyper-V host.
We installed Hyper-V and configured a switch with external access.
The next post will be more detailed with the actual Hyper-V guest installations
During vlan configuration for my new lab (see previous post Home Data Center)
I had to change some vlans, for some reason my Hybrid Cloud Device Management controller got “lost in translation”
It all starts with the adoption of devices onto the cloud key – no problems there.
But when your Cloud Key is lost in a vlan with no connectivity or access to other devices, then its back to basics.
My problem was that I deleted the valid networks/vlans added on ports – BIG mistake!
So nothing really works and you can’t change anything, but tuning a bit on the vlans on the router seemed to open up a bit.
From there we can SSH to localhost on port 2222
Click anykey to get the Warning!: The changes may break controller settings and only be effective until reboot.
It will not give a response and will be awaiting a key stroke before your ready to go
Keep in mind all configurations will be lost, once connected back and provisioned by the cloud key.
To enter user privilege mode type: Enable
To enter Global Config mode type: Configure
And now we can configure the entire switch (also without the controller and more advanced settings.
In this case,
Selecting an interface (port 2): interface 0/2
adding a vlan to the interface (port 2): interface vlan participation include 22
and your lost Cloud Key should now be back on the correct vlan.
If you just need to bring back to management network on the switch, you can use: network mgmt_vlan 1
Note: 1 being the vlan you want to participate in.
If you need multiple vlan on 1 port – maybe with a UniFi AP AC Pro, you will see that the AP doesn’t have a configuration for management vlan, so we need to configure the native LAN for the device. It only requires 3 steps, it can be a bit confusing configuring and adding a bit more complexity.
– Defined Netowrk/VLANs in Controller Settings
– Manage or Create Network Profiles for the switch in the Switch Configuration
– Assign Networks/VLANS or Profiles to the Port(s)
There is a nice explanation here: A-non-expert-Guide-to-VLAN-and-Trunks-in-Unifi-Switches
The next step for the lab or so-called home data center: Installing and Configuring Deduplication
I was going to use a USB stick for the Windows Server 2016 OS.
The main reason for this: DEDUPLICATION.
I did start out with a USB stick, but due to performance issues this was changed – read the follow-up post (https://blog.thomasmarcussen.com/follow-up-on-the-home-datacenter-hardware/)
The reason for having the OS on a separate volume: Deduplication is not supported on system or boot volumes. Read more about Deduplication here: About Data Deduplication
Let’s get started
Installing and Configuring Deduplication
- Open an elevated PowerShell prompt
- Execute: Import-Module ServerManager
- Execute: Add-WindowsFeature -Name FS-Data-Deduplication
- Execute: Import-Module Deduplication
Now we installed data Deduplication and it’s ready for configuration.
My Raid 0 volume is D:
The volume will primarily hold Virtual Machines (Hyper-V)
I’m going to execute the following command: Enable-DedupVolume D: -UsageType HyperV
You can read more about the different usage types here: Understanding Data Deduplication
Some quick info for the usage type Hyper-V:
You can get the deduplication status with the command: Get-DedupStatus
The currently saved space on my volume is 46.17 GB
That is for a 2 ISO files and a reference machine for Windows Server 2016 and the reference disks copied to separate folder.
More usefull powershell cmdlets here: Deduplication Cmdlets in Windows PowerShell
I do love deduplication especially for virtual machines, hence most of the basic data is the same.
The disks are also rather expensive so getting the most out of them is preferred.
It’s time for a small update – the previous post is available here: https://blog.thomasmarcussen.com/new-lab-home-datacenter/
The datacenter has been running for about a week now – quite good…. but…..
I’ve been using the Samsung USB as OS drive – Samsung USB 3.0 Flash Drive FIT 32GB
It does have fast read, and a not that slow write, according to Samsung: Up to 130 MB/s
The week passed with setting up and installing VMs – using the actual VMs etc.
But when installing Windows Updates on the Hyper-V host, installing Features/Roles or anykind of configuration, it seems to slow down to useless/freeze.
Running a full Windows Update took about 2 days to reach fully patched level.
During that time it was useless as in no respondig.
I ran a WinSat drive test on the Samsung USB Flash Drive:
Random 16.0 Read: 8.87 MB/s
Random 16.0 Write: 5.45 MB/S
Random reads and writes seems pretty low.
The sequential seems a bit better:
Sequential 64.0 Read: 76.89 MB/s
Sequential 64.0 Write: 86.95 MB/s
The Commands used with winsat:
Winsat disk -drive C: -ran -write (Random 16.0 Write)
Winsat disk -drive C: -ran -read (Random 16.0 Read)
Winsat disk -drive C: -seq -write (Sequential 64.0 Read)
Winsat disk -drive C: -seq -read (Sequential 64.0 Write)
So I decided to replace to Samsung USB 3.0 Flash Drive FIT as a OS Drive.
The new hardware choosen ended up being:
NOTE: the StarTech.com enclosure does not support NVMe, so did choose a m.2 SSD.
I know that StarTech also have USB 3.1, but i really do want to keep the USB 3.1 port free for an additional RAID enclosure when/if needed. Properly a StarTech enscloure but not sure yet.. (USB 3.1 (10Gbps) External Enclosure for Dual 2.5″ SATA Drives) still looking for a nice USB 3.1 enclosure that supports m.2 NVMe…
Samsung states the specs for the new disk as:
- Up to 500MB/s Sequential Write
- Up to 540/s Sequential Read
The actual performance test on the Samsung 850 EVO M.2 2280 SSD:
Random 16.0 Read: 276.51 MB/s
Random 16.0 Write: 271.37 MB/S
Sequential 64.0 Read: 388.85 MB/s
Sequential 64.0 Write: 383.71 MB/s
So in any case it’s quite a performance boost for the OS disk.
Finally i managed to setup the new lab and home-datacenter.
Due to several home limitations (cost of power, space and noise)
The decision was clear:
The NUC can run RAID 0 and 1 on the internal NVMe drives, i’m going for RAID 0 (Stripe)
This is where it gets a bit interesting.. Mostly i’m going to run VM’s within Hyper-V.
Hyper-V and deduplication that is… of course.
I needed to move the OS to another disk, for maximum storage.
Keep in mind, deduplication will not run on OS/System disk.
This is where the USB Flash Drives comes in handy, Windows Server 2016 can run directly on that, leaving me with 2 full NVMe drives in RAID 0 and deduplication – YAY!
that’s the hardware part 🙂
The follow up post is here: https://wp.me/p8YLCL-aL
The author of the original Petya ransomware going by the name of Janus Cybercrime Solutions, has released the master decryption key of all past Petya versions.
This key can decrypt all ransomware families part of the Petya family except NotPetya, which isn’t the work of Janus.
Janus released the master key on Wednesday in a tweet that linked to an encrypted and password-protected file uploaded on Mega.nz.
Malwarebytes security researcher Hasherezade cracked the file yesterday and shared its content:
Here is our secp192k1 privkey:
We used ECIES (with AES-256-ECB) Scheme to encrypt the decryption password into the “Personal Code” which is BASE58 encoded.
The key is tested and confirmed by Kaspersky Lab.