<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>powershell on bramstoop.com</title>
    <link>https://www.bramstoop.com/categories/powershell/</link>
    <description>Recent content in powershell on bramstoop.com</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Thu, 07 Nov 2019 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.bramstoop.com/categories/powershell/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Useful [Sitecore] KQL Application Insights queries</title>
      <link>https://www.bramstoop.com/posts/2019/11/2019-11-07-useful-sitecore-kql-ai-querys/</link>
      <pubDate>Thu, 07 Nov 2019 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2019/11/2019-11-07-useful-sitecore-kql-ai-querys/</guid>
      <description>BACK TO BLOG OVERVIEW
 As a successor to one of my previous posts, I would like to share some additional KQL queries which might help you during the troubleshooting sessions of your Sitecore application:Availability Results:
 availabilityResults | where timestamp &amp;gt; ago(7d) | summarize avg(toint(success)) * 100 by bin(timestamp, 1h), name | order by timestamp asc | render timechart
 Get unique users per day past 90 days:</description>
    </item>
    
    <item>
      <title>Monitor Sitecore certificates and RunAsAccount(s) using Azure Automation</title>
      <link>https://www.bramstoop.com/posts/2019/09/2019-09-16-monitor-sitecore-certificates-and-runasaccount-azure-automation/</link>
      <pubDate>Mon, 16 Sep 2019 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2019/09/2019-09-16-monitor-sitecore-certificates-and-runasaccount-azure-automation/</guid>
      <description>BACK TO BLOG OVERVIEW
 Using the instructions underneath you will be able to import an Azure Automation runbook that will alert you using Sendgrid before certificates will expire.
The urge of creating this script was to find a way to inform us whenever the private certificate for Sitecore X-connect would expire. The script will, however, help you to monitor all your certificates within your Azure subscription. Next to that it will assure you will renew the certificates for your RunAsAccounts, causing it not to expire, so that your runbooks will be operational.</description>
    </item>
    
    <item>
      <title>Sitecore Hotfix Version Selector</title>
      <link>https://www.bramstoop.com/posts/2019/08/2019-08-29-sitecore-hotfix-version-selector/</link>
      <pubDate>Thu, 29 Aug 2019 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2019/08/2019-08-29-sitecore-hotfix-version-selector/</guid>
      <description>BACK TO BLOG OVERVIEW
 Because of the fact we are running a lot of different Sitecore versions for our customers we love to have a good overview of the available hot fixes. Sitecore has a great GitHub page for this:https://github.com/SitecoreSupport. Unfortunately it is hard to list all specific hotfixes per version.
The idea to daily crawl the GitHub page began to rise. A runbook writes the needed JSON data to a private storage account wheres we read the data using a .</description>
    </item>
    
    <item>
      <title>Validate (all) your Sitecore ARM templates on build</title>
      <link>https://www.bramstoop.com/posts/2019/05/2019-05-16-validate-all-your-sitecore-arm-templates-on-build/</link>
      <pubDate>Thu, 16 May 2019 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2019/05/2019-05-16-validate-all-your-sitecore-arm-templates-on-build/</guid>
      <description>BACK TO BLOG OVERVIEW
 While working with ARM templates and Azure DevOps it definitely adds value to validate all your Json files during build. This might save you a lot of time. To implement this you could setup the following tasks within your build pipeline:
Add a &amp;lsquo;npm&amp;rsquo; task within your build and configure it as below:
Now add a subsequent Powershell task, run it inline and add the following script:</description>
    </item>
    
    <item>
      <title>Disabling Sitecore config files in Azure App Service using Azure DevOps</title>
      <link>https://www.bramstoop.com/posts/2018/10/2018-10-22-disabling-sitecore-config-files-in-azure-app-service-using-azure-devops/</link>
      <pubDate>Mon, 22 Oct 2018 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2018/10/2018-10-22-disabling-sitecore-config-files-in-azure-app-service-using-azure-devops/</guid>
      <description>BACK TO BLOG OVERVIEW
 Since we are keen on keeping the Sitecore scwdp packages OOTB as untouched as can be (as of our deployment strategy) we have two type of tasks in our release pipeline to disable/rename config files after deploying a vanilla package. Please keep in mind that, while using these tasks, we are always deploying to a staging slot with status &amp;lsquo;stopped&amp;rsquo;.
 While checking the script(s), note that you are able to write your own powershell scripts within the $commandBody variable: &amp;quot;$commandBody = @{ command = &amp;quot;powershell.</description>
    </item>
    
    <item>
      <title>Check your Sitecore environment using these Application Insights query&#39;s</title>
      <link>https://www.bramstoop.com/posts/2018/08/2018-08-09-check-sitecore-using-these-ai-querys/</link>
      <pubDate>Thu, 09 Aug 2018 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2018/08/2018-08-09-check-sitecore-using-these-ai-querys/</guid>
      <description>BACK TO BLOG OVERVIEW
 While using Sitecore on Azure you will most likely be able to find your way around using Application Insights. Keeping your Sitecore instances running smooth will, however, require you to check the available logs on a regular base. The most common way to check your environment is to browse trough AI within the Azure Portal. Given the fact you are using AI as ALM monitoring, obviously.</description>
    </item>
    
    <item>
      <title>Monitor your Azure SSL certificate expiration</title>
      <link>https://www.bramstoop.com/posts/2018/08/2018-08-03-monitor-your-azure-ssl-certificates-expiration/</link>
      <pubDate>Fri, 03 Aug 2018 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2018/08/2018-08-03-monitor-your-azure-ssl-certificates-expiration/</guid>
      <description>BACK TO BLOG OVERVIEW
 Using the instructions underneath you will be able to import an Azure Automation runbook that will alert you using Sendgrid whenever certificates will expire.
The urge of creating this script was to find a way to inform us whenever the private certificate for Sitecore X-connect would expire. The script will, however, help you to monitor all your certificates within your Azure subscription.
Prerequisites: - Azure Automation account - Azure Automation module - AzureRM.</description>
    </item>
    
    <item>
      <title>Replacing the Sitecore client certificate on Azure in 5 steps</title>
      <link>https://www.bramstoop.com/posts/2018/06/2018-06-13-replacing-the-sitecore-client-certificate-on-azure-in-5-steps/</link>
      <pubDate>Wed, 13 Jun 2018 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2018/06/2018-06-13-replacing-the-sitecore-client-certificate-on-azure-in-5-steps/</guid>
      <description>BACK TO BLOG OVERVIEW
 These instructions are for a Sitecore 9.0.1. XP1 Topology - on Azure.
For using X-connect there is a need of using client certificates. In Azure these certificates are named private certificates. Since these certificates expire there is a need to replace them.
To make life easier I will describe this process in the 5 steps underneath:
Step 1 Upload the new certificate (pfx) to Azure using ARM template or portal.</description>
    </item>
    
    <item>
      <title>Download Sitecore media items to local disk</title>
      <link>https://www.bramstoop.com/posts/2018/06/2018-06-08-download-sitecore-media-items-to-local-disk/</link>
      <pubDate>Fri, 08 Jun 2018 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2018/06/2018-06-08-download-sitecore-media-items-to-local-disk/</guid>
      <description>BACK TO BLOG OVERVIEW
 For one of our customers we were in need of downloading all media files from Sitecore to our local hard disk. Since we are using the Sitecore SPE extension, the following script gave us all the urls we needed to download them using our local Powershell.
 [code language=&amp;quot;powershell&amp;rdquo;] $url = &amp;ldquo;https://URLOFTHESITECOREWEBSITE/&amp;rdquo; $mediaLibraryRootPath = &amp;ldquo;master:/sitecore/media library/Images/&amp;rdquo; $listAllItems = Get-ChildItem -Recurse $mediaLibraryRootPath
foreach($item in $listAllItems){</description>
    </item>
    
    <item>
      <title>Sitecore hardening using Azure App Authentication</title>
      <link>https://www.bramstoop.com/posts/2017/08/2017-08-11-sitecore-hardening-using-azure-app-authentication/</link>
      <pubDate>Fri, 11 Aug 2017 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2017/08/2017-08-11-sitecore-hardening-using-azure-app-authentication/</guid>
      <description>BACK TO BLOG OVERVIEW
  With Azure App Authentication it is easy to secure your app with an identity provider. The steps to take are described at the following page: https://docs.microsoft.com/en-us/azure/app-service-mobile/app-service-mobile-how-to-configure-active-directory-authentication .
For securing certain url paths it is required to set Action to take when request is not authenticated to Allow request (no action).
When you have followed the instructions above, the next step is to create a authorization.</description>
    </item>
    
    <item>
      <title>ipSecurityRestrictions on Azure App Services</title>
      <link>https://www.bramstoop.com/posts/2017/07/2017-07-16-ipsecurityrestrictions-on-azure-app-services/</link>
      <pubDate>Sun, 16 Jul 2017 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2017/07/2017-07-16-ipsecurityrestrictions-on-azure-app-services/</guid>
      <description>BACK TO BLOG OVERVIEW
  With the powershell scripts underneath you can easily close and open traffic towards your azure app services. Note: by adjusting the resource name variable you can add appsettings to your staging slot as well.
 [expander_maker id=&amp;quot;1&amp;rdquo; more=&amp;quot;Script: open to the world&amp;rdquo; less=&amp;quot;Collapse&amp;rdquo;] ### Open to the world ### Write-Host &amp;ldquo;Open all traffic to app service&amp;rdquo; $resourceGroupName = &amp;lsquo;TOBEFILLED&amp;rsquo; $resourceName = &amp;lsquo;YOURAPPNAMEHERE&amp;rsquo; + &amp;lsquo;/web&amp;rsquo; $r = Get-AzureRmResource -ResourceGroupName $resourceGroupName -ResourceType Microsoft.</description>
    </item>
    
    <item>
      <title>How to export Sitecore SQL Azure databases to Storage Account</title>
      <link>https://www.bramstoop.com/posts/2017/06/2017-06-12-how-to-export-sql-azure-to-storage-account/</link>
      <pubDate>Mon, 12 Jun 2017 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2017/06/2017-06-12-how-to-export-sql-azure-to-storage-account/</guid>
      <description>BACK TO BLOG OVERVIEW
  The script underneath can be used to export a sql azure database to a storage account. It will create a storage account if it does not exist. Remark: script underneath is based on exporting Sitecore master, core and web database but can be changed to your standards easily.
Note: the database names we use are based on tfs_buildnumbers that we set in a appsetting within the azure app service.</description>
    </item>
    
  </channel>
</rss>