Silent IIS UrlRewrite, ARR and FARM provisioning by #PowerShell

Recently, I had the task to run several fitnesse instances in on the single AWS EC2 instance. The requirement was what each fitnesse instance should be accessible trough port 80 (HTTP). IIS as reverse proxy came to the rescue. But there were one more requirement – IIS Reverse Proxy configuration should be automated. Here >> konstantinvlasenko/IIS

Silent install IIS UrlRewrite and ARR by #PowerShell

Create-Item c:/msi -Type Directory Invoke-WebRequest ‘http://download.microsoft.com/download/C/F/F/CFF3A0B8-99D4-41A2-AE1A-496C08BEB904/WebPlatformInstaller_amd64_en-US.msi’ -OutFile c:/msi/WebPlatformInstaller_amd64_en-US.msi Start-Process ‘c:/msi/WebPlatformInstaller_amd64_en-US.msi’ ‘/qn’ -PassThru | Wait-Process cd ‘C:/Program Files/Microsoft/Web Platform Installer’; .\WebpiCmd.exe /Install /Products:’UrlRewrite2,ARRv3_0′ /AcceptEULA /Log:c:/msi/WebpiCmd.log

Change local administrator password by command line

([ADSI]”WinNT://localhost/Administrator, user”).psbase.Invoke(“SetPassword”, ‘{PASSWORD}’)

#PowerShell script to wait while any MSI process is running

while($true) { try { $mutex = [System.Threading.Mutex]::OpenExisting(‘Global\_MSIExecute’) $mutex = $null Sleep 10 ‘MSI running…’ | Out-Default } catch [System.Threading.WaitHandleCannotBeOpenedException] { # Mutex not found; MSI isn’t running break } }

Disable the option to check for server certificate revocation on Internet Explorer

We are doing an extensive acceptance testing against SharePoint Online by using PowerSlim (PowerShell). Unfortunately sometimes our automated tests are blocked by popup below: As we truly believe that our DNS is not spoiled an we know exactly what we are looking for (pre-created data) – this verification doesn’t make any sense for us. So

#PowerShell: Register AWS EC2 instances in Amazon Route53 (new way)

Amazon Route 53 is a highly available and scalable Domain Name System (DNS) web service. Just in case – Amazon EC2 I use this script https://github.com/konstantinvlasenko/cloud/blob/master/Register-CNAME.ps1 to provide meaningful names for them. Simple usage: $config = @{ DomainName = ‘mylab.com’ } $name = “www.$($config.DomainName)” # get instances $instance = (Get-EC2Instance $InstanceId).RunningInstance # update R53 .\Register-CNAME.ps1

Find region from within EC2 instance by #PowerShell

(ConvertFrom-Json (Invoke-WebRequest -Uri http://169.254.169.254/latest/dynamic/instance-identity/document -UseBasicParsing).Content).region

AWS EC2 Windows current spot price by PowerShell

Get-EC2SpotPriceHistory -ProductDescription Windows -InstanceType m1.large, cc1.4xlarge -s (Get-Date -format s) | sort SpotPrice | format-list

PowerShell; SharePoint 2010: Set Alternate Access Mapping

I need to set Alternate Access Mapping remotely as part of my automation. I can’t find how to specify PowerShell version for Invoke-Command CMDlet. So I decided to use this workaround: Invoke-Command -computer sp2010.vlasenko.org -script { $command = “Add-PSSnapin Microsoft.SharePoint.PowerShell; New-SPAlternateURL ‘http://vlasenko.nmsp.org’ -Zone ‘Internet’ -WebApplication ‘SharePoint – 80′” PowerShell -v 2 -Command “& { $command

PowerShell: Register AWS EC2 instances in AWS R53

UPDATE: #PowerShell: Register AWS EC2 instances in Amazon Route 53 (new way) Suppose you have a variable $lab: $lab = @{id=’ami-7300091a’; name=’1.dc.mylab.com’; type=’m1.small’; maxbid=’0.02′; CNAME=’ec2-54-000-117-7.compute-1.amazonaws.com’}, @{id=’ami-49000e20′; name=’1.sql.mylab.com’; type=’cc1.4xlarge’; maxbid=’0.09′; CNAME=’ec2-184-73-000-182.compute-1.amazonaws.com’} Let’s update AWS R53 entries by using instances CNAME: $zoneId = ‘ZB00X5FI00YBB’ foreach($computer in $lab){ “[$($computer.name)]`t[R53] update… ” | Out-Default $result = Get-R53ResourceRecordSet -HostedZoneId $zoneId -StartRecordName $computer.name -MaxItems 1