<?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>Thin-Clients on BAFM</title><link>https://christian.blog.pakiheim.de/tags/thin-clients/</link><description>Recent content in Thin-Clients on BAFM</description><generator>Hugo -- 0.160.1</generator><language>en</language><lastBuildDate>Sat, 16 Aug 2014 10:15:10 +0000</lastBuildDate><atom:link href="https://christian.blog.pakiheim.de/tags/thin-clients/index.xml" rel="self" type="application/rss+xml"/><item><title>VBscript undamp; Active Directory and printers</title><link>https://christian.blog.pakiheim.de/posts/2014-08-16_vbscript-amp-active-directory-and-printers/</link><pubDate>Sat, 16 Aug 2014 10:15:10 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/2007/10/13/vbscript-active-directory/</guid><description>&lt;p&gt;Well, since our current solution for mapping printers is an ugly batch file, which needs to be put into &lt;em&gt;Startup&lt;/em&gt;, I today poked at doing it in VBscript (I know, but it&amp;rsquo;s less ugly than the batch script, trust me).&lt;/p&gt;
&lt;p&gt;As some of you know, printers are only applicable to users (as in you can&amp;rsquo;t put a startup script onto an OU, which is going to map the printers). So as we store users and the computes in different OU&amp;rsquo;s in our Active Directory (we do have about 15.000 students), I can&amp;rsquo;t apply the printer.vbs to the users OU directly either, unless I implement some intelligence into the script itself.&lt;/p&gt;</description></item><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>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>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>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></channel></rss>