Article Updates February 2013

I don’t revisit my old articles so often, usually because they stand complete as they are, and I’d rather produce new ones. However I saw it fit to make a few minor updates now as I have gained some more insight on the topics.

Last things first; in my article on MDM for Windows RT:
http://mobilitydojo.net/2012/12/20/windows-rt-mdm-first-impressions/

I said the following “the tool tip for the encryption setting states that Windows RT does not support encryption”, and found that slightly strange since RT should support encryption as such. I’ve run this by the Intune team, and it seems the tool tip is misleading. Windows RT supports encryption of the whole device, and it will be enabled by default provided you sign in to the device with your Microsoft account. This means that there is no setting for Intune to enable or disable it. So Intune doesn’t technically support controlling this on the device, but it should be in play nonetheless. (Of course it’s hard to enforce whether the user logs in with a Microsoft account or a local account.) You will not get encryption with a local account. The explanation I got for this design choice was that the cloud was needed for recovery of the Bitlocker key should you lose it.

Back in September I played around with mobile devices and IPv6:
http://mobilitydojo.net/2012/09/19/mobile-devices-and-ipv6-how-goes-part-ii/

Since I didn’t have access to Windows Phone 8 or Windows RT at the time I wasn’t able to test those operating systems. It’s been a couple of months since that though, so I have been able to test it now. I actually rolled out IPv6 on my secondary site in the meantime, and got it working properly more or less. (There are some minor snags but it works in general.)

Unsurprisingly Windows RT has top-notch support for IPv6 as it’s working just like regular Windows 8 for the desktop. I saw no issues using IPv6 on the Surface RT.

Windows Phone 8 however… Well, it supports IPv6 as far as I can tell, sort of…If you check the properties for the Wi-Fi connection it will only tell you the IPv4 address, but looking in the DHCP console I could see it having an address assigned by IPv6. I have also enabled SLAAC, but I’m not able to tell if the device has been in contact with the gateway device. I am however able to tell that I’m not able to get the device to connect to the IPv6 Internet in any way. That just isn’t working. Typing IPv6 addresses directly in the browser also informs me that it’s not a valid address. I don’t know for sure, but to me it looks like Windows Phone 8 supports DHCPv6, but not SLAAC. And as I said when I showed the setup for Windows Server you can’t get a fully working IPv6 infrastructure with DHCP alone… Could I have researched this further by setting up a non-Microsoft DHCP server? (I also tested with the Airport Express doing DHCP.) Yeah, probably, but my reasoning is that if Windows Phone doesn’t support IPv6 with a standard Microsoft architecture it doesn’t support IPv6.

I made some minor bug fixes for my online version of EAS MD, and most importantly I removed the captcha because it was a pain. It was just to darn hard to get right even if you are human.
It can still be found at https://easmd.labs.mobilitydojo.net

That’s it for now, and I’ll see to it that I update the original articles with this info as well.

Leave a Reply

Your email address will not be published. Required fields are marked *

*