Remote Manage Workgroup Windows Server 2016 Core

I wrote an article about how to manage Windows Server 2016 TP remotely. Today I had some spare time to re-build my lab environment by the latest release of Windows Server 2016 Core. It’s easy to remotely manage a Windows Server in a domain, but a trick for workgroup Windows Server. Following is an improved procedure.

One Windows Server 2016 Core

  1. Run sconfig command on Windows Server 2016 Core.
  2. Go to Configure Remote ManagementEnable Remote Management to enable remote management.
  3. Then enable responding to ping in same page.
  4. Enable NetBIOS protocol on the firewall by PowerShell.
    Set-NetFirewallRule -Name FPS-NB_Name-In-UDP -Enabled True
    Set-NetFirewallRule -Name FPS-NB_Name-Out-UDP -Enabled True

One client Windows 10

  1. Install Remote Server Administration Tools on the client Windows 10.
  2. Reboot the client.
  3. Open “Server Manager“.
  4. Add the Windows Server 2016 Core machine by IP address.
  5. Go to “All Servers” in “Server Manager“.
  6. Right-click the newly added server – “Managed As…“.
  7. Enter the administrator credential of the target server. Format is “workgroup/Administrator”.  For example, my workgroup is “DC”, so the account is “dc/Administrator”.

 

Mouse Cursor Disappeared in Remote Desktop in mRemoteNG

mRemoteNG is a very nice fork of open source remote tools. It supports multi-protocol. The official website says:

mRemoteNG supports the following protocols:
RDP (Remote Desktop/Terminal Server)
VNC (Virtual Network Computing)
ICA (Citrix Independent Computing Architecture)
SSH (Secure Shell)
Telnet (TELecommunication NETwork)
HTTP/HTTPS (Hypertext Transfer Protocol)
rlogin
Raw Socket Connections

But one thing makes me frustrated is the mouse cursor disappeared randomly when I try select strings in browser or notepad in remote desktop. I use Windows 10, the issue doesn’t occur in Windows native remote desktop. I went through the bug list of mRemoteNG, and figured out it may be related to HiDPI of my screen. 

Looks like no solution at this moment until 1.77 release. The workaround is the following:

  1. Right click desktop – PersonalizeThemes.
  2. Click Mouse cursor.
  3. Change Scheme to Windows Black

“The Update is Not Applicable to Your Computer” When Install KB3046101

  HPE 3PAR upgrading team usually sends a per-requisites before upgrading. One thing in the guide incorrect is the Windows 2012 required patch KB3046101.     You may see error below when you install the path on Windows 2012 server.    
The update is not applicable to your computer
      The reason is the version of mpio.sys and msdsm.sys on your server is higher than 6.3.9600.17809. Usually, because the server installed KB3121261 already. You can ignore KB3046101.

Vlan ‘xxx’ resolved to unsupported VLAN ID in Cisco UCS Manager

You may need only 1 IP address for blade console in Cisco UCS Manager. You can follow Understanding “Management IP” of Cisco UCS Manager to configure it. You may see warning “Vlan ‘xxx’ resolved to unsupported VLAN ID” when you delete existing inbound and outbound IP pools if you are trying to clean up existing management IP pools.

That’s because inbound IP address for blade is not cleaned. You have to go to “Equipment” -> “Chassis” -> Target chassis -> “Servers” -> Target server -> Go to “Inventory” tab -> “CIMC” tab -> Click “Change Inbound Management IP” -> Remove existing VLAN and IP pool.

You will see inband IP tab is blank once it’s saved. Please note, the IP address reassign back after 1 minute if you clicked “Delete Inband Configuration” instead of “Change Inbound Managemnt IP“.

Understanding “Management IP” of Cisco UCS Manager

IP address for KVM in Cisco UCS Manager is different with HPE servers. It may assign multiple IP addresses to same blade if you don’t configure it properly. In my case each blade gets 3 IP addresses!

There are actually 3 types of IP address for KVM. (Cisco manual says 2):

  • Outbound Management IPs.
  • Inbound Management IPs for Blades.
  • Inbound Management IPs for Service Profiles.

Outbound Management IP” is default for KVM. Every new deployed blade will try to get a DHCP IP over management port in same VLAN of Cisco UCS Manager.

The more confused is the 2nd and 3rd IPs.  “Inbound Management IPs for Blades” is from “hardware” perspective. “Inbound Management IPs for Service Profiles” is from “logical” perspective.

If you go to “Equipment” -> Chassis -> blade -> Click the KVM to go console. You get console over either “Outbound Management IP” or “Inbound Management IPs for Blades“.

If you go to “Servers” -> “Service Profiles” -> Click the KVM of a service profile. You get console over either “Outbound Management IP” or “Inbound Management IPs for Service Profiles”.

If you want to configure just 1 IP for a blade whatever it’s for hardware or service profile. You need to do following:

  1. Delete the range of the default “ext-mgmt” in “IP Pools” of “LAN” node in Cisco UCS Manager.
  2. Create a new inbound IP pool and a VLAN group without uplink.
  3. Assign the VLAN and inbound IP pool to templates or service profile.

Refer to Setting the Management IP Address of Cisco UCS Manager manual for detail.

BTW, you may see Vlan ‘xxx’ resolved to unsupported VLAN ID in Cisco UCS Manager when you clean up existing IP pool and create new inbound pool.

Highlight Scripts in Microsoft OneNote 2016

I usually document my scripts in OneNote. It would be perfect if OneNote 2016 can highlight scripts. I found a nice plugin call “NoteHighlight2016” for OneNote 2016. It’s not only for 32 bit but also for 64 bit. You can download it in Github.

The default codes are C#, SQL, CSS, JS, HTML, XML, JAVA, PHP, Perl, Python, Ruby, and CPP. But you can change the settings to show more or less in riboon.xml in the installation folder.

“x/xx on FI-A is connected by a unknown server device” on Cisco UCS

You may see following errors in ‘info’ category of error messages in the Cisco UCS Manager after upgrading infrastructure firmware to 3.2.x.

“x/xx on FI-A is connected by a unknown server device”

This is bug documented in CSCvk76095. You have to reset the port on FI to fix it.

  1. Go to “Equipment” in Cisco UCS Manager.
  2. Go to “Fabric Interconnects” -> Go to the corresponding FI.
  3. Right-click the port x/xx -> Choose “Disable“.
  4. You will see multiple major faults. Wait for 5 seconds.
  5. Right click the port x/xx -> Choose “Enable“.
  6. All warnings disappeared after 5 mins. You may still see the warning in GUI due to cache. Relogin and check.

This change impacts to one link between IOM and the FI port. You need downtime if the IOM only has a single path. I don’t see any impact to ESXi blades in the pod.

Connect to New Provisioned Raspberry Pi Less than $3

The IP configuration of new provisoined Raspberry Pi struggled me a long time. I need to connect to a monitor so I login to system and configure IP address. The problem was I don’t have monitor. I only have a laptop.

Last year, my old laptop dead. I connected the laptop monitor to a HDMI board to my Raspberry Pi. It’s not a low cost solution, it costed me more than $10. And the monitor, cables and board looks uglily.

IMG_1844

Actually there is another solution to leveraging laptop keyboard and monitor. It’s serials port to console. Something similar like when you configure Cisco network switches. Following is how to do it. I achieve that on Raspberry Pi 2.

  1. You need to buy a USB to TTL device with chipset CP2102.
  2. Connect the pins to Raspberry Pi 2. Refer here for GPIO layout.
    TXD > Pi RXD Pin #10 (GPIO 16)
    RXD > Pi TXD Pin #08 (GPIO 15)
    GND > Pi GND Pin #6
  3. Connect the USB to laptop. You will see a device in ‘Device Manager’ needs drivers.
  4. Download driver and install.
  5. Download Putty and install.
  6. Open Putty and “Serial”.
  7. “Serial line” is COM3 or COM4.
  8. “Speed” is 115200.

The USB to TTL I bought on Taobao (Chinese version of Aliexpress). It’s around $1.2 including shipping.

Show CDP Neighbor of Cisco UCS Uplinks

There are two ways to know which network switch ports the network uplinks of Cisco UCS Fabric Interconnects are connected to.

By CLI

  • SSH to the Cisco UCS Manager.
  • Connect to FI-A.
# connect nxos a
  • Show neighbor of network uplinks.
# show cdp neighbor interface ethernet <port num>

By PowerShell

  • Make sure Cisco PowerTool (For UCS Manager) is installed.
  • Enabling the Information Policy via UCSM GUI.
    • Go to “Equipment” -> “Policies” tab -> “Global Policies” tab -> “Info Policy” area.
    • Change to “Enabled“. (No impact to running blades)
  • Open a PowerShell window.
  • Connect to the UCS Manager.
# Connect-Ucs <UCS FQDN>
  • Show CDP neighbor details.
# Get-UcsNetworkLanNeighborEntry

Side notes

Following command can shows network switch name, network switch ports and FI ports

# Get-UcsNetworkLanNeighborEntry | Select deviceid,remoteinterface,localinterface

If you prefer to enable the “Info Policy” by PowerShell, run following command

# Get-UcsTopInfoPolicy | Set-UcsTopInfoPolicy -State enabled -Force