﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>New Boundary Support Forum / Package Deployment / Prism Deploy &amp; Prism Pack  / Running scripts hidden from users view / Latest Posts</title><generator>InstantForum.NET v4.1.3</generator><description>New Boundary Support Forum</description><link>http://www.nbtnet.newboundary.com/forum/</link><webMaster>support@newboundary.com</webMaster><lastBuildDate>Fri, 21 Nov 2008 18:21:13 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Running scripts hidden from users view</title><link>http://www.nbtnet.newboundary.com/forum/Topic1265-5-1.aspx</link><description>The Prism client can detect the return code from a process that it launched with the /run command. However, many installations spawn other processes, and Prism has no way of tracking those. So there are cases where Prism reports completion, but the other processes that were launched may still be running.</description><pubDate>Thu, 15 Feb 2007 13:06:04 GMT</pubDate><dc:creator>New Boundary Support</dc:creator></item><item><title>RE: Running scripts hidden from users view</title><link>http://www.nbtnet.newboundary.com/forum/Topic1265-5-1.aspx</link><description>I know this is old, but in running msiexec as a Deploy Script is it a bad idea to use /Wait ?&lt;/P&gt;&lt;P&gt;/RUN /WAIT msiexec /i software.msi /qn&lt;/P&gt;&lt;P&gt;With the many instances of msiexec I am curious how deploy would know the task is really complete.&lt;/P&gt;&lt;P&gt;Thanks, as always.</description><pubDate>Tue, 13 Feb 2007 14:11:40 GMT</pubDate><dc:creator>martyy</dc:creator></item><item><title>RE: Running scripts hidden from users view</title><link>http://www.nbtnet.newboundary.com/forum/Topic1265-5-1.aspx</link><description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;It isn't necessary to use %comspec% when running msiexec to install an MSI file. The %comspec% variable refers to the system's command processor. It is only needed when you're running one of the built-in commands, such as xcopy, set, rmdir, etc. The switch /C closes the window; without that, the DOS window would have to be manually closed.&lt;/P&gt;&lt;P&gt;Your script should look like this:&lt;/P&gt;&lt;P&gt;/run msiexec /qn /i "\\server\share\Client package.msi"&lt;BR&gt;/Installpackage "\\server\share\My Own package for shortcuts.PWC"&lt;/P&gt;</description><pubDate>Wed, 26 Apr 2006 16:02:00 GMT</pubDate><dc:creator>New Boundary Support</dc:creator></item><item><title>Running scripts hidden from users view</title><link>http://www.nbtnet.newboundary.com/forum/Topic1265-5-1.aspx</link><description>In some other posts I read about errorlevel reporting back to Deploy. It states to use the %COMSPEC% variable. Now when I use this in my script I see a CMD-box open and close while script is running. I want to hide this from users view.&lt;br&gt;Is this script with all the options correct, or do I need to change things. Do I need to use %COMSPEC%?&lt;br&gt;&lt;br&gt;/run %COMSPEC% /C msiexec /qn /i "Client package.msi"&lt;br&gt;/Installpackage "My Own package for shortcuts.PWC"&lt;br&gt;&lt;br&gt;I can also create one big PWC, but I want to use supplied MSI's where thy can be silently installed and only append with simple PWC's if possible.</description><pubDate>Wed, 26 Apr 2006 09:48:00 GMT</pubDate><dc:creator>pizza</dc:creator></item></channel></rss>