<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>Lab - Category - pr0mpt</title>
        <link>https://pr0mpt.com/categories/lab/</link>
        <description>Lab - Category - pr0mpt</description>
        <generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Fri, 27 Jul 2018 13:37:51 &#43;0200</lastBuildDate><atom:link href="https://pr0mpt.com/categories/lab/" rel="self" type="application/rss+xml" /><item>
    <title>Windows Server 2019 - Windows Admin Center</title>
    <link>https://pr0mpt.com/2018-07-27-windows-server-2019-windows-admin-center/</link>
    <pubDate>Fri, 27 Jul 2018 13:37:51 &#43;0200</pubDate>
    <author>robert</author>
    <guid>https://pr0mpt.com/2018-07-27-windows-server-2019-windows-admin-center/</guid>
    <description><![CDATA[<p>After having played around a bit with Windows 2019 server, it was time to see what this &ldquo;Project Honolulu&rdquo; was all about.
Only to find out it&rsquo;s no longer called that, it&rsquo;s now been re-branded to it&rsquo;s (hopefully) final name: Windows Admin Center</p>]]></description>
</item><item>
    <title>VM Lab - Switch it up</title>
    <link>https://pr0mpt.com/2016-07-07-vm-lab-switch-it-up/</link>
    <pubDate>Thu, 07 Jul 2016 12:00:33 &#43;0200</pubDate>
    <author>robert</author>
    <guid>https://pr0mpt.com/2016-07-07-vm-lab-switch-it-up/</guid>
    <description><![CDATA[Back again for another part in my VM Lab series.
So far I&rsquo;ve created the folder structure which we will use to store our ISO files, VHD files [including template VHDs and Unattend.xml files] and VM&rsquo;s. In order to manipulate the ReadOnly status of various files [such as the template VHD&rsquo;s and Unattend.xml files], I&rsquo;ve provided simple functions which will assist us.
Now we need to make sure that the final piece of the infrastructure is ready: the Hyper-V VM Switches.]]></description>
</item><item>
    <title>VM Lab - Read Only status</title>
    <link>https://pr0mpt.com/2016-07-06-vm-lab-read-only-status/</link>
    <pubDate>Wed, 06 Jul 2016 12:30:50 &#43;0200</pubDate>
    <author>robert</author>
    <guid>https://pr0mpt.com/2016-07-06-vm-lab-read-only-status/</guid>
    <description><![CDATA[In this next installment of my VM Lab series of posts, I have created a tiny set of tools which basically do exactly as the names imply. While I admit, not quite hard to do, perhaps you&rsquo;d even prefer to type things manually, but as mentioned in my previous post, for me it&rsquo;s all about re-usability.
Requirements In one of the upcoming installments of my VM Lab series, I will create a template VHD file, which will need to be set to Read Only in order to prevent changes to be made accidentally.]]></description>
</item><item>
    <title>VM Lab - Lab Folders</title>
    <link>https://pr0mpt.com/2016-07-05-vm-lab-lab-folders/</link>
    <pubDate>Tue, 05 Jul 2016 12:53:45 &#43;0200</pubDate>
    <author>robert</author>
    <guid>https://pr0mpt.com/2016-07-05-vm-lab-lab-folders/</guid>
    <description><![CDATA[Lets get started…
First of all, I always prefer my lab to have the same layout and tend to use the same solutions, since they&rsquo;re either best practice or the most logical approach for me. Now in a Lab environment, this starts at the basics, creating a folder structure to put everything in, from VHDs, VMs to ISO files and templates.
Requirements For my Lab I always want it to have the same folder structure.]]></description>
</item><item>
    <title>VM Lab - Introduction</title>
    <link>https://pr0mpt.com/2016-07-03-vm-lab-introduction/</link>
    <pubDate>Sun, 03 Jul 2016 15:38:53 &#43;0200</pubDate>
    <author>robert</author>
    <guid>https://pr0mpt.com/2016-07-03-vm-lab-introduction/</guid>
    <description><![CDATA[Hey guys,
It&rsquo;s been a bit quiet lately, some holiday time and most importantly a change of jobs! As of July 1st I now work for OSC as an Infrastructure Specialist and will hopefully have more time to expand my knowledge and share this with the community.
The last few weeks I&rsquo;ve been busy playing around with a solution in order to quickly create a Lab with VM&rsquo;s.
While I know how to manually set them up and create machines, I had a somewhat &lsquo;ideal&rsquo; method in mind and didn&rsquo;t really want to stray from that idea.]]></description>
</item><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>
