5 Replies Latest reply: Aug 9, 2013 1:20 PM by Wei Chu RSS

How to change installation directory of plantronics sdk msi while installing?

meenakshi negi Newbie

Hi,

I am stuck in a problem.I want to install PlantronicsURE-SDK.msi in a user defined folder.But while running msi it gets installed in "C:\Program Files (x86)\Plantronics\" folder.I had tried to install msi by using script msiexec /qb /l* log.txt/i PlantronicsURE-SDK.msi  TARGETDIR="C:\MyTargetDirectory" .This script successfully runs and installs plantronics but not in the target directory location.Is this the desired behaviour of msi or I am lacking something.So,please suggest me some solution to this problem.Your quick response is highly appreciated.

 

Thanks

Meenakshi

  • Re: How to change installation directory of plantronics sdk msi while installing?
    Wei Chu Adventurer

    Hi Meenakshi,

     

    While the current msi installer does not support user defined install folder, what you can easily do is to manually copy and paste the entire 'PlantronicsSDK' folder to a destination directory you choose.

     

    However be aware that in most of the sample code the instructions assumed the SDK is installed in the default folder. So if you are trying out the sample code, you have to make the corresponding changes,

     

    Wei Chu

     


    • Re: How to change installation directory of plantronics sdk msi while installing?
      meenakshi negi Newbie

      Hi ,

      I am stuck in a problem.I am creating a msi using plantronics merge module msm.

      This msi installs Plantronics set up at Program files directory.Is this possible to change it or not?

      Currently I want to install my msi for all user type(admin and non admin).But it is not installing it for Non-Admin Users.

      Your quick responses will be highly appreciated.

       

      Thanks

      meenakshi

      • Re: How to change installation directory of plantronics sdk msi while installing?
        Wei Chu Adventurer

        Hi Meenakshi,

         

        If you are using the Plantronics msm file to install, the default install path is the "Program Files " folder. If you want the installation to go to a different folder, you can create your own customized install script to install in a destination folder of your choosing, However the complication is you also need to set the registry to the correct settings which is non trivial. The simplest solution in my opinion is still install to the default folder with Plantronics install process and copy what you need to a different destination folder.

         

        Because the installation requires writing into the "Program Files" folder and changing the registry, both steps require admin privilege.

         

        Wei

         


        • Re: How to change installation directory of plantronics sdk msi while installing?
          meenakshi negi Newbie

          Hi Wei,


          Thanks for response.My problem is actually to install plantronics set up for NON ADMIN user accounts.According to your response "The simplest solution in my opinion is still install to the default folder with Plantronics install process and copy what you need to a different destination folder."  means I need to install first in program files then copy.But in case of non admin user it will never install into "program files" ,then to copy is so far.


           

           

          Thanks

          Meenakshi

          • Re: How to change installation directory of plantronics sdk msi while installing?
            Wei Chu Adventurer

            Hi meenakshi,

             

            I am sorry to say there is no way to get around the admin privilege requirement for Spokes 2.x. Not only installing into “Program Files” folder requires admin privilege, but Spokes itself is based on a set of COM interfaces which requires setting the registry, again this requires admin privilege and there is no workaround.

             

            If you are thinking about distributing your software to non-admin end users, stay tuned for Spokes 3.0. There will be a native DLL solution without COM interfaces and no registry editing will be needed.

             

            Wei Chu