<?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>James&#039; Tools and Tricks &#187; MSI</title>
	<atom:link href="http://jrudd.org/wordpress/tag/msi/feed/" rel="self" type="application/rss+xml" />
	<link>http://jrudd.org/wordpress</link>
	<description>Tools, Tips and Hints for managing a network.</description>
	<lastBuildDate>Mon, 26 Jul 2010 03:13:40 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Google Earth Zenworks Deployment</title>
		<link>http://jrudd.org/wordpress/2009/02/20/google-earth-zenworks-deployment/</link>
		<comments>http://jrudd.org/wordpress/2009/02/20/google-earth-zenworks-deployment/#comments</comments>
		<pubDate>Fri, 20 Feb 2009 04:26:02 +0000</pubDate>
		<dc:creator>James Rudd</dc:creator>
				<category><![CDATA[Windows]]></category>
		<category><![CDATA[AdminUser]]></category>
		<category><![CDATA[ChangeInstallDirForNonAdmin]]></category>
		<category><![CDATA[Condition]]></category>
		<category><![CDATA[deploy]]></category>
		<category><![CDATA[deployment program]]></category>
		<category><![CDATA[google earth]]></category>
		<category><![CDATA[InstallExecuteSequence]]></category>
		<category><![CDATA[InstallUISequence]]></category>
		<category><![CDATA[local settings]]></category>
		<category><![CDATA[MSI]]></category>
		<category><![CDATA[orca]]></category>
		<category><![CDATA[School]]></category>
		<category><![CDATA[Zenworks]]></category>

		<guid isPermaLink="false">http://jrudd.org/wordpress/?p=98</guid>
		<description><![CDATA[How to deploy Google Earth to C:\Program Files\Google\Google Earth instead of Local Settings\Application Data\Google\Google Earth by removing AdminUser checks from the MSI.]]></description>
			<content:encoded><![CDATA[<p><a href="http://earth.google.com/">Google Earth</a> is a great program for schools, as it allows teachers and students to explore the worlds geography and use layers to examine  history, socio-economic information and many other areas.</p>
<p>It used to be fairly easier to deploy on your network, but after version 4.2 it became significantly more difficult if you use a deployment program like Zenworks. A new MSI test was introduced to determine where to install Google Earth. If the current user is not an Admin User it would redirect to <em>[LocalAppDataFolder]Google\Google Earth</em> (usually C:\Documents and Settings\username\Local Settings\Application Data\Google\Google Earth) which made it inaccessible to other users.</p>
<p>As Zenworks uses the System account, which is not an admin user, this would happen when the installer was launched by a student.</p>
<p>To fix this problem there are a few different techniques. You can use either <a href="http://www.technipages.com/download-orca-msi-editor.html">ORCA </a>or Admin Studio Tuner (from Zenworks) to create a transform file that ignores these checks. Alternatively you can use ORCA to edit the msi file directly, I had to use this technique for V5 due to some exisiting problems in the Google Earth MSI.</p>
<p>First download the full version of Google Earth, (<a href="http://dl.google.com/earth/client/GE5/release_5_0/GoogleEarth-Win-Plus-5.0.11337.1968.exe">V5.0.11337</a>). You should be able to find later versions through Google.</p>
<p>To find what you need to edit you can do a search in ORCA for <em>AdminUser </em>you should find around 3 entries.</p>
<p>The major entries are:</p>
<ul>
<li><em>InstallExecuteSequence: ChangeInstallDirForNonAdmin: NOT AdminUser</em> (Delete this row)</li>
<li><em>InstallExecuteSequence: setALLUSERS: AdminUser</em> (remove the word AdminUser so it applies to all installs)</li>
<li><em>InstallUISequence: ChangeInstallDirForNonAdmin: NOT AdminUser</em> (Delete this row)</li>
</ul>
<p>You may also wish to remove <em>AdminUser </em>as a <em>Condition </em>from <em>Component: Plus_Registry_wavdest.ax</em></p>
<p>Once these are removed or modified it should install in C:\Program Files\Google\Google Earth regardless of which user is logged in.</p>
]]></content:encoded>
			<wfw:commentRss>http://jrudd.org/wordpress/2009/02/20/google-earth-zenworks-deployment/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Changing MSI filename in a Zenworks Application Object</title>
		<link>http://jrudd.org/wordpress/2007/12/04/changing-msi-filename-in-a-zenworks-application-object/</link>
		<comments>http://jrudd.org/wordpress/2007/12/04/changing-msi-filename-in-a-zenworks-application-object/#comments</comments>
		<pubDate>Tue, 04 Dec 2007 04:36:51 +0000</pubDate>
		<dc:creator>James Rudd</dc:creator>
				<category><![CDATA[Novell]]></category>
		<category><![CDATA[ConsoleOne]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[MSI]]></category>
		<category><![CDATA[Path]]></category>
		<category><![CDATA[UNC]]></category>
		<category><![CDATA[Zenworks]]></category>

		<guid isPermaLink="false">http://jrudd.org/wordpress/2007/12/04/changing-msi-filename-in-a-zenworks-application-object/</guid>
		<description><![CDATA[In ConsoleOne it is relatively easy to change the path to an MSI but much more difficult to change the file name of the MSI itself. A trick is to install a second copy of ConsoleOne without any plugins. (I just have link to Clean ConsoleOne.) Using this version you can then Open the App <a href='http://jrudd.org/wordpress/2007/12/04/changing-msi-filename-in-a-zenworks-application-object/'>[...]</a>]]></description>
			<content:encoded><![CDATA[<p>In ConsoleOne it is relatively easy to change the path to an MSI but much more difficult to change the file name of the MSI itself.</p>
<p>A trick is to install a second copy of ConsoleOne without any plugins. (I just have link to <em>Clean ConsoleOne</em>.) Using this version you can then Open the App Object and go to the <em>Other </em>tab, and expand <em>zenappPackageName</em>, double click the filename to change.</p>
<p>I use this quite regularly when updating <a href="http://www.frontmotion.com/FMFirefoxCE/">FrontMotion&#8217;s Firefox</a> MSI&#8217;s. I just keep two object and alternate between them. One production and one testing.</p>
<p>To change the location of an MSI you need to change 2 locations in ConsoleOne (with Zen plugins):</p>
<ul>
<li>Identification Tab (initial page loaded): Administration Package Path</li>
<li>Common Tab: Sources: Modify or Add a new source</li>
</ul>
<p>Make sure all paths use UNC paths. I recommend using <a href="http://jrudd.org/wordpress/2007/11/17/ninotech-path-copy-40/">Path Copy</a> for this.</p>
]]></content:encoded>
			<wfw:commentRss>http://jrudd.org/wordpress/2007/12/04/changing-msi-filename-in-a-zenworks-application-object/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
