- #Royal ts connect to console how to
- #Royal ts connect to console install
- #Royal ts connect to console code
This file activates your Royal TS application. The lic folder contains the actual license file. Msiexec /i "\\\Sources\Applications\RoyalTS\RoyalTSInstaller_6.61216.msi" /qĬopy "\\\Sources\Applications\RoyalTS\lic\*.*" "C:\Program Files (x86)\\Royal TS V3\" /y The destination folder is C:\Program Files (x86)\\Royal TS V3\. The next command copies the license file from sources folder to destination computer. The installer is a msi file and it’s easy to deploy.
#Royal ts connect to console install
The lic batch file contains Royal TS install command.
Royal TS installer is the msi installer file. #Royal ts connect to console code
It also contains the code to copy license file to destination computer.
lic batch file contains the code to install Royal TS. lic folder contains the actual license file. In the below screenshot, there are four files. How to Deploy Royal TS using SCCM (Including License File)īefore we deploy Royal TS using SCCM, let’s look at some of the files. And yes that worked and we will use the same method in this post. I thought maybe I could use a batch file to copy the license file to a folder. To activate Royal TS, the xml file (license file) needs to be copied to folder where Royal TS executable is present. This looked tedious to me and I believe this can be achieved using PowerShell. Now this is not easy because SCCM has to find out current user account. If you look at point 1, the license file has to be copied over to %appdata%\code4ward folder. Copy and deploy the *.xml file to the install directory of Royal TS (where RTS*App.exe/RoyalTS.exe is located). Copy and deploy the *.xml file to the %appdata%\code4ward using a log on script for each user. I had to do some research about this and I came with this post.Īs per this Royal TS article, the app can be licensed in two ways. But what about deploying license file along with Royal TS app using SCCM ?. Deploying msi file using SCCM is very easy. When you download Royal TS app, it’s an msi file. However this was not the case with Royal TS app. That was easy because if you have the license file in same folder along with executable, winrar uses that license. While deploying winrar, I had to ensure winrar is also licensed post deployment. I could remember my post on deploying winrar using SCCM. However he also mentioned that he wanted to deploy the license along with app using SCCM. Since I already use Royal TS, I knew about the deployment. #Royal ts connect to console how to
Few days ago one of my colleague asked me how to deploy Royal TS using SCCM.
0 kommentar(er)
