<?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>Nico.Berlee.nl &#187; Ghost</title>
	<atom:link href="http://nico.berlee.nl/tag/ghost/feed/" rel="self" type="application/rss+xml" />
	<link>http://nico.berlee.nl</link>
	<description>a digital portfolio</description>
	<lastBuildDate>Sat, 21 Jan 2012 21:31:25 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Faster deployment of new PC&#8217;s using GSS 2</title>
		<link>http://nico.berlee.nl/faster-deployment-of-new-pcs-using-gss-2/</link>
		<comments>http://nico.berlee.nl/faster-deployment-of-new-pcs-using-gss-2/#comments</comments>
		<pubDate>Sun, 15 Apr 2007 14:55:26 +0000</pubDate>
		<dc:creator>Nico</dc:creator>
				<category><![CDATA[Network-/System Administration]]></category>
		<category><![CDATA[deploy]]></category>
		<category><![CDATA[Ghost]]></category>
		<category><![CDATA[pxe_boot]]></category>
		<category><![CDATA[Symantec]]></category>

		<guid isPermaLink="false">http://nico.berlee.nl/faster-deployment-of-new-pcs-using-gss-2/</guid>
		<description><![CDATA[When you have a fine Symantec Ghost Solution Suite deployment environment, it could still be a pain to deploy new computers. These are the steps you probably have to do: Boot with PXE boot Write down the last four MAC digits Change the computer name in the ghost console configuration Clone the new pc&#8217;s with [...]]]></description>
			<content:encoded><![CDATA[<p>When you have a fine Symantec Ghost Solution Suite deployment environment, it could still be a pain to deploy new computers. These are the steps you probably have to do:<br />
<span id="more-40"></span></p>
<ul>
<li>Boot with PXE boot</li>
<li>Write down the last four MAC digits</li>
<li>Change the computer name in the ghost console configuration</li>
<li>Clone the new pc&#8217;s with a configuration template (for domain etc)</li>
</ul>
<p>Especially step 2 and 3 are time consuming&#8230; This started me to think about a solution. The easiest way was to ask for a computer name during PXE boot and give that computer name as a parameter to NGCTDOS.exe (which is the Ghost Console client for dos). NGCTDOS then would deliver the computer name to the ghost console.</p>
<p>Nice huh? Except for one thing&#8230; there is no such parameter. I asked this question on the Symantec Forum and Nigel Bree (a really great Principal Software Engineer for the Ghost Solution Suite) <a href="https://forums.symantec.com/syment/board/message?board.id=109&amp;message.id=3335">kindly replied</a> it would be a fairly natural extension.</p>
<p>This started me to think about other ways to get this done, without a pain. I came up with a solution involving ghconfig (which is part of the PXE boot image), change.com (a 19 year old text replacing utility of 737 bytes!) and <a href="http://home.mnet-online.de/horst.muc/ui.htm">wbat</a>.exe (a dialog box utility by Horst Schaeffer).</p>
<p><img src="http://nico.berlee.nl/files/2007/04/new-pc-boot.gif" alt="Network boot, asking if itâ€™s a new pc?" width="360" height="200" class="centered" /></p>
<p>The end result is a dialog box with mouse support, which asks for 15 seconds for a computer name. If no input is given during that period or cancel is pressed, the Ghost Console Client will behave as a normal Ghost Console dos client. If a computer name is entered, the computer name will be set after the ghost image process.</p>
<p>If you also want to speed up your new pcâ€™s deployment process, follow the following steps:</p>
<ol>
<li>Go to the ghost console and pick a Machine configuration. <a href='http://nico.berlee.nl/files/2007/04/gss2-replacecompname.gif' title='Ghost Solution Suite 2 - Replace Computer name'><img src='http://nico.berlee.nl/files/2007/04/gss2-replacecompname.thumbnail.gif' alt='Ghost Solution Suite 2 - Replace Computer name' class='centered' /></a>Change the computer name in REPLACE (in capitals). Change other settings to the settings you want on your new pc&#8217;s.<br />
<a href='http://nico.berlee.nl/files/2007/04/gss2-exportcompconf.gif' title='Ghost Solution Suite 2 - Export Computer Configuration'><img src='http://nico.berlee.nl/files/2007/04/gss2-exportcompconf.thumbnail.gif' alt='Ghost Solution Suite 2 - Export Computer Configuration' class='centered' /></a><br />
Export the configuration, and name the file: ghregupd.reg</li>
<li>Download <a href="http://nico.berlee.nl/wp-content/uploads/ghost-console-new-pc.zip" title="Download files for in the PXE image">ghost-console-new-pc.zip</a> and unpack the zip file</li>
<li>Open the 3Com Boot Image Editor (which is part of the 3Com Boot services on the Ghost install CD)<br />
<a href='http://nico.berlee.nl/files/2007/04/3cbs-bie.gif' title='3Com Boot Image Editor'><img src='http://nico.berlee.nl/files/2007/04/3cbs-bie.thumbnail.gif' alt='3Com Boot Image Editor' class='centered' /></a><br />
Edit the sys pxe file that was created by the Ghost Boot Wizard<br />
<a href='http://nico.berlee.nl/files/2007/04/3cbs-bie2.gif' title='Boot Image Editor'><img src='http://nico.berlee.nl/files/2007/04/3cbs-bie2.thumbnail.gif' alt='Boot Image Editor' class='centered' /></a><br />
Place the just unpacked files (from the downloaded zip file) in the root of the boot image. And put ghregupd.reg in the GHOST directory.</li>
</ol>
<p>You are done.</p>
<p>Please note that if you are now deploying new pcâ€™s the pcâ€™s will appear in the folder New Computers on the Ghost Console initially with their MAC addresses. But after you run a successful task with the following steps:</p>
<ul>
<li>Clone</li>
<li>Execute Command in Ghost Boot Partition: ghconfig.exe /a</li>
<li>Configuration Refresh</li>
<li>(Optionally packages, but absolutely <b>not</b> Configuration!)</li>
</ul>
<p>The computer names will magically appear.</p>
<p>Please note that because Ghost Console is normally in charge of creating or resetting the computer domain account. This means that the new computers are probably not a domain member. You can fix this by running a configuration task with a configuration template afterwards.</p>
<p>Good luck!</p>
]]></content:encoded>
			<wfw:commentRss>http://nico.berlee.nl/faster-deployment-of-new-pcs-using-gss-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Symantec Ghost Console networkcard detection update</title>
		<link>http://nico.berlee.nl/symantec-ghost-console-networkcard-detection-update/</link>
		<comments>http://nico.berlee.nl/symantec-ghost-console-networkcard-detection-update/#comments</comments>
		<pubDate>Sun, 21 Jan 2007 22:21:39 +0000</pubDate>
		<dc:creator>Nico</dc:creator>
				<category><![CDATA[Network-/System Administration]]></category>
		<category><![CDATA[broadcom]]></category>
		<category><![CDATA[Ghost]]></category>
		<category><![CDATA[intel]]></category>
		<category><![CDATA[networkcard]]></category>
		<category><![CDATA[Symantec]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://nico.berlee.nl/symantec-ghost-console-networkcard-detection-update/</guid>
		<description><![CDATA[When you install new computers in your corporate network with Symantec Ghost, choosing the right dos networkcard template could be a pain when you didn&#8217;t update your drivers that Ghost use for booting using the virtual partition in dos.Â  Major networkchip vendors like Broadcom or Intel are releasing every 2 months a new chip model [...]]]></description>
			<content:encoded><![CDATA[<p>When you install new computers in your corporate network with Symantec Ghost, choosing the right dos networkcard template could be a pain when you didn&#8217;t update your drivers that Ghost use for booting using the virtual partition in dos.Â  Major networkchip vendors like Broadcom or Intel are releasing every 2 months a new chip model along with a driver update&#8230;<span id="more-32"></span></p>
<p>So you finally download, unpacked and updated your <a href="http://www.broadcom.com/support/ethernet_nic/driver-sla.php?driver=570x-DOSNDIS2" title="Download DOS NDIS2 driver">Broadcom BCM57xx</a>Â or <a href="http://downloadfinder.intel.com/scripts-df-external/license_agr.aspx?url=/4239/eng/PRODOS.exe&amp;ProductID=62&amp;agr=Y&amp;sType=&amp;PrdMap=&amp;DwnldId=4239&amp;strOSs=All&amp;OSFullName=All+Operating+Systems&amp;lang=eng" title="Download DOS NDIS2 drivers">Intel Pro 100/1000</a>Â NDIS2 drivers using <a href="http://service1.symantec.com/SUPPORT/ghost.nsf/docid/2000011211551725" title="Symantec Ghost Knowledge base on how to update/add/modify networkcard templates">Ghost Boot Wizard</a>Â but Ghost doesn&#8217;t suggest / autoselectÂ your just updated drivers like it does with the default shipped ones! What&#8217;s that all about?</p>
<p>In order to detect networkcards, Symantec ghost needsÂ to know on a per driver bases the PCI device IDs. PCI device IDs are normally stored in inf that are packedÂ with the drivers. Those inf filesÂ tells Windows for which device the drivers are and how to install them. I have extracted the PCI device IDs from the inf&#8217;s and formatted them into the Ghost file format.</p>
<p>If you updated the BCM57XX driver go to the directory: C:DocumentsÂ AndÂ SettingsAllÂ UsersApplication DataSymantecGhostTemplateBCM57XX (some directories might be hidden) or if you added a template replace the last directory by the template name of the template you added.</p>
<p>Edit the mcassist.cfg and replace all the PCI-TAG lines with the following lines: (these are based on the Broadcom BCM57XX 9.81 driver:</p>
<pre>PCI-TAG = 14e4 1600 : Broadcom BCM5750A1$
PCI-TAG = 14e4 1601 : Broadcom BCM5750A1M$
PCI-TAG = 14e4 1644 : Broadcom BCM5700$
PCI-TAG = 14e4 1645 : Broadcom BCM5701$
PCI-TAG = 14e4 1646 : Broadcom BCM5702$
PCI-TAG = 14e4 1647 : Broadcom BCM5703$
PCI-TAG = 14e4 1648 : Broadcom BCM5704$
PCI-TAG = 14e4 1653 : Broadcom BCM5705$
PCI-TAG = 14e4 1654 : Broadcom BCM5705A2$
PCI-TAG = 14e4 1658 : Broadcom BCM5750$
PCI-TAG = 14e4 1659 : Broadcom BCM5750A1$
PCI-TAG = 14e4 165D : Broadcom BCM5705M$
PCI-TAG = 14e4 165E : Broadcom BCM5705MA2$
PCI-TAG = 14e4 1668 : Broadcom BCM5714$
PCI-TAG = 14e4 1669 : Broadcom BCM5714S$
PCI-TAG = 14e4 166A : Broadcom BCM5780$
PCI-TAG = 14e4 166B : Broadcom BCM5714S$
PCI-TAG = 14e4 166e : Broadcom BCM5705F$
PCI-TAG = 14e4 1672 : Broadcom BCM5750A1M$
PCI-TAG = 14e4 1673 : Broadcom BCM5750A1DMOBILE$
PCI-TAG = 14e4 1676 : Broadcom BCM5750$
PCI-TAG = 14e4 1677 : Broadcom BCM5750A1$
PCI-TAG = 14e4 1677 : Broadcom BCM5750$
PCI-TAG = 14e4 1678 : Broadcom BCM5714$
PCI-TAG = 14e4 1679 : Broadcom BCM5714S$
PCI-TAG = 14e4 167A : Broadcom BCM5750A1$
PCI-TAG = 14e4 167B : Broadcom BCM5750A1$
PCI-TAG = 14e4 167C : Broadcom BCM5750A1$
PCI-TAG = 14e4 167D : Broadcom BCM5750$
PCI-TAG = 14e4 167E : Broadcom BCM5750A1F$
PCI-TAG = 14e4 167F : Broadcom BCM5750A1F$
PCI-TAG = 14e4 1693 : Broadcom BCM5750A1M$
PCI-TAG = 14e4 1696 : Broadcom BCM5705A2$
PCI-TAG = 14e4 169A : Broadcom BCM5750A1$
PCI-TAG = 14e4 169B : Broadcom BCM5750A1$
PCI-TAG = 14e4 169c : Broadcom BCM5788$
PCI-TAG = 14e4 169d : Broadcom BCM5789$
PCI-TAG = 14e4 16a6 : Broadcom BCM5702$
PCI-TAG = 14e4 16a7 : Broadcom BCM5703$
PCI-TAG = 14e4 16A8 : Broadcom BCM5704S$
PCI-TAG = 14e4 16C6 : Broadcom BCM5702$
PCI-TAG = 14e4 16C7 : Broadcom BCM5703$
PCI-TAG = 14e4 16DD : Broadcom BCM5789$
PCI-TAG = 14e4 16F7 : Broadcom BCM5750A1$
PCI-TAG = 14e4 16FD : Broadcom BCM5750A1M$
PCI-TAG = 14e4 16FF : Broadcom BCM5750B0M$
PCI-TAG = 14e4 170D : Broadcom BCM5901$
PCI-TAG = 14e4 170E : Broadcom BCM5901$</pre>
<p>If you updated theÂ Intel Pro 100Â driver go to the directory: C:DocumentsÂ AndÂ SettingsAllÂ UsersApplication DataSymantecGhostTemplateIntel Pro 100Â (some directories might be hidden) or if you added a template replace the last directory by the template name of the template you added.</p>
<p>Edit the mcassist.cfg and replace all the PCI-TAG lines with the following lines: (these are based on theÂ Intel Prodos 11.2Â driver:</p>
<pre>PCI-TAG = 8086 1037 : Intel(R) PRO/100 Adapter$
PCI-TAG = 8086 103C : Intel(R) PRO/100 Adapter$
PCI-TAG = 8086 103D : Intel(R) PRO/100 Adapter$
PCI-TAG = 8086 103E : Intel(R) PRO/100 Adapter$
PCI-TAG = 8086 2459 : Intel(R) PRO/100 Adapter$
PCI-TAG = 8086 245D : Intel(R) PRO/100 Adapter$
PCI-TAG = 8086 1059 : Intel(R) PRO/100 Adapter$
PCI-TAG = 8086 1050 : Intel(R) PRO/100 Adapter$
PCI-TAG = 8086 1051 : Intel(R) PRO/100 Adapter$
PCI-TAG = 8086 1052 : Intel(R) PRO/100 Adapter$
PCI-TAG = 8086 1053 : Intel(R) PRO/100 Adapter$
PCI-TAG = 8086 1054 : Intel(R) PRO/100 Adapter$
PCI-TAG = 8086 1055 : Intel(R) PRO/100 Adapter$
PCI-TAG = 8086 1056 : Intel(R) PRO/100 Adapter$
PCI-TAG = 8086 1057 : Intel(R) PRO/100 Adapter$
PCI-TAG = 8086 1064 : Intel(R) PRO/100 Adapter$
PCI-TAG = 8086 1065 : Intel(R) PRO/100 Adapter$
PCI-TAG = 8086 1066 : Intel(R) PRO/100 Adapter$
PCI-TAG = 8086 1067 : Intel(R) PRO/100 Adapter$
PCI-TAG = 8086 1068 : Intel(R) PRO/100 Adapter$
PCI-TAG = 8086 1069 : Intel(R) PRO/100 Adapter$
PCI-TAG = 8086 106A : Intel(R) PRO/100 Adapter$
PCI-TAG = 8086 106B : Intel(R) PRO/100 Adapter$
PCI-TAG = 8086 27DC : Intel(R) PRO/100 Adapter$
PCI-TAG = 8086 1091 : Intel(R) PRO/100 Adapter$
PCI-TAG = 8086 1092 : Intel(R) PRO/100 Adapter$
PCI-TAG = 8086 1093 : Intel(R) PRO/100 Adapter$
PCI-TAG = 8086 1094 : Intel(R) PRO/100 Adapter$
PCI-TAG = 8086 1095 : Intel(R) PRO/100 Adapter$
PCI-TAG = 8086 1029 : Intel(R) PRO/100 M Mobile Connection$
PCI-TAG = 8086 1059 : Intel(R) PRO/100 M Mobile Connection$
PCI-TAG = 8086 1031 : Intel(R) PRO/100 VE Network Connection$
PCI-TAG = 8086 1032 : Intel(R) PRO/100 VE Network Connection$
PCI-TAG = 8086 1033 : Intel(R) PRO/100 VE Network Connection$
PCI-TAG = 8086 1034 : Intel(R) PRO/100 VE Network Connection$
PCI-TAG = 8086 1035 : Intel(R) PRO/100 VE Network Connection$
PCI-TAG = 8086 1036 : Intel(R) PRO/100 VE Network Connection$
PCI-TAG = 8086 1038 : Intel(R) PRO/100 VE Network Connection$
PCI-TAG = 8086 1039 : Intel(R) PRO/100 VE Network Connection$
PCI-TAG = 8086 103A : Intel(R) PRO/100 VE Network Connection$
PCI-TAG = 8086 103B : Intel(R) PRO/100 VM Network Connection$
PCI-TAG = 8086 1229 : Intel(R) 82557 Based Adapter$
PCI-TAG = 8086 2449 : Intel(R) PRO/100E Adapter$</pre>
<p>If you updated the Intel Pro 1000 driver go to the directory: C:DocumentsÂ AndÂ SettingsAllÂ UsersApplication DataSymantecGhostTemplateIntel Pro 1000 (some directories might be hidden) or if you added a template replace the last directory by the template name of the template you added.</p>
<p>Edit the mcassist.cfg and replace all the PCI-TAG lines with the following lines: (these are based on the Intel Prodos 11.2 driver:</p>
<pre>PCI-TAG = 8086 1000 : Intel Pro 1000$
PCI-TAG = 8086 1001 : Intel Pro 1000$
PCI-TAG = 8086 1004 : Intel Pro 1000$
PCI-TAG = 8086 1008 : Intel Pro 1000$
PCI-TAG = 8086 1009 : Intel Pro 1000$
PCI-TAG = 8086 100C : Intel Pro 1000$
PCI-TAG = 8086 100D : Intel Pro 1000$
PCI-TAG = 8086 100E : Intel Pro 1000$
PCI-TAG = 8086 100F : Intel Pro 1000$
PCI-TAG = 8086 1010 : Intel Pro 1000$
PCI-TAG = 8086 1011 : Intel Pro 1000$
PCI-TAG = 8086 1012 : Intel Pro 1000$
PCI-TAG = 8086 1013 : Intel Pro 1000$
PCI-TAG = 8086 1015 : Intel Pro 1000$
PCI-TAG = 8086 1016 : Intel Pro 1000$
PCI-TAG = 8086 1017 : Intel Pro 1000$
PCI-TAG = 8086 1018 : Intel Pro 1000$
PCI-TAG = 8086 1019 : Intel Pro 1000$
PCI-TAG = 8086 101D : Intel Pro 1000$
PCI-TAG = 8086 101E : Intel Pro 1000$
PCI-TAG = 8086 1013 : Intel Pro 1000$
PCI-TAG = 8086 1018 : Intel Pro 1000$
PCI-TAG = 8086 1019 : Intel Pro 1000$
PCI-TAG = 8086 101D : Intel Pro 1000$
PCI-TAG = 8086 101E : Intel Pro 1000$
PCI-TAG = 8086 1026 : Intel Pro 1000$
PCI-TAG = 8086 1027 : Intel Pro 1000$
PCI-TAG = 8086 1028 : Intel Pro 1000$
PCI-TAG = 8086 1049 : Intel Pro 1000$
PCI-TAG = 8086 104A : Intel Pro 1000$
PCI-TAG = 8086 104B : Intel Pro 1000$
PCI-TAG = 8086 104C : Intel Pro 1000$
PCI-TAG = 8086 104D : Intel Pro 1000$
PCI-TAG = 8086 105E : Intel Pro 1000$
PCI-TAG = 8086 105F : Intel Pro 1000$
PCI-TAG = 8086 1060 : Intel Pro 1000$
PCI-TAG = 8086 1075 : Intel Pro 1000$
PCI-TAG = 8086 1076 : Intel Pro 1000$
PCI-TAG = 8086 1077 : Intel Pro 1000$
PCI-TAG = 8086 1078 : Intel Pro 1000$
PCI-TAG = 8086 1079 : Intel Pro 1000$
PCI-TAG = 8086 107A : Intel Pro 1000$
PCI-TAG = 8086 107B : Intel Pro 1000$
PCI-TAG = 8086 107C : Intel Pro 1000$
PCI-TAG = 8086 107D : Intel Pro 1000$
PCI-TAG = 8086 107E : Intel Pro 1000$
PCI-TAG = 8086 107F : Intel Pro 1000$
PCI-TAG = 8086 108A : Intel Pro 1000$
PCI-TAG = 8086 108B : Intel Pro 1000$
PCI-TAG = 8086 108C : Intel Pro 1000$
PCI-TAG = 8086 1097 : Intel Pro 1000$
PCI-TAG = 8086 1098 : Intel Pro 1000$
PCI-TAG = 8086 109A : Intel Pro 1000$
PCI-TAG = 8086 10A4 : Intel Pro 1000$
PCI-TAG = 8086 10B5 : Intel Pro 1000$
PCI-TAG = 8086 10B9 : Intel Pro 1000$
PCI-TAG = 8086 10BA : Intel Pro 1000$
PCI-TAG = 8086 10BB : Intel Pro 1000$
PCI-TAG = 8086 10BC : Intel Pro 1000$
PCI-TAG = 8086 10C4 : Intel Pro 1000$
PCI-TAG = 8086 10C5 : Intel Pro 1000$</pre>
<p>After you are done editing the files, restart the Ghost Console. Now your Intel or Broadcom chipbased networkcard are getting recognized again!</p>
]]></content:encoded>
			<wfw:commentRss>http://nico.berlee.nl/symantec-ghost-console-networkcard-detection-update/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

