Something tells me this is rather simple but I'm in a rush and can't quite wrap my head around this.
(I get the feeling I'm going to kick myself when somebody answers this with a one liner).
To make a long story short we need to change our Wireless key (Unable to make a smooth transition like setting up a 2nd SSID or anything).
I modified an Autoit script to make the changes which seems to be working well.
Just need to figure out deployment. I would like to deploy the package over the span for a couple days to make sure everybody get's it.
Then have the package trigger at say 5PM (When most of the Students and Staff have left) then we would change the key on the AP's.
The hope is that if they using their laptops the script would run and they would be ready for the next day (Or if they are onsite they might be down for 15 mins while we change keys). Those that have their machines turned off would automatically launch the cached script when they turn their machine the next day or at least when they login.
- I need my package to deploy itself and sit on the machine and run a certain time or when the machine is next turned on.
I'm guessing I could to accomplish this by writing a batch file that calls for LocalSch.exe
Which I guess eliminates the need to worry about the caching of the file prior to the change.
Which leaves me with the simple question of:
If my machine is off when my task is set to run by the local scheduler will it run the next time the machine is turned on?
Despite having possibly answered most of my question I'll leave it up here incase somebody has a better solution.