Inventory scheduling 1

[LawnBoy]

Stupid question, but I can't find an answer in the manuals...
If I schedule an inventory scan once a month, and a computer is turned off that day, will the scan run at the next opportunity? Or is it skipped?

 

[Provogeek]

It will run the next time it is brought on line.


The schedule is based on local workstation time. There isn't a network event that occures to tell workstations to run the inventory scanner. The workstation scheduler reads the policy schedule from eDirectory and stores it. When the PC boots, it will see that the execution date is before the current date and the last execution was either never or the previous scan date. So it will run the scan and send in it's inventory.

=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Brent Schmidt Certified nut case
Senior Network Engineer
Keep IT Simple

http://www.kiscc.com

 

[LawnBoy]

Thanks, that's what I expected.

 

[LawnBoy]

... but that's not what's happening. I have 4 workstations that were not powered up during the scheduled execution time, and they have not run the scan since (one of them is mine).

Currently the schedule is:
Every Wednesday
Start time 8:00am, End time 3pm.
"Randomly dispatch policy during time period" is checked.

Any ideas what to check? Zen is fully functional on these machines, one of them has run an inventory scan in the past.

 

[LawnBoy]

Err, make that
... one of them has run a scheduled inventory scan in the past.

 

[Provogeek]

Go to

%PROGRAMFILES%\Novell\ZENworks and look for the executable WMSCHED.EXE and see if that gives you any usefull info, mostly I want you to look at the NEXT secheduled run.

=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Brent Schmidt Certified nut case
Senior Network Engineer
Keep IT Simple

http://www.kiscc.com

 

[LawnBoy]

On the workstation that has run a scheduled inventory before (but missed the last execute time) it shows the next runtime to be tommorrow, which is what is scheduled in C1.

It also shows that a scheduled inventory has never been run before, which is not true.

 

[Provogeek]

I will try to duplicate this since I am currently working on an inventory schedule for my current client.

Over 1200 PC's spread out on a WAN with only 256k lines (240 sites, 5 PC's each site) with a bandwidth Nazi WAN admin that flips out when I peg the bandwidth on his WAN to 90% doing system wide Inventory in the middle of the night .... when everyone is sleeping and the only traffic is network monitoring traffic (and other typical network chatter). So I have been forced to create 240 Inventory policies for each site to do their inventory at different times through out the month = as much fun a waxing my butt.

So I will see if I can duplicate this and get back to you, I could have sworn it would just kick off, but I may just be wrong about that.

BTW: the whole "It also shows that a scheduled inventory has never been run before, which is not true." You may have gotten an inventory of the system before, but was it done with this exact version of your inventory policy? If you changed the policy in any way, the last run becomes never, because it has never run the policy in it's current configuration (or has never run that particular policy before).

=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Brent Schmidt Certified nut case
Senior Network Engineer
Keep IT Simple

http://www.kiscc.com

 

[LawnBoy]

Ah, yes, I believe I did modify the policy.