![]() ![]() If you want to add some custom logic to your EXE installer, create a script and place it in the same folder.Any regular “dumb” files (that aren’t installers).Make sure to select packages that perform per-machine installation per-user installation isn’t supported by Action1. For custom transform (*.MST) files, consider using the ORCA tool. MSI with MST (transform) files that customize your installation, for example, add a license code or create a preconfigured profile.EXE and other files such as configurations.What kind of ZIP packages can you create? This way Internet traffic usage is minimized and download reliability is accomplished. Each endpoint would download approximately 20 MB and share it with other managed endpoint endpoints. Let’s say you have 100 endpoints and need to download a 2 GB package. ![]() Managed endpoints will download the package data using our cloud file-sharing technology, which works by sharing chunks of data across multiple computers. Once this package is uploaded to Action1 Cloud, you will be able to deploy it as any regular package. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |