quote:

---

3. How to run the script scheduled

There are 2 kinds of scheduler services on current Microsoft Server systems - The old one (NT4,ie older than 5.0);
to be recognized by AtSvc.exe as the Service executable, and the new one, MS Task Scheduler; To be recognized by
existance of a control panel item ...
AtSvc.exe : on a command prompt type the appropriate at command and hit [ENTER]
ie. - AT 03:00 /interactive /every:M,T,W,TH,F,Sa,Su "c:\AdminScripts\Exch_Copy\exch_cpy.cmd"
Sets the scheduler to run the script (Package extracted to c:\AdminScripts ) at 03:00 am on a
daily base(recommended)
MS Task Scheduler : Create a new scheduled task and follow the Instructions !
(alternatively download the new jt.exe which replaces at.exe as commandline tool for the new
and improved MS Task Scheduler at www.microsoft.com)

(...)

6. Scheduled KiXtart Scripts and System Event 1312 !

As a design feature KiXtart enumerates some Client Information at startup !
one of these informations is the user name of the current user ...
If the Scheduler Service is set to run under the System Account (default) KixTart will (still)
log an event with the id 1312 containing information about failure of WKSTA_USER_GET_INFO ...
This System event can either be ignored (it doesn't influence the execution of the script in question)
or can be solved by running the Scheduler Service under a specific User account (To be set in Control Panel -
Services).
If you decide to run the Scheduler Service under such an account, make sure that it has at least Backup Operator
rights (better local or domain admin) and has the privilege to logon as Service (SE_LOGON_AS_SERVICE)

---

additionally i would recommend having the batch file just like this sample:

code:

---

@echo off
%0\..\[folder]\kix32 %0\..\[folder]\script.kix
exit

---

hmmm ... please correct me if there's something wrong ! Wrote that Documentation after 10:00 pm

Jochen

_________________________