<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Wds on BAFM</title><link>https://christian.blog.pakiheim.de/tags/wds/</link><description>Recent content in Wds on BAFM</description><generator>Hugo -- 0.160.1</generator><language>en</language><lastBuildDate>Fri, 24 Feb 2012 17:31:26 +0000</lastBuildDate><atom:link href="https://christian.blog.pakiheim.de/tags/wds/index.xml" rel="self" type="application/rss+xml"/><item><title>WDS and multi-architecture boot images</title><link>https://christian.blog.pakiheim.de/posts/2012-02-24_wds-and-multi-architecture-boot-images/</link><pubDate>Fri, 24 Feb 2012 17:31:26 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=4185</guid><description>&lt;p&gt;Well, I recently stumbled upon another cute bug/feature with Windows Deployment Services. When you already have 32bit boot images (as we do) and then add an 64bit boot image (which we needed, since the drivers for UCS firmware v2.0 only support Windows Server 2008 R2) you still only see the 32bit images.&lt;/p&gt;
&lt;p&gt;Why ? Because apparently the client (in my case a UCS blade) isn&amp;rsquo;t reporting it&amp;rsquo;s architecture correctly in the PXE phase. Microsoft actually has a &lt;a href="http://support.microsoft.com/kb/932447/en-us"&gt;KB article&lt;/a&gt; for this. You only need to enable architecture discovery.&lt;/p&gt;</description></item><item><title>WDS and DL580 G7</title><link>https://christian.blog.pakiheim.de/posts/2011-01-15_wds-and-dl580-g7/</link><pubDate>Sat, 15 Jan 2011 17:14:56 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=3684</guid><description>&lt;p&gt;We recently received a shipment of Hewlett Packards all-new DL580 G7. While I&amp;rsquo;m impressed with what they did with the iLO3, I&amp;rsquo;m quite disappointed with what they did to the PXE-ROM.&lt;/p&gt;
&lt;p&gt;Sure, gPXE may be the future and is offering more possibilites than &amp;ldquo;normal&amp;rdquo; PXE, however breaking customers deployment option(s) &amp;ndash; at least for Windows that is &amp;ndash; really wouldn&amp;rsquo;t be an option.&lt;/p&gt;
&lt;p&gt;Now for the long story, we needed to install a temporary Windows on this DL580 (one with testing purposes). That said, we tried for three days to actually make this work (trying different things with the boot image), but it kept ending with the same result.&lt;/p&gt;</description></item><item><title>Install issues with Proliant BL460c G6 and Windows Deployment Services</title><link>https://christian.blog.pakiheim.de/posts/2010-10-22_install-issues-with-proliant-bl460c-g6-and-windows-deployment-services/</link><pubDate>Fri, 22 Oct 2010 17:56:53 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=3554</guid><description>&lt;p&gt;We&amp;rsquo;ve been dealing with authentification issues on newly delivered HP Proliant BL460c G6 blade servers. Most threads on HPs customer forum, suggests changing the NIC driver, embedded within the WDS boot image.&lt;/p&gt;
&lt;p&gt;We tried that, but still were getting the following error:&lt;/p&gt;
&lt;figure&gt;
&lt;img loading="lazy" src="%28/uploads/2010/10/wds-installation-issues.png"
alt="WDS: installation issues"/&gt; &lt;figcaption&gt;
&lt;p&gt;WDS: installation issues&lt;/p&gt;
&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;p&gt;As it turns out, it ain&amp;rsquo;t really so damn hard .. we tried several times changing various things within the boot image, but it still didn&amp;rsquo;t change anything. Somehow it was rather easy.&lt;/p&gt;</description></item></channel></rss>