New Boundary Support Forum
Home      Members   Calendar   Who's On
Welcome Guest ( Login | Register )
      



Running scripts hidden from users viewExpand / Collapse
Author
Message
Posted 4/26/2006 9:48:00 AM
Junior Member

Junior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior Member

Group: Forum Members
Last Login: 10/25/2006 3:31:08 AM
Posts: 12, Visits: 37
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.
Is this script with all the options correct, or do I need to change things. Do I need to use %COMSPEC%?

/run %COMSPEC% /C msiexec /qn /i "Client package.msi"
/Installpackage "My Own package for shortcuts.PWC"

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.

That that doesn't kill me, only makes me stronger!
Post #1265
Posted 4/26/2006 4:02:00 PM


Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Moderators
Last Login: 10/8/2008 1:15:23 PM
Posts: 655, Visits: 810

Hello,

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.

Your script should look like this:

/run msiexec /qn /i "\\server\share\Client package.msi"
/Installpackage "\\server\share\My Own package for shortcuts.PWC"





New Boundary Technologies Support
support@newboundary.com

Post #1267
Posted 2/13/2007 2:11:40 PM
Junior Member

Junior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior Member

Group: Forum Members
Last Login: 7/18/2008 3:28:01 PM
Posts: 15, Visits: 75
I know this is old, but in running msiexec as a Deploy Script is it a bad idea to use /Wait ?

/RUN /WAIT msiexec /i software.msi /qn

With the many instances of msiexec I am curious how deploy would know the task is really complete.

Thanks, as always.

Lumpy

Post #1429
Posted 2/15/2007 1:06:04 PM


Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Moderators
Last Login: 10/8/2008 1:15:23 PM
Posts: 655, Visits: 810
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.



New Boundary Technologies Support
support@newboundary.com

Post #1432
« Prev Topic | Next Topic »


Reading This TopicExpand / Collapse
Active Users: 0 (0 guests, 0 members, 0 anonymous members)
No members currently viewing this topic.
Forum Moderators: New Boundary Support

PermissionsExpand / Collapse

All times are GMT -6:00, Time now is 7:31am

Powered By InstantForum.NET v4.1.3 © 2008
Execution: 0.281. 9 queries. Compression Enabled.