[Debau]

When I reboot my Windows 2003 server, running a Domino 6.5.5 server, the Dispatcher and Policy services don't restart. I have to manually restart them.

Does anyone have this issue? Or a fix? It is aggrevating if that server has to be rebooted and the manual restart step is missed.

[silver_2000]

what account are the services starting under ?

make sure they are starting under same account as the rest of the services

BES has a BAD habit of instalilng and running services as the user who installed it rather than the system account

[|||||||]

Originally Posted by silver_2000

BESAdmins have a BAD habit of installing services as the wrong user

Fixed for you.

[silver_2000]

Originally Posted by |||||||

Fixed for you.

Please dont attempt to put words in my mouth

I login to the propsed BES server as myself ( the only way allowed in most corporate environments ) and install the BES. As I said the BES installer installs mant of the BES services as the user who did the install rather than the local system account which is the standard for most other Windows installers.

EDIT - the idea that I should ( if it were possible ) have to run the setup.exe as someone else is rediculous and in fact if its required should be documented in the Install docs. The facts are that its NOT possible in this corporate environment to "run as" the System account "

Debau- just make sure you go back and check the logon properties of the BES services

[|||||||]

The only supported way to install it is as the admin user. RTFM.

[silver_2000]

Rather than pointing out how smart you are why dont you try to help the poster ?

Page 29 of the install guide

login to the computer using an administrative account with appropriate database permissions

Im a domain admin which means that my login exceeds the requirements.

Once again in my opinion the installer is written in a way that is different than the majority of other apps.

The fact that RIM's policies dont mesh with modern corporate culture is a problem for RIM. An example is the failure to support Virtual servers. Most BIG a nd medium sized corporations are RUNNING to Virtualization for ALL new servers. Another example is expecting admins to login as LOCAL admin, most IT polices prevent Domain admins fdrom logging into ANY machine as ANYTHING other than yourself to ensure that tracking and Sarbanes related auditing works.

[Debau]

Thanks Silver_2000

I checked the log on properties. It is set to be the same as the other Bes services. The other services start properly.

I am going to have my network guy look at that more closely when he gets in.

Anything else that I can check on that server?

Thanks for you help!