After installing Exchange 2010 SP3 OWA gives the error "A problem occurred while you were trying to use your mailbox."

An odd problem post Exchange 2010 SP3, I tested OWA and all was fine, then a user called to say he was getting an error after a random number of clicks and sometimes immediately after login. It turns out there is a limit on the number of non-MAPI connections and this was locking out OWA.

The Microsoft article does not give a value for the registry key, I set mine to 100 Decimal, so far so good.


You cannot connect to an Exchange Server 2010 mailbox from Outlook Web Access:

1. On the server that is running the Exchange Server 2010 Mailbox role, click Start, click Run, type regedit, and then clickOK.
2. Locate and then click the following key in the registry:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
3. On the Edit menu, point to New, and then click DWORD Value.
4. Type Maximum Allowed Service Sessions Per User, and then press ENTER.
5. On the Edit menu, click Modify.
6. Type the decimal value that specifies the number of sessions that you want to use, and then click OK.
7. Exit Registry Editor.

Note The registry value Maximum Allowed Service Sessions Per User affects all Mailbox Databases on the server and is not applied on a per-user basis. If you increase this value, server performance may be adversely affected. For example, doubling the number of service sessions from 16 to 32 could slow server performance.

Configure new Offline Address Book on Exchange 2003

This is something that pops up from time to time.

1. Create a new OAB in ESM/Recipients/Offline Address Lists

2. Right click/Set as default

3. Go to the mailbox store ESM/Administrative Groups/First Admi.../Servers/Servername/Mailbox Store

4. Right click/Properties set the Address Book as the new one.

Windows 8.1 and Server 2012 R2: Quick start guide for sysadmins • The Register

Having struggled with Microsoft KMS in the past I found this quick guide very useful.

Windows 8.1 and Server 2012 R2: Quick start guide for sysadmins • The Register:

Don't use hibernation? hiberfil.sys too big?

Open an Administrative command prompt.

POWERCFG -H OFF

All done. :)

Android Nexus Root Toolkit

After years of using custom ROM's on my Android phone and tablet I've just come across a great utility I wanted to share, it makes flashing and recovering a Nexus 4 almost n00b proof.

If you have any of the following Nexus devices you can use this handy util to backup, restore, unlock the bootloader, root the device, return it to a stock Google android image and even install the ADB-mode drivers on your PC without the usual hassles.

It works on...

Galaxy Nexus

Nexus S

Nexus 7

Nexus 10

and of course Nexus 4

Instructions and downloads can be found at http://www.wugfresh.com/nrt/ 

I'll be posting more Android related stuff as I find the time to document it.

Error 0x8007005 when activating Office 2013 Office365 (we're sorry something went wrong)

Despite the Office 365 portal saying the product was activated the software continued to display the red banner across the title bars of all Office apps, I was receiving the error 'We're sorry something went wrong.' and error code 0x8007005 when trying to activate.

The solution turned out to be very simple. Run an office application as Administrator and wait a minute until it activates it's self, I didn't need to do anything other than right click Excel and run as Administrator then wait.

It will then tell you it has activated and you can go back to using the apps as usual.

Setting calendar permissions via PowerShell

Microsoft Office 365 Community:

'via Blog this'

Stop Office 365 login passwords from expiring

**You must have the following installed.
*Microsoft Online Services Module for Windows PowerShell
*Microsoft Online Services Sign-In Assistant



Import-Module msonline
$cred = Get-Credential
Connect-MsolService -cred $cred


**Get a list of users and their password expiration status**
Get-MSOLUser | Select UserPrincipalName, PasswordNeverExpires


**Set all users passwords not to expire**
Get-MSOLUser | Set-MsolUser -PasswordNeverExpires $true


**Get a list of commands**
Get-Command –Module msonline

"0x00000050" Stop error when you create a volume snapshot in Windows Vista, in Windows Server 2008, in Windows 7 or in Windows Server 2008 R2

I found this useful to upgrade the Volsnap.sys file version on Hyper-V 2008R2 fixing some VSS errors I was getting in VM backups.

"0x00000050" Stop error when you create a volume snapshot in Windows Vista, in Windows Server 2008, in Windows 7 or in Windows Server 2008 R2:

'via Blog this'

Brothertu: RSOP.MSC error: 64 help string specified more than once

#aer_1055.adm

Brothertu: RSOP.MSC error: 64 help string specified more than once:

'via Blog this'

Microsoft gives you choice. ;)

“Allow Logon through Terminal Services” group policy and “Remote Desktop Users” group.

“Allow Logon through Terminal Services” group policy and “Remote Desktop Users” group.

TechNet Blogs: