If you spend any amount of time working with Unix, you will come across Cron and the CronTab file.

What is it?

Cron allows you to schedule programs to run at specified intervals, like every Sunday at 1AM.

Now I can already hear it…”Steve, that is what the task scheduler is for in Windows”

While it is true you can schedule tasks in Windows, one big issue with task scheduler is how do you transfer scheduled tasks from one computer to another?

You could copy the folder c:\windows\tasks, but this is totally unsupported and it does not always work.

That is the beauty of Cron. Every bit of scheduling info is contained within the Crontab file.

If you want a group of servers to have the same scheduled jobs, you just need to sync this file. No registry hacks, no tricks. Just one file.

Not only that, since it is just a simple text file you can easily schedule jobs from PHP, PowerShell or VBScript…without any ActiveX or hooks into Windows. You just need to modify a simple text file.

There are a few Windows implementations out there…but most of them are quite old. We wanted something that would work on 2000 through 2008 x64 – so we built our own

To use it, download the setup file from our downloads page:

http://www.intelliadmin.com/index.php/downloads/

The install does not create any icons, or shortcuts. It installs all the application files into c:\program files\IntelliAdmin\Cron by default, and automatically starts the cron service (Named icronsvr).

There are two files for configuration, they are both in the same folder as the service.

The first to look at is the file config.cfg:

[Configuration]
status_enabled=true
status_handler=
path=


Here is what each option does:

status_enabled (true/false) – If set to true, each time a program is executed it is logged to a file named status.log in the same folder as the service

status_handler – If set to point to an executable file, it is executed each time a process is run. The first argument is the status text shown in status.log. (Example usage of this would be to send an email each time a process is executed by cron..using a bat file and a command like tool blat)

path – An alternative path for the crontab file. By default the service looks for the crontab in the same folder as the service. Setting this tells the service to look at the specified folder for the crontab file

The next is the actual crontab file. It roughly follows the same format as the Unix crontab

The file is formatted in this way:

[M] [H] [D] [M] [DOW] [Process Name] [Process Arguments]

M – The minute that the process should be executed (0-59)
H – The hour that the process should be executed (0-23)
D – The day that the process should be executed (1-31)
M – The month that the process should be executed (1-12)
DOW – The day of the week that the process should be executed (0-6 Sunday = 0, Monday = 1, Etc)

Note: Our format does not support names such as THU, or JAN…only numerical values

Each section can:

-Have a range of values like this: 12-24 (All items from 12 to 24)
-Have a list of values like this: 12,13,14,15
-Include all possible values like this: *
-Skip values using the / like this: 0-59/5 (This would only include 0,5,10,15,20,etc)

Lets put it all together. If we wanted a process to run every 5 minutes we would create a line like this in our crontab file:

*/5 * * * * c:\process.bat

See how the skip value works? We specified the * for the minute section (All minutes), and then told it to skip 5. This means it will run at 0, 5, 10, 15, 20, etc.

If you wanted to run a process every Sunday at 1 pm:

00 01 * * 00 c:\process.bat

Or how about, only every Sunday from June to the end of the year:

00 01 * 06-12 00 c:\process.bat

At 15, and 30 minutes past every hour:

15,30 * * * * c:\process.bat

This might give you a clearer picture:

*     *     *   *    *     C:\SomeEXE.EXE ARG1 ARG2 ARG3
-     -     -   -    -
|     |     |   |    |
|     |     |   |    +----- day of week (0 - 6) (Sunday=0)
|     |     |   +------- month (1 - 12)
|     |     +--------- day of        month (1 - 31)
|     +----------- hour (0 - 23)
+------------- min (0 - 59)

It takes a little time to get used to the format, but once you do it is a breeze to work with.

A few things to think about when using this:

-Make sure you secure the crontab file by only allowing ‘System’ and Administrator write access. Otherwise a standard user could simply alter the crontab file and start running stuff as ‘System’

-The programs are run in the context of a service. By default the user account is ‘System’, and for security reasons it does not have network share access. If you want to allow access to network shares you would have to go into the settings of the IntelliAdmin Cron Service, and have it login as a user with the appropriate rights.

-Since it is a service, make sure your program does not pop up forms or message boxes…otherwise they will just get stuck and you will never see them. Test…test…test before you deploy.

If you have any other features you would like to add to this little tool, let us know and we will see what we can do.

This is a quick one – The final version of Remote Control 4.0 has been released. Current customers with an upgrade protection license should receive their email within 24 hours. If you did not, please send an email to support@intelliadmin.com and we will take care of you as soon as possible.

Here are the screenshots:
http://www.intelliadmin.com/RemoteControl4_ScreenShots.htm

