<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Windows-Server-2008-R2 on When Software Attacks!</title><link>https://rikhepworth.com/tags/windows-server-2008-r2/</link><description>Recent content in Windows-Server-2008-R2 on When Software Attacks!</description><generator>Hugo -- gohugo.io</generator><language>en_GB</language><copyright>&amp;copy; Rik Hepworth</copyright><lastBuildDate>Sun, 29 Sep 2013 00:00:00 +0000</lastBuildDate><atom:link href="https://rikhepworth.com/tags/windows-server-2008-r2/index.xml" rel="self" type="application/rss+xml"/><item><title>Building environments for Lab Manager: Why bare metal scripting fails</title><link>https://rikhepworth.com/posts/building-environments-for-lab-manager-why-bare-metal-scripting-fails/</link><pubDate>Sun, 29 Sep 2013 00:00:00 +0000</pubDate><guid>https://rikhepworth.com/posts/building-environments-for-lab-manager-why-bare-metal-scripting-fails/</guid><description>&lt;p&gt;In the world of DevOps it’s all about the scripts: I’ve seen some great work done by some clever people to create complex environments with multiple VMs all from scratch using PowerShell. That’s great, but unfortunately in the world of Lab Manager it just doesn’t work well at all.&lt;/p&gt;</description></item><item><title>Adding DHCP Option 119 (Domain Search List) to Windows Server 2008 R2</title><link>https://rikhepworth.com/posts/adding-dhcp-option-119-domain-search-list-to-windows-server-2008-r2/</link><pubDate>Mon, 18 Jun 2012 00:00:00 +0000</pubDate><guid>https://rikhepworth.com/posts/adding-dhcp-option-119-domain-search-list-to-windows-server-2008-r2/</guid><description>&lt;p&gt;If you’ve seen my recent blog post on making Android work in Hyper-V you will have seen my problems around DNS resolution when in the office. That turned out to be down to the DHCP options being handed back by our Server 2008 R2 box. Or rather, it was what &lt;em&gt;wasn’t&lt;/em&gt; being handed back to the client that was the problem.&lt;/p&gt;</description></item><item><title>Server Core, Hyper-V and VLANs: An Odyssey</title><link>https://rikhepworth.com/posts/server-core-hyper-v-and-vlans-an-odyssey/</link><pubDate>Mon, 06 Dec 2010 00:00:00 +0000</pubDate><guid>https://rikhepworth.com/posts/server-core-hyper-v-and-vlans-an-odyssey/</guid><description>&lt;h2 class="relative group"&gt;A sensible plan
 &lt;div id="a-sensible-plan" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#a-sensible-plan" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;This is a torrid tale of frustration and annoyance, tempered by the fun of digging through system commands and registry entries to try and get things working.&lt;/p&gt;</description></item><item><title>Fixing SharePoint 2007 IIS WAMREG DCOM 10016 activation errors on Server 2008 R2</title><link>https://rikhepworth.com/posts/fixing-sharepoint-2007-iis-wamreg-dcom-10016-activation-errors-on-server-2008-r2/</link><pubDate>Mon, 08 Feb 2010 00:00:00 +0000</pubDate><guid>https://rikhepworth.com/posts/fixing-sharepoint-2007-iis-wamreg-dcom-10016-activation-errors-on-server-2008-r2/</guid><description>&lt;p&gt;Anybody who works will SharePoint will grumble if you mention DCOM activation permissions. No matter how hard we try, how many patches we install (or how hard we try to ignore it), granting activation and launch permissions to the SharePoint service accounts is like plugging a dike with water-soluble filler.&lt;/p&gt;</description></item><item><title>NewSID fails on Windows Server 2008 R2</title><link>https://rikhepworth.com/posts/newsid-fails-on-windows-server-2008-r2/</link><pubDate>Fri, 08 May 2009 00:00:00 +0000</pubDate><guid>https://rikhepworth.com/posts/newsid-fails-on-windows-server-2008-r2/</guid><description>&lt;p&gt;The title says it all. I’m currently building a virtual lab to test DirectAccess and every time I run newsid on windows server 2008 R2 the system bluescreens irrevocably on reboot. I’ve now switched to using sysprep to change the SID. Here’s hoping the sysinternals guys update what is undoubtedly one of the most useful tools around!&lt;/p&gt;</description></item></channel></rss>