AzureStack-QuickStart-Templ.../anti-malware-ext-win
Deepa Thomas 9392d98c0c Fix AzureStack QuickStartTemplates' Storage account resources to use … (#428)
* Fix AzureStack QuickStartTemplates' Storage account resources to use sku and kind - round2

* Fix AzureStack QuickStartTemplates' Storage account resources to use sku and kind - round3

* Proxy resources don't need to specify api version anymore as the bug is fixed, so remove the api version
2019-04-08 16:25:48 -07:00
..
README.md Updating to Development Kit references (#268) 2017-07-31 11:36:49 -07:00
azuredeploy.json Fix AzureStack QuickStartTemplates' Storage account resources to use … (#428) 2019-04-08 16:25:48 -07:00
azuredeploy.parameters.json Vikasnav patch 1 (#189) 2016-11-02 12:58:59 -07:00
metadata.json Adding 2 templates that use managed disks and updating the updated date (#399) 2018-11-07 10:45:44 -08:00

README.md

A template that creates a simple Windows VM with Anti-Malware extension enabled with the following configuration:

Exclusions: none Realtime protection enabled: true Scheduled scan settings: Scan type: Quick Day: 7 (Saturday) Time: 120 (measured as minutes after midnight = 2AM)

Prerequisites

None

Parameters

  • adminUsername: Username for the Virtual Machine local administrator.
  • adminPassword: Password for the Virtual Machine local administrator.

Notes

The Anti-Malware extension disables the Anti-Malware application from opening (but the service is configured). If access to the application is needed run the following commands: cd C:/program files/microsoft security client configsecuritypolicy cleanuppolicy.xml

Deployment steps

  1. Deploy to azure stack portal using custom deployment.
  2. Deploy through Visual Studio using azuredeploy.json and azuredeploy.parameters.json
  3. Deploy the solution from PowerShell with the following PowerShell script
## Specify your AzureAD Tenant in a variable. 
# If you know the prefix of your <prefix>.onmicrosoft.com AzureAD account use option 1)
# If you do not know the prefix of your <prefix>.onmicrosoft.com AzureAD account use option 2)

# Option 1) If you know the prefix of your <prefix>.onmicrosoft.com AzureAD namespace.
# You need to set that in the $AadTenantId varibale (e.g. contoso.onmicrosoft.com).
    $AadTenantId = "contoso"

# Option 2) If you don't know the prefix of your AzureAD namespace, run the following cmdlets. 
# Validate with the Azure AD credentials you also use to sign in as a tenant to Microsoft Azure Stack Development Kit.
    $AadTenant = Login-AzureRmAccount
    $AadTenantId = $AadTenant.Context.Tenant.TenantId

## Configure the environment with the Add-AzureRmEnvironment cmdlt
    Add-AzureRmEnvironment -Name 'Azure Stack' `
        -ActiveDirectoryEndpoint ("https://login.windows.net/$AadTenantId/") `
        -ActiveDirectoryServiceEndpointResourceId "https://azurestack.local-api/"`
        -ResourceManagerEndpoint ("https://api.azurestack.local/") `
        -GalleryEndpoint ("https://gallery.azurestack.local/") `
        -GraphEndpoint "https://graph.windows.net/"

## Authenticate a user to the environment (you will be prompted during authentication)
    $privateEnv = Get-AzureRmEnvironment 'Azure Stack'
    $privateAzure = Add-AzureRmAccount -Environment $privateEnv -Verbose
    Select-AzureRmProfile -Profile $privateAzure

## Select an existing subscription where the deployment will take place
    Get-AzureRmSubscription -SubscriptionName "SUBSCRIPTION_NAME"  | Select-AzureRmSubscription

# Set Deployment Variables
$myNum = "001" #Modify this per deployment
$RGName = "myRG$myNum"
$myLocation = "local"

$templateFile= "azuredeploy.json"
$templateParameterFile= "azuredeploy.parameters.json"

# Create Resource Group for Template Deployment
New-AzureRmResourceGroup -Name $RGName -Location $myLocation

# Deploy Template 
New-AzureRmResourceGroupDeployment `
    -ResourceGroupName $RGName `
    -TemplateFile $templateFile `
	-TemplateParameterFile $templateParameterFile