I have two SharePoint server 2013 farms as follow:-
- Live farm. Which have 2 MS windows 2008 r2 servers; SharePoint server + SQl server.
- Staging server which have one MS windows 2008 r2 server containing both SharePoint + sql server.
Now I always try to keep the two farms in the same sharepoint farm build number. so I can backup/restore/test site collections easily between the 2 farms. and when our system admins patch the servers each 2 months (by installing the latest windows security updates using the GIFs tool), I always inform them to install these patches one staging first , so I can test the patches then ask them to do it on live if everything work well on staging.
Now I have installed SharePoint designer one both the staging and live . Although I should not do so on live,, but this my current situation.
Today I read an article (which refer to SharePoint 2007 not 2013) that sometimes some updates for SharePoint designer can affect SharePoint server dll files, and can break some modules on SharePoint. So based on this article i am a bit confused about having sharepoint designer installed on live server. I have these 2 options to follow:-
- To un-install the SharePoint designer from the live SharePoint server. and if I want to modify a live site collection I can use the SharePoint designer inside the staging to access live sites. But in this case some updates on staging which is targeting SharePoint designer , will not be install inside the live server ,, which can result in different farm build numbers being generated inside the staging compared to live ..
- Second approach is to have SP designer on both servers (as I am currently doing) . I mean to assume my software requirement for my SharePoint farm to have both SharePoint server + SharePoint designer installed… and since I am testing the updates on staging before applying them to live,,, so I can minimize the risk , if an update for SP designer will negatively affect SharePoint server..
Second question . now the article I read was talking about SharePoint 2007 , where some updates for office products have affect dll files used by SharePoint. So the author of the article was saying to not install any office products inside live sharepoint servers… so mu question if this case is still valid inside SP 2013? I mean can a security update or other update for SharePoint designer affect a dll used by SharePoint server 2013?