Hello, My image is nearly complete and I am having an issue with just one piece of software. The software I am having a problem with is the Citrix Web Client. I want this to install during the imaging process. I am using the following command to install the software from a command line task in OSD. I can't get it to work for the life of me. msiexec -i "\\UNC\XenAppWeb.msi" /qb- /l*v %temp%\SCCM_Citrix.log ALLUSERS=1 The error that I am receiving is the following. The task sequence execution engine failed executing the action (Citrix Web Client 11) in the group (Applications) with the error code 1603 Action output: =======================[ smsswd.exe ] ======================= PackageID = '' BaseVar = '', ContinueOnError='' SwdAction = '0001' Run command line under a user account Set command line: Run command line Working dir 'not set' Executing command line: Run command line Create a process under given user token Process completed with exit code 1603 Command line returned 1603. The operating system reported error 1603: Fatal error during installation. I have never been really able to get the msiexec command to work under a command line task in OSD. Apparantly I am doing something wrong but I can't really figure it out. Nonetheless, the software needs to run with the msiexec /i command. If it is run any other way, it gives a windows security warning... This is becomming overly frustrating. Any help would be greatly appreciated.

what does SCCM_Citrix.log say ? My step by step SCCM Guides I'm on Twitter > ncbrady

The log is never created. I guess I am just asking if msiexec can be called from a "Run Command Line" task in OSD? One more piece I left out is that I did select the "Run this step as the following account" checkbox and put in sufficient credentials so there is no problem accessing the UNC.

i normally kick off msiexec via VBS wrapper scripts, if you examine your SMSTS.log file does it reveal what went wrong ? where are you trying to install this software in the task sequence ? in Winpe stage or in the Windows stage ? My step by step SCCM Guides I'm on Twitter > ncbrady

This install occurs during the windows stage. I attached the failure lines from the SMSTS.log file below. Could you give me an example of a VBS wrapper script that you use to kick off msiexec? My scripting knowledge is limited. Start executing an instruciton. Instruction name: Citrix Web Client 11. Instruction pointer: 39 TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) Set a global environment variable _SMSTSCurrentActionName=Citrix Web Client 11 TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) Set a global environment variable _SMSTSNextInstructionPointer=39 TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) Set a local default variable SMSTSDisableWow64Redirection TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) Set a local default variable _SMSTSRunCommandLineAsUser TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) Set a local default variable SMSTSRunCommandLineUserName TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) Set a local default variable SMSTSRunCommandLineUserPassword TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) Set a global environment variable _SMSTSLogPath=C:\windows\system32\CCM\Logs\SMSTSLog TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) Expand a string: smsswd.exe /run: msiexec /i "\\UNC\XenAppWeb.msi" /qb- /l*v %temp%\SCCM_Citrix.log ALLUSERS=1 TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) Expand a string: TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) Command line for extension .exe is "%1" %* TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) Set command line: smsswd.exe /run: msiexec /i "\\UNC\XenAppWeb.msi" /qb- /l*v %temp%\SCCM_Citrix.log ALLUSERS=1 TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) Start executing the command line: smsswd.exe /run: msiexec /i "\\UNC\XenAppWeb.msi" /qb- /l*v %temp%\SCCM_Citrix.log ALLUSERS=1 TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) !--------------------------------------------------------------------------------------------! TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) Expand a string: WinPEandFullOS TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) Executing command line: smsswd.exe /run: msiexec /i "\\UNC\XenAppWeb.msi" /qb- /l*v %temp%\SCCM_Citrix.log ALLUSERS=1 TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) =======================[ smsswd.exe ] ======================= InstallSoftware 4/22/2011 3:17:29 PM 524 (0x020C) PackageID = '' InstallSoftware 4/22/2011 3:17:29 PM 524 (0x020C) BaseVar = '', ContinueOnError='' InstallSoftware 4/22/2011 3:17:29 PM 524 (0x020C) SwdAction = '0001' InstallSoftware 4/22/2011 3:17:29 PM 524 (0x020C) Run command line under a user account InstallSoftware 4/22/2011 3:17:30 PM 524 (0x020C) Set command line: Run command line InstallSoftware 4/22/2011 3:17:30 PM 524 (0x020C) Working dir 'not set' InstallSoftware 4/22/2011 3:17:30 PM 524 (0x020C) Executing command line: Run command line InstallSoftware 4/22/2011 3:17:30 PM 524 (0x020C) Create a process under given user token InstallSoftware 4/22/2011 3:17:30 PM 524 (0x020C) Process completed with exit code 1603 InstallSoftware 4/22/2011 3:17:35 PM 524 (0x020C) Command line returned 1603 InstallSoftware 4/22/2011 3:17:35 PM 524 (0x020C) Process completed with exit code 1603 TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) !--------------------------------------------------------------------------------------------! TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) Failed to run the action: Citrix Web Client 11. Fatal error during installation. (Error: 00000643; Source: Windows) TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) Sending status message . . . TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) Send a task execution status message SMS_TSExecution_ActionFailError TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) MP server CORRECTSERVERNAME.DOMAIN.LOCAL and port 80. SSL=false. CRL=false. TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) Site code: CM1 TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) Client machine name: MACHINENAME TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) Client Identity: GUID:c1cc6eb3-cbcc-4bde-b3b8-b7e879530651 TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) Advertisement ID: CM1200A8 TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) Package ID: CM10004D TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) Sending StatusMessage TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) Formatted header: TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) <Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>ECBF8754-7BE1-4A33-B3DE-23F4F071311D</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2011-04-22T20:17:45Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="2972"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg> TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) CLibSMSMessageWinHttpTransport::Send: URL: CORRECTSERVERNAME.DOMAIN.LOCAL:80 CCM_POST /ccm_system/request TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) The request has succeeded. 200 OK TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) Set a global environment variable _SMSTSLastActionRetCode=1603 TSManager 4/22/2011 3:17:46 PM 3176 (0x0C68) Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 4/22/2011 3:17:46 PM 3176 (0x0C68) Clear local default environment TSManager 4/22/2011 3:17:46 PM 3176 (0x0C68) The execution engine ignored the failure of the action (Citrix Web Client 11) and continues execution TSManager 4/22/2011 3:17:46 PM 3176 (0x0C68)

