locked
Software package RRS feed

  • Question

  • I am trying to install Office Communicator on Windows XP environment. I used creat and deploy a new software package menu.

    This Office Communicator has to installers as follow:

    Communicator.MSI

    Communicator.MSP

     

    When I check the deployment ststus it shows as follow:

    installed:0

     


    Deep Kumar
    Friday, January 28, 2011 6:25 PM

Answers

  • are you running communicator 2007R2?  I used this command line for our windows deployment which works very well.  You can do the same by calling msiexec in your software package as opposed to the msi itself.  example: select msiexec.exe as your setup package, then the additional installation parameters would be /i \\server\share\communicator.msi /qn remember to put quotes around the path if there are spaces in it.  some installers don't like specifying the /qn, if it fails (which it shouldn't) leave the /qn off and see if it installs silently anyway.

    Here is good documentation along with some examples of how manipulate the msi installer behavior.  http://msdn.microsoft.com/en-us/library/aa367988%28v=vs.85%29.aspx


    Ok, so I changed my name...you can still call me Tom if you like. It's a...jump...to conclusions...mat.
    My Blog Site: http://tmagnuson.wordpress.com
    • Marked as answer by Yog Li Friday, February 4, 2011 9:28 AM
    Monday, January 31, 2011 2:42 PM

All replies

  • Hello Deep,

    For MSI application, if the application is already instaled on the client, then it will not be downloaded and offered from the SCE server.

    Is there an instance of Office Communicator installed on the Windows XP environment? If not, please run the command "wuauclt /detectnow" and then check the "WindowsUpdate.log" afte about 10 minutes to see if any error message was logged.

    Thanks,


    Yog Li -- Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, January 31, 2011 8:40 AM
  • are you running communicator 2007R2?  I used this command line for our windows deployment which works very well.  You can do the same by calling msiexec in your software package as opposed to the msi itself.  example: select msiexec.exe as your setup package, then the additional installation parameters would be /i \\server\share\communicator.msi /qn remember to put quotes around the path if there are spaces in it.  some installers don't like specifying the /qn, if it fails (which it shouldn't) leave the /qn off and see if it installs silently anyway.

    Here is good documentation along with some examples of how manipulate the msi installer behavior.  http://msdn.microsoft.com/en-us/library/aa367988%28v=vs.85%29.aspx


    Ok, so I changed my name...you can still call me Tom if you like. It's a...jump...to conclusions...mat.
    My Blog Site: http://tmagnuson.wordpress.com
    • Marked as answer by Yog Li Friday, February 4, 2011 9:28 AM
    Monday, January 31, 2011 2:42 PM
  • Okay Tom,

    Here is what I have:

    \\OCS\OCS_2007_R2_install\Communicator.msi

    \\OCS\OCS_2007_R2_install\service pack for OCS_2007_R2\Communicator.msp

     

    So now how and where I change the msiexec and sekect msiexec.exe?

    Please help me with this what to type on:

    Package Setup file:

    Package Name:

    Package Description:

     

    Thanks


    Deep Kumar
    Monday, January 31, 2011 9:27 PM
  • Hello Deep,

    For your reference:

    • Package Setup file: msiexec.exe
    • Package Name: Anything which can help you to identify this software package.
    • Package Description: Anything which can help you to identify this software package.
    • Installation Properties: /i \\server\share\communicator.msi /qn

    Make sure to replace the letters in italic type with your own scenarios.

    Thanks,


    Yog Li -- Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Wednesday, February 2, 2011 6:26 AM
  • I can't tell if your paths have spaces in them or not.  If they do, put the whole path in quotes.  You can also take a COPY of msiexec.exe  and put it out to the network share if the action account has problems gaining access to %windir%\system32
    Ok, so I changed my name...you can still call me Tom if you like. It's a...jump...to conclusions...mat.
    My Blog Site: http://tmagnuson.wordpress.com
    Wednesday, February 2, 2011 3:07 PM