How PowerShell can manage Longhorn Core

It turns out that there actually is a way to manage Longhorn Core with PowerShell.

While I was preparing for my Longhorn Airlift session I kept thinking of the Microsoft’s decision to not allow PowerShell on Longhorn Core, and whether there could be any workaround to that. And it turned out that a workaround exists and is actually pretty straight-forward.

The answer is… using PowerShell remotely! While this answer is not applicable for managing operating system stuff (processes, services, registry, files and so on) AD cmdlets work just fine when installed to any computer in the network – not necessarily a DC.

By default they would pick some DC in the network and run against it with your current credentials, or you can use Connect-QADService to specify a specific DC and/or credentials. And in either case they work just fine even if your DCs are in the “headless” mode.

So to maximize your security in the Longhorn world:

1. Use Server Core installation option.

2. Use PowerShell to manage your AD.

Tags: , , , , , , , ,


0 Responses to “How PowerShell can manage Longhorn Core”

  1. Leave a Comment

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

My Recent Tweets


The posts on this blog are provided “as is” with no warranties and confer no rights. The opinions expressed on this site are mine and mine alone, and do not necessarily represent those of my employer - WSO2 or anyone else for that matter. All trademarks acknowledged.

© 2007-2014 Dmitry Sotnikov

May 2007
« Apr   Jun »

%d bloggers like this: