Exciting things i have seen on the internet, 29/11/13

2013 sp1 has been announced – edge servers, support for 2012 r2 and a shift in how service packs work – from now on they’re going to be a lot more like cumulative updates, and we need to see them as such. SP1 will be in place of CU4, and CU5 will include SP1, which is different to previous releases where rollups were for a particular service pack – from now on it will all flow in together. in an earlier mail i suggested that the difference between a service pack and a cumulative update is a schema update, however CU1, CU2 and CU3 include a schema update, so that blows that out of the water. expect a post on how we need to redefine our services in response to this in the near future.

 

Exchange 2010 sp3 rollup 3 has also been announced. note the large numbers of fixes for CAS crashes. be aware that issues with the client access service crashing may be fixed (or substantially altered) by the code changes made in this rollup.

 

Rhod Milne has highlighted some useful Microsoft Virtual Academy courses in a post here. if you’ve not yet tried the MVA stuff then i urge you to find some time for it – it’s much better than free training has any right to be.

 

He has also posted an exceptionally handy list of things you should do to Exchange 2010.You should consider these things best practice, and think about how to incorporate them into your Exchange 2010 environment. if you are unsure if they apply to you, then please give me a ring. there are also some recommendations here that Rhod refers to; these are interesting and useful, but less likely to apply to everybody.

 

Scott Schnoll is always an interesting read, and he’s just published some new documentation for Exchange 2013 managed availability.

 

after last week’s post about IPv6, Microsft have updated their article on how to re-enable it or temporarily disable it for troubleshooting purposes only.

 

Microsoft have changed article 297019 again. this is the networked PST article. it no longer explicitly states that PST files accessed over a network are not supported (although it is still heavily implied). for the avoidance of doubt; PST files that are accessed on a network share are not supported. there are too many issues associated with it, and if MS find out that you have PST files stored on a network share then they will stop doing any troubleshooting until you disable them all. Please do not store PST files on a network share, and please don’t suggest to your customers that it won’t be a problem. it ALWAYS causes a problem. the MS document that is referenced in the kb article is titled “network stored pst files: don’t do it“. That should be a good clue as to what the product group think about it.

 

no-one has reported a problem with iOS 7 to me, but just in case, here’s a hotfix that Microsoft have released for a problem that iOS7 created.

 

and just to prove it’s not just apple, the latest version of android (kitkat, or 4.4) breaks active sync. google have marked the problem as “closed (to be fixed in a later release)”, so basically there’s a reasonable chance that upgrading to kitkat on an android device will BREAK exchange activesync for the long-term. not a good idea.

Advertisements
Post a comment or leave a trackback: Trackback URL.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: