If you’re looking for the SharePoint 2013 prereqs that aren’t actually available from TechNet, head over to Todd Klindt’s blog…
Just a heads up that the Windows Management Framework version 4.0 has been released.
If you remember the past year or so that it wasn’t until Service Pack 2 was released for SharePoint 2010 that you were able to use Windows Management Framework 3.0 with the application server. In similar fashion, version 4 is not compatible with a boat load of applications (Exchange 2013, SharePoint 2013, SharePoint 2010).
So before you get excited and run out and install it to start taking advantage of some of the improvements in Windows Remote Management, be mindful that it will break your applications.
Uncertain as to when we’ll see fixes to allow for compatibility with all of these application servers…
Recently I came across a thread on SPYAM regarding whether it’s possible to block SharePoint 2013 installations using group policy or through the registry.
Sure enough it’s possible to use the SharePoint 2010 installation blocking technique for SharePoint 2013 with a minor modification. Rather than having the Registry Key be for 14.0, just modify it to be 15.0.
So the key that end up implementing either through Group Policy, Power Shell or Registry key setting is:
HKLM\SOFTWARE\Policies\Microsoft\Shared Tools\Web Server Extensions\15.0\SharePoint
With a DWORD Value of ‘DisableInstall’ with a property value of 1.
Sure you can still install the pre-reqs for 2013, but when you attempt to install the actual SharePoint 2013 binary, this is what you end up with:
Time to pick up that VOIP handset and call the administrator about the GPO that seems to be pushed to my server and why I should be allowed to be moved to another OU that has a different domain linked policy.
I’m curious but what is the deal with Microsoft requiring that you contact PSS to get one of the software requirements for running SharePoint 2013 on Windows Server 2012.
If you notice, in the Hardware and Software Requirements document on TechNet for SharePoint 2013 (http://technet.microsoft.com/en-us/library/cc262485.aspx) you’ll notice that there’s a hot fix required for a Race Condition issue for SharePoint 2013 on Windows Server 2008 R2 and 2012.
Funny enough, if you go to the KB article link referenced, you get (2765317), you’ll notice the following text:
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, go to the following Microsoft website:
So if I’m Microsoft, and I’m looking to get more and more market share moved over to Windows Server 2012, why in the world would I not make this pre-requisite available?
Oddly enough though, the same fix for Windows Server 2008 / 2008 R2 (2759112) lists the exact same text.
So I guess we have to call PSS to get the fix before we can start experimenting with SharePoint 2013 in a non-Microsoft hosted environment (I’m guessing that the Azure pre-baked bits already have this but haven’t double checked).
Bottom line, not cool that there’s an extra call involved.
So recently in the download center for Microsoft the Office 365 Security document popped up as being published on 3/7/2013… not quite certain if there were any changes since Microsoft still doesn’t maintain standardization around documents, the download center and change logs, the document was published back in June 2011. If you’ve not read this document it’s a decent overview that covers everything from physical security to user authorization for Office 365, it’s data centers and its service.
http://go.spdan.com/o365security – Office 365 Security
So you’re still catching up on getting certified on Microsoft technologies that your clients and customers are using … may want to consider either switching over to ludicrous speed or just skipping ahead to the next iteration of Visual Studio exams.
Why praytell? Well Microsoft is retiring the exams on 31 July 2013. They (Microsoft) may consider pushing the exam retirement date, but for now that’s when they’re going bye bye.
So what exams does this apply to?
- 70-511: TS: Windows Applications Development with Microsoft .NET Framework 4
- 70-513: TS: Windows Communication Foundation Development with Microsoft .NET Framework 4
- 70-515: TS: Web Applications Development with Microsoft .NET Framework 4
- 70-516: TS: Accessing Data with Microsoft .NET Framework 4
- 70-518: Pro: Designing and Developing Windows Applications Using Microsoft .NET Framework 4
- 70-519: Pro: Designing and Developing Web Applications Using Microsoft .NET Framework 4
For more information on this topic, check out the Born to Learn blog yonder at: Update on Visual Studio 2010 Exam Retirement Dates
Microsoft has published an update for their Office 365 Dedicated Service Level Agreements and Service Descriptions. If you’re not working with an Office 365 Dedicated client, but are instead working with an OnPremise deployment these documents provide a great starting point when defining your O&M strategy as well as helping to define processes and service level agreements.
For instance, the Custom Solutions Developers Guide for Office 365 Dedicated provides an outline that can be used for onPremise deployments in terms of areas that need to be considered for developers to operate within. That’s not to say that there isn’t greater flexibility in developing full trust farm solutions for your SharePoint implementation, but it is to say that Microsoft has invested significant cycles to put together this guide among other documentation that helps to think through the entire process.
If your client is however looking to go to Office 365 Dedicated – definitely need to become familiar with the information housed within this set of documents available here:
Microsoft Office 365 Service Descriptions and Service Level Agreements for Dedicated Subscription Plans
Interestingly enough, but if you’re using SharePoint Online in Office 365 in a dedicated environment there are opportunities for content migration from onPrem to the cloud by providing copies of content databases to Microsoft. Or at least you used to have that option as described in this document:
SharePoint Online Content Migration Policy – Office 365 Dedicated Plans – January 2013 – http://download.microsoft.com/download/0/4/0/04054360-DC5E-4AB8-B3AB-6BF01BB3946C/SharePoint%20Online%20Content%20Migration%20Policy_Office%20365%20Dedicated%20Plans_Jan%202013.docx
If you’re looking to have a backup copy of your data perhaps or looking to move off of Office 365 Dedicated, the cut off for having content databases pushed out of Microsoft’s system is 15 April 2013 as stated in the documentation:
Starting April 15, 2013, Microsoft will no longer process outbound migrations for SharePoint Online dedicated plan customers. Outbound migrations will instead be accomplished by third-party independent software vendor (ISV) solutions, just like Inbound migrations are today.
Microsoft states that they are doing this for a number of reasons to include:
ISVs provide an effective solution for migrating content out of your SharePoint Online farm, just like for inbound migrations. Using an ISV solution has the following benefits:
- Reduces technical requirements and complexity involved in successfully attaching the data to an on-premises SharePoint farm.
- Frees up customer change windows for deployment of configuration changes and custom solutions.
- Removes the risk and inconvenience of a USB drive shipment.
For information about using ISV solutions for content migration, see the SharePoint Online Content Migration by Third-Party Solutions Policy document, available to customers on the Customer Extranet site.
Overall the document is an interesting read regarding the SharePoint Online 2010 Dedicated service offering that is a component of Office 365 and outbound data migrations. Just remember however that you do have an impending deadline in April if you wish to utilize Microsoft’s outbound data migration service.
So while tooling around in PowerShell this morning in Windows Server 2012, I had to chuckle when I ran a get-help command and read through the text where it stated Windows Server “8″ Beta. I suppose that even though this was released back in late September that Microsoft hasn’t had a chance to do an update of their help files.
And for anyone curious, yes, I did run an update-help prior to running the get-help cmdlet. Check it out
Just in case you’re using Mac OSX as your primary operating system (hey Office 365 supports it now right?) and you’re wondering why you’re seeing errors with Lync here and there, consider getting the Lync update. Fresh from the Internet press, Microsoft has released update 14.0.4 available here:
48 MB of downloadable DMG goodness
Seems to help with a few stability items and also the following:
2793013 A user cannot start an encrypted desktop sharing or application sharing session together with a Lync for Mac 2011 user
2793011 An update is available that enables Lync for Mac 2011 to be supported in Mac OS X 10.8 Mountain Lion
2793012 Video call or conference is stretched to a 4:3 aspect ratio when you use Lync for Mac 2011
2803796 “Lync was unable to sign in” error message when you try to sign in to Lync Online by using Lync for Mac 2011 in a Mac OS