Thursday, July 21, 2016

Script for updating URLrewrite-rules

In these days urlrewrite might not be the first choice for using but I had a situationen where i needed to be applied.
This offered an oppertunity to create a script to automate the addition of custom rules sets for a specific file.
And I got to fiddle with xml-manipulation which is also fun.

This script reads an csv for inputaddress and ruleTemplate file
csv – addresses.csv


<?xml version="1.0" encoding="UTF-8"?>
        <rule name="#RuleName#_RevProxyInbound" enabled="true" stopProcessing="true">
                    <match url="(.*)" />
                    <conditions logicalGrouping="MatchAll" trackAllCaptures="false">
                        <add input="{HTTP_HOST}" pattern="#target#" />
                        <set name="HTTP_ACCEPT_ENCODING" value="" />
                    <action type="Rewrite" url="{R:1}" />
                <rule name="#RuleName#_Links_To_Pages" preCondition="ResponseIsHtml" enabled="true">
                    <match filterByTags="A" pattern="(.*)/#destination#/(.*).aspx" />
                    <conditions logicalGrouping="MatchAll" trackAllCaptures="true" />
                    <action type="Rewrite" value="http://#target#/{R:2}.aspx" />
                <rule name="#RuleName#_Response_Location_querystring" preCondition="ResponseIsHtml" enabled="true">
                    <match serverVariable="RESPONSE_LOCATION" pattern="*)" />
                    <conditions logicalGrouping="MatchAll" trackAllCaptures="true">
            <add input="{URL}" negate="true" pattern="\.axd$" />
                    <action type="Rewrite" value="{R:1}" />
Powershellscript, this script reads web.config from designated place makes a copy to $workingDir where updates are applied to file in $workingDir. This a pretty specific script, for example outboundRules are applied before <precondition>-tagg, but haven’t really experimented what happens if the preconditions aren’t there for example. So better to use as inspiration rather than copy paste. Also rewriteRules will need to be adjusted for your particuliar scenarios. Matching for rules to change are made with replace() towards #rulename#, #destination and #target# cause this was easier for this scenario.

#Desc: Adds rewrite rules for washers, only adds if rules doesn't exist.

