<?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>Active-Directory on BAFM</title><link>https://christian.blog.pakiheim.de/tags/active-directory/</link><description>Recent content in Active-Directory 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/active-directory/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>Active Directory authentification for Samba on SLES11</title><link>https://christian.blog.pakiheim.de/posts/2009-10-21_active-directory-authentification-for-samba-on-sles11/</link><pubDate>Wed, 21 Oct 2009 18:46:25 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=2663</guid><description>&lt;p&gt;I recently &amp;ldquo;redesigned&amp;rdquo; the PXE-installation server, which comes with a Samba service to easily move files on/off the box. The old one had the restriction, you need to create local user accounts. Since I also did an distribution upgrade, I wanted to try the integration of SLES11 into Active Directory.&lt;/p&gt;
&lt;p&gt;And as it turns out, it really is simple. Just follow the steps &lt;a href="http://www.suse.com/documentation/sles11/book_sle_admin/data/sec_samba_adnet.html"&gt;outlined in the handbook&lt;/a&gt;.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Open the Windows Domain Membership module, yast samba-client (or yast, then Network Services -&amp;gt; Windows Domain Membership) and enter your Domain information&lt;/li&gt;
&lt;li&gt;Open the Samba Server Module, yast samba-server (or yast, then Network Services -&amp;gt; Samba Server) and also enter your Domain information&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Just make sure, you also check the box labeled &lt;em&gt;&lt;strong&gt;Also Use SMB Information for Linux Authentication&lt;/strong&gt;&lt;/em&gt;, otherwise it won&amp;rsquo;t work &amp;ndash; don&amp;rsquo;t ask me why &amp;hellip;&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>Nagios3 with Active Directory authorization on SLES10</title><link>https://christian.blog.pakiheim.de/posts/2008-07-14_nagios3-with-active-directory-authorization-on-sles10/</link><pubDate>Mon, 14 Jul 2008 17:32:04 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=494</guid><description>&lt;p&gt;Well, it seems to be getting a &amp;ldquo;trend&amp;rdquo; for me, to integrate stuff into our Active Directory. Now that I know why, and how easy that is, I expect to add more stuff. The good thing about the integration is, that you only need to maintain a single source for authorization.&lt;/p&gt;
&lt;p&gt;The bad thing about that is, that stuff becomes dependent on the Active Directory (we do have four domain controllers, so that should be fine).&lt;/p&gt;</description></item><item><title>subversion on WebDAV with Active Directory authorization on SLES10</title><link>https://christian.blog.pakiheim.de/posts/2008-06-29_subversion-on-webdav-with-active-directory-authorization-on-sles10/</link><pubDate>Sun, 29 Jun 2008 17:49:29 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=425</guid><description>&lt;p&gt;Okay, so I ended up toying with subversion via WebDAV on SLES today (I know, I know .. it&amp;rsquo;s bloody Sunday). It wasn&amp;rsquo;t much of a hassle though, after reading this. Sure, I made a few errors at first (simply confused the logic behind &amp;quot; &lt;em&gt;&lt;a href="http://httpd.apache.org/docs/2.2/mod/core.html#location"&gt;Location&lt;/a&gt;&lt;/em&gt;&amp;quot; and &amp;quot; &lt;em&gt;&lt;a href="http://httpd.apache.org/docs/2.2/mod/core.html#directory"&gt;Directory&lt;/a&gt;&lt;/em&gt;&amp;quot;), but after that plain subversion commits via WebDAV (thus utilizing Apache) worked fine.&lt;/p&gt;
&lt;p&gt;For POC or as a hint to myself, here&amp;rsquo;s where and what I needed to add/change:&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></channel></rss>