Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • Thanks for you reply Paul. So if i understand correctly even if we are just updating the solution using Update-SPSolution your steps 2- 5 should be valid? Also correct me if am wrong, when this activity is done on App server WFE will not be able to serve the request so still there will be a down time i suppose? Commented Feb 4, 2016 at 7:22
  • I am pretty sure that IIS Reset doesn't affect service applications - just tested this with 2 WFEs and 1 APP server - iisreset being run in a loop on APP server while uploading documents and setting user/managed metadata fields - everything worked like a charm. You can Add/Install/Update solutions on APP server whenever you want. Keep in mind, that if you are doing Update-SPSolution you will need to install new SPFeatures manually by running Install-SPFeature (just a note). Commented Feb 4, 2016 at 10:11
  • Yes here my Questions but when we follow 2-5 steps in APP server App pools are recycled in and it will not be able to serve any requests coming from WFE as it gives 503 error?? Thats what my understanding. Commented Feb 4, 2016 at 10:32
  • I was recycling app pools in a loop on my test APP server and WFEs kept working fine. Maybe you've got something configured in a wrong way? Commented Feb 4, 2016 at 11:08
  • Okie i will check this when our setup is ready. Also instead of opening each server and deploying from RDC is there any way to automate above steps from one server itself to deploy in all servers? Commented Feb 5, 2016 at 7:42