- Core configuration: Email Server Settings
-
Other configuration: Email Settings
- Enable Email Setting: System Settings (Events), System Settings (Rooms)
Configure the scheduled task on the new server:
1. Edit the Scheduled Task Batch file.
- Use My Computer to browse to the evanced\lib folder created earlier.
- Right-click on the "notify.bat" file and select Edit or Open With and select a simple text editor.
- The batch file should contain the following line:
HttpRequester.vbs http://localhost/evanced/lib/eventnotify.asp?opmode=all
- Edit this line to point to your installation. Mainly replace the "localhost" with the path to your web site.
2. Build the Scheduled Task.
- Open the Scheduled Task Wizard on the server. Typically this can be found under 'Start-->Control Panel-->Scheduled Tasks-->Add Scheduled Task'.
- Select Next when the wizard starts.
-
Click on Browse and find the "notify.bat" file under the lib directory created earlier and select it.
-
Change the name of the task to something like "Evanced Notify", click Daily then click Next.
-
Select the time you want the notification script to run then click Next. Typically this is during a slow traffic time like 11:00 PM.
-
Enter a user name and password for an administrator account that does not change or remember to change this password whenever your security policy requires you to change passwords.
-
Click Next then click Finish.
-
Action: Select "Start a program" from the drop list.
-
Program/Script: Type "cmd.exe"
-
Add arguments: Type "/c notify.bat"
-
Start in: Type here the full path to the containing folder of the notify.bat file on your server. For example, it could be this "c:\inetpub\wwwroot\evanced\lib\" for the instance on hand. Do not forget about the back slash at the end.
3. Test the Scheduled Task
- Right click on the scheduled task you just created and select Run.
- If it runs with no more user interaction then it is installed correctly.
- If it requires ANY user interaction then this must be addressed or it will not run automatically.
- Here are a couple of items you may need to tweak. (It doesn't hurt to just apply these settings anyway). Right-click on the task and choose 'Properties'.
- Within the 'General' tab of the Properties window, select 'Run whether user is logged on or not'.
- Now put a check mark in the box for 'Run with highest privileges'.
- Within the 'Settings' tab of the Properties window, change the drop-down list to 'Stop the existing instance'.
- Remember to apply your changes.
NOTE: One common issues is a popup that requires user interaction to click on OK to continue running. If this window is displayed, be sure check the box for "Do Not Display This Warning Again". The server may also give a "Always show this message before running this type of file". Be sure to uncheck the box before hitting ok.
The key is to make sure the message does not repeat. Take whatever action necessary to be sure the message only displays once. Keep an eye on it for the following two days to be sure the task is running correctly.
Failure to check this box will cause the task to fail.