Difference between revisions of "Startup Scripts"

[checked revision]

Latest revision as of 08:57, 30 June 2026

When starting the Windows services, a startup script can be executed for each role before the actual service comes up. This can be used to execute certain commands at system account level.

The service launcher looks for the following files in the config directory (default: %PROGRAMFILES%\MailStore Infrastructure\config) on the server where the service is started:

MailStoreManagementServerStartup.cmd
MailStoreInstanceHostStartup.cmd
MailStoreClientAccessServerStartup.cmd

Revision as of 17:01, 21 January 2014 (view source) Admin (talk \| contribs)		Latest revision as of 08:57, 30 June 2026 (view source) Ltalaschus (talk \| contribs)
Line 1:		Line 1:
−	When starting the Windows services, a startup script can be executed for each role before the actual service comes up. This can be used to execute certain commands at system account level ~~such as establishing connections to network shares for later use via the <tt>net use</tt> command~~.	+	When starting the Windows services, a startup script can be executed for each role before the actual service comes up. This can be used to execute certain commands at system account level.

	The service launcher looks for the following files in the <tt>config</tt> directory (default: <tt>%PROGRAMFILES%\MailStore Infrastructure\config</tt>) on the server where the service is started:		The service launcher looks for the following files in the <tt>config</tt> directory (default: <tt>%PROGRAMFILES%\MailStore Infrastructure\config</tt>) on the server where the service is started: