We’re currently having a weird issue (which we had before); the Windows XP Embedded powering our Wyse V90’s isn’t applying any GPO settings if you log on with a user that has a configured profile. Googling (is that a valid word yet ?!) for it, only resulted in one useful link, which is apparently a guy with the exact same problem … 🤷 I’m completely out of ideas by now, as I don’t even have a place to start (as in where the reason might be located). ...
Well, as I said in my previous post, I do have some weird things happening. Apparently adding the domain user to the local group “Administrators” makes everything just works fine, yet he can’t do administrator like stuff (like turning off the write protection, changing local user accounts, …). Also, if you’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: ...
I recently “redesigned” 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. And as it turns out, it really is simple. Just follow the steps outlined in the handbook. Open the Windows Domain Membership module, yast samba-client (or yast, then Network Services -> Windows Domain Membership) and enter your Domain information Open the Samba Server Module, yast samba-server (or yast, then Network Services -> Samba Server) and also enter your Domain information Just make sure, you also check the box labeled Also Use SMB Information for Linux Authentication, otherwise it won’t work – don’t ask me why …
As I posted earlier, I tried working around some limitations in Microsoft’s Active Directory by teaching the script some intelligence. 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’t work quite the same as a " normal" Windows XP (that’s where I tested the script on), and it simply dies when running the WMI Query. Bollocks. ...
Well, it seems to be getting a “trend” 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. 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). ...
Okay, so I ended up toying with subversion via WebDAV on SLES today (I know, I know .. it’s bloody Sunday). It wasn’t much of a hassle though, after reading this. Sure, I made a few errors at first (simply confused the logic behind " Location" and " Directory"), but after that plain subversion commits via WebDAV (thus utilizing Apache) worked fine. For POC or as a hint to myself, here’s where and what I needed to add/change: ...
OK, so about an hour (yeah, yeah; I know .. I shouldn’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 real weird behaviour when applying group policies, or more precise the user based configuration of a group policy. ...