news and know-how about microsoft, technology, cloud and more.

Windows 8 on a MacBook Air

I am an Ultrabook Fan: Ultrabooks are small, lightweight and easy to handle. You need a lot of adapters (which have some weight too) and Ultrabooks can be used as a permanent working device. On my Ultrabook I am able to test how Office 2011 works together with Office 365. All in all a lot of advantages.   My Ultrabook is the “I am a PC” Version: I use Windows on a separate Partition and have included a second Windows 7 Installation via VHD-boot. Both Windows Installations are present via Bootloader and I can choose between them. The switch to Windows 8 was an easy going process. First of all I used Windows EasyTransfer to save all my data and settings. The I started the setup process directly from an USB Stick within the Windows 7 Installation. This is the setup process (please forgive the German screenshots): The Setup of Windows 8 took approximately 8 minutes: After the installation there is a new bootloader. The “old” VHD was recognized already: What about the drivers? Windows 8 recognized almost everything. Almost: the USB-LAN Adapter and the Bluetooth drivers are missing. Bluetooth half way: Windows 8 recognizes some devices but not my Bluetooth mouse. The touchpad does not recognize right clicks. Also I could not not see my Mac partition. To solve that you have to install Boot Camp 4: Boot your Mac partition and prepare a driver stick with the Boot Camp Assistant. Then reboot Windows 8 again and install the driver packages. After that LAN, Bluetooth and the touchpad are working as expected. My Mac partition was visible, too. This is a Screenshot of the installed packages after Boot Camp: Because I am used to the Windows-style keyboards I removed the Apple-Keyboard Layout and set the Windows partition to start automatically within Boot Camp. After that you can restore your settings and data via Windows EasyTransfer. If you like to test Windows 8: all TechNet or MSDN Users can download it already. All others can download a 90 days Trial. //

How to develop Windows 8 Apps in Azure

Find a cool article about Developing Windows Azure, Cloud-Based Applications With Windows 8-What you need and how to get there in Bruno Terkaly´s msdn-blog! His tips: Use VS2010 + Azure SDK 1.6 (Visual Studio 2011 does not yet support the Azure SDK and tooling) parallel with VS11 Beta and SQL Server 2008 R2 Express with SP1. And Windows 8 of course.

Hop count exceeded-how to resolve a possible mail loop in Office 365

In this blogpost I will describe a solution for IT Administrators with the following situation: You are unable to receive E-Mails in your Office 365 account, senders receive a NDR (non delivery report). The NDR says: The following organization rejected your message: Diagnostic information for administrators: Generating server: #< #5.4.6 smtp;554 5.4.6 Hop count exceeded - possible mail loop> #SMTP# …this can be caused by a duplicate entry in FOPE! To get this situation resolved you don’t need a support call with Microsoft. You can solve it with a little PowerShell magic. First take a look in your Exchange Online Management Board where you can access the FOPE portal (if you are on an E-Plan) . Simply click on Exchange Online / Mail control / Forefront Online Protection for Exchange. Check if you see a duplicate entry within the Domain section in FOPE! If that’s the case you can set the entry with PowerShell. As I am aware that PowerShell is not everyone's most loved tool, here are all commands you have to run within PowerShell, so you can make your life easier with simply copy & paste from here. $LiveCred = Get-Credential $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri -Credential $LiveCred -Authentication Basic –AllowRedirection Import-PSSession $Session –AllowClobber Set-AcceptedDomain -Identity -OutboundOnly $true Set-AcceptedDomain -Identity -OutboundOnly $false After that, wait for approximately one hour. Check your FOPE entries. All should be set to normal and mail-flow starts working again! Attention: use this only if you are in the above mail loop situation. Hope that helps! Martina Grom, MVP Office 365. Follow me on Twitter

#MVP12 summit photo mosaic

@magrom and me, @atwork, had a great time at MVP 12 summit in Redmond! We met a lot of great people and had a lot of fun! We created a photo mosaic from our photos and photos of some other MVPs. MVP12 summit photo mosaic Our photo mosaic of #mvp12 summit made it into "What's new in the Microsoft MVPs world". Also there is some traffic with really nice tweets about our mosaic... thx!    Glad, you like it! Exactly there are 1.836 photos included in this DeepZoom mosaic. Again thanks to Olaf Engelke (about 930 photos), Oliver Sommer (the great title photo, 11 photos), Rainer Stropek (9 photos) and Toni Pohl (about 890 photos) for your photos! BTW: We have made some further DeepZooms. If you like this kind of presentation, see our Harley Davidson photo mosaic or WPC2010... Enjoy!

Passwordneverexpires-How to disable password policy settings in BPOS and Office 365 with PowerShell

Office 365 has a password policy, which is by default set to expire on a regular basis (90 days). There are some guidelines which help to make sure that the password is secure: Use 8 to 16 characters combination of upper- and lowercase letters at leat one numer or one symbol (be aware that the symbol is available in every language on every keyboard) Do not use spaces, tabs, line breaks, your user name Each user is able to change his password at any time. If a user forgets his password it can be reset by an Office 365 administrator. In some cases – for example for service accounts – it is useful to change the password expiration policy to never expire. In this post I will show you how you can disable the password expiration for Office 365 and for BPOS as well. Password Policy change to never expire in Office 365 In office 365 you need only two lines to disable the password policy. First open the Microsoft Online Services Modul for Windows Powershell. (Download: 32bit or 64bit). Connect to Office 365 Connect-MsolService In the dialog enter the credentials of an administrator: To change a single user: Set-MsolUser -UserPrincipalName <username> -PasswordNeverExpires $True To change all users at once: Get-MsolUser | Set-MsolUser -PasswordNeverExpires $True That’s it. You can control the result with the following command: Get-MsolUser | fl Password Policy change to never expire in BPOS You can also change the password policy for former BPOS accounts. Here we use a csv-File, which contains all enabled users: First of all you need PowerShell for Migration (Download 32bit and 64bit). Our first step is to export all users to a csv-File. $Cred = Get-Credential Get-MSOnlineUser -Credential $Cred -Enabled | select-object -property Identity | export-csv C:\data\user.csv Now you find a csv-File with your enabled BPOS Users. Our Script looks like that: $Cred = Get-Credential $Users = Import-Csv -Path "C:\data\user.csv" ForEach($User in $Users) {         $User.Identity         Set-MSOnlineUserPasswordNeverExpire –Identity $User.Identity –PasswordNeverExpire $true –Credential $Cred } Save the script as disableexpire.ps1 in the same directory as your user.csv file. In PowerShell start the script with this command: &"C:\Data\disableexpire.ps1" This is the result: All user account expiration settings have been changed. Please be aware that it is – for security reasons – a good idea to change your passwords frequently! //