SSH File Transfer Protocol or SFTP has been around for over 20 years, and still remains a great way to transfer files securely, specifically allowing the use of SSH keys to ensure that only the right users can perform the necessary operations.
One of the cool features introduced in Windows Server 2012 was Storage Spaces, which is the ability to create Storage Pools that span multiple physical disks; it is sort of like software RAID on steroids. Storage Spaces was further enhanced in 2012 R2, and some additional polish has been added in 2016.
Been a hectic past year, but I’ll hopefully be updating this blog a bit more frequently now.
After all the fun of dealing with NETBIOS in a previous Field Notes post, you would have thought I would have learnt my lesson: always check NETBIOS name resolution when working with System Center products! Alas, I encountered another head-scratcher, and (spoiler alert!) NETBIOS was once again the culprit.
Traditionally, IT departments have been seen as either “the people who fix the magic box I use for work” or “the people who break the magic box I use for work”. They are black holes for budgets, always under-staffed and overworked, blamed when something changes, but never praised when it all carries on serenely. IT departments are not all cloud providers, and so resource is almost always constrained in some respects, but the rest of the business is rarely aware of this fact.
Microsoft has made a big push for Server Core as the default installation option for servers in recent times in order to reduce the number of required patches, reduce the installation footprint, and make the OS more secure by removing unnecessary features. As a result of this, knowing how to do things in PowerShell is becoming absolutely essential and, with the introduction of Nano Server in Windows Server 2016 (which has no GUI at all!), the command line will once again be king.
If you are using HNV for your VMs, you may run into the following error when connecting a VM to a VM network: