While restarting system all BO Servers fail to register themselves with the CMS from the first try. They manage to do this after automatic retry. Usually this error occurs if CMS is down but according to Application log it starts first of all (CMS log shows nothing).
Your suggestions, please.
AlexKey (BOB member since 2006-08-18)
This typically only happens if the non-CMS servers are starting up, and the CMS is not yet fully started. Check i the app event log if the CMS has not just written the “Central Management Server started” information but also the “CMS Startup completed”. It can take anything from a few seconds to a few minutes between the two messages, depending on your environment.
The non-CMS servers can only register once the second message has appeared.
Also, normally the servers will try and retry automatically. You seem to describe this, so is this not really just a ‘cosmetic’ issue? Does anything happen during the reboot that needs manual intervention?
Orange 
(BOB member since 2006-09-18)
I assume that the source of this problem is CMS delayed startup and generally this fact didn’t disturb me much cause finally all Servers had started and registered without providing any actions manually. But as to commercial clients they consider this ‘cosmetic’ issue is a consequence of the bad configured system. :?
Do you know any solution of this problem?
AlexKey (BOB member since 2006-08-18)
The only way to get around is this issue is to hard-code an order for all services to startup. So first it should start the CMS server, wait a few minutes and then start all the other servers which will then be able to register with the CMS cleanly - again, this is purely information you see in the event log. It is by design and nothing is going wrong.
So perhaps you can set all servers to startup ‘manually’ except for the CMS. And then start all the NON-cms servers using a batch script. But that will only work if an actual user logs into the server. So I wouldnt be mad about that if I was an administrator.
On the other hand - if your problem is the CMS trying to connect to the database, and the DB is not ‘up’ yet, then the CMS will fail to connect eventually and will stop trying after 3 times. So restarting the CMS service would be sufficient. In that case, maybe setting the CMS as a dependent service (in the CCM) for any non-CMS server could do the trick…
Orange (BOB member since 2006-09-18)
It could be the way but I really want to find natural solution.
DB is located on dedicated server so this is not a reason of fault.
Thanks for assistance.
AlexKey (BOB member since 2006-08-18)