SPWakeUp Release Rss Feed

Created Release: 2.4 (Nov 13, 2009)

akennel — Fri, 13 Nov 2009 18:10:01 GMT

New features added. Now supports setting login name and password at run time. Also supports Basic and Digest authentication in addition to NTLM.

The new authentication code was created by Rafale. Many thanks for the addition!

Released: 2.4 (Nov 13, 2009)

Fri, 13 Nov 2009 18:10:01 GMT

Reviewed: 2.3a (Feb 25, 2009)

Dublette — Wed, 25 Feb 2009 15:05:59 GMT

Rated 5 Stars (out of 5) - Great tool! Definitely worth the download.

Reviewed: 2.3a (Feb 25, 2009)

Dublette — Wed, 25 Feb 2009 15:05:57 GMT

Rated 5 Stars (out of 5) - Great tool! Definitely worth the download.

Reviewed: 2.3a (Oct 17, 2008)

MrSciFi — Fri, 17 Oct 2008 10:17:51 GMT

Rated 4 Stars (out of 5) - The additional features make this simple tool flexible enough for varied environments.

Created Release: 2.3a (Oct 07, 2008)

akennel — Tue, 07 Oct 2008 19:35:08 GMT

(This latest release is a bug fix for version 2.3. It does not add any new features. If you are running 2.3, I'd recommend upgrading as the bug fixes should increase performance by up to 30%.)

Version 2.3 adds a new feature which allows you to exclude URLs from being woken. If you want to exclude a single site, use the option spwakeup.exe -exclude:http://server.mycompany.com/site.
If you need to exclude several sites, list them in file called exclude.conf located in the same folder as spwakeup.exe. Once listed on the exclude list, spwakeup will ignore that site, and any of its subsites.

Discovery mode is now turned on by default. If you want to disable discovery mode, use the runtime option
spwakeup.exe -nodiscover.

If you encounter trouble running against localhost, try specifying the site using the option
spwakeup.exe -site:http://server.mycompany.com, or use discovery mode.

If you need to wake up more than one Site, list them in a file called sites.conf located in the same folder as spwakeup.exe.

For complete instructions, run spwakeup.exe -help

Released: 2.3a (Oct 07, 2008)

Tue, 07 Oct 2008 19:35:08 GMT

Updated Release: 2.3 (Sep 22, 2008)

akennel — Mon, 22 Sep 2008 17:05:53 GMT

(If you are upgrading from an older version, please note that the -depth:XX run time option is no longer supported. If you have a scheduled task running spwakeup, you should remove this option.)

This release adds a new feature which allows you to exclude URLs from being woken. If you want to exclude a single site, use the option spwakeup.exe -exclude:http://server.mycompany.com/site.
If you need to exclude several sites, list them in file called exclude.conf located in the same folder as spwakeup.exe. Once listed on the exclude list, spwakeup will ignore that site, and any of its subsites.

Discovery mode is now turned on by default. If you want to disable discovery mode, use the runtime option
spwakeup.exe -nodiscover.

If you encounter trouble running against localhost, try specifying the site using the option
spwakeup.exe -site:http://server.mycompany.com, or use discovery mode.

If you need to wake up more than one Site, list them in a file called sites.conf located in the same folder as spwakeup.exe.

For complete instructions, run spwakeup.exe -help

Released: 2.3 (Sep 22, 2008)

Mon, 22 Sep 2008 17:05:52 GMT

Updated Release: 2.3 (Sep 22, 2008)

akennel — Mon, 22 Sep 2008 17:03:46 GMT

(If you are upgrading from an older version, please note that the -depth:XX run time option is no longer supported. If you have a scheduled task running spwakeup, you should remove this option.)

This release adds a new feature which allows you to exclude URLs from being woken. If you want to exclude a single site, use the option spwakeup.exe -exclude:http://server.mycompany.com/site.
If you need to exclude several sites, list them in file called exclude.conf located in the same folder as spwakeup.exe. Once listed on the exclude list, spwakeup will ignore that site, and any of its subsites.

Discovery mode is now turned on by default. If you want to disable discover mode, use the runtime option
spwakeup.exe -nodiscover.

If you encounter trouble running against localhost, try specifying the site using the option
spwakeup.exe -site:http://server.mycompany.com, using discovery mode.

If you need to wake up more than one Site, list them in a file called sites.conf located in the same folder as spwakeup.exe.

For complete instructions, run spwakeup.exe -help

Updated Release: 2.3 (Sep 22, 2008)

akennel — Mon, 22 Sep 2008 17:02:18 GMT

(If you are upgrading from an older version, please note that the -depth:XX run time option is no longer supported. If you have a scheduled task running spwakeup, you should remove this option.)

This release adds a new feature which allows you to exclude URLs from being woken. If you want to exclude a single site, use the option spwakeup.exe -exclude:http://server.mycompany.com/site.
If you need to exclude several sites, list them in file called exclude.conf located in the same folder as spwakeup.exe. Once listed on the exclude list, spwakeup will ignore that site, and any of its subsites.

Discovery mode is now turned on by default. If you want to disable discover mode, use the runtime option -nodiscover.

If you encounter trouble running against localhost, try specifying the site using the option
spwakeup.exe -site:http://server.mycompany.com, using discovery mode.

If you need to wake up more than one Site, list them in a file called sites.conf located in the same folder as spwakeup.exe.

For complete instructions, run spwakeup.exe -help

Created Release: 2.3 (Sep 22, 2008)

akennel — Mon, 22 Sep 2008 17:00:52 GMT

(If you are upgrading from an older version, please note that the -depth:XX run time option is no longer supported. If you have a scheduled task running spwakeup, you should remove this option.)

This release adds a new feature which allows you to exclude URLs from being woken. If you want to exclude a single site, use the option
spwakeup.exe -exclude:http://server.mycompany.com/site. If you need to exclude several sites, list them in file called exclude.conf located in the same folder as spwakeup.exe. Once listed on the exclude list, spwakeup will ignore that site, and any of its subsites.

Discovery mode is now turned on by default. If you want to disable discover mode, use the runtime option -nodiscover.

If you encounter trouble running against localhost, try specifying the site using the option
spwakeup.exe -site:http://server.mycompany.com, using discovery mode.

If you need to wake up more than one Site, list them in a file called sites.conf located in the same folder as spwakeup.exe.

For complete instructions, run spwakeup.exe -help

Created Release: 2.2 (Sep 15, 2008)

akennel — Mon, 15 Sep 2008 17:32:29 GMT

(If you are upgrading from an older version, please note that the -depth:XX run time option is no longer supported. If you have a scheduled task to run spwakeup, you'll need to remove this option.)

This release is mostly for fixing some bugs from the previous version. Most importantly, the app was crashing when trying to open localhost on some servers. I'm still trying to track down why, but it seems to be something in the server configuration where the web app is configured to use only the server name instead of the fully resolved hostname. I'm catching this error now, and am offering two work-arounds.
If you encounter trouble running against localhost, try specifying the site using the option spwakeup.exe -site:server.domain.com. Alternately, you can use the new option spwakeup -discover to have spwakeup find all the web applications on the server. This new option works for both stand-alone servers and server farms.

If you need to wake up more than one Site, list them in a file called sites.conf located in the same folder as spwakeup.exe.

For complete instructions, run spwakeup.exe -help

Released: 2.2 (Sep 15, 2008)

Mon, 15 Sep 2008 17:32:28 GMT

Created Release: 2.1 (Sep 12, 2008)

akennel — Sat, 13 Sep 2008 01:05:49 GMT

Long time between releases. Sorry about that, I've been side-tracked with other projects lately.

(If you are upgrading from an older version, please note that the -depth:XX run time option is no longer supported. If you have a scheduled task to run spwakeup, you'll need to remove this option.)

This is an almost complete rewrite of the application, focused on improving performance. The original version of the application was not much more than a glorified batch script. It used a starting URL(s) to shell out to stsadm.exe then parsed the results. Repeat until all the sub sites on your site were found then wake them up one by one.

This worked...but it was agonizingly slow. For example, my test server has 47 sites on it, and took almost 4 minutes to wake from a cold start. Most of that time was just shelling out to stsadm to build the site list. This new version uses .Net to connect directly to the server's configuration. This has reduced the run time on my test server to just 1 1/2 minutes.

One further note, the old version required you to set a search depth. This is no longer needed in the new version. It will find every Site Collection and Sub Site on the server regardless of depth.

If you are running your MOSS or WSS site on a single server, you can just run spwakeup.exe without any configuration files or run time options. It will search through the Site Collections hosted on http://localhost and wake up every sub site. (I did notice a bug on one server where localhost was failing. If this happens to you, try using the option -site:http://server.domain.com instead. I'm working on eliminating this bug.)

If you need to wake up more than one Site, list them in a file called sites.conf located in the same folder as spwakeup.exe.

For complete instructions, run spwakeup.exe -help

Released: 2.1 (Sep 12, 2008)

Sat, 13 Sep 2008 01:05:48 GMT

CREATED RELEASE: 2.0 (Apr 11, 2008)

Fri, 11 Apr 2008 17:37:47 GMT

Earlier versions of this application can be found here: http://code.msdn.microsoft.com/spwakeup

This is a ground-up rewrite of the application, focused on making it easier to use while improving performance.
In this new version, the searchdepth.conf file is no longer needed. Additionally, the sites.conf file is now optional. Performance has increased by about 30% compared to the last release.

If you are running your MOSS or WSS site on a single server, you can just run spwakeup.exe without any configuration files or run time options. It will search through the Site Collections hosted on http://localhost and find every site up to 3 levels deep.

If you need to wake up more than one Site, list them in a file called sites.conf located in the same folder as spwakeup.exe.

For complete instructions, run spwakeup.exe -help