$sourceFileRewrite = "C:\Eriks\Powershell\Prod_rewriteUrlsUpdate\From\rewrite\web.config"
$scriptPath = $(split-path -Parent $myinvocation.MyCommand.Definition)
$AddressUrlFile = "$($scriptPath)\Addresses.csv"
$workingDir = "$($scriptPath)\UpdatedFiles"
$templateRuleFile = "$($scriptPath)\rewriteTemplate.xml"
#step1 copy files
try {
    $fileRewrite = "$($workingDir)\$(($sourceFileRewrite.Split('\'))[-2])\$(($sourceFileRewrite.Split('\'))[-1])"
    if ((Test-Path -Pathtype container -Path $($fileRewrite.TrimEnd("web.config"))) -eq $false)
        New-Item -ItemType directory -Force -Path $($fileRewrite.TrimEnd("web.config")) |Out-Null
    Copy-Item -Path $sourceFileRewrite -Destination $fileRewrite   
    write-output "Copied to $($fileRewrite) successfully"
catch {}
#step2 read files
[xml]$xmlRewriteInput = (Get-Content $fileRewrite -ReadCount -1)
$AddressCollection = import-csv -Delimiter "," -Path $AddressUrlFile -Encoding UTF8
$templateRuleStatic = (Get-Content $templateRuleFile -raw)
$rewriteNodes = $xmlRewriteInput.configuration.'system.webServer'
foreach ($address in $AddressCollection ) {
    write-output "Processing $($address.rulename)..."
    #step3 update files   
    $tempTemplate = $templateRuleStatic.Replace("#RuleName#",$address.ruleName).Replace("#destination#",$address.destination).replace("#target#",$
    [xml]$tempXMLTemplate = $tempTemplate   
    foreach ($node in $tempXMLTemplate.configuration.'system.webServer'.rewrite.rules.rule) {
        #check if exists
        if ($ -notcontains $ {
            $extractedInbound = $xmlRewriteInput.ImportNode(($node),$true)     
            $xmlRewriteInput.configuration.'system.webserver'.rewrite.rules.AppendChild($extractedInbound)  |Out-Null
        else { write-warning "Rule $($ already exists in file! Skipping..." }
    foreach ($secondNode in $tempXMLTemplate.configuration.'system.webServer'.rewrite.outboundRules.rule) {
        if ($ -notcontains $ {
            $extractedInbound = $xmlRewriteInput.ImportNode(($secondNode),$true)                     
            $before = $xmlrewriteInput.configuration.'system.webserver'.rewrite.outboundrules.preconditions
            $xmlRewriteInput.configuration.'system.webserver'.rewrite.outboundRules.InsertBefore($extractedInbound,$before) |out-null          
        else { write-warning "Rule $($ already exists in file! Skipping..." }
    try {
        write-output "Updated file saved to $fileRewrite"
    catch {}

Monday, July 18, 2016

Finding duplicate content types

Got to a chance to build a script for finding content type duplicates in a Site Collection

#Description:Find duplicate content types in sitecollection

Add-PSSnapin microsoft.sharepoint.powershell

$siteURL = ""
$site = get-spsite $siteURL
$object = @()

foreach ($newWeb in $site.AllWebs) {
    foreach ($cType in $newWeb.contentTypes) {
        $tempObj = new-object PSObject -Property @{webURL=$newWeb.Url; CTName=$cType.Name; CTid=$cType.Id}
        $object += $tempObj
#sort out duplicates
$duplicates = $object |Group-Object ctid |Where-Object {$_.count -gt 1} |select -ExpandProperty group

write-output "Found $($object.count) content types in $siteURL"
write-output "Total duplicates: $($duplicates.count)"

Monday, March 14, 2016

Urlrewrite and sharepoint 2013

I some trouble recently getting urlrewrite to play along with SP2013 and IIS 8.
HostNamedSiteCollection wasn’t doable for a lot of other reasons.
Scenario: Using urlrewrites to handle vanityurls for site collections in SP2007. When migrating to SP2013 these rules don’t work at all.

Symptoms: image

  • With outboundrules activated nothing works for webapplication. (Website cannot display the page) 
  • Always lands on top site collection, rewrite dont work.

A combination of a few fixes

  • Install patch kb2749660 to fix outboundrules
  • Add registry key ("HKLM:\Software\Microsoft\InetStp\Rewrite\" (Dword) LogRewrittenUrlEnabled=0)
  • Deactivate Static Compression on IIS-site
  • Add rewrite rule like {HTTP_HOST} matches pattern ^*)


References: - Response is corrupted when you configure an outgoing rule in URL Rewrite Module 2.0 for IIS 7.0 or IIS 7.5 – example (without sharepoint) – similar problem. - rewrite with sharepoint 2013 - why use outbound rules? - supported assymentrical solutions

Tuesday, January 26, 2016

A fun script for creating meetings in Outlook.
For the very lazy admin

function createMeeting(
    $Subject = "Test Meeting",
    $body = "Just Testing",
    $location = "Here",
    $start = "1/26/2016 12:00 PM",
    $duration = 60,
    $reminderSet = $true,
    $reminderMinutesBeforeStart = 15
$olAppointmentItem = 1
$o = New-Object -comobject outlook.application
$a = $o.CreateItem($olAppointmentItem)
$a.Start = $start
$a.Duration = $duration
$a.Subject = $Subject
$a.body = $body
$a.Location = $location
$a.ReminderMinutesBeforeStart = $reminderMinutesBeforeStart
$a.reminderSet = $true
$result = $a.Save()

$Duration = 60
$Subject = "Test1"
$Body = "testar2"
$ReminderMinutesBeforeStart = 30
$reminderSet = $true

#This scenario is set of dates with same meeting time
$arrayOfDates =  "2016-01-26", "2016-01-27","2016-01-28"
$hour = 10
$minute = 00
for ($i=0;$i -le ($ArrayOfDates.count-1);$i++) {
$dateTime = get-date $ArrayOfDates[$i] -Hour $hour -Minute $minute
createMeeting -Subject $Subject -body $Body -location $Location -reminderSet $reminderSet -reminderMinutesBeforeStart $ReminderMinutesBeforeStart -duration $Duration -start $dateTime