Reboot and shut down scripts failed on open dialogue window

Question

I have a headless server.
It is scheduled to shut down at 01.00 AM via the control panel.
I have a script (tested it works) to shut down the server should the control panel fail.
tell application "System Events"
shut down
end tell
Should this fail for some reason there is a second script that tell the computer to reboot shortly before the control panel schedule should start the server.
tell application "System Events"
restart
end tell
Yesterday it failed to execute either script. ITunes had been running and checked for updates and found one. It was installed and this resulted in the dialogue box appearing that wants you to promise not to steal the code etc. No person there to click OK so it hung and cancelled all processes.
So this stopped the shut down as well as the reboot.
The reason I have this script is as to make sure the computer has no hanging programmes or windows and shuts down and fires up on the desired time.
Anybody knows how to make it force to quit the programme?
Or better would be (and my preference too) to have it check if such windows are open and OK them before shutting down.
I know this is only a one in thousand occurrence, but it would be nice to have it not happen again, this time I was there to fix it.
Thanks.

Answer 1

'b4' - ?
Your problem is not with the provided instructions; but, the version of 'Script Editor', SE, you use.
I use SE, v. 2.0 (43) from a 'Panther' (MacOS X 10.3.x) installation. This application version works on PPC Macs running 'Panther' and 'Tiger' (MacOS X 10.4.x), and Intel Macs running 'Tiger' and (dog crap) 'Leopard' (MacOS X 10.5.x). At least here.
The features and (intuitive) ease of use of SE v. 2.0 are superior to its equivalents of 'Tiger' and (dog crap) 'Leopard'. Besides allowing one to view the 'Description' textarea field of a 'Run Only' script, SE v. 2.0 allows one to select all of the 'Suites' titles in the left side list, click on the right side panel, and then search for any character, word, or string - such as 'a', 'is', 'the', 'reference', 'in MHz' - anything. Try such a search with SE v. 2.1 and v. 2.2.
Try this example:
Select SEs' 'Window, Library' menu item. A window titled 'Standard Additions.asdictionary' will appear.
From the 'Library' windows' list, double click on 'StandardAdditions'.
SE v. 2.0 only - Select all of the suites of the left side panel, then click once on the right side panel.
In the search field (SE v 2.1 and v. 2.2) or search window (SE v. 2.0) enter 'in MHz', and press the <return> key. Did SE v. 2.1 or 2.2 find it? SE v. 2.0 goes right to it; even highlighting the search string result.
As an exercise - waste your time looking for 'in MHz' in SE v. 2.1 and / or v. 2.2.
Hint 01: Search for 'system'. Now you have a one (1) in four (4) chance of locating the user desired string (of 'in MHz') by viewing the text of each listed result.
Hint 02: Try searching by 'Description' - click on the search 'magnifying glass' and a popup button of choices appears - click on the 'Description' menu item. Still, unlike with SE v. 2.0, SE v. 2.1 or v. 2.2 does not actually highlight the located character, word, or string.
Ok, you finally located the line of 'in MHz'; but now - you want to see all of the commands of the related 'Suite' - how do you do it? In SE v. 2.0 you may have to scroll up a little; but, in SE v. 2.1 and v. 2.2 ...