<?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>Windows-Xpe on BAFM</title><link>https://christian.blog.pakiheim.de/tags/windows-xpe/</link><description>Recent content in Windows-Xpe on BAFM</description><generator>Hugo -- 0.160.1</generator><language>en</language><lastBuildDate>Sat, 16 Aug 2014 09:57:51 +0000</lastBuildDate><atom:link href="https://christian.blog.pakiheim.de/tags/windows-xpe/index.xml" rel="self" type="application/rss+xml"/><item><title>Windows XP Embedded and GPO settings</title><link>https://christian.blog.pakiheim.de/posts/2014-08-16_windows-xp-embedded-and-gpo-settings/</link><pubDate>Sat, 16 Aug 2014 09:57:51 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=260</guid><description>&lt;p&gt;We&amp;rsquo;re currently having a weird issue (which we had before); the Windows XP Embedded powering our Wyse V90&amp;rsquo;s isn&amp;rsquo;t applying any GPO settings if you log on with a user that has a configured profile.&lt;/p&gt;
&lt;p&gt;Googling (is that a valid word yet ?!) for it, only resulted in &lt;a href="http://windows.ittoolbox.com/groups/technical-functional/activedirectory-l/applying-gpo-to-xp-embedded-thin-client-1259431"&gt;one useful link&lt;/a&gt;, which is apparently a guy with the exact same problem &amp;hellip; &amp;#x1f937; I&amp;rsquo;m completely out of ideas by now, as I don&amp;rsquo;t even have a place to start (as in where the reason might be located).&lt;/p&gt;</description></item><item><title>Windows XP Embedded and GPO settings (continued)</title><link>https://christian.blog.pakiheim.de/posts/2014-08-16_windows-xp-embedded-and-gpo-settings-continued/</link><pubDate>Sat, 16 Aug 2014 09:56:20 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=325</guid><description>&lt;p&gt;Well, as I said in my &lt;a href="https://christian.blog.pakiheim.de/posts/2008-06-04_windows-xp-embedded-windows-server-2003-and-gpo-settings-the-solution" title="Windows XP Embedded and GPO settings"&gt;previous post&lt;/a&gt;, I do have some weird things happening. Apparently adding the domain user to the local group &amp;ldquo;Administrators&amp;rdquo; makes everything just works fine, yet he can&amp;rsquo;t do administrator like stuff (like turning off the write protection, changing local user accounts, &amp;hellip;).&lt;/p&gt;
&lt;p&gt;Also, if you&amp;rsquo;re looking for a smart way of how to add a certain global group (as in Active Directory group) to a local group, try this:&lt;/p&gt;</description></item><item><title>Windows XP(e) refusing to connect to a terminal server</title><link>https://christian.blog.pakiheim.de/posts/2009-07-23_windows-xp-e-refusing-to-connect-to-a-terminal-server/</link><pubDate>Thu, 23 Jul 2009 14:48:52 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=2411</guid><description>&lt;p&gt;Today a error message reappeared I thought I wouldn&amp;rsquo;t see again. We use Wyse Thin Clients and 2X running on two terminal servers, to provide the thin clients with applications. Now, once a while one of the thin clients (not all at once, just a single one) refuse to connect to the terminal server jabbing about this:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;div class="chroma"&gt;
&lt;table class="lntable"&gt;&lt;tr&gt;&lt;td class="lntd"&gt;
&lt;pre tabindex="0" class="chroma"&gt;&lt;code&gt;&lt;span class="lnt" id="hl-0-1"&gt;&lt;a class="lnlinks" href="#hl-0-1"&gt;1&lt;/a&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;
&lt;td class="lntd"&gt;
&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-fallback" data-lang="fallback"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;The remote computer disconnected the session because of an error in the licensing protocol.
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;p&gt;The error message you get from the 2X client ain&amp;rsquo;t the slightest bit more helpful.&lt;/p&gt;</description></item><item><title>VBscript undamp; Active Directory and printers (continued)</title><link>https://christian.blog.pakiheim.de/posts/2008-12-05_vbscript-amp-active-directory-and-printers-continued/</link><pubDate>Fri, 05 Dec 2008 21:54:09 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/index.php/2007/10/25/vbscript-active-directory-and-printers-continued/</guid><description>&lt;p&gt;As I &lt;a href="https://christian.blog.pakiheim.de/posts/2008-12-05_vbscript-amp-active-directory-and-printers-continued" title="VBscript &amp;amp; Active Directory and printers ?"&gt;posted earlier&lt;/a&gt;, I tried working around some limitations in Microsoft&amp;rsquo;s Active Directory by teaching the script some intelligence.&lt;/p&gt;
&lt;p&gt;But, since we recently started using Thin Clients, all the stuff I did with the fancy vbs was just a waste-of-time. Turns out, Windows XP Embedded doesn&amp;rsquo;t work quite the same as a &amp;quot; &lt;em&gt;normal&lt;/em&gt;&amp;quot; Windows XP (that&amp;rsquo;s where I tested the script on), and it simply dies when running the WMI Query. Bollocks.&lt;/p&gt;</description></item><item><title>GPO (behind the scenes)</title><link>https://christian.blog.pakiheim.de/posts/2008-06-05_gpo-behind-the-scenes/</link><pubDate>Thu, 05 Jun 2008 06:46:20 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=340</guid><description>&lt;p&gt;Well, to begin with we had this really weird problem that the &lt;a href="https://christian.blog.pakiheim.de/posts/2008-06-04_windows-xp-embedded-windows-server-2003-and-gpo-settings-the-solution" title="Windows XP Embedded and GPO settings"&gt;thin clients&lt;/a&gt; as well as the terminal server would only load user based group policy if you are a &lt;a href="https://christian.blog.pakiheim.de/posts/2014-08-16_windows-xp-embedded-and-gpo-settings-continued" title="Windows XP Embedded and GPO settings (continued)"&gt;member of the group of local administrators&lt;/a&gt;. While that&amp;rsquo;s ok for the thin clients (users can&amp;rsquo;t actually change something unless they log in as &amp;ldquo;Administrator&amp;rdquo; - don&amp;rsquo;t ask me why), it&amp;rsquo;s a real no-no on the terminal server.&lt;/p&gt;</description></item><item><title>Windows XP Embedded, Windows Server 2003 and GPO settings (the solution)</title><link>https://christian.blog.pakiheim.de/posts/2008-06-04_windows-xp-embedded-windows-server-2003-and-gpo-settings-the-solution/</link><pubDate>Wed, 04 Jun 2008 19:35:57 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=338</guid><description>&lt;p&gt;OK, so about an hour (yeah, yeah; I know .. I shouldn&amp;rsquo;t be working at that time, but it really gave me sleepless nights) ago, I finally figured out why the hell both my Windows XP Embedded thin clients as well as my Windows Server 2003 systems where showing this &lt;a href="https://christian.blog.pakiheim.de/posts/2014-08-16_windows-xp-embedded-and-gpo-settings-continued" title="Windows XP Embedded and GPO settings (continued)"&gt;real &lt;em&gt;&lt;strong&gt;weird&lt;/strong&gt;&lt;/em&gt; behaviour&lt;/a&gt; when applying group policies, or more precise the user based configuration of a group policy.&lt;/p&gt;</description></item><item><title>Integrating Windows XPe into Active Directory</title><link>https://christian.blog.pakiheim.de/posts/2008-03-07_integrating-windows-xpe-into-active-directory/</link><pubDate>Fri, 07 Mar 2008 22:12:44 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=231</guid><description>&lt;p&gt;As the guys over at &lt;a href="http://www.freewysemonkeys.com"&gt;FreeWyseMonkeys&lt;/a&gt; demonstrated with JoinDomain.zip, it ain&amp;rsquo;t hard to integrate a Windows XP Embedded system into Active Directory.&lt;/p&gt;
&lt;p&gt;You basically need this:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A system powered by Windows XP Embedded&lt;/li&gt;
&lt;li&gt;netdom.exe (from any Windows XP - SP2 in your MUI language)&lt;/li&gt;
&lt;li&gt;some know-how, on how to use netdom to integrate it into your AD&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Everything else is already present on the Windows XP Embedded systems I&amp;rsquo;ve seen. Then let&amp;rsquo;s get it on !&lt;/p&gt;</description></item><item><title>Customizing Thin Clients</title><link>https://christian.blog.pakiheim.de/posts/2007-10-12_customizing-thin-clients/</link><pubDate>Fri, 12 Oct 2007 22:14:53 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/2007/10/06/thin-clients-active-directory/</guid><description>&lt;p&gt;As some of you know, the company I&amp;rsquo;m currently working for, recently acquired some thin clients to replace our old computers for the students to work on. Those PC&amp;rsquo;s are like P3 800 MHz with 512MB RAM and sadly don&amp;rsquo;t run Office 2007 anymore, so we replaced them with thin clients and are streaming those applications from a Windows Terminal Server cluster (created by and with 2X Application LoadBalancer).&lt;/p&gt;
&lt;p&gt;So far so good, getting them to display the applications ain&amp;rsquo;t hard, the real hard part starts when you want additional things from this Windows XPe (Embedded), like lets say getting them to display a German language.&lt;/p&gt;</description></item><item><title>Thin clients</title><link>https://christian.blog.pakiheim.de/posts/2007-10-06_thin-clients/</link><pubDate>Sat, 06 Oct 2007 14:13:44 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/2007/10/06/thin-clients/</guid><description>&lt;p&gt;As some of you people know, we (as in the University) recently purchased some Thin Clients in order to replace some oldish&amp;rsquo; computers and solve the software management at the same time.&lt;/p&gt;
&lt;p&gt;The Thin Clients ain&amp;rsquo;t bad, they are &lt;a href="http://www.wyse.com/products/hardware/thinclients/V90L/index.asp"&gt;Wyse V90L&lt;/a&gt;&amp;rsquo;s and they (as in Wyse) use their own management software to manage and deploy those thin clients and software. The bad thing about that, is it&amp;rsquo;s using it&amp;rsquo;s own &amp;ldquo;Scripting Language&amp;rdquo; (if you can call it that way - it&amp;rsquo;s more pseudo scripting since you can&amp;rsquo;t do much with it besides some basic actions).&lt;/p&gt;</description></item></channel></rss>