And a link to the trial download:
setupex.exe

We have been working hard on the new version of IntelliAdmin Remote Control.

Some things that will be in the new version:

Screen scaling – The client will automatically shrink the view to fit the screen within the window. With huge resolutions, you no longer are forced to constantly scroll around

Alpha Capture Disable – Applications like Office 2007 need alpha capture turned on, or parts of their windows will not be sent back to the remote client. This was always turned on in 3.x. Once side effect of this setting is the mouse flickers with some video cards. Now you have the option to turn this off and keep the mouse flicker to a minimum – great if you are given the task of watching a user without them knowing.

Screen Shots – You can easily save the current view in the client window to a JPG file. This is good for keeping a visual log of crash events, or activity of users.

Auto-Reconnect – When a connection is lost, it will automatically attempt to re-establish the connection

Computer Lists – We have loaded it up with options for getting lists of computers. You can get them from Windows Networking like you do right now, but in addition you can import them from an XML file, add them manually, or update them in real time from a http URL – this allows you to create a common computer list that all administrators can see and use.

Computer Search – This is the big one. When talking with customers the biggest complaint is finding a single computer among 1000s. When remote control connects to a machine, it will pull username, computername, and operating system info. All of this is stored in a database. When you click on the find button in the client window, you are shown a full listing of computers:

When you start typing in the search box at the top it will narrow down your results immediately. So, if you get a call from a user you can simply start typing their username and their computer will be automatically filtered out – no more digging around for their IP address, or computer name.

Lots of time was spent to make sure this was efficient – we threw the client on an old XP machine and it was able to search 10,000 computer records in less than 1 second.

Everything about the “find computer” section was designed to reduce the time it takes to find and control a computer, and make you more productive.

Why am I teasing you with all of this? Because I want you to join our beta program. To join, simply follow this link:

Make sure you check the 4.0 beta option.

The final release date will be June 27th. If you order Remote Control 3.2 right now the upgrade protection option will allow you to get a free upgrade when it comes out – a good deal since this will give you close to 40% in savings

While we are at it. What do you want to see in 4.5? File Transfers, Chat, or what other wish do you have for the next version. Post in the comments.

Since 2000 every version of Windows uses object reuse protection. When you create a file, the space on the hard drive for that file will be zeroed out.

Another way of looking at this is when a file is created, Windows will make it impossible to see what was there before.

But what about right after you delete a file? Nothing has been written to that space yet. What is on the physical hard drive? The entire file of course. Not good if the file is highly confidential.

What if you wanted to delete a file securely?

There are plenty of tools out there that can do this, and most of them cost quite a bit of money. But there is a free alternative.

It is called SDelete and it is from Microsoft:

http://download.sysinternals.com/Files/SDelete.zip

How does it work?

Simply download the program and run it from the command line. By default it will only complete 1 pass when erasing a file. I would suggest overriding that with a higher number – the higher the better, but it will be slower.

Lets delete a file with it, using 25 passes:

sdelete.exe -p 25 FileToDelete.zip

This will securely delete FileToDelete.zip

SDelete implements the Department of Defense clearing and sanitizing standard DOD 5220.22-M. This will give you confidence that once deleted with this tool, your file is gone forever. Note that it does delete the file, but the file name is still recoverable from the file system (Make sure the file name itself does not have any revealing information).

The full list of possible commands for SDelete are:

usage: sdelete [-p passes] [-s] [-q]
sdelete [-p passes] [-z|-c] [drive letter]
-c Zero free space (good for virtual disk optimization)
-p passes Specifies number of overwrite passes (default is 1)
-q Don’t print errors (Quiet)
-s Recurse subdirectories
-z Clean free space

It supports wildcards too. So if you wanted to securely delete an entire folder you can call it like this:

C:\>sdelete c:\temp\*.*

SDelete is set for 1 pass.
c:\temp\Eula.txt…deleted.
c:\temp\Import.csv…deleted.
c:\temp\readme.txt…deleted.
c:\temp\sdelete.exe…deleted.
c:\temp\VCdControlTool.exe…deleted.
c:\temp\VCdRom.sys…deleted.

If you have files that need to remain secure, SDelete is a great way to make sure they are removed from your hard drive.

I have quite a few scripts that are run by task scheduler on my server.  One of the ways I track the results is by writing to a text file in a common share. After a while this can become a little ridiculous to follow.

Recently I discovered that it is possible to create your own Application, or System events from a script that will show up in the Windows event viewer.

To create your own events, you need to use the “eventcreate” command line argument. This command line program is available in Windows XP, 2003, Vista, and Windows 7 – unfortunately not in Windows 2000.

