Windows server 2003 service startup order

Improve this question. Mike B Mike B Add a comment. Active Oldest Votes. Improve this answer. Evan Anderson Evan Anderson k 18 18 gold badges silver badges bronze badges. Yup, sounds good, and when you think about it, it's probably the way things should be. Can you imagine the support calls - "I changed the startup order and now my machine is broken" - eeewww. That aside, if service A depends on service B then the depencency stuff seems the best place to control the order.

Stephen Thompson Stephen Thompson 1, 9 9 silver badges 10 10 bronze badges. I initially upvoted this--Microsoft's own lit agrees with you--but today I realized that this approach means that if you need to restart, say, the DHCP service, it downs whatever services you have made dependent on it that actually aren't. Sign up or log in Sign up using Google.

Use information in the local database to try to contact other nodes to begin the join procedure. If a node is contacted and authentication is successful, the join procedure is successful. If no other node is available, the Cluster service uses the information in the local database to mount the quorum device and updates the local copy of the database by loading the latest checkpoint file and replaying the quorum log.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:.

Verify that the cluster node that is having problems is able to properly authenticate the Service account. You can determine this by logging on to the computer with the Cluster service account, or by checking the System event log for Cluster service logon problem event messages.

Start Registry Editor Regedt Make note of the network and quorum keys. If the database is not valid, you can copy and use the cluster database from a live node. If all nodes do not have a valid cluster database, see the following article in the Microsoft Knowledge Base:. If the node is not the first node in the cluster, check connectivity to other cluster nodes across all available networks. The order of services within a group specified in the tags order vector.

This information is stored in the GroupOrderList value in the following registry key:. The dependencies listed for each service. By default, this value is not set. The system simply reports that the boot was successful after the first user has logged on. You can supply a boot verification program that checks the system for problems and reports the boot status to the SCM using the NotifyBootConfigStatus function.

After a successful boot, the system saves a clone of the database in the last-known-good LKG configuration. The system can restore this copy of the database if changes made to the active database cause the system reboot to fail. The following is the registry key for this database:. If the LKG configuration is already being used, the boot fails. Please refer to the following link: Automatically Starting Services. Please also check the following link:. Troubleshooting the Startup Process.

Best Regards,. Forum Support. After the user attaches a debugger to the resource monitor process, and the resource monitor process starts up, the Cluster service continues with its initialization. Function : The norepevtlogging switch prevents replication of those events recorded in the event log. This switch is useful in reducing the amount of information displayed in the command window by filtering out events already recorded in the event log.

Event log replication is a feature that was added in Windows Usage scenarios : This switch is used to prevent replication of the event logs. If there's a large number of event log entries, the Cluster service will replicate these, and log these to the cluster. This can cause the cluster. The switch can also be used to start the Cluster service and log those events that aren't recorded in the event log to a local file, Debugnorep. Operation : The norepevtlogging command can be set as a start parameter when starting the Cluster service from the Computer Management console.

This command prevents the node that was started with this switch from replicating its information to other nodes, but it will still receive information from other nodes that were started normally. Function : Turns off all logging of the cluster registry changes to the quorum disk. Registry check pointing doesn't affect other resources. Requirements : This switch must be used only in diagnosis mode to diagnose problems with the quorum log file Quolog.

If one node is started up by using this switch, any other node must also be started up by using this switch. Typically, this switch is used on one node alone. Usage scenarios : Use this switch when the quorum log file or checkpoint files become corrupted and you want to manually replace these files with backup copies. Operation : The Cluster service completely bypasses the logging functionality in this case.

When run in this mode, "partition-in-time" scenarios can occur. If this is the case, cluster node registry entries can fall out of synchronization, and new changes can be lost. Function : When you use a Majority Node Set MNS quorum model on a Windows Server cluster, in some cases a cluster must be allowed to continue to run even if it doesn't have quorum majority. Consider the case of a geographically dispersed cluster with four nodes at the primary site and three nodes at the secondary site.

While there are no failures, the cluster is a seven-node cluster where resources can be hosted on any node, on any site. If there's a communications failure between the sites or if the secondary site is taken offline or fails , the primary site can continue because it will still have quorum.

All resources will be re-hosted and brought online at the primary site. In the event of a catastrophic failure of the primary site, however, the secondary site will lose quorum, and, therefore, all resources will be terminated at that site. One of the primary purposes for having a multi-site cluster is to survive a disaster at the primary site; however, the cluster software itself can't make a determination about the state of the primary site.

The cluster software can't differentiate between a communications failure between the sites and a disaster at the primary site. That must be done by manual intervention.