Scheduled task..

[shawn]

I have a scheduled task that I need to run on a nightly basis. I can only
get it to work while logged on to Windows.

I am running Windows XP Pro on a domain running Windows Small Business
Server 2003.

I have everything setup in my task, I have the "run only if logged on" box
unticked and I do have the correct RUN AS and password.

I looked at the task and it says "Could Not Start". Doing some Googling I
found out that I should have "log on as batch job" in my security policy,
which I already did / always do.

I looked in the log file and all it says is ÿþ" (copied that directly from
the file).

Any help is most appreciated as this will save us about 45 minutes of time
during the work day where I can automatically schedule our backup at night
instead of during our work.

 

[shawn]

I did find one thing interesting.

While looking around I went back into my scheduled task's property. Under
the Security tab I didn't see myself listeed. I saw Administrators, System,
and one other. I forget what it was.. a long name like S-I-4-1-S blah blah.

So, I sat at that screen for a few seconds and the last one went away and
now I am in there.

 

[shawn]

Yeah, I rechecked.. when I go to security it gives me a very long number
everytime and takes about 8 or 10 seconds before my account shows up.

 

[Pegasus [MVP]]

I have a scheduled task that I need to run on a nightly basis. I can only
get it to work while logged on to Windows.

I am running Windows XP Pro on a domain running Windows Small Business
Server 2003.

I have everything setup in my task, I have the "run only if logged on" box
unticked and I do have the correct RUN AS and password.

I looked at the task and it says "Could Not Start". Doing some Googling I
found out that I should have "log on as batch job" in my security policy,
which I already did / always do.

I looked in the log file and all it says is ÿþ" (copied that directly from
the file).

Any help is most appreciated as this will save us about 45 minutes of time
during the work day where I can automatically schedule our backup at night
instead of during our work.

It is standard practice to use a dedicated account to run scheduled tasks.
Make sure that this account has sufficient privileges to access the
resources it needs to access.

 

[shawn]

Unfortunately I will not be able to do that. Our consultant would have to
create me an account on the server. He's hard to get a hold of and we don't
really like dealing with him unless we have to.

 

[Pegasus [MVP]]

If you don't like dealing with your consultant then it's time to find
someone else. This is the way I gained several clients for my own business:
They were disgruntled with my predecessors because they were hard to get
hold of, provided poor service and tended to be dogmatic.

As the owner of your business you MUST be given a domain admin
account/password, if only so that you are not toally dependent on your
consultant. A consultant must retain his clients by the service he provides
and by being competitive, not by denying his clients full access to their
systems. This sort of dependency will sooner or later result in a major
disaster.

 

[shawn]

Yep. I know. We've already been small jams a few times. The owner of our
company has our consultant be the only one who has a password to our email
accounts, our server, and our hardware firewall.

Sometimes he'll only read the subject of an email and assume that's all he
needs to know, when the email might say more. It's like sending an email to
someone with the subject of "Cats are finicky" but then in the email you ask
what that person is doing this weekend and if they want to hang out. This
person only read the subject.

Any calls to him to take up his time will be billed to us and if he can't
figure out our problem and needs to call a friend then we get billed for 2
people's time!

I think we'd consider shopping around for another firm or consultant, but
they can't even come in an give us an evaulation because we can't even let
the look at our server since it's passworded.