<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>ServerCore - Tag - pr0mpt</title>
        <link>https://pr0mpt.com/tags/servercore/</link>
        <description>ServerCore - Tag - pr0mpt</description>
        <generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Tue, 25 Aug 2015 11:26:02 &#43;0200</lastBuildDate><atom:link href="https://pr0mpt.com/tags/servercore/" rel="self" type="application/rss+xml" /><item>
    <title>Lab: Configure PowerShell WebAccess for management</title>
    <link>https://pr0mpt.com/2015-08-25-lab-configure-powershell-webaccess-for-management/</link>
    <pubDate>Tue, 25 Aug 2015 11:26:02 &#43;0200</pubDate>
    <author>robert</author>
    <guid>https://pr0mpt.com/2015-08-25-lab-configure-powershell-webaccess-for-management/</guid>
    <description><![CDATA[Now that I have my Lab configured and set up to accept remoting from my Client machine, I want to set up a small Hyper-V lab onto this Host.
Since my goal is to manage as much as possible through PowerShell, my current setup will run into the following problem: I can remote into my lab host, but due to single-hop remoting, it is not recommended to daisy chain sessions.]]></description>
</item><item>
    <title>Lab: Connect to your ServerCore using remoting - step by step</title>
    <link>https://pr0mpt.com/2015-08-05-lab-connect-to-your-servercore-using-remoting-step-by-step/</link>
    <pubDate>Wed, 05 Aug 2015 14:03:49 &#43;0200</pubDate>
    <author>robert</author>
    <guid>https://pr0mpt.com/2015-08-05-lab-connect-to-your-servercore-using-remoting-step-by-step/</guid>
    <description><![CDATA[The next part in my Lab setup now that I&rsquo;ve gotten network configured is to actually no longer touch my new Lab machine…
While that might sound strange at first, the reason for this is simple. My Lab should be a headless server, stuffed in a cabinet somewhere with power and a network connection and I should be able to do ALL my management tasks remotely.
This should be a simple task you&rsquo;d say, but for the sake of clarity [and to learn this process better myself] I have decided to write down all the steps required to do this.]]></description>
</item><item>
    <title>Lab: Intel NUC with Windows ServerCore 2012R2</title>
    <link>https://pr0mpt.com/2015-08-04-lab-intel-nuc-with-windows-servercore-2012r2/</link>
    <pubDate>Tue, 04 Aug 2015 09:00:04 &#43;0200</pubDate>
    <author>robert</author>
    <guid>https://pr0mpt.com/2015-08-04-lab-intel-nuc-with-windows-servercore-2012r2/</guid>
    <description><![CDATA[Since I&rsquo;ve decided to get more serious about updating my skills and knowledge again [also why I started blogging], I thought about getting a proper lab setup.
The goal is to have a small, portable but powerful Hyper-V based lab which I can carry along with me from home and to work if need be. Now I tend to have a test setup on my home machine and one on my work laptop, depending on what I need at that moment.]]></description>
</item></channel>
</rss>
