How do I embed the 12-digit deployment code into the Windows streamer installer?


Update (4/13/2016) - This article has been replaced. The 3.0.6.x versions of Splashtop streamer support an easier way to achieve a similar result, and both Windows and Mac are now supported. Please refer to the new article "How do I embed the deployment code into the installer?"

Note 1: This idea is contributed by a fellow user ("Info") back in January 2015 in the user comments section of the support article How do I use Splashtop Business for remote support. It really works great. @Info, thank you!

Note 2: Embedding the code directly into the streamer as downloaded from Splashtop is on our development roadmap. We don't have a time frame yet.

Get your Splashtop deployable streamer and 12-digit code

Follow the instructions on this support article to create a deployment package.

From the deployment package, you will get two important components required in the later steps:

  1. Windows streamer installer
  2. 12-digit deployment code

Get InstallForge

Download InstallForge from

Create package in InstallForge

(closely based on the instructions written by "Info")

  1. Launch InstallForge
  2. In General > General > Program name field, type the program name that will be used to name the folder under \Program Files.
  3. In Setup > Files, click on "Add Files..."
    Select the Windows streamer installer that you downloaded earlier for your deployment package.
    Also uncheck the box that says "Allow user to change installation path" to eliminate an installation prompt.

  4. In Setup > Uninstall, check "Include Uninstaller" so the system will have an uninstaller to uninstall the wrapper created by InstallForge.
    (Splashtop Streamer still has its own, separate uninstaller.)

  5. In Setup > Commands, click on "Add..."
    Set "Type" to Execute application
    Set "Command" to <installpath> followed by file name of the Windows streamer installer (e.g. <installpath>\streamer.exe)
    Set "Parameters" to prevercheck /s /i dcode=your_code,confirm_d=0,autologin=1,hidewindow=1 (replace your_code with the 12-digit deployment code for your deployment package)

  6. Then just click on the Build icon

That's it!

Now you can send the resulting Windows installer to your users.

The user just needs to double click on the Windows installer to launch it. Then it's only 3 clicks for the whole process to complete (UAC, "Next" button, "Finish" button).

Have more questions? Submit a request


  • Avatar
    James Barrett

    This is great, to an extent.  The real drawback we have found is mass deployment with our RMM tool.  If there were a way to generate an MSI file with the code embedded, we could then push out to all of our managed servers and workstations.

  • Avatar


    Sorry but there is no such MSI file supported. Actually we suggest that you could use EXE file with your RMM tool to deploy, and you could refer to for more details.

  • Avatar

    This is a great way to do it. Found it really helpful.

    The only problem i've had is the installforge tool. i've built a few installers now for a few different deployments and it's reall inconsisent if it works or not. Some of the builds display an error "could not extract file! streamer.exe"

    I've contacted the installforge support, but I might try a different install tool.

    Just wanted to share in case anyone else has this issue (or finds a fix!)

  • Avatar

    We have found it useful too and have successfully deployed it on our support pages.

    However, the problem we have are various security warnings when users go to download and run the link to the InstallForge package. Has anyone else had this issue and has anyone overcome the warnings?


  • Avatar

    Hi Fred,

    As mentioned above I had some issues with install forge and got no help on the forum. Here is my alternative method which I think is easier:


    To create a self-installing package you can use a program that comes with windows called IExpress Wizard

    1. Open c:\windows\system32\iexpress.exe
    2. Create a new 'Self Extracting Directive' (SED) file
    3. Choose 'extract files and run an installation command'
    4. Give your package a name
    5. Choose if you want a confirmation prompt
    6. Choose if you want a licence agreement
    7. Add your streamer.exe file
    8. In 'install program' put: streamer.exe prevercheck /s /i dcode=YOUR_CODE_HERE,confirm_d=0,autologin=1,hidewindow=1
      leave post install command as 'none'
    9. Leave show window on 'default' (it will be hidden anyway by the streamer command above)
    10. Choose if you want a finish message
    11. Choose where you want to save the new EXE file and also if you want to hide the extraction progress animation
    12. Leave on 'only restart if needed'
    13. Choose where to save the SED file. This will help if you need to modify it later
    14. The new EXE will now be created

    These SED files are then text editable in notepad, which is handy!


  • Avatar


    Tried your method numerous times. Keep getting errors, even with short file names in and creating and storing short folder name - Remote- in the Root directory. Errors are:

    Unable to open the Report file 'C:\Remote~Splash.RPT


    Error creating Cabinet.

    Might try original method at top of this post.

  • Avatar

    @Martin, re: Brad.Lane

    The command fails because you need to run it with admin rights . Try it again & you'll be pleasantly surprised.

  • Avatar


    Tried and works, the IExpress does not like the long file name of the splash top streamer exe file, so I just renamed it to streamer.exe

    if the deployment has to be re-created , please make sure that you delete the old filles,  there are two files for the package, one exe and the other one is SED

    SED is the ini file


  • Avatar

    Dear Sir!

    I have 12 codes in windows.but now I can't installation new windows account .what's happen ?

  • Avatar


    What was the error? Did you read the new FAQ article with a new way to embed the deployment code?

    Splashtop team