<?xml version='1.0' encoding='utf-8' ?>
<rss version='2.0'>
<channel>
	<title>neilpahl.com Logs Feed: Network With Windows Clients And Linux Admin</title>
	<link></link>
	<description></description>
	<pubDate>Thu, 22 Jul 21 07:39:49 -0400</pubDate>
	<ttl>60</ttl>
	<item>
		<title>Network With Windows Clients And Linux Admin:: Entry 3: Network/PXE Boot with FOG Flashes Menu Too Quick</title>
		<description><![CDATA[After setting up a FOG server and configuring a machine to boot off the network using PXE / Network Boot, I had an issue with the boot menu flashing too quickly to choose anything (even if I held a key down beforehand). It turned out that the timeout was set too small by default for my machine to handle.so, In/tfptboot/pxelinux.cfg/default  I changedTIMEOUT 30toTIMEOUT 300
it appears that that timeout value is in 10ths of seconds~ and only defaulted to 30 (which, in my opinion, should be enough but for some reason my machine flashed it so quick).my original post on the FOG forum]]></description>
		<pubDate>Mon, 02 Jan 12 18:29:30 -0500</pubDate>
		<link>http://archived.neilpahl.com/logs/network-with-windows-clients-and-linux-admin/3/</link>
	</item>
	<item>
		<title>Network With Windows Clients And Linux Admin:: Entry 2: Ghosting Solution for Linux Server and Windows Clients</title>
		<description><![CDATA[Came across FOG today, this is going to be essential for managing the windows client PC images and their software updates. A blurb from their website:FOG is a Linux-based, free and open source computer imaging solution for Windows XP, Vista and 7 that ties together a few open-source tools with a php-based web interface. FOG doesn't use any boot disks, or CDs; everything is done via TFTP and PXE. Also with fog many drivers are built into the kernel, so you don't really need to worry about drivers (unless there isn't a linux kernel driver for it). FOG also supports putting an image that came from a computer with a 80GB partition onto a machine with a 40GB hard drive as long as the data is less than 40GB. ]]></description>
		<pubDate>Wed, 21 Dec 11 17:05:35 -0500</pubDate>
		<link>http://archived.neilpahl.com/logs/network-with-windows-clients-and-linux-admin/2/</link>
	</item>
	<item>
		<title>Network With Windows Clients And Linux Admin:: Entry 1: Where to Start</title>
		<description><![CDATA[This log is focused on the topic of administering a windows network with a linux server.I'm setting up a network to manage windows PC's. We're not in a place to invest into Windows Servers (why would you when you can use linux?) and that fact is not going to let us utallize the well travelled route of Active Directory. The current state of the 'Network' is just a room full of PC's all running independantly with the same software setup, and there is a definate need to have all these computers properly networked with their user data centrallized.So, after searching around for good ways to avoid Windows Server, I came across a nice HOW-TO which will use samba to implement policies and redirect user folders to the network drives. The HOW-TO was found here:http://tldp.org/HOWTO/Samba-Authenticated-Gateway-HOWTO-]]></description>
		<pubDate>Tue, 13 Dec 11 18:05:03 -0500</pubDate>
		<link>http://archived.neilpahl.com/logs/network-with-windows-clients-and-linux-admin/1/</link>
	</item>
</channel>
</rss>