This install occurs during the windows stage. I attached the failure lines from the SMSTS.log file below. Could you give me an example of a VBS wrapper script that you use to kick off msiexec? My scripting knowledge is limited. Start executing an instruciton. Instruction name: Citrix Web Client 11. Instruction pointer: 39 TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) Set a global environment variable _SMSTSCurrentActionName=Citrix Web Client 11 TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) Set a global environment variable _SMSTSNextInstructionPointer=39 TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) Set a local default variable SMSTSDisableWow64Redirection TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) Set a local default variable _SMSTSRunCommandLineAsUser TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) Set a local default variable SMSTSRunCommandLineUserName TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) Set a local default variable SMSTSRunCommandLineUserPassword TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) Set a global environment variable _SMSTSLogPath=C:\windows\system32\CCM\Logs\SMSTSLog TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) Expand a string: smsswd.exe /run: msiexec /i "\\UNC\XenAppWeb.msi" /qb- /l*v %temp%\SCCM_Citrix.log ALLUSERS=1 TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) Expand a string: TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) Command line for extension .exe is "%1" %* TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) Set command line: smsswd.exe /run: msiexec /i "\\UNC\XenAppWeb.msi" /qb- /l*v %temp%\SCCM_Citrix.log ALLUSERS=1 TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) Start executing the command line: smsswd.exe /run: msiexec /i "\\UNC\XenAppWeb.msi" /qb- /l*v %temp%\SCCM_Citrix.log ALLUSERS=1 TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) !--------------------------------------------------------------------------------------------! TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) Expand a string: WinPEandFullOS TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) Executing command line: smsswd.exe /run: msiexec /i "\\UNC\XenAppWeb.msi" /qb- /l*v %temp%\SCCM_Citrix.log ALLUSERS=1 TSManager 4/22/2011 3:17:29 PM 3176 (0x0C68) =======================[ smsswd.exe ] ======================= InstallSoftware 4/22/2011 3:17:29 PM 524 (0x020C) PackageID = '' InstallSoftware 4/22/2011 3:17:29 PM 524 (0x020C) BaseVar = '', ContinueOnError='' InstallSoftware 4/22/2011 3:17:29 PM 524 (0x020C) SwdAction = '0001' InstallSoftware 4/22/2011 3:17:29 PM 524 (0x020C) Run command line under a user account InstallSoftware 4/22/2011 3:17:30 PM 524 (0x020C) Set command line: Run command line InstallSoftware 4/22/2011 3:17:30 PM 524 (0x020C) Working dir 'not set' InstallSoftware 4/22/2011 3:17:30 PM 524 (0x020C) Executing command line: Run command line InstallSoftware 4/22/2011 3:17:30 PM 524 (0x020C) Create a process under given user token InstallSoftware 4/22/2011 3:17:30 PM 524 (0x020C) Process completed with exit code 1603 InstallSoftware 4/22/2011 3:17:35 PM 524 (0x020C) Command line returned 1603 InstallSoftware 4/22/2011 3:17:35 PM 524 (0x020C) Process completed with exit code 1603 TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) !--------------------------------------------------------------------------------------------! TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) Failed to run the action: Citrix Web Client 11. Fatal error during installation. (Error: 00000643; Source: Windows) TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) Sending status message . . . TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) Send a task execution status message SMS_TSExecution_ActionFailError TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) MP server CORRECTSERVERNAME.DOMAIN.LOCAL and port 80. SSL=false. CRL=false. TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) Site code: CM1 TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) Client machine name: MACHINENAME TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) Client Identity: GUID:c1cc6eb3-cbcc-4bde-b3b8-b7e879530651 TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) Advertisement ID: CM1200A8 TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) Package ID: CM10004D TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) Sending StatusMessage TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) Formatted header: TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) <Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>ECBF8754-7BE1-4A33-B3DE-23F4F071311D</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2011-04-22T20:17:45Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="2972"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg> TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) CLibSMSMessageWinHttpTransport::Send: URL: CORRECTSERVERNAME.DOMAIN.LOCAL:80 CCM_POST /ccm_system/request TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) The request has succeeded. 200 OK TSManager 4/22/2011 3:17:45 PM 3176 (0x0C68) Set a global environment variable _SMSTSLastActionRetCode=1603 TSManager 4/22/2011 3:17:46 PM 3176 (0x0C68) Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 4/22/2011 3:17:46 PM 3176 (0x0C68) Clear local default environment TSManager 4/22/2011 3:17:46 PM 3176 (0x0C68) The execution engine ignored the failure of the action (Citrix Web Client 11) and continues execution TSManager 4/22/2011 3:17:46 PM 3176 (0x0C68)

