Introduction
Terraform* and PowerShell* scripts for automated creation of an Intel® EMA instance and all required back-end services
Available Downloads
- Windows Server 2022 family*, Windows Server 2019 family*, Windows Server 2016 family*
- Size: 27.4 KB
- SHA256: 60737C57B6FE2C0518FCE29F8612331D99697F0F706E98BC3B81FC61E6455617
Detailed Description
Detailed Description
The following template files are intended for advanced users to be able to customize their virtual machine and/or the default configuration of the Intel EMA instance locally or in either the Amazon*, Google*, or Microsoft Azure* cloud services.
These scripts may be modified for personal use. Manual changes to the Terraform* scripts allow you to control the different configurations for your virtual machine, such as the VM selection, disk size, SQL license, etc.
Manual changes to the PowerShell* scripts will allow you to select different cloud providers and the default configuration of your Intel® EMA instance.
Modifications are made at your own risk. Please see the included software license for usage limitations.
You are responsible for all costs and maintenance of cloud services incurred.
Users also have the option to use the template below for creating a Virtual Machine in Microsoft Azure for Intel® EMA environment.
Detailed Description
Available downloads
Download Intel® Endpoint Management Assistant (Intel® EMA) Cloud Start Tool for Azure* 2.0 - Quick-Start Guide.pdf.
Applies to:
- Windows® 10, 64-bit*, Windows 10, 32-bit, Windows Server 2019* family, Windows 10
- Size: 544.2 KB
- SHA1: a97e71148b9fa9edf1cef2e81f19b843d7903db7
Detailed description
The links below will create a Virtual Machine in Microsoft Azure* with all necessary background services and Intel EMA automatically installed with a default configuration.
The estimated cost below is based on a Hybrid Benefit (Windows*) License.
Allow up to 30 minutes for the build operation to complete.
You are responsible for all costs and maintenance of Azure services.
Advanced users may want to customize the setup scripts for their Azure environment: The source package is available for download here.
Select the link that best fits your needs
Deploy Intel® EMA for a Single-Server Small-Scale Evaluation (recommended for up to 500 endpoints)
Click here (This is an external link to Microsoft Azure.)
Uses Azure template “Standard_D2s_v3” [2CPU 8GB RAM] with Windows 2019 and SQLExpress*: Estimated Microsoft Azure cost ~$80/month
Deploy Intel® EMA for a Single-Server Medium-Scale Evaluation (recommended for up to 5000 endpoints)
Click here (This is an external link to Microsoft Azure.)
Uses Azure template “Standard_D4s_v3” [4CPU 16GB RAM] with Windows 2019 and SQLExpress: Estimated Microsoft Azure cost ~$170/month
Deploy Intel® EMA for Large-Scale Evaluation (advanced template that supports scalable deployments)
Click here (This is an external link to Microsoft Azure.)
Choose between “Standard_D2s_v3” [2CPU 8GB RAM] and “Standard_D4s_v3” [4CPU 16GB RAM] with Windows 2019 and Azure SQL Server: Estimated Microsoft Azure cost ~$95 - ~$200/month (varies based on selected options)
The Intel® Endpoint Management Assistant (Intel® EMA) Cloud Start Tool for Azure* Download Page Link
Other useful links to get started with Intel® Endpoint Management Assistant (Intel® EMA)
Intel® Endpoint Management Assistant (Intel® EMA) Quick Start Guide
Intel® Endpoint Management Assistant (Intel® EMA) Single Server Installation and Maintenance Guide
Intel EMA Remote Management Quick-Start Video Guide
The content on this page is a combination of human and computer translation of the original, English-language content. This content is provided for your convenience and for general information only and should not be relied upon as complete or accurate. If there is any contradiction between the English-language version of this page and the translation, the English-language version will govern and control. View the English-language version of this page.
Disclaimers1
Product and Performance Information
Intel is in the process of removing non-inclusive language from our current documentation, user interfaces, and code. Please note that retroactive changes are not always possible, and some non-inclusive language may remain in older documentation, user interfaces, and code.