Category Archives: microsoft

WSUS Service Crashing

We had an odd thing happen the other day at work. The WSUS console kept crashing for not apparent reason.  It worked fine up until just now.  Digging into the error message, it seemed that the WSUS console was unable to reason the WSUS service and said to check and make sure IIS & SQL we’re running.  They both were.

As it turns out, in the IIS logs,  there was an error about about IIS exceeding its Private Memory limit and crashing.  Eventually I found this blog post:

That indicated that there was a problem with WSUS application pool.  As it turned out, that app pool was in fact stopped on our server!  Starting it enabled WSUS to function for a while until it crashed again, at which point the app pool was stopped again.

Per the above article, I changed the following entry to “0”:

IIS Manager->Server->Application Pools->WSUS Pool->Advanced Actions->Recycling

And changed Private Memory Limit to 0.  A reboot later, and the application pool was able to access much more than the 1.8 GB it is allowed by default.  However…..It was still crashing.  A second option in that same blog mentioned changing the application pools to default to being 64 bit instead of the default of 32 bit.

All that was required was going IIS->Manager->WSUS Website->ISAPI Filters-> right click – edit->and change the loading order of the 32 bit vs 64 bit entries so the 64 bit option loads first.

Another reboot, and ever since then WSUS has been 100% stable.  I don’t know for certain what caused this, other than we recently added some new servers to the domain for WSUS to manage as well as a new OS for it to manage patches for.  Those two things combined to be enough to push it over the line and crash out of memory crashes.

Exchange & UPN Suffixes

I recently ran into a problem where we reactivated ActiveSync after having it disabled for years because we used a solution for mobile email that didn’t rely on ActiveSync (Good for Enterprise). We decided to re-evaluate ActiveSync, it’s improved a lot since Exchange 2003 and early versions of iOS. Re-enabling the proper settings for a couple users to test with and we were good to go (note, Outlook for iOS is awesome….check it out if you haven’t already). After a bit of testing we decided to increase the number of users using it. Enabling ActiveSync for those mailboxes is all we need to do, right?

Not so much.

I ran into a problem where none of them could setup thier Exchange account in either Outlook for iOS or Mail.app. It failed at the authenication setup. To make things more confusing my user account worked just fine, even on the same phones thier user account failed on.

A newly created test account failed in the same way, so off to https://testconnectivity.microsoft.com I went. The test the website performed an Exchange ActiveSync test and said it worked fine. Connected, authenicated, logged in, etc It’s all good, except no one can connect using thier phone, outside of a few people it worked for orginally (and continues to work for). OWA and Outlook on a PC has always worked and continues to work. It seems to be limited just to ActiveSync. At this point I’m completely out of ideas.

Check the firewall, nothing seems wrong there. Trying a more complex password, no difference. Trying a simpler password, no difference. Finally I think to try a Mac OS X based mail app that talks to Exchange via ActiveSync. Boom, it works! What in the world…..? So it isn’t an ActiveSync problem after all, or least not 100% an ActiveSync problem.

Eventually I found an error when trying one of the Autodiscover tests at https://testconnectivity.microsoft.com/ with the test account. In the past this same test had worked fine with my account, but I decided to try it with the test account. And it failed! Finally, something to dig into.

What I found was that the Auto Discover test reported:

An HTTP 401 Unauthorized response was received from the remote Unknown server. This is usually the result of an incorrect username or password. If you are attempting to log onto an Office 365 service, ensure you are using your full User Principal Name (UPN).

Digging into that error this was helpful, I found out the UPN suffix for my test account was set to domain.local instead of domain.com (which is what our email address is). Changed that and the test account was able to be setup on phones and devices as expected!

One Drive Pricing

Microsoft recently announced changes to thier One Drive pricing.  They’ve done away with the unlimted tier completely, citing they had users actually using it as unlimited storage (to the tune of 75 TB for each top end user).  Obviously that is extreme, but still…..if you sell something as an unlimited thing shouldn’t it be unlimited?  Whatever you think about it, Microsoft’s answer was to remove the unlimted storage option completely.  Other changes to the paid tier include:

  • Removal of the 100 GB and 200 GB plans, to be replaced with a 50 GB plan for $1.99 a month
  • The free tier will decrease from 15 GB to 5 GB, and the bonus 15 GB storage for uploading camera photos will be discontinued

Office 365 subscribers will be able to keep thier current level of storage for 12 months while they find someplace else to put the data.

Something worth pointing with all of these changes, the much “hated” and much complained about iCloud storage prices are either the same price or cheaper in 2 of the 3 tiers!

  • 50 GB for $.99 / month vs 200 GB for $1.99 / month
  • 200 GB for $2.99 / month vs $3.99 / month
  • 1 TB for $9.99 /month vs  $6.99 /month (includes Office 365)

I’ve not been able to find out for certain, but I believe Microsoft hosts One Drive themselves (I would assume on Azure) vs building it on top of a competing product like AWS.  I wonder what Microsoft will do with all of this reclaimed storage?  Users have 12 months to get the data off, given the lifecycle of enterprise storage….it wouldn’t suprise me in the slightest to find out 12 months from now is the planned end of life for a lot of disk arrays.  By doing this now, Microsoft will save themselves from needing to purchase a ton of hardware in 2016.  Either that, or perhaps we’ll see a reduction in storage pricing on Azure as the extra capacity is folding into that system.  Which works out great, anytime Azure or AWS lowers pricing the other one usually follows suit.  Works out great for consumers!