DexterPOSH's Blog

This will be a quick and short post on using Azure Automation Runbook to add a Data Disk to one of the Azure VMs already provisioned on Azure and then initialize-format the Disk added using the Storage cmdlets available on Server 2012 onwards. The Workflow is available @Technet >> Download [Blog-Ad] Please check two of my earlier posts revolving around Azure Automation, if you are trying to use this feature for first tim: PowerShell + Azure Automation : Deploy a Windows 10 VM (Server Tech Preview) & domain join PowerShell + Azure Automation : Unleash the Automation Cmdlets Below is the explanation of the Workflow:

Recently at our PowerShell Bangalore User group, we had fun participating in a one day PowerShell + ConfigMgr Hackathon event. Where we had a bunch of ConfigMgr admins worked on using Azure to deploy a full fledged ConfigMgr Lab, also we had fun interacting with each other. Below pic was the theme for the event, says it all ;) My friend Harjit  suggested few ideas for the Hackathon. Below is one of the ideas: " Script that can tell me which collections a particular system or several Systems belong to " The Final Script is available @Technet for Download      

This is the third post in series of poking around EAS protocol using PowerShell, find the first 2 posts below : PowerShell + EAS : Getting Started PowerShell + EAS + MSExchange : Autodiscovery If you are a interested in looking at the C# code samples then checkout posts  @MobilityDojo.net in the Resources section at the bottom. Once you have discovered the URL of the EAS endpoint to connect to, it is time to follow below 3 requests in order to establish an ActiveSync Partnership with Exchange Server:

This post is going to be on how to use PowerShell to get an insight in the Autodiscovery process which the EAS Mail clients use. Second entry in my #PowerShell + #EAS posts: PowerShell + EAS : Getting Started Once you enter Email Address and Password in the Mail setup in the device, the Autodiscovery process kicks in. Remember there is no such thing as the mail account getting magically configured :) To explain the process is not my intent, Please refer to the MSDN blog post here . In short the Autodiscovery process tries to get a valid XML response from 4 sources (based on the workflow explained at the MSDN blog ). In this post we will be looking at a way to make those 4 requests and study the responses we get back using PowerShell. This is a more of a hands on approach here. I will be taking an account for the demo, for which we will see the discovery process in action : TestUser Account on Office365   (testuser@dexterposh.in) The EAS client looks at your ema