We had an Exchange Server 2007 and we wanted to go to the cloud, because lets face it, the cloud is cool.
So we got a consultant to set up ADFS and all necessary connections so we could start migrating to the cloud.
Problem was, now we had to “migrate” mailboxes and we where not going to do that manually.
When I was trying to configure a scheduled task to use a specific service account the task manager did not want to accept my service account credentials.
I wanted a quick way to find out if the credentials I was using where correct. Some quick browsing on the web lead me to this.
This is a very comfortable setup.
Version Control combined with the (currently) best PowerShell editor.
Best part is: it’s all free and very scalable.
This setup can be used for teams of every size.
Nicely written and structured article as well.
Version control allows you and others to work on the same scripts, check them in and out, etc. By following these steps, it is possible to use version control system for PowerShell as well as a number of other programming languages.
For PowerShell, PowerGUI is by far my favourite GUI/Script Editor, it is free, far superior to ISE (which is improving) and my preference to PrimalScript. Although PowerGUI is my preference for PowerShell development, for pretty much all other scripting, PrimalScript is superb.
Primal’s PowerShell Studio is an excellent PowerShell GUI/Script Editor. It has a similar feature set to PowerGUI, with some advantages and some disadvantages- one thing that it excels at is PowerShell GUI development.
One thing that PowerGUI, PowerShell Studio and PrimalScript all have in common, is that they support the MSSCCI provider/Source Control Plug-in API. The following guide shows you how to install the provider and…
View original post 400 more words
Very useful when setting up new wmi filters.
GPO WMI filters can get screwed up when edited. Quick way of testing a WMI filter is available using Powershell:
- Grab the GPO WMI filter from GPMC and put it into clipboard
- in Powershell console:
gwmi -Query ‘Paste your WMI filter here’
write gwmi -Query ‘ (single qoute)
paste in your wmi filter
‘ (single qoute)
Result could look like this:
gwmi -Query ‘SELECT ProductType, CSName FROM Win32_OperatingSystem WHERE (ProductType = “1”) AND Not CSName = “CB002021”)‘
When any results are returned WMI filter evaluates to $true (GPO applies), else $false (GPO does not aplly)
Don’t forget that you get the luxury to test against multiple computer just by adding the -Computername parameter:
gwmi -Query ‘SELECT ProductType, CSName FROM Win32_OperatingSystem WHERE (ProductType = “1”) AND Not CSName = “CB002021”)‘ -Computername PC01,PC02
For the hundredth time I Googled how to convert String to DateTime.
It’s time I put it in my memory extension.