Wrestling with Microsoft's Nano Server preview

The current technical glimpse is promising, but so painful


How to install apps? It's a problem

Another issue is how to install anything. Microsoft has trimmed away the Windows Installer service, so Msiexec (the command line for installing a .MSI package) will not work, and most setups will not run.

Microsoft stated at Build that it is working on an installer for Nano Server, which can handle files, permission, services, COM registrations and custom actions; it sounds good, though how many vendors will want to create both MSI and Nano Server installers for their software?

Features available in Nano Server

Running DISM gives an idea of what features are available in Nano Server

The DISM tool works for the few built-in features. This leaves a few options for deploying applications:

  • Copy files across and perform any necessary registrations manually. Note that you need to open the file sharing ports using ‘netsh advfirewall firewall set rule group="File and Printer Sharing" new enable=Yes’ before you can access the file system across the network.
  • Use an automation platform such as Chef and/or PowerShell DSC (Desired State Configuration). Microsoft showed Chef running at Ignite, though it is not clear how you install Chef itself on the preview.

Nano Server should be ideal for running ASP.NET 5.0 applications on .NET Core, and I tried to get this working. I built a basic ASP.NET Preview web application with Visual Studio 2015 and published it to a directory, making sure to deploy the 64-bit and .NET Core version of DNX (.NET Execution Environment).

Then I tried to start the application using the generated script. This should work, since ASP.NET 5.0 is designed to be deployed like this, with all the necessary .NET Libraries contained in the application directory. In my case though I got a NativeCommandError.

A quick call to support; and it turns out that this is a known bug. You need Beta 5 of DNX, whereas Visual Studio 2015 RC comes with Beta 4. I installed DNX Beta 5, but could not persuade Visual Studio 2015 to let go of its attachment to Beta 4, so running an actual ASP.NET app on Nano Server remains a work in progress.

Similar topics


Other stories you might like

  • Everything you wanted to know about modern network congestion control but were perhaps too afraid to ask

    In which a little unfairness can be quite beneficial

    Systems Approach It’s hard not to be amazed by the amount of active research on congestion control over the past 30-plus years. From theory to practice, and with more than its fair share of flame wars, the question of how to manage congestion in the network is a technical challenge that resists an optimal solution while offering countless options for incremental improvement.

    This seems like a good time to take stock of where we are, and ask ourselves what might happen next.

    Congestion control is fundamentally an issue of resource allocation — trying to meet the competing demands that applications have for resources (in a network, these are primarily link bandwidth and router buffers), which ultimately reduces to deciding when to say no and to whom. The best framing of the problem I know traces back to a paper [PDF] by Frank Kelly in 1997, when he characterized congestion control as “a distributed algorithm to share network resources among competing sources, where the goal is to choose source rate so as to maximize aggregate source utility subject to capacity constraints.”

    Continue reading
  • How business makes streaming faster and cheaper with CDN and HESP support

    Ensure a high video streaming transmission rate

    Paid Post Here is everything about how the HESP integration helps CDN and the streaming platform by G-Core Labs ensure a high video streaming transmission rate for e-sports and gaming, efficient scalability for e-learning and telemedicine and high quality and minimum latencies for online streams, media and TV broadcasters.

    HESP (High Efficiency Stream Protocol) is a brand new adaptive video streaming protocol. It allows delivery of content with latencies of up to 2 seconds without compromising video quality and broadcasting stability. Unlike comparable solutions, this protocol requires less bandwidth for streaming, which allows businesses to save a lot of money on delivery of content to a large audience.

    Since HESP is based on HTTP, it is suitable for video transmission over CDNs. G-Core Labs was among the world’s first companies to have embedded this protocol in its CDN. With 120 points of presence across 5 continents and over 6,000 peer-to-peer partners, this allows a service provider to deliver videos to millions of viewers, to any devices, anywhere in the world without compromising even 8K video quality. And all this comes at a minimum streaming cost.

    Continue reading
  • Cisco deprecates Microsoft management integrations for UCS servers

    Working on Azure integration – but not there yet

    Cisco has deprecated support for some third-party management integrations for its UCS servers, and emerged unable to play nice with Microsoft's most recent offerings.

    Late last week the server contender slipped out an end-of-life notice [PDF] for integrations with Microsoft System Center's Configuration Manager, Operations Manager, and Virtual Machine Manager. Support for plugins to VMware vCenter Orchestrator and vRealize Orchestrator have also been taken out behind an empty rack with a shotgun.

    The Register inquired about the deprecations, and has good news and bad news.

    Continue reading

Biting the hand that feeds IT © 1998–2021