<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Schose's Blog &#187; Unattended</title>
	<atom:link href="http://blog.schose.net/index.php/archives/category/unattended/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.schose.net</link>
	<description>I like default settings!!! ;)</description>
	<lastBuildDate>Tue, 03 Mar 2009 01:01:01 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Druckerkonfiguration / -Anlage scripten</title>
		<link>http://blog.schose.net/index.php/archives/127</link>
		<comments>http://blog.schose.net/index.php/archives/127#comments</comments>
		<pubDate>Wed, 13 Feb 2008 17:19:59 +0000</pubDate>
		<dc:creator>andreas</dc:creator>
				<category><![CDATA[Deployment]]></category>
		<category><![CDATA[Unattended]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://blog.schose.net/index.php/archives/127</guid>
		<description><![CDATA[Wer mehr als eine handvoll Drucker, -Treiber und -Warteschlangen zu managen hat, kommt früher oder später nicht umher die Anlage zu automatisieren. Besonders in Printercluster- oder Terminalumgebungen sollten Verwaltungscripte das Management übernehmen. Nur so kann sichergestellt werden, dass Treiberversionen über alle Maschinen konsistent sind.
Die benötigten Scripte liefert Microsoft bereits bei der Installation mit. Sie befinden [...]]]></description>
			<content:encoded><![CDATA[<p>Wer mehr als eine handvoll Drucker, -Treiber und -Warteschlangen zu managen hat, kommt früher oder später nicht umher die Anlage zu automatisieren. Besonders in Printercluster- oder Terminalumgebungen sollten Verwaltungscripte das Management übernehmen. Nur so kann sichergestellt werden, dass Treiberversionen über alle Maschinen konsistent sind.</p>
<p>Die benötigten Scripte liefert Microsoft bereits bei der Installation mit. Sie befinden sich bei WindowsXP/2003 unter C:\windows\system32. Bei Vista wird man je nach Sprachversion unter C:\Windows\System32\Printing_Admin_Scripts\de-DE\ fündig. Die Parameter und Funktionen sind aber identisch.</p>
<p>Als Beispiel lege ich meinen neuen Homeofficesdrucker per Batchdatei an. <span id="more-127"></span> Dieser ist per TCP/IP (TCP/9100) auf 192.168.178.6 erreichbar. Die Modellbezeichnung des Druckertyps kann von OS zu OS unterschiedlich sein. Man findet sie in der entsprechenden .inf Datei im Treiberverzeichnis unter [MODEL]. Weiterhin wird der Standort sowie Beschreibung gesetzt und im Netzwerk freigegeben.</p>
<p><strong>Treiber hinzufügen:<br />
</strong>cscript C:\windows\system32\prndrvr.vbs -a -m &#8220;Samsung CLX-216x Series&#8221; -v 3 -i &#8220;D:\temp\treiber\clx2160\GDI_COLOR\WINXP_2000<br />
_VISTA_32\cx21s.inf&#8221;</p>
<p><strong>TCP/IP-Druckerport:<br />
</strong>cscript C:\windows\system32\prnport.vbs -a -r &#8220;IP_192.168.178.6&#8243; -h 192.168.178.6 -o raw</p>
<p><strong>Drucker hinzufügen:</strong><br />
cscript C:\windows\system32\prnmngr.vbs -a -p &#8220;SamsungPrinter&#8221; -m &#8220;Samsung CLX-216x Series&#8221; -r &#8220;IP_192.168.178.6&#8243;</p>
<p><strong>Druckerbeschreibung ändern:<br />
</strong>cscript C:\windows\system32\prncnfg.vbs -t -p SamsungPrinter -l &#8220;Neudietendorf&#8221; -m &#8220;Homeprinter&#8221;</p>
<p><strong>Drucker freigeben:<br />
</strong>cscript C:\windows\system32\prncnfg.vbs -t -p SamsungPrinter -h &#8220;SamsungShare&#8221; +shared -direct</p>
<p><strong>alle Drucker und Treiber von Maschine entfernen:<br />
</strong><code><br />
REM spooler neu starten<br />
net stop spooler<br />
net start spooler</code><br />
<code><br />
REM alle Drucker löschen:<br />
cscript C:\windows\system32\prnmngr.vbs -x</code></p>
<p><code>REM alle Druckertreiber löschen:<br />
cscript C:\windows\system32\prndrvr.vbs -x</code></p>
<p>mehr Infos:<br />
<a href="http://technet2.microsoft.com/WindowsServer/de/Library/aed6763a-458c-48e6-bfea-ae94a82997b61031.mspx?mfr=true">Microsoft Technet</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.schose.net/index.php/archives/127/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>pimp my RHEL / CentOS / Fedora</title>
		<link>http://blog.schose.net/index.php/archives/112</link>
		<comments>http://blog.schose.net/index.php/archives/112#comments</comments>
		<pubDate>Thu, 03 Jan 2008 21:25:37 +0000</pubDate>
		<dc:creator>andreas</dc:creator>
				<category><![CDATA[Deployment]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Unattended]]></category>

		<guid isPermaLink="false">http://blog.schose.net/index.php/archives/112</guid>
		<description><![CDATA[Die Redhat Repositories geben im Vergleich zu Debian-basierenden Distributionen nicht ausreichend Software her. Beispielsweise ist Nagios nicht in der Distribution vorhanden.
Wer trotzdem nicht auf den Luxus einer Paketverwaltung verzichten möchte greift zum DAG.
Einfach /etc/yum.conf um das Repository (hier CentOS4):
[dag]
name=dag
baseurl=http://apt.sw.be/redhat/el4/en/$basearch/dag
gpgcheck=0
erweitern und updaten.
Link zu FAQ
]]></description>
			<content:encoded><![CDATA[<p>Die Redhat Repositories geben im Vergleich zu Debian-basierenden Distributionen nicht ausreichend Software her. Beispielsweise ist Nagios nicht in der Distribution vorhanden.</p>
<p>Wer trotzdem nicht auf den Luxus einer Paketverwaltung verzichten möchte greift zum <a href="http://dag.wieers.com/rpm/">DAG</a>.</p>
<p>Einfach /etc/yum.conf um das Repository (hier CentOS4):</p>
<p>[dag]<br />
name=dag<br />
baseurl=http://apt.sw.be/redhat/el4/en/$basearch/dag<br />
gpgcheck=0</p>
<p>erweitern und updaten.</p>
<p><a href="http://dag.wieers.com/rpm/FAQ.php">Link zu FAQ</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.schose.net/index.php/archives/112/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>fully hardware-independent unattended ESX3 Server installation &#8211; Part 1</title>
		<link>http://blog.schose.net/index.php/archives/60</link>
		<comments>http://blog.schose.net/index.php/archives/60#comments</comments>
		<pubDate>Sun, 09 Sep 2007 18:55:00 +0000</pubDate>
		<dc:creator>andreas</dc:creator>
				<category><![CDATA[Deployment]]></category>
		<category><![CDATA[Howto]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Unattended]]></category>
		<category><![CDATA[VMware]]></category>

		<guid isPermaLink="false">http://blog.schose.net/index.php/archives/60</guid>
		<description><![CDATA[This article will show you how to build an unique installjob for unattended ESX3 installations. It will run on different hardware plattforms.
The process of setting up an VMware ESX3 Host ist quite similar to RHEL3/Centos3. I&#8217;m using Altriris Deployment Server (or HP Rapid Deployment Pack) but IMHO you could easily customize it for any other [...]]]></description>
			<content:encoded><![CDATA[<p>This article will show you how to build an unique installjob for unattended ESX3 installations. It will run on different hardware plattforms.</p>
<p>The process of setting up an VMware ESX3 Host ist quite similar to RHEL3/Centos3. I&#8217;m using Altriris Deployment Server (or HP Rapid Deployment Pack) but IMHO you could easily customize it for any other deployment solution.</p>
<p><span id="more-60"></span></p>
<p>The main steps are:<br />
1. create a bootable dos partition with all necessary files for booting up the linux installer with loadlin &#8211; or linld.<br />
2. create bootentries depending on your physical hardware (Proliant, PowerEdge Server&#8230;)<br />
3. create a custom kickstart (ks.cfg) file which uses hostname and ip you entered in you deployment server console.<br />
4. create virtual switches, portgroups etc. depending on your enviroment.<br />
5. install further Managmentsoftware (e.g.: Openmanage, Proliant Support Pack), Backup- or Monitoringagents</p>
<p><strong>Step One:</strong><br />
Deploy an empty FAT32 partition to you deploment client. Mine is 100MB, but it can be much smaller &#8211; you can use rdeploy. Reboot your maschine.<br />
The install01.bat file attached is copying the needed files from deplomentserver share.</p>
<p><code>copy %OSFilesPath%\dosutils\loadlin.exe c:\loadlin.exe<br />
copy %OSFilesPath%\dosutils\linld.com c:\linld.com<br />
copy %OSFilesPATH%\dosutils\autoboot\initrd.img c:\initrd.img<br />
copy %OSFilesPATH%\dosutils\autoboot\vmlinuz c:\vmlinuz</p>
<p>echo dos2unix.exe ks.cfg > C:\autoexec.bat<br />
</code></p>
<p><strong>Step 2:</strong><br />
Now you have to create a custom bootentry for your linux loader. The main problem is that the ks.cfg will be located on hardware and the devicenames differ from vendor to vendor (e.g. /dev/cciss/c0d0 for HP with SmartArray &#8211; /dev/sda for MegaRaid). Be aware that the 9th generation of PowerEdge Server (PE1950, PE2950&#8230;) will not work with loadlin. Nobody really knows why, but I found it <a href="http://juice.altiris.com/article/1076/deploying-vmware-esx-3-0-x-to-9th-generation-dell-poweredge-servers">here</a>.</p>
<p>install02.bat does make the decision for you what server hardware you&#8217;ve got:</p>
<p><code>if "%#!computer@right(prod_name,4)%" =="2850" goto sda<br />
if "%#!computer@right(prod_name,4)%" =="2950" goto sdalld<br />
if "%#!computer@right(prod_name,2)%" =="G4" goto cciss</p>
<p>REM if nothing ins found make sda entry<br />
goto exitsda</p>
<p>:sda<br />
echo i boot from sda<br />
echo c:\loadlin c:\vmlinuz initrd=c:\initrd.img ramdisk_size=12288 ks=hd:sda1/ks.cfg >> c:\autoexec.bat<br />
goto Exit</p>
<p>:sdalld<br />
echo i boot with linld from sda<br />
echo c:\linld.com image=c:\vmlinuz initrd=c:\initrd.img "cl=ramdisk_size=12288 ks=hd:sda1/ks.cfg" >> c:\autoexec.bat<br />
goto Exit</p>
<p>:cciss<br />
echo i boot from cciss<br />
echo c:\loadlin c:\vmlinuz initrd=c:\initrd.img ramdisk_size=12288 ks=hd:cciss/c0d0p1:/ks.cfg >> c:\autoexec.bat<br />
goto Exit</p>
<p>:exitsda<br />
echo i boot from sda<br />
echo c:\loadlin c:\vmlinuz initrd=c:\initrd.img ramdisk_size=12288 ks=hd:sda1/ks.cfg >> c:\autoexec.bat<br />
goto Exit</p>
<p>:Exit<br />
exit</code></p>
<p>The strange looking &#8220;%#!computer@right(prod_name,4)%&#8221; is Altiris DS specific. It&#8217;s reading out the vendor description for the Server presented at PXE Boot. This will differ to other Deployment solutions.<br />
Now reboot you maschine and make C:\ drive bootable (install03.bat) and copy further files.</p>
<p><code>f:\bootwiz\dos\sys.com f:\bootwiz\dos c:<br />
f:<br />
copy f:\bootwiz\dos\himem.sys c:\<br />
copy f:\bootwiz\dos\smartdrv.exe c:\<br />
echo device=c:\himem.sys>>c:\config.sys<br />
echo @echo on>>c:\autoexec.bat</code></p>
<p><strong>Step3a: create ks.cfg file</strong></p>
<p>The ks.cfg file is the answer file for the ESX Installer. If you are not familar with the kickstart procedure you can fancy it as an unattended.txt or winnt.sif file for Windows Installations. <img src='http://blog.schose.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  The main difference is that you also define package source (in my case a webserver with the hole cd copied to &#8220;http://webserverurl/esx3&#8243; and partition scheme. The important section begins at %post and process self written scripts after the installation. I&#8217;m using it for creating virtual networks, installing the altiris (adl)agent and some small jobs.</p>
<p>You can easily create a ks.cfg file with installing ESX Server one time manually. The specified options are written to /root/anaconda-ks.cfg. For further information about kickstartfile consult <a href="http://www.vmware.com/pdf/vi3_301_201_installation_guide.pdf">VI Installation guide</a>. </p>
<p><strong>Step3b: Token Replacement Process</strong><br />
The Replacement Process is also Altris DS specific und uses for creating a machine specific kickstart file. It is replacing placeholders with the values you entered in Deployment Server Console. Because there is no Token for VMKernel network ip, I&#8217;m using the os license entry for it. Do <strong>not remove</strong> any &#8220;rem&#8221;ed line. &#8211; the Token Replacement will not work.</p>
<p><code>rem bootwork unload</p>
<p>rem replacetokens .\deplmes\deploy\pre-os\esx3\ks.cfg .\deplmes\deploy\pre-os\esx3\%ID%.cfg<br />
Firm Copy F:\deplmes\deploy\pre-os\esx3\%ID%.cfg C:\ks.cfg<br />
Firm Copy F:\deplmes\centos\unixdo16\dos2unix.exe C:\dos2unix.exe<br />
</code></p>
<p>After the Token Replacement process you installation is ready to be booted to production. This will start the installer with the ks.cfg file. Good luck!</p>
<p>You will find more information about step 4 and step 5 in the next Blog-entry &#8220;fully hardware-independent unattended ESX3 Server installation &#8211; Part 2&#8243;. This will be published in the next days.</p>
<p><strong>Attachments: </strong><br />
<a href="http://andreas.ndfnet.de/showfiles/esx/install01.bat">install01.bat</a><br />
<a href="http://andreas.ndfnet.de/showfiles/esx/install02.bat">install02.bat</a><br />
<a href="http://andreas.ndfnet.de/showfiles/esx/install03.bat">install03.bat</a><br />
<a href="http://andreas.ndfnet.de/showfiles/esx/ks.cfg">Kickstart file ks.cfg</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.schose.net/index.php/archives/60/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
