Encapsulate subset creation into single call to script

• resource group
• storage accounts
• ...

resize existing vms to make room for CPU under 20 cpu limit

For each user should represent the permission profile of some one/role as vch ds. include what group membership and or permissions are required to accurately represent the vch ds role

• move step 2 to be step one

deployment walk through

High level walk explains how to deploy infrastructure components

what it does

• provide self contained step by step instructions required to deploy complete infrastructure into new resource group

what it doesn't

• Explain technical design decisions

How are data mapped to a hard drive? Fragmented?
What is an image?

• auto shut down schedule
• DSC modules

https://azure.microsoft.com/en-us/blog/announcing-auto-shutdown-for-vms-using-azure-resource-manager/

{
"apiVersion": "2016-05-15",
"type": "Microsoft.DevTestLab/schedules",
"name": "[variables('policyName')]",
"location": "[resourceGroup().location]",
"properties": {
"status":"Enabled",
"timeZoneId":"Pacific Standard Time",
"taskType":"ComputeVmShutdownTask",
"notificationSettings":{
"status":"Disabled",
"timeInMinutes":15,
"webhookUrl":null
},
"targetResourceId":"[variables('vmResourceId')]",
"dailyRecurrence":{
"time":"2000"
}}}

We need to understand how and if our MSDN subscription works with Azure in terms of BYOL VMs (click here for documentation)

general review of where code is at

copy vm deployment used for DC

include
vnet, subset, nsg, vm

follow Configuration.ini from SPDBSSPS008 installation

• create AD accounts
• create data disks
• modify configuration.ini for Azure

Network setup

2 servers in same vnet and subnet

• ADDCVm1a
• domainserver

All servers have:

• static public and private ips
• can ping one another (using ip not machine name)

release v1.0 (eden)

Release standalone of all PowerShell scripts, deployment templates, and template parameter files required to provision and configure blank environment

blank pre-SharePoint environment

• vnet
• subsets
• AD
• 4 factory default VMs (for SharePoint farm)
• 1 factory default VM (for data warehouse)

Install-ADDSForest docs for different ways
doc for powershell

for each on prem server:

• drive letter
• drive size

Add provision of a addc's subnet to it's pip, loadbalancer, vm etc deployment

depends on #42

makes it simpler to restore VMs from an backed up image see back up docs

There is a limit of 20 in a subscription and we've reached it.
I'd like to use a the cores for a DC VM.

Could we talk about deleting the ScoreCard VM?
It uses classic deployment and isn't in the main vnet so it would be able to communicate with the other VMs in the main vnet.

What are the minimal requirements in terms resources and their configurations to allow us to start experimenting with sharepoint installation?

• how many vms?
• is active directory needed before any meaningful experimentation?
• config exports from on premises?

• confirm with alan/jeff
• add email to azure subscription

Code as infrastructure

• use declarative json template (rather than imperative powershell script)
  • json functions to simplify resource naming by having child resource names be a function of parent names.
• plan to use Chef (#27) to handle post deploy configuration with desired state configuration

add code to existing Virtual Network.ps1 to include file share

flatten logic deployment logic

1. Permanent shared resources

• Vnet
• Storage

2. Disposable workload specific resources
   1 deployment per workload

• subnet
• nsg
• vms
• nic
• pip
• etc

What about configuration scripts (dsc)

Determine the difference between VM deployment options:

• SQL 2016 VM (BYOL) this option depends on issue: #4
• SQL 2016 VM (per minute billing)
• Empty VM with SQL 2016 manually installed
  • installation media from downloaded directly to VM from MSDN subscription
  • installation downloaded from Graham's Dropbox

in terms of:

• cost
• time and effort

• is Chef best option? What else is there.
• what are prereqs of infrastructure to use Chef?
• json template to network and vms then Chef for software installs? (sp, sql etc)

technical preview of on premises power bi

$env:<var_name>

To replicate the SSL enabled prod environment we need to have the Azure -SP SSL enabled as well.

This may require to get a new SSL certificate.

set user name to VM/role name

if all vms have have same user/pass combo it's hard to differentiate between users/accounts/AD entries.

to improve transparency and manageability of permissions set user name to VM/role name