Introduction
Template for creating a Virtual Machine in Microsoft Azure for Intel® EMA environment.
Detailed Description
Available Downloads
Download Intel EMA CloudStart 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.
Please 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 wish 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)
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.