Why are you running this from a UNC? The whole point of software distribution in ConfigMgr is to readily make source files available in a distributed environment via the Distribution Point model without having to micro-manage locations or permissions. Not using a package for an install is anti-ConfigMgr. Note that your problem above most liekly stems from the fact the the local computer account does not have permissions to the UNC path you specified. The local computer account is used because Task Sequences use the local SYSTEm account to run; the local SYSTEM account's identity on the network is that of the AD computer account. But, asI said, putting this in a package makes this moot as ConfigMgr takes care of these details for you when it's in a package. Also, why use a command-line task for this? Why not just import the MSI into ConfigMgr and let it build the software Distribution package and programs for you? Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Why are you running this from a UNC? The whole point of software distribution in ConfigMgr is to readily make source files available in a distributed environment via the Distribution Point model without having to micro-manage locations or permissions. Not using a package for an install is anti-ConfigMgr. Note that your problem above most liekly stems from the fact the the local computer account does not have permissions to the UNC path you specified. The local computer account is used because Task Sequences use the local SYSTEm account to run; the local SYSTEM account's identity on the network is that of the AD computer account. But, asI said, putting this in a package makes this moot as ConfigMgr takes care of these details for you when it's in a package. Also, why use a command-line task for this? Why not just import the MSI into ConfigMgr and let it build the software Distribution package and programs for you? Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Why are you running this from a UNC? The whole point of software distribution in ConfigMgr is to readily make source files available in a distributed environment via the Distribution Point model without having to micro-manage locations or permissions. Not using a package for an install is anti-ConfigMgr. Note that your problem above most liekly stems from the fact the the local computer account does not have permissions to the UNC path you specified. The local computer account is used because Task Sequences use the local SYSTEm account to run; the local SYSTEM account's identity on the network is that of the AD computer account. But, asI said, putting this in a package makes this moot as ConfigMgr takes care of these details for you when it's in a package. Also, why use a command-line task for this? Why not just import the MSI into ConfigMgr and let it build the software Distribution package and programs for you? Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys I actually use packages for all of the other installs in my task sequences except for this one. I need it to run with the exact command that i entered above. And I assumed that using the "Run this step as the following account" dialog box in junction with a domain account with sufficient privileges would be ok. This msi will not run correctly as a package. I have tried numerous times. It will only install silently and without user interaction if I use the msiexec /i. Lets say I create a package that points to the msi and create a program with a command line saying the following... msiexec /i XenAppWeb.msi /qb- ALLUSERS=1 This should theoretically work right? I am only really asking how to use the msiexec /i command with and OSD task sequence.

That will work. Just create a new package (or import the MSI into ConfigMgr) and either use the pre-created install program (if importing the MSI) or create your own new program with the exact install logic you require. If you want more information about how to use msiexec, open up a command prompt and type msiexec /? which will show you all the switches you can use. /qb will not be totally silent - it stands for Basic which will show a progress bar. /qn or /quiet will be silent. But definitely, create a package - there's no reason to use the command line task for this.