MOSS-Exchange

I created a new web application and site collection on SharePoint 2013 Enterprise. Everything worked great until the users tried to open Excel documents. They were challenged with and Excel Services error:   We don't know what happened, but something went wrong.  Could you please try that again? The issue was that the document library was configured to open documents in the  browser  as it's default behavior. I changed it to Client Application and all was working as expected. Go into Site Contents click the three dotted menu then Settings. Go to Advanced Settings: Select Open in the client application: If you are truly trying to get Excel Services to handle the file, you will need to configure this as a trusted site and perhaps modify the permissions on the Temp directory to allow the application pool account to modify.

I hope I can save you the frustration I had in debugging my script: New-SPIISWebServiceApplicationPool -Name ManagedMetadataServiceAppPool -Account domain\user The term 'Get-SPIISWebServiceApplicationPool' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. This command worked fine in pre-release versions of SharePoint 2010, but for the RTM they the cmdlet is missing! My scripts and documentation needed to be updated for the missing command as they changed the name in the RTM version of SP 2010. SPServiceApplicationPool is the new cmdlet name. New-SPServiceApplicationPool -Name ManagedMetadataServiceAppPool -Account domain\user works great. I am off to discover what other cmdlets have been renamed.