Wrong installation process overall

May 13, 2010 at 11:18 AM


one thing that I don't get is why there is a check to see if the admin and timer services are turned on. During installation they should actually be turned OFF together with the WWW service. The point being that you can control what happens better if there aren't any services hammering SharePoint. The SharePoint installer itself (psconfig) does this, quite visibly also.

Why was the choice made to enable these services instead of disabling them, installing using execadmsvcjobs and then re-enabling the services. This is the only right process for SharePoint installations.


May 13, 2010 at 1:07 PM
Edited May 13, 2010 at 1:11 PM

Hi Wouter, this is not correct! The timer service is required to deploy a solution to all servers in the farm. Without it you would need to deploy the solution locally on each server using STSADM -deploysolution <name> -local. The Microsoft SharePoint installer does of course not require the timer service as it installs it and you also need to run the SharePoint installer on each server in the farm

Actually, the solution installer should at best check the status of the timer service on all servers. But it only checks it on the local server as there is no straight forward way to check the status of the service across servers.

/Lars F.