All new versions of the BES Client are set to delayed start by default. This is a good thing, and you should set all systems this way, even if they are older versions of the client.
The reason this is a good thing is for many reasons:
- It minimizes any impact that the BES Client has on system boot up
- It helps ensure that the network is up before the BES Client goes to work
- There is a lot of disk activity on boot, it is nice to keep the client from contributing right away
Even though the client should always have minimal impact on the system, these are definitely good things.
If for some reason the BES Client service isn’t starting at all, then that is an entirely different issue, and you should probably file a PMR.
Does anything show up in the client logs?
If it doesn’t seem to start when set to delayed start, does it start automatically after a few minutes when the system is rebooted, or does it just never start, no matter what?