<?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>Unattend It! &#187; unattended</title>
	<atom:link href="http://www.unattendit.com/tag/unattended/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.unattendit.com</link>
	<description>Automate Everything!</description>
	<lastBuildDate>Mon, 14 Jun 2010 07:21:24 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Deploying AutoCAD 2010</title>
		<link>http://www.unattendit.com/2009/12/03/deploying-autocad-2010/</link>
		<comments>http://www.unattendit.com/2009/12/03/deploying-autocad-2010/#comments</comments>
		<pubDate>Fri, 04 Dec 2009 03:06:29 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[scripting]]></category>
		<category><![CDATA[silent installation]]></category>
		<category><![CDATA[unattend]]></category>
		<category><![CDATA[unattended]]></category>

		<guid isPermaLink="false">http://www.unattendit.com/?p=42</guid>
		<description><![CDATA[Installing AutoCAD 2010 with scripts is fairly painless. First use the setup utility to create a new &#8220;Deployment,&#8221; saving the deployment to a network path. Once you have created a new deployment browse to the network path you saved it to. In this folder you should have three items, a folder called &#8220;AdminImage&#8221;, a folder [...]]]></description>
			<content:encoded><![CDATA[<p>Installing AutoCAD 2010 with scripts is fairly painless. First use the setup utility to create a new &#8220;Deployment,&#8221; saving the deployment to a network path. Once you have created a new deployment browse to the network path you saved it to. In this folder you should have three items, a folder called &#8220;AdminImage&#8221;, a folder called &#8220;Tools&#8221;, and a shortcut with the name of your deployment. View the properties of the shortcut and copy the &#8220;Target&#8221; field.</p>
<p>The target field should be simular to the following (One Line):</p>
<blockquote><p>\\server\share\AutoCAD_2010\AdminImage\setup.exe /qb /I \\server\share\AutoCAD_2010\AdminImage\AutoCAD_2010_x86.ini /language en-us</p></blockquote>
<p>Append this line with /wait to acheive a result simular to the following (one line):</p>
<blockquote><p>\\server\share\AutoCAD_2010\AdminImage\setup.exe /qb /I \\server\share\AutoCAD_2010\AdminImage\AutoCAD_2010_x86.ini /language en-us /wait</p></blockquote>
<p>Now just execute the command above from your scripts!</p>
<p>The AutoDesk Documentation is available <a title="AutoCAD 2010 Network Administrator's Guide" href="http://images.autodesk.com/adsk/files/acad_nag0.pdf" target="_blank">here</a> (pdf), but the document only provides an example in visual basic script.</p>
<h2>Bonus:</h2>
<p>If you wish to deploy the Visual C Runtime, DirectX, .NET 3.5 SP1, etc separately you can edit the .ini file referenced in the command above to remove this functionality (&#8220;\AdminImage\AutoCAD_2010_x86.ini&#8221; in this example). Simply open the file in a plain text editor and remove the references to the components you do not wish to have the setup install on the &#8220;PREREQUISITE&#8221; lines in the &#8220;[ACAD]&#8221; and &#8220;[ADR]&#8221; sections.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.unattendit.com/2009/12/03/deploying-autocad-2010/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Deploying Maya 2010</title>
		<link>http://www.unattendit.com/2009/11/20/deploying-maya-2010/</link>
		<comments>http://www.unattendit.com/2009/11/20/deploying-maya-2010/#comments</comments>
		<pubDate>Sat, 21 Nov 2009 03:42:32 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Unattended Installations]]></category>
		<category><![CDATA[deployments]]></category>
		<category><![CDATA[scripting]]></category>
		<category><![CDATA[silent installation]]></category>
		<category><![CDATA[unattended]]></category>

		<guid isPermaLink="false">http://www.unattendit.com/?p=36</guid>
		<description><![CDATA[Below is a sample script for installing Maya 2010 Silently. Keep in mind many of the lines are long, and are likely to wrap in a web browser.
SET MAYA2010INSTALLPATH=&#60;Insert Your Path to the folder containing the MSI Files below&#62;
SET MAYA2010SERIALNUMBER=&#60;Insert Your S/N&#62;
SET MAYA2010PRODUCTKEY=&#60;Insert Your Product Key&#62;
SET MAYA2010LICSERVER=&#60;Insert Name of your License Server (i.e. DNS Name)&#62;
msiexec [...]]]></description>
			<content:encoded><![CDATA[<p>Below is a sample script for installing Maya 2010 Silently. Keep in mind many of the lines are long, and are likely to wrap in a web browser.</p>
<blockquote><p>SET MAYA2010INSTALLPATH=&lt;Insert Your Path to the folder containing the MSI Files below&gt;</p>
<p>SET MAYA2010SERIALNUMBER=&lt;Insert Your S/N&gt;</p>
<p>SET MAYA2010PRODUCTKEY=&lt;Insert Your Product Key&gt;</p>
<p>SET MAYA2010LICSERVER=&lt;Insert Name of your License Server (i.e. DNS Name)&gt;</p>
<p>msiexec /i &#8220;%MAYA2010INSTALLPATH%\Maya_Docs_en_US2010.msi&#8221; /qb REBOOT=REALLYSUPPRESS</p>
<p>msiexec /i &#8220;%MAYA2010INSTALLPATH%\isscript.msi&#8221; /qb REBOOT=REALLYSUPPRESS</p>
<p>msiexec /i &#8220;%MAYA2010INSTALLPATH%\Maya2010.msi&#8221; /qb ADLMSERIALNUMBER=%MAYA2010SERIALNUMBER% ADLM_PRODKEY=%MAYA2010PRODUCTKEY% ADLMPRODUCTKEY=%MAYA2010PRODUCTKEY% ADLMLICENSETYPE=3 ADLMSERVERNAME=%MAYA2010LICSERVER% REBOOT=REALLYSUPPRESS</p>
<p>msiexec /i &#8220;%MAYA2010INSTALLPATH%\MatchMover2010.msi&#8221; /qb ADLMSERIALNUMBER=%MAYA2010SERIALNUMBER% ADLM_PRODKEY=%MAYA2010PRODUCTKEY% ADLMPRODUCTKEY=%MAYA2010PRODUCTKEY% ADLMLICENSETYPE=3 ADLMSERVERNAME=%MAYA2010LICSERVER% REBOOT=REALLYSUPPRESS</p>
<p>msiexec /i &#8220;%MAYA2010INSTALLPATH%\AutodeskDirectConnect4.0.msi&#8221; /qb  ADLMSERIALNUMBER=%MAYA2010SERIALNUMBER% ADLM_PRODKEY=%MAYA2010PRODUCTKEY% ADLMPRODUCTKEY=%MAYA2010PRODUCTKEY% ADLMLICENSETYPE=3 ADLMSERVERNAME=%MAYA2010LICSERVER% REBOOT=REALLYSUPPRESS</p></blockquote>
<p>Source: <a title="http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&amp;id=13813754&amp;linkID=9242258" href="http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&amp;id=13813754&amp;linkID=9242258" target="_blank">Deployment of Maya 2010</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.unattendit.com/2009/11/20/deploying-maya-2010/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Better Altiris Deployment Solution Job Shortcuts</title>
		<link>http://www.unattendit.com/2009/10/20/better-altiris-deployment-solution-job-shortcuts/</link>
		<comments>http://www.unattendit.com/2009/10/20/better-altiris-deployment-solution-job-shortcuts/#comments</comments>
		<pubDate>Tue, 20 Oct 2009 21:21:35 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Altiris]]></category>
		<category><![CDATA[Unattended Installations]]></category>
		<category><![CDATA[deployment soluation]]></category>
		<category><![CDATA[deployments]]></category>
		<category><![CDATA[scripting]]></category>
		<category><![CDATA[unattended]]></category>

		<guid isPermaLink="false">http://www.unattendit.com/?p=30</guid>
		<description><![CDATA[While it&#8217;s nothing new that you can use the Altiris Exit Codes to schedule another job and essentially create a shortcut, if you drag and drop large groups of jobs quickly enough, some jobs can run before other jobs are scheduled and things can get out of the expected order. To alleviate this issue you [...]]]></description>
			<content:encoded><![CDATA[<p>While it&#8217;s <a href="http://www.symantec.com/connect/blogs/deployment-solution-job-shortcuts" target="_blank">nothing new</a> that you can use the Altiris Exit Codes to schedule another job and essentially create a shortcut, if you drag and drop large groups of jobs quickly enough, some jobs can run before other jobs are scheduled and things can get out of the expected order. To alleviate this issue you can set the &#8220;shortcut&#8221; job to run on the deployment server. This will allow the &#8220;shortcut&#8221; jobs to schedule their corresponding jobs more quickly. Click the thumbnail below for a demonstration of where to set this option.</p>
<p><img class="alignnone size-medium wp-image-31" title="better-altiris-shortcuts" src="http://www.unattendit.com/wp-content/uploads/2009/10/better-altiris-shortcuts-297x300.jpg" alt="better-altiris-shortcuts" width="297" height="300" /></p>
]]></content:encoded>
			<wfw:commentRss>http://www.unattendit.com/2009/10/20/better-altiris-deployment-solution-job-shortcuts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Disable PC Speaker Beep</title>
		<link>http://www.unattendit.com/2009/10/17/disable-pc-speaker-beep/</link>
		<comments>http://www.unattendit.com/2009/10/17/disable-pc-speaker-beep/#comments</comments>
		<pubDate>Sun, 18 Oct 2009 01:17:22 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Unattended Installations]]></category>
		<category><![CDATA[beep]]></category>
		<category><![CDATA[scripting]]></category>
		<category><![CDATA[sound]]></category>
		<category><![CDATA[unattended]]></category>

		<guid isPermaLink="false">http://www.unattendit.com/?p=14</guid>
		<description><![CDATA[Just open an elevated command prompt, and type the command below in. It will disable the &#8220;beep&#8221; service.

sc config beep start= disabled
To turn it back on, type:
sc config beep start= auto
]]></description>
			<content:encoded><![CDATA[<p>Just open an elevated command prompt, and type the command below in. It will disable the &#8220;beep&#8221; service.<code><br />
</code></p>
<blockquote><p><code>sc config beep start= disabled</code></p></blockquote>
<p>To turn it back on, type:</p>
<blockquote><p><code>sc config beep start= auto</code></p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.unattendit.com/2009/10/17/disable-pc-speaker-beep/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Unattended installation of Windows Installer (.MSI Files)</title>
		<link>http://www.unattendit.com/2009/10/11/unattended-installation-of-windows-installer-msi-files/</link>
		<comments>http://www.unattendit.com/2009/10/11/unattended-installation-of-windows-installer-msi-files/#comments</comments>
		<pubDate>Mon, 12 Oct 2009 04:22:33 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Unattended Installations]]></category>
		<category><![CDATA[msi]]></category>
		<category><![CDATA[silent installation]]></category>
		<category><![CDATA[unattended]]></category>
		<category><![CDATA[Windows Installer]]></category>

		<guid isPermaLink="false">http://www.unattendit.com/?p=4</guid>
		<description><![CDATA[If your installer has a .msi file extension, it uses the Windows Installer. Typically all that is needed is to execute the file with one of the following switches.
example.msi /QB
example.msi /QN
The /QB switch will run the installer and display a progress box while installing the software. The /QN switch will run the installer and display [...]]]></description>
			<content:encoded><![CDATA[<p>If your installer has a .msi file extension, it uses the Windows Installer. Typically all that is needed is to execute the file with one of the following switches.</p>
<blockquote><p>example.msi /QB</p>
<p>example.msi /QN</p></blockquote>
<p>The /QB switch will run the installer and display a progress box while installing the software. The /QN switch will run the installer and display no nothing at all.</p>
<p>Some installers reboot automatically after the installation has run. To suppress the reboot you can run the installer with the switch &#8220;REBOOT=Suppress.&#8221; For example:</p>
<blockquote><p>example.msi /QB REBOOT=Suppress</p>
<p>example.msi /QN REBOOT=Suppress</p></blockquote>
<p>The following are all of the switches available for MSI files:</p>
<blockquote><p>Windows ® Installer. V 5.0.7100.0</p>
<p>msiexec /Option &lt;Required Parameter&gt; [Optional Parameter]</p>
<p>Install Options<br />
&lt;/package | /i&gt; &lt;Product.msi&gt;<br />
Installs or configures a product<br />
/a &lt;Product.msi&gt;<br />
Administrative install &#8211; Installs a product on the network<br />
/j&lt;u|m&gt; &lt;Product.msi&gt; [/t &lt;Transform List&gt;] [/g &lt;Language ID&gt;]<br />
Advertises a product &#8211; m to all users, u to current user<br />
&lt;/uninstall | /x&gt; &lt;Product.msi | ProductCode&gt;<br />
Uninstalls the product<br />
Display Options<br />
/quiet<br />
Quiet mode, no user interaction<br />
/passive<br />
Unattended mode &#8211; progress bar only<br />
/q[n|b|r|f]<br />
Sets user interface level<br />
n &#8211; No UI<br />
b &#8211; Basic UI<br />
r &#8211; Reduced UI<br />
f &#8211; Full UI (default)<br />
/help<br />
Help information<br />
Restart Options<br />
/norestart<br />
Do not restart after the installation is complete<br />
/promptrestart<br />
Prompts the user for restart if necessary<br />
/forcerestart<br />
Always restart the computer after installation<br />
Logging Options<br />
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] &lt;LogFile&gt;<br />
i &#8211; Status messages<br />
w &#8211; Nonfatal warnings<br />
e &#8211; All error messages<br />
a &#8211; Start up of actions<br />
r &#8211; Action-specific records<br />
u &#8211; User requests<br />
c &#8211; Initial UI parameters<br />
m &#8211; Out-of-memory or fatal exit information<br />
o &#8211; Out-of-disk-space messages<br />
p &#8211; Terminal properties<br />
v &#8211; Verbose output<br />
x &#8211; Extra debugging information<br />
+ &#8211; Append to existing log file<br />
! &#8211; Flush each line to the log<br />
* &#8211; Log all information, except for v and x options<br />
/log &lt;LogFile&gt;<br />
Equivalent of /l* &lt;LogFile&gt;<br />
Update Options<br />
/update &lt;Update1.msp&gt;[;Update2.msp]<br />
Applies update(s)<br />
/uninstall &lt;PatchCodeGuid&gt;[;Update2.msp] /package &lt;Product.msi | ProductCode&gt;<br />
Remove update(s) for a product<br />
Repair Options<br />
/f[p|e|c|m|s|o|d|a|u|v] &lt;Product.msi | ProductCode&gt;<br />
Repairs a product<br />
p &#8211; only if file is missing<br />
o &#8211; if file is missing or an older version is installed (default)<br />
e &#8211; if file is missing or an equal or older version is installed<br />
d &#8211; if file is missing or a different version is installed<br />
c &#8211; if file is missing or checksum does not match the calculated value<br />
a &#8211; forces all files to be reinstalled<br />
u &#8211; all required user-specific registry entries (default)<br />
m &#8211; all required computer-specific registry entries (default)<br />
s &#8211; all existing shortcuts (default)<br />
v &#8211; runs from source and recaches local package<br />
Setting Public Properties<br />
[PROPERTY=PropertyValue]</p>
<p>Consult the Windows ® Installer SDK for additional documentation on the<br />
command line syntax.</p>
<p>Copyright © Microsoft Corporation. All rights reserved.<br />
Portions of this software are based in part on the work of the Independent JPEG Group.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.unattendit.com/2009/10/11/unattended-installation-of-windows-installer-msi-files/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
