Another option you have is to create a different agent for those netbooks and change the inventory, vulscan, policy sync schedule to the desired times.
Yeah I thought about that since I'm going to have to make a new Agent configuration to take out activities during the day anyways.
But I’m trying to make the task a little more ridged to avoid problems in the event of large software deployments or patches.
Sine these machines are “sucktastic” also trying to avoid having these machine perform more than one task at a time.
The initial thought was to have the machines:
-Wakeup at 1am (give them time to boot)
-1:05 Run the Inventory scan
-1:10 run policy sync
-1:15 run vulscan
-1:20 run other tasks such as purgefile and clientdbutil
Then have the machines shutdown when they become inactive for 10 mins due to a Power Management policy
I’m assuming a download from a policy or patch manager would constitute as activity.
But I get the felling I’m asking for trouble doing it this way.
Which is why I thought it would be best to use some kind of script that runs the tasks one after the other then powers down.
Local Scheduled tasks would be my first choice, just my preference. As to the batch file you could easily run the commands with Start /wait.
Not sure why I didn't think of that when I posted... =o)
Here is what I came up with, am I missing something here?
@echo off echo -= Validate DB schema =- Start "" /wait "%ProgramFiles%\LANDesk\LDClient\clientdbutil.exe" /VALIDATE Start "" /wait "%ProgramFiles%\LANDesk\LDClient\purgefile.exe" $(TMCCacheDir)\preferredservers.STSITVS-LDCORE1.dat 0 echo -= Running Inventory Scan =- Start "" /wait "%ProgramFiles%\LANDesk\LDClient\LDIScn32.EXE" /NTT=<LANDeskCore>:5007 /S=STSITVS-LDCORE1 /I=HTTP://<LANDeskCore>/ldlogon/ldappl3.ldz /NOUI echo -= Running Policy Sync =- Start "" /wait "%ProgramFiles%\LANDesk\LDClient\policy.sync.exe" echo -= Running Vulscan =- Start "" /wait "%ProgramFiles%\LANDesk\LDClient\vulScan.exe" echo -= Powering down =- %WinDir%\system32\poweroff.exe 120