Ikea Australia new METOD Kitchens coming 1st June 2015

Looks like the new Ikea “METOD” kitchen range will released in Australia from 1st June 2015!

“The METOD range is launching on the 1st of June 2015. FAKTUM items will still be available to purchase until the 31st May 2015 and there will be an after sales service to support the FAKTUM 25 year guarantee.”

You local ikea store will have the new range installed between the following dates:-

Stores and installation dates

  • Springvale Store install between 20th April – 22nd May
  • Richmond Store install between 20th April – 22nd May
  • Rhodes Store install between 20th April – 22nd May
  • Tempe Store install between 18th of May – 22nd of May
  • Logan Store install between 20th April – 22nd May

The METOD range was recently release in the USA and has been available in europe for many months.

As someone looking to upgrade my kitchen very soon, I think I will hold out for the new range to be available! or possibly Ikea will do a run out sale of the old kitchen? maybe there will be discounts.
In any case, the new system looks good and offers some more options when designing your kitchen.

Using PowerShell to Install RSAT for Windows 10 Tech Preview

Found a good guide here:-https://superwidgets.wordpress.com/2014/10/02/remote-server-administration-tools-rsat-for-windows-10-technical-preview/#comment-254

Download the WindowsTH-KB2693643-x64.msu file as usual – save it to the default location under ‘downloads’

Run the following script in Powershell_ISE (as administrator – elevated permissions)

$Path = "$env:USERPROFILE\downloads\WindowsTH-KB2693643-x64.msu"
# Exctract .cab file $Target = "$env:USERPROFILE\downloads\RSAT" wusa.exe $Path /extract:$Target
# Install via DISM $CAB = "$env:USERPROFILE\downloads\RSAT\WindowsTH-KB2693643-x64.cab" Dism.exe /Online /Add-Package /PackagePath:$CAB

Updating the RemoteAPP icon using PowerShell and presenting RDP file as RemoteApp (Work Resources)

Here is a way to update the WorkResources shortcut icon when using RemoteAPP

I am also using an RDP file as a “RemoteAPP” that connects to another legacy server (win2k3) to run an old app.

All hail #PowerShell

*Note* there is an easier way by just updating the “.ico” file under –

%WINDIR%\RemotePackages\CPubFarms\CPubRemoteApps on the server

I found this article here – http://msfreaks.wordpress.com/2014/01/08/change-a-remoteapp-program-icon-in-windows-2012-r2-rd-web-access/

Which explains the process

In my case I was working with an RDP file – connecting to a legacy application on an old 2003 terminal server.

I didn’t think RDP files would work (I thought I tested this ages ago?) with RemoteApp, however it does! So now I can publish an application that is on an old 2003TS using RemoteApp.

All my files are located in c:\RDP

Open an administrative PowerShell prompt and type the following command:

PS C:\Windows\system32> Get-RDRemoteApp -alias “pinnacle” | fl

CollectionName : QuickSessionCollection

Alias : Pinnacle

DisplayName : Pinnacle

FolderName :

FilePath : c:\RDP\Pinnacle.RDP

FileVirtualPath : c:\RDP\Pinnacle.RDP

CommandLineSetting : DoNotAllow

RequiredCommandLine :

IconContents : {0, 0, 1, 0…}

IconIndex : 0

IconPath : c:\RDP\Pinnacle.RDP

UserGroups : {POWERHOUSE\robertk}

ShowInWebAccess : True

PS C:\Windows\system32> Get-RDRemoteApp -Alias “pinnacle” | Set-RDRemoteApp -IconPath “c:\RDP\pinnacle_1000.ico”

Refresh your RemoteApps


Windows 8.1 workstation

RemoteApp application properties on Server

Alternative Option

You can go directly to

%WINDIR%\RemotePackages\CPubFarms\CPubRemoteApps on the server

And upload the “.ico” file there (renamed to the name of the application)


Office365 – Enabling the use of Microsofts Built in Safe List

In office365 Microsoft subscribes to various third-party sources of trusted senders. Selecting this check box skips spam filtering on messages sent from these senders, ensuring that they are never mistakenly marked as spam.

