Greg,

I think the limitation is mostly for remote tasks (limited to 24hs, but it was long time ago I did something with it, so do not trust me). About the TimeZone offset... yes, I found that info was wrong, or my way of collecting it was wrong, and I created an ugly, ugly, very ugly program to get the right one (I think it works). If you are interested I can give you the whole package (The WMI function to create the task and 2 functions to get the timezone (Shrudder!) after I come back from lunch)

>>
>>You can use the Win32_ScheduledJob class to create and/or modify jobs locally or remotelly (although iirc the second alternative is limited)
>
>Yes, I recall that method too. It is a WMI means, but you are right is very limited in it features. Also, tasks create by a difficult to update.
>
>By the way. In my investigation I discovered that the AT.EXE has the same limitation as the Win32_ScheduledJob, and SchTasks.exe applies that wrong timezone offset, and will not apply the users password. If I recall right.