How can you use it?

Let me take a simple example, and then I will walk you through writing an event to the log. In one of my scripts I have an xcopy that I check for errors:

:EXIT

The above script looks for the different error codes that XCOPY can return – right now we won’t concentrate on that. What we want to do is add our EventCreate command right around where we have our “REM FAILURE”

There are a few details we need to collect together before we can call our command. First we want to determine which event log we want to write.

For our example I want to pick the “Application” log

Then, we need to determine an event source. The event source specifies the text that will be shown as the source in the log. The trick is you need to pick something unique that won’t have a name conflict with Windows, or other scripts. This means don’t pick DNS, VSS, or W32Time – or any common windows service name. At the same time, no spaces, and keep it short.

I picked XCOPYRESLT

Next we need to pick an event type. Our choices are Information, Warning, or Error. In the case of my example, I am only going to report errors so the obvious pick is “Error”.

What else? Well an event ID is needed. This is an arbitrary number that you may pick to suite your own custom needs. 1000 sounds good to me.

And finally, a description. “Domain Controller XCOPY Failure” seems like an easy description.

Now, lets bring it all together at the command line:

eventcreate /l Application /so XCOPYRESLT /t Error /id 1000 /d “Domain Controller XCOPY Failure”

One run at the prompt:

Now, if we take a peek at the event log:

So there you go. Custom event log items right from your batch file. For more detailed information on the eventcreate command, visit this section on Microsoft Technet.

We have updated our Network Administrator product – You can use it to deploy the patch, and verify it’s installation on machines across your network. Also we have updated the free patch More info about it here

Update 10/25/2009: We have updated our patch again. Both the patch, and Network Administrator have been updated with the latest

Update 2/12/2007 12:57 AM EST – We created a different patch for Windows 98/ME. Visit here for more information

Update 2/12/2007 12:56 AM EST – We want to also remind you that Outlook, Exchange and Java have their own issues. This patch will not fix that. Please see these links for more info on fixing those issues:

See this article for Exchange, and Outlook
http://www.microsoft.com/windows/timezone/dst2007.mspx

For Java:
http://java.sun.com/developer/technicalArticles/Intl/USDST/

Update for 2009:

We have updated our free DST patch for Windows NT, 2000, 2003 and XP. You don’t need it for Vista, 2008, or Windows 7 since Microsoft still supports those operating systems

For Windows XP, you only need it if you don’t want to be forced to upgrade to the latest service pack, and 2000 and NT, you need it if you want your time to be right. There were a few changes across the world since last year, so we have released an update

You can download the free application from here:

Daylight Saving Fix Download

You can use Network Administrator to deploy it across your network, since it has the updated settings too:

You can download it from here:

Network Administrator Download

Post from 2007 Continues below:

You may have forgotten by now, but two years ago the US government changed the dates for daylight saving time. When the law was passed it was set to take effect in 2007.

Well, here we are. It is 2007, and Microsoft has published updates for XP, and 2003. But…No update for 2000 Workstation, or any of the server editions.

This is a huge problem for many organizations. I know some companies that have hundreds of Windows 2000 boxes. The thought that they will need to upgrade to XP or 2003 (Just for this) is a nightmare. Microsoft is providing a hotfix – but only to the companies that have an extended support contract. To their credit, Microsoft does provide a registry workaround for the rest of us.

The workaround that Microsoft provides is not easy to follow. Check out the KB article at Microsoft.

We have created a utility that will update any machine to the new daylight saving format (XP, NT, 2000, 2003, Vista). Obviously you only need it for 2000, or NT since those operating systems have dropped off support.

It updates Daylight Saving Time (Yes it is Saving, not Savings) in these time zones:

-Alaska Standard Time Zone
-Central Standard Time Zone
-Eastern Standard Time Zone
-Mountain Standard Time Zone
-Pacific Standard Time Zone
-Atlantic Standard Time Zone (Canada)
-Newfoundland Standard Time Zone (Canada)

If we are missing another US timezone that supports daylight saving time, please let us know by emailing support@intelliadmin.com

The utility can install, or uninstall the change. It runs without any setup and requires no extra DLLs or runtime. It is less than 1mb, so you can put it on a flash drive:

It can run silently from the command line if you use these options:

Install:

DaylightSavingFix.exe /qinstall

UnInstall:

DaylightSavingFix.exe /quninstall

Please note that the program must be run as administrator since it access HKEY_LOCAL_MACHINE

If you want to roll it out to multiple machines we have updated our Network Administrator product to install the patch.

Both can be downloaded from our downloads section