How to turn it on?
EAC > Protection > Connection filter >
edit the default filter
select the tickbox

However what exactly is in this safe list???

Importing Bulk Domains List into Office365 whitelist with CSV file

Do you need to import a bulk list of domains into office365 to create a whitelist or blacklist rule?

Ok this took me a while to figure out how to get it to work.

I’m sure there are other ways to accomplish this, however this was the first way that I could get working with a CSV file.


  1. Create a new TR rule called “Accepted Domains” (or whatever you want to call it)
  2. Import the CSV file
  3. Inject the csv list into the new TR created in 1.

Why this way?

Well I tried many ways to process the csv first and then create a new TR and inject the csv list but I was unsuccessful. I got close, but no dice :(

However if we create a new rule (or have one already i.e. “whitelist”), we can then add additional domains to it.

  1. Import the CSV

$allowed = import-csv C:\scripts\domains.csv

  1. Create a new Transport Rule (if you do not have a “whitelist” rule already)

*note* this rule will add two domains “a.com ” and “b.com
which you will need to delete afterwards

For some reason this wont work unless there is two or more domains in the whitelist already!!! Don’t ask why, it will import but as one long string….

Skip this step if you already have a whitelist rule

new-transportrule -name “Accepted Domains” -senderdomainIs a.com, b.com -setscl -1

  1. Process the CSV file

$domains=Get-TransportRule “Accepted Domains” | select -ExpandProperty senderdomainis

foreach ($a in $allowed)


$domains += $a.domain

$domainstoadd = $domains | select -Unique


  1. Import the CSV list into the Transport Rule

Set-TransportRule “Accepted Domains” -SenderDomainIs $domainstoadd

  1. Delete a.com and b.com

Note that the column in the CSV file has a heading of “domain”.

Created with Microsoft OneNote for Mac.

Office365 and Winmail.dat – use Powershell to disable TNEF Message Formatting with Remote Domains

“Do some of your users report that e-mail recipients in external domains can’t open their messages that contain a Winmail.dat attachment? If so, the recipients in the external domain are probably using an e-mail client that doesn’t support the Transport Neutral Encapsulation Format (TNEF). Microsoft Outlook is one of the few e-mail clients that support TNEF-encoded messages, although some third-party utilities can help convert Winmail.dat attachments.”

Load Up Powershell and run the following:-

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell/ -Credential $LiveCred -Authentication Basic –AllowRedirection Import-PSSession $Session Set-RemoteDomain Default -TNEFEnabled $false

Microsoft article is here:

#Powershell #Office365

Office365 converting user to shared mailbox account

Open Power-shell Windows Azure AD Module

Run the connection command:

$LiveCred = Get-Credential

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri “https://ps.outlook.com/powershell/” -Credential $LiveCred -Authentication Basic -AllowRedirection

Import-PSSession $Session

Connect-MsolService -Credential $LiveCred

Set the Mailbox Type

Set-Mailbox “mailbox” -Type “type”

You can use the following values for the Type parameter:

  • Regular
  • Room
  • Equipment
  • Shared

So in our case we are making a shared mailbox so the command will be

Set-Mailbox account -Type Shared

We then need to setup the Quota limits on the shared mailbox as they are limited to 10GB

Set-Mailbox account@domain -ProhibitSendQuota 9.98GB -ProhibitSendReceiveQuota 10GB -IssueWarningQuota 9.96GB


SCCM2012 Windows 8.1 OSD with DotNet3.5

Installing dotnet3.5 on windows 8.1 ….
Wow, this was an extremely long and difficult process for me to achieve, but in the end a simple solution was the answer – DISM!

One of our corp apps requires .NetFramework 3.5 (dotnet3) and as you know, windows 8 comes pre-loaded with dotnet4.

We are going to use System Center (SCCM2012) server to deploy a windows 8.1 image (that was built using the build and capture process) and "update" it with dotnet3.5 using DISM on the OFFLINE image (wim) file.

Note: I tried countless times to use the WDS, OSD process to install dotnet3.5, i tried using powershell, creating package files, using the "roles and features", nothing worked. now there was one process i didnt try
here -


which basically involved copying the SXS source files to the local c drive – to me this seems counter intuitive, I *should* be able to use the source files on a network share, but reading many blogs; the consensus was that the way to do this was to copy the sxs locally and run a script install.

Even using the MDT "install roles and Features" didnt work:
I tried setting a Task Sequence Variable "WindowsSource" and pointed to \\sccmserver\Sources\win8_sxs_dir

No dice!

The Process:
In any case, this is the following method i used to make it work for me. and at the end of the day, does what i need it to do.

Here we are assuming that, you have SCCM2012 r2 in a working environment, you know how to build and capture, deploy application etc etc.

1. I copied my Windows 8 image file (incase sometime borked up) and named it with -"dotnet"; this would ten be the image file that includes dotnet.

2. now using powershell or cmd prompt we are going to perform an offline install for the "roles and features" using DISM.
on the SCCM server:

Dism /Get-ImageInfo /ImageFile:"E:\Sources\Operating Systems\Images\Windows 8.1\Win8.1u1-x64-dotnet.wim"

//mount the image to a local folder (create a new folder if it doesnt exist e.g. c:\temp\win")

Dism /Mount-Image /ImageFile:"E:\Sources\Operating Systems\Images\Windows 8.1\Win8.1u1-x64-dotnet.wim" /index:2 /MountDir:C:\temp\win

// USE DISM to install-dotnet into the image

DISM /Image:C:\temp\win /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:E:\Sources\win8_sxs

// Check the installation

DISM /Image:c:\temp\win /Get-Features /Format:Table

//Commit the changes

Dism /Commit-Image /MountDir:C:\temp\win

//I ran the check again, it showed "pending" but after deploying it worked so seems to be all good.

Screen Shot 2014-07-28 at 3.19.51 pm

//now unmount the image
Dism /Unmount-Image /MountDir:C:\temp\win /commit

3. Now we have a new Image file, we need to upload this into SCCM.

and distribute content to the DP.

4. I copied my previous Task Sequence, renamed it to include "dotnet"

Make sure you update your Image locations for the "apply data image 1" and "Apply Operating System".

Also update your OS image
Make sure you have 2-2 selected (for your OS partition – *note* this may depend on your image file and build process)

5. PXE boot and test the deployment
(*note* on my initial deployment I disabled installing applications and updates in the Task Sequence, in order to speed up the deployment and test that its working as required)

6. check ".NET Framework 3.5" is enabled

(now head down to your local and turn down a glass or three…)

7. Now after i know this works, I deployed "scheduled updates" to the image file and once completed updated the DP.

8. In the Task Sequence I re-enabled "install updates" and "install applications" deployments.
9. Test deploying the Task Sequence again and make sure everything is working for workstation deployment

802.11x Authentication with Cisco WiFi Kit + AD

This was a good tutorial on howto set 802.11x authentication with Cisco Wireless Kit + AD

impelmented this within a few hours…

Tutorial: 802.1X Authentication via WiFi – Active Directory + Network Policy Server + Cisco WLAN + Group Policy



Yammer DSync and accidentally introducing the social workplace

With the slow introduction of office365 I thought I would get my hands wet with yammer and its DSync (Directory Sync) application.

Now unfortunately the Yammer DSync tool doesn't do password sync, unlike "Azure AD" DirSync which introduced password sync some time ago. before this users would have to mange their local AD user account to login to their computer and also a separate "office365" user account to access email = not cool! thankfully that was sorted many moons ago…

On the roadmap for Microsoft office365 and yammer is eventual integration/merge of the two distinct products as well as the single user account – utilising Azure AD

Some of the pluses of Yammer DSync was that it actually worked in syncing the on-premise AD user accounts with Yammer along with the users details, position title etc.  The issue for me was that once the new user account is setup in yammer it sends out emails to the new user to sign in.

whoops… i just introduced the org to yammer and the whole world of "Social Productivity" …

Some users though it was spam (delete!), some jumped in and tested the waters and some well … just dont want another system to manage….

in IT the only constant is change, however change is difficult, and changing the way people work is … a challenge


I really like the simplicity of yammer, and the potential it can bring to an orginsation to increase social collaboration and new ways to work.  The future of office 365 and yammer is exciting.