Timeline for SharePoint 2013 Downgrade from Enterprise to Standard
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Sep 24, 2016 at 7:36 | history | bounty ended | CommunityBot | ||
| S Sep 24, 2016 at 7:36 | history | notice removed | CommunityBot | ||
| Sep 19, 2016 at 14:56 | answer | added | Steve Sheppard | timeline score: 0 | |
| Sep 16, 2016 at 7:38 | answer | added | MHeld | timeline score: 4 | |
| S Sep 16, 2016 at 6:28 | history | bounty started | TheCoder | ||
| S Sep 16, 2016 at 6:28 | history | notice added | TheCoder | Improve details | |
| Sep 1, 2016 at 7:19 | comment | added | Christoffer | Well, if the problem is paying for a enterprise key, you should set up a new environment and copy the content databases to the new environment (it's important that all enterprise features are deactivated, otherwise the databases won't work). If you are fine to pay for a enterprise key but not use it's feature, you should be able to disable most of the enterprise features using PowerShell. Uninstalling features does not sound to safe and you might end up breaking a core service. | |
| Sep 1, 2016 at 7:17 | comment | added | TheCoder | Read on some forums that downgrade can be achieved by deactivating and uninstalling some features? Is it possible? | |
| Sep 1, 2016 at 7:14 | comment | added | Christoffer | No, you cannot downgrade. | |
| Sep 1, 2016 at 7:13 | answer | added | Patrick | timeline score: 1 | |
| Sep 1, 2016 at 7:07 | history | asked | TheCoder | CC BY-SA 3.0 |