<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="/rss.xsl"?><rss version="2.0"><channel><title>sbs Release Rss Feed</title><link>http://www.codeplex.com/sbs/Release/ProjectReleases.aspx</link><description>sbs Release Rss Description</description><item><title>Updated Release: Server Specification Information (Jan 08, 2012)</title><link>http://sbs.codeplex.com/releases/view/80200</link><description>&lt;div class="wikidoc"&gt;•Server Specification Information : Adds Server Specification as reporting in SBS 2003 reports into SBS 2008 Security page and daily reports.&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>Bitzie</author><pubDate>Mon, 09 Jan 2012 08:03:26 GMT</pubDate><guid isPermaLink="false">Updated Release: Server Specification Information (Jan 08, 2012) 20120109080326A</guid></item><item><title>Released: Server Specification Information (Jan 08, 2012)</title><link>http://sbs.codeplex.com/releases/view/80200</link><description>
&lt;div class="wikidoc"&gt;•Server Specification Information : Adds Server Specification as reporting in SBS 2003 reports into SBS 2008 Security page and daily reports.&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
</description><author></author><pubDate>Mon, 09 Jan 2012 08:03:26 GMT</pubDate><guid isPermaLink="false">Released: Server Specification Information (Jan 08, 2012) 20120109080326A</guid></item><item><title>Updated Release: FSE Extension Adds number of attachments scanned (Jan 08, 2012)</title><link>http://sbs.codeplex.com/releases/view/80201</link><description>&lt;div class="wikidoc"&gt;•FSE Extension : Adds number of attachments scanned, cleaned and deleted by FSE into SBS 2008 Security page and daily reports&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>Bitzie</author><pubDate>Mon, 09 Jan 2012 08:01:56 GMT</pubDate><guid isPermaLink="false">Updated Release: FSE Extension Adds number of attachments scanned (Jan 08, 2012) 20120109080156A</guid></item><item><title>Released: FSE Extension Adds number of attachments scanned (Jan 08, 2012)</title><link>http://sbs.codeplex.com/releases/view/80201</link><description>
&lt;div class="wikidoc"&gt;•FSE Extension : Adds number of attachments scanned, cleaned and deleted by FSE into SBS 2008 Security page and daily reports&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
</description><author></author><pubDate>Mon, 09 Jan 2012 08:01:56 GMT</pubDate><guid isPermaLink="false">Released: FSE Extension Adds number of attachments scanned (Jan 08, 2012) 20120109080156A</guid></item><item><title>Updated Release: Automated Deletion of WSUS Logs (Oct 30, 2010)</title><link>http://sbs.codeplex.com/releases/view/54880</link><description>&lt;div class="wikidoc"&gt;To deploy this automation&lt;br /&gt;&lt;br /&gt;Download zip file to servers desktop&lt;br /&gt;
&lt;h2&gt;STEP I&lt;/h2&gt;Extract it, that will create an install folder called AutoWSUSlogdeletion on your desktop.&lt;br /&gt;Open the folder&lt;br /&gt;
&lt;h2&gt;STEP II&lt;/h2&gt;You will need to right click and select &lt;b&gt;edit&lt;/b&gt; on the enclosed xml file &lt;i&gt;&lt;b&gt;&amp;quot;WSUS Log file cleanup.xml&amp;quot;&lt;/b&gt;&lt;/i&gt;.&lt;br /&gt;      Find the line &lt;i&gt;&lt;b&gt;&amp;lt;Author&amp;gt;DOMAIN\adminuser&amp;lt;/Author&amp;gt;&lt;/b&gt;&lt;/i&gt;&lt;br /&gt;      and replace DOMAIN with you domain name ALL CAPS&lt;br /&gt;      then replace ADMINIUSER with you domain administrator account&lt;br /&gt;      Then do the same for the line&lt;br /&gt;      &lt;i&gt;&lt;b&gt;&amp;lt;UserId&amp;gt;DOMAIN\adminuser&amp;lt;/UserId&amp;gt;&lt;/b&gt;&lt;/i&gt; 14 lines down&lt;br /&gt;   &lt;b&gt;DO NOT ADD ANYTHING ELSE TO THE EML FILE - IT WILL CAUSE ERRORS&lt;/b&gt;&lt;br /&gt;
&lt;h2&gt;STEP III&lt;/h2&gt;Now open the Task Scheduler&lt;br /&gt;and in the left colum under the Microsoft - Windows folders, create a new folder called &lt;i&gt;&lt;b&gt;WSUS Cleanup&lt;/b&gt;&lt;/i&gt;.&lt;br /&gt;Select that folder in the left colum and then in the far right colum click &lt;b&gt;import&lt;/b&gt;&lt;br /&gt;Then navigate to the folder &lt;i&gt;&lt;b&gt;&amp;quot;C:\Program Files\Windows Small Business Server\WSUS Log File Cleanup&amp;quot;&lt;/b&gt;&lt;/i&gt;&lt;br /&gt;Now select the &lt;i&gt;&lt;b&gt;&amp;quot;WSUS log file cleanup.xml&amp;quot;&lt;/b&gt;&lt;/i&gt; file and click &lt;b&gt;open&lt;/b&gt;&lt;br /&gt;Adjust the settings to your prefered configuration, times and day/date to run.&lt;br /&gt;
&lt;h2&gt;STEP IV&lt;/h2&gt;Now next step is to edit the powershell file to match your folder names in the &lt;i&gt;&lt;b&gt;C:\inetpub\logs\LogFiles&lt;/b&gt;&lt;/i&gt; directory&lt;br /&gt;In the &lt;i&gt;&lt;b&gt;AutoWSUSlogdeletion&lt;/b&gt;&lt;/i&gt; folder on the desktop right click on the &lt;i&gt;&lt;b&gt;&amp;quot;DeleteOldFiles.ps1&amp;quot;&lt;/b&gt;&lt;/i&gt; file&lt;br /&gt;     Select &lt;b&gt;Open&lt;/b&gt; to open in notepad to edit&lt;br /&gt;       OR&lt;br /&gt;     Select &lt;b&gt;Edit&lt;/b&gt; to edit with the Powershell GUI editor&lt;br /&gt;In the file you will find a Function section for each folder that exists&lt;br /&gt;They each begin Function DeleteOldLogFileinFolder1  - Number 1 - 8&lt;br /&gt;In each of the section you need to edit the line&lt;br /&gt;&lt;i&gt;&lt;b&gt;$TargetFolder = &amp;quot;C:\inetpub\logs\LogFiles\W3SVC1&amp;quot;&lt;/b&gt;&lt;/i&gt;&lt;br /&gt;To match the name of your folders (these are all crated with random names by WSUS install.&lt;br /&gt;
&lt;h2&gt;STEP V - Last step&lt;/h2&gt;Then right click on the &lt;i&gt;&lt;b&gt;install.bat&lt;/b&gt;&lt;/i&gt; and &lt;b&gt;run as administrator&lt;/b&gt;. It will create a directory and copy the files &lt;br /&gt;you&amp;#39;ve just edited, for the automated task&lt;br /&gt;to - &amp;quot;C:\Program Files\Windows Small Business Server\WSUS Log File Cleanup&amp;quot;*_&lt;br /&gt;&lt;br /&gt;And you finished.&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>theisdept</author><pubDate>Mon, 01 Nov 2010 01:53:36 GMT</pubDate><guid isPermaLink="false">Updated Release: Automated Deletion of WSUS Logs (Oct 30, 2010) 20101101015336A</guid></item><item><title>Released: Automated Deletion of WSUS Logs (Oct 30, 2010)</title><link>http://sbs.codeplex.com/releases/view/54880</link><description>
&lt;div class="wikidoc"&gt;To deploy this automation&lt;br&gt;
&lt;br&gt;
Download zip file to servers desktop&lt;br&gt;
&lt;h2&gt;STEP I&lt;/h2&gt;
Extract it, that will create an install folder called AutoWSUSlogdeletion on your desktop.&lt;br&gt;
Open the folder&lt;br&gt;
&lt;h2&gt;STEP II&lt;/h2&gt;
You will need to right click and select &lt;b&gt;edit&lt;/b&gt; on the enclosed xml file &lt;i&gt;&lt;b&gt;&amp;quot;WSUS Log file cleanup.xml&amp;quot;&lt;/b&gt;&lt;/i&gt;.&lt;br&gt;
Find the line &lt;i&gt;&lt;b&gt;&amp;lt;Author&amp;gt;DOMAIN\adminuser&amp;lt;/Author&amp;gt;&lt;/b&gt;&lt;/i&gt;&lt;br&gt;
and replace DOMAIN with you domain name ALL CAPS&lt;br&gt;
then replace ADMINIUSER with you domain administrator account&lt;br&gt;
Then do the same for the line&lt;br&gt;
&lt;i&gt;&lt;b&gt;&amp;lt;UserId&amp;gt;DOMAIN\adminuser&amp;lt;/UserId&amp;gt;&lt;/b&gt;&lt;/i&gt; 14 lines down&lt;br&gt;
&lt;b&gt;DO NOT ADD ANYTHING ELSE TO THE EML FILE - IT WILL CAUSE ERRORS&lt;/b&gt;&lt;br&gt;
&lt;h2&gt;STEP III&lt;/h2&gt;
Now open the Task Scheduler&lt;br&gt;
and in the left colum under the Microsoft - Windows folders, create a new folder called
&lt;i&gt;&lt;b&gt;WSUS Cleanup&lt;/b&gt;&lt;/i&gt;.&lt;br&gt;
Select that folder in the left colum and then in the far right colum click &lt;b&gt;import&lt;/b&gt;&lt;br&gt;
Then navigate to the folder &lt;i&gt;&lt;b&gt;&amp;quot;C:\Program Files\Windows Small Business Server\WSUS Log File Cleanup&amp;quot;&lt;/b&gt;&lt;/i&gt;&lt;br&gt;
Now select the &lt;i&gt;&lt;b&gt;&amp;quot;WSUS log file cleanup.xml&amp;quot;&lt;/b&gt;&lt;/i&gt; file and click
&lt;b&gt;open&lt;/b&gt;&lt;br&gt;
Adjust the settings to your prefered configuration, times and day/date to run.&lt;br&gt;
&lt;h2&gt;STEP IV&lt;/h2&gt;
Now next step is to edit the powershell file to match your folder names in the &lt;i&gt;
&lt;b&gt;C:\inetpub\logs\LogFiles&lt;/b&gt;&lt;/i&gt; directory&lt;br&gt;
In the &lt;i&gt;&lt;b&gt;AutoWSUSlogdeletion&lt;/b&gt;&lt;/i&gt; folder on the desktop right click on the
&lt;i&gt;&lt;b&gt;&amp;quot;DeleteOldFiles.ps1&amp;quot;&lt;/b&gt;&lt;/i&gt; file&lt;br&gt;
Select &lt;b&gt;Open&lt;/b&gt; to open in notepad to edit&lt;br&gt;
OR&lt;br&gt;
Select &lt;b&gt;Edit&lt;/b&gt; to edit with the Powershell GUI editor&lt;br&gt;
In the file you will find a Function section for each folder that exists&lt;br&gt;
They each begin Function DeleteOldLogFileinFolder1 - Number 1 - 8&lt;br&gt;
In each of the section you need to edit the line&lt;br&gt;
&lt;i&gt;&lt;b&gt;$TargetFolder = &amp;quot;C:\inetpub\logs\LogFiles\W3SVC1&amp;quot;&lt;/b&gt;&lt;/i&gt;&lt;br&gt;
To match the name of your folders (these are all crated with random names by WSUS install.&lt;br&gt;
&lt;h2&gt;STEP V - Last step&lt;/h2&gt;
Then right click on the &lt;i&gt;&lt;b&gt;install.bat&lt;/b&gt;&lt;/i&gt; and &lt;b&gt;run as administrator&lt;/b&gt;. It will create a directory and copy the files
&lt;br&gt;
you&amp;#39;ve just edited, for the automated task&lt;br&gt;
to - &amp;quot;C:\Program Files\Windows Small Business Server\WSUS Log File Cleanup&amp;quot;*_&lt;br&gt;
&lt;br&gt;
And you finished.&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
</description><author></author><pubDate>Mon, 01 Nov 2010 01:53:36 GMT</pubDate><guid isPermaLink="false">Released: Automated Deletion of WSUS Logs (Oct 30, 2010) 20101101015336A</guid></item><item><title>Updated Release: Automated Deletion of WSUS Logs (Oct 30, 2010)</title><link>http://sbs.codeplex.com/releases/view/54880</link><description>&lt;div class="wikidoc"&gt;To deploy this automation&lt;br /&gt;&lt;br /&gt;Download zip file to servers desktop&lt;br /&gt;
&lt;h2&gt;STEP I&lt;/h2&gt;Extract it, that will create an install folder called AutoWSUSlogdeletion on your desktop.&lt;br /&gt;Open the folder&lt;br /&gt;
&lt;h2&gt;STEP II&lt;/h2&gt;You will need to right click and select &lt;b&gt;edit&lt;/b&gt; on the enclosed xml file &lt;i&gt;&lt;b&gt;&amp;quot;WSUS Log file cleanup.xml&amp;quot;&lt;/b&gt;&lt;/i&gt;.&lt;br /&gt;      Find the line &lt;i&gt;&lt;b&gt;&amp;lt;Author&amp;gt;DOMAIN\adminuser&amp;lt;/Author&amp;gt;&lt;/b&gt;&lt;/i&gt;&lt;br /&gt;      and replace DOMAIN with you domain name ALL CAPS&lt;br /&gt;      then replace ADMINIUSER with you domain administrator account&lt;br /&gt;      Then do the same for the line&lt;br /&gt;      &lt;i&gt;&lt;b&gt;&amp;lt;UserId&amp;gt;DOMAIN\adminuser&amp;lt;/UserId&amp;gt;&lt;/b&gt;&lt;/i&gt; 14 lines down&lt;br /&gt;   &lt;b&gt;DO NOT ADD ANYTHING ELSE TO THE EML FILE - IT WILL CAUSE ERRORS&lt;/b&gt;&lt;br /&gt;
&lt;h2&gt;STEP III&lt;/h2&gt;Now open the Task Scheduler&lt;br /&gt;and in the left colum under the Microsoft - Windows folders, create a new folder called &lt;i&gt;&lt;b&gt;WSUS Cleanup&lt;/b&gt;&lt;/i&gt;.&lt;br /&gt;Select that folder in the left colum and then in the far right colum click &lt;b&gt;import&lt;/b&gt;&lt;br /&gt;Then navigate to the folder &lt;i&gt;&lt;b&gt;&amp;quot;C:\Program Files\Windows Small Business Server\WSUS Log File Cleanup&amp;quot;&lt;/b&gt;&lt;/i&gt;&lt;br /&gt;Now select the &lt;i&gt;&lt;b&gt;&amp;quot;WSUS log file cleanup.xml&amp;quot;&lt;/b&gt;&lt;/i&gt; file and click &lt;b&gt;open&lt;/b&gt;&lt;br /&gt;Adjust the settings to your prefered configuration, times and day/date to run.&lt;br /&gt;
&lt;h2&gt;STEP IV&lt;/h2&gt;Now next step is to edit the powershell file to match your folder names in the &lt;i&gt;&lt;b&gt;C:\inetpub\logs\LogFiles&lt;/b&gt;&lt;/i&gt; directory&lt;br /&gt;In the &lt;i&gt;&lt;b&gt;AutoWSUSlogdeletion&lt;/b&gt;&lt;/i&gt; folder on the desktop right click on the &lt;i&gt;&lt;b&gt;&amp;quot;DeleteOldFiles.ps1&amp;quot;&lt;/b&gt;&lt;/i&gt; file&lt;br /&gt;     Select &lt;b&gt;Open&lt;/b&gt; to open in notepad to edit&lt;br /&gt;       OR&lt;br /&gt;     Select &lt;b&gt;Edit&lt;/b&gt; to edit with the Powershell GUI editor&lt;br /&gt;In the file you will find a Function section for each folder that exists&lt;br /&gt;They each begin Function DeleteOldLogFileinFolder1  - Number 1 - 8&lt;br /&gt;In each of the section you need to edit the line&lt;br /&gt;&lt;i&gt;&lt;b&gt;$TargetFolder = &amp;quot;C:\inetpub\logs\LogFiles\W3SVC1&amp;quot;&lt;/b&gt;&lt;/i&gt;&lt;br /&gt;To match the name of your folders (these are all crated with random names by WSUS install.&lt;br /&gt;
&lt;h2&gt;STEP V - Last step&lt;/h2&gt;Then right click on the &lt;i&gt;&lt;b&gt;install.bat&lt;/b&gt;&lt;/i&gt; and &lt;b&gt;run as administrator&lt;/b&gt;. It will create a directory and copy the files needed for the automated task&lt;br /&gt;at - &amp;quot;C:\Program Files\Windows Small Business Server\WSUS Log File Cleanup&amp;quot;*_&lt;br /&gt;&lt;br /&gt;And you finished.&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>theisdept</author><pubDate>Mon, 01 Nov 2010 01:52:17 GMT</pubDate><guid isPermaLink="false">Updated Release: Automated Deletion of WSUS Logs (Oct 30, 2010) 20101101015217A</guid></item><item><title>Created Release: Automated Deletion of WSUS Logs (Oct 30, 2010)</title><link>http://sbs.codeplex.com/releases?ReleaseId=54880</link><description>&lt;div class="wikidoc"&gt;To deploy this automation&lt;br /&gt;&lt;br /&gt;Download zip file to servers desktop&lt;br /&gt;
&lt;h2&gt;STEP I&lt;/h2&gt;Extract it, that will create an install folder called AutoWSUSlogdeletion on your desktop.&lt;br /&gt;Open the folder&lt;br /&gt;
&lt;h2&gt;STEP II&lt;/h2&gt;You will need to right click and select &lt;b&gt;edit&lt;/b&gt; on the enclosed xml file &lt;i&gt;&lt;b&gt;&amp;quot;WSUS Log file cleanup.xml&amp;quot;&lt;/b&gt;&lt;/i&gt;.&lt;br /&gt;      Find the line &lt;i&gt;&lt;b&gt;&amp;lt;Author&amp;gt;DOMAIN\adminuser&amp;lt;/Author&amp;gt;&lt;/b&gt;&lt;/i&gt;&lt;br /&gt;      and replace DOMAIN with you domain name ALL CAPS&lt;br /&gt;      then replace ADMINIUSER with you domain administrator account&lt;br /&gt;      Then do the same for the line&lt;br /&gt;      &lt;i&gt;&lt;b&gt;&amp;lt;UserId&amp;gt;DOMAIN\adminuser&amp;lt;/UserId&amp;gt;&lt;/b&gt;&lt;/i&gt; 14 lines down&lt;br /&gt;   &lt;b&gt;DO NOT ADD ANYTHING ELSE TO THE EML FILE - IT WILL CAUSE ERRORS&lt;/b&gt;&lt;br /&gt;
&lt;h2&gt;STEP III&lt;/h2&gt;Now open the Task Scheduler&lt;br /&gt;and in the left colum under the Microsoft - Windows folders, create a new folder called &lt;i&gt;&lt;b&gt;WSUS Cleanup&lt;/b&gt;&lt;/i&gt;.&lt;br /&gt;Select that folder in the left colum and then in the far right colum click &lt;b&gt;import&lt;/b&gt;&lt;br /&gt;Then navigate to the folder &lt;i&gt;&lt;b&gt;&amp;quot;C:\Program Files\Windows Small Business Server\WSUS Log File Cleanup&amp;quot;&lt;/b&gt;&lt;/i&gt;&lt;br /&gt;Now select the &lt;i&gt;&lt;b&gt;&amp;quot;WSUS log file cleanup.xml&amp;quot;&lt;/b&gt;&lt;/i&gt; file and click &lt;b&gt;open&lt;/b&gt;&lt;br /&gt;Adjust the settings to your prefered configuration, times and day/date to run.&lt;br /&gt;
&lt;h2&gt;STEP IV&lt;/h2&gt;Now next step is to edit the powershell file to match your folder names in the &lt;i&gt;&lt;b&gt;C:\inetpub\logs\LogFiles&lt;/b&gt;&lt;/i&gt; directory&lt;br /&gt;In the &lt;i&gt;&lt;b&gt;AutoWSUSlogdeletion&lt;/b&gt;&lt;/i&gt; folder on the desktop right click on the &lt;i&gt;&lt;b&gt;&amp;quot;DeleteOldFiles.ps1&amp;quot;&lt;/b&gt;&lt;/i&gt; file&lt;br /&gt;     Select &lt;b&gt;Open&lt;/b&gt; to open in notepad to edit&lt;br /&gt;       OR&lt;br /&gt;     Select &lt;b&gt;Edit&lt;/b&gt; to edit with the Powershell GUI editor&lt;br /&gt;In the file you will find a Function section for each folder that exists&lt;br /&gt;They each begin Function DeleteOldLogFileinFolder1  - Number 1 - 8&lt;br /&gt;In each of the section you need to edit the line&lt;br /&gt;&lt;i&gt;&lt;b&gt;$TargetFolder = &amp;quot;C:\inetpub\logs\LogFiles\W3SVC1&amp;quot;&lt;/b&gt;&lt;/i&gt;&lt;br /&gt;To match the name of your folders (these are all crated with random names by WSUS install.&lt;br /&gt;
&lt;h2&gt;STEP V - Last step&lt;/h2&gt;Then right click on the &lt;i&gt;&lt;b&gt;install.bat&lt;/b&gt;&lt;/i&gt; and &lt;b&gt;run as administrator&lt;/b&gt;. It will create a directory for the task files to be stored at &lt;br /&gt;&lt;i&gt;&lt;b&gt;&amp;quot;C:\Program Files\Windows Small Business Server\WSUS Log File Cleanup&amp;quot;&lt;/b&gt;&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;And you finished.&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>theisdept</author><pubDate>Sun, 31 Oct 2010 06:30:30 GMT</pubDate><guid isPermaLink="false">Created Release: Automated Deletion of WSUS Logs (Oct 30, 2010) 20101031063030A</guid></item><item><title>Released: Automated Deletion of WSUS Logs (Oct 30, 2010)</title><link>http://sbs.codeplex.com/releases/view/54880</link><description>
&lt;div class="wikidoc"&gt;To deploy this automation&lt;br&gt;
&lt;br&gt;
Download zip file to servers desktop&lt;br&gt;
&lt;h2&gt;STEP I&lt;/h2&gt;
Extract it, that will create an install folder called AutoWSUSlogdeletion on your desktop.&lt;br&gt;
Open the folder&lt;br&gt;
&lt;h2&gt;STEP II&lt;/h2&gt;
You will need to right click and select &lt;b&gt;edit&lt;/b&gt; on the enclosed xml file &lt;i&gt;&lt;b&gt;&amp;quot;WSUS Log file cleanup.xml&amp;quot;&lt;/b&gt;&lt;/i&gt;.&lt;br&gt;
Find the line &lt;i&gt;&lt;b&gt;&amp;lt;Author&amp;gt;DOMAIN\adminuser&amp;lt;/Author&amp;gt;&lt;/b&gt;&lt;/i&gt;&lt;br&gt;
and replace DOMAIN with you domain name ALL CAPS&lt;br&gt;
then replace ADMINIUSER with you domain administrator account&lt;br&gt;
Then do the same for the line&lt;br&gt;
&lt;i&gt;&lt;b&gt;&amp;lt;UserId&amp;gt;DOMAIN\adminuser&amp;lt;/UserId&amp;gt;&lt;/b&gt;&lt;/i&gt; 14 lines down&lt;br&gt;
&lt;b&gt;DO NOT ADD ANYTHING ELSE TO THE EML FILE - IT WILL CAUSE ERRORS&lt;/b&gt;&lt;br&gt;
&lt;h2&gt;STEP III&lt;/h2&gt;
Now open the Task Scheduler&lt;br&gt;
and in the left colum under the Microsoft - Windows folders, create a new folder called
&lt;i&gt;&lt;b&gt;WSUS Cleanup&lt;/b&gt;&lt;/i&gt;.&lt;br&gt;
Select that folder in the left colum and then in the far right colum click &lt;b&gt;import&lt;/b&gt;&lt;br&gt;
Then navigate to the folder &lt;i&gt;&lt;b&gt;&amp;quot;C:\Program Files\Windows Small Business Server\WSUS Log File Cleanup&amp;quot;&lt;/b&gt;&lt;/i&gt;&lt;br&gt;
Now select the &lt;i&gt;&lt;b&gt;&amp;quot;WSUS log file cleanup.xml&amp;quot;&lt;/b&gt;&lt;/i&gt; file and click
&lt;b&gt;open&lt;/b&gt;&lt;br&gt;
Adjust the settings to your prefered configuration, times and day/date to run.&lt;br&gt;
&lt;h2&gt;STEP IV&lt;/h2&gt;
Now next step is to edit the powershell file to match your folder names in the &lt;i&gt;
&lt;b&gt;C:\inetpub\logs\LogFiles&lt;/b&gt;&lt;/i&gt; directory&lt;br&gt;
In the &lt;i&gt;&lt;b&gt;AutoWSUSlogdeletion&lt;/b&gt;&lt;/i&gt; folder on the desktop right click on the
&lt;i&gt;&lt;b&gt;&amp;quot;DeleteOldFiles.ps1&amp;quot;&lt;/b&gt;&lt;/i&gt; file&lt;br&gt;
Select &lt;b&gt;Open&lt;/b&gt; to open in notepad to edit&lt;br&gt;
OR&lt;br&gt;
Select &lt;b&gt;Edit&lt;/b&gt; to edit with the Powershell GUI editor&lt;br&gt;
In the file you will find a Function section for each folder that exists&lt;br&gt;
They each begin Function DeleteOldLogFileinFolder1 - Number 1 - 8&lt;br&gt;
In each of the section you need to edit the line&lt;br&gt;
&lt;i&gt;&lt;b&gt;$TargetFolder = &amp;quot;C:\inetpub\logs\LogFiles\W3SVC1&amp;quot;&lt;/b&gt;&lt;/i&gt;&lt;br&gt;
To match the name of your folders (these are all crated with random names by WSUS install.&lt;br&gt;
&lt;h2&gt;STEP V - Last step&lt;/h2&gt;
Then right click on the &lt;i&gt;&lt;b&gt;install.bat&lt;/b&gt;&lt;/i&gt; and &lt;b&gt;run as administrator&lt;/b&gt;. It will create a directory for the task files to be stored at
&lt;br&gt;
&lt;i&gt;&lt;b&gt;&amp;quot;C:\Program Files\Windows Small Business Server\WSUS Log File Cleanup&amp;quot;&lt;/b&gt;&lt;/i&gt;&lt;br&gt;
&lt;br&gt;
And you finished.&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
</description><author></author><pubDate>Sun, 31 Oct 2010 06:30:30 GMT</pubDate><guid isPermaLink="false">Released: Automated Deletion of WSUS Logs (Oct 30, 2010) 20101031063030A</guid></item><item><title>Updated Release: Shutdown_reboot.cmd to speed up the rebooting (Jan 14, 2010)</title><link>http://sbs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=38791</link><description>&lt;div class="wikidoc"&gt;This is a batch file to shut down and reboot the SBS server.&lt;br /&gt;&lt;br /&gt;Put in the system32 directory so they&amp;#39;re on your path&lt;br /&gt;&lt;br /&gt;You will also need to download the shut down exchange script from &lt;br /&gt;&lt;a href="http://sbs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=38792" class="externalLink"&gt;http://sbs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=38792&lt;span class="externalLinkIcon"&gt;&lt;/span&gt;&lt;/a&gt; and &lt;a href="http://sbs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=38794" class="externalLink"&gt;http://sbs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=38794&lt;span class="externalLinkIcon"&gt;&lt;/span&gt;&lt;/a&gt; that download site to complete the script.&lt;br /&gt;&lt;br /&gt;@echo off&lt;br /&gt;@REM ****************************************************************&lt;br /&gt;@REM Batch file to shut down and reboot the SBS server. For when it&amp;#39;s&lt;br /&gt;@REM mis-behaving. Calls stopexch.cmd, then uses shutdown -r -t 5&lt;br /&gt;@REM&lt;br /&gt;@REM   Requires a separate stopexch.cmd and sleep.exe from the &lt;br /&gt;@REM     Server 2k3 RK. &lt;br /&gt;@REM&lt;br /&gt;@REM  Possible enhancements:&lt;br /&gt;@REM     Use command line parameters to control wait times and &lt;br /&gt;@REM     shutdown warning commands. &lt;br /&gt;@REM&lt;br /&gt;@REM   Modified: 23/04/2009 -- pick up server name from env&lt;br /&gt;@REM           : 27/10/2009 -- second date/time stamp after exchange&lt;br /&gt;@REM&lt;br /&gt;@REM ****************************************************************&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;@REM Ignore any sleep errors if you don&amp;#39;t have a copy of sleep on this&lt;br /&gt;@REM   machine. It&amp;#39;s not critical, just for neatness.&lt;br /&gt;@REM&lt;br /&gt;&lt;br /&gt;SET LOGFILE=C:\Shutdown.log&lt;br /&gt;SET WARNING=5&lt;br /&gt;SET SLEEP=2&lt;br /&gt;SET STOPEXCH=%WINDIR%\system32\stopexch.cmd&lt;br /&gt;&lt;br /&gt;@echo Automatic reboot %COMPUTERNAME% initiated...&lt;br /&gt;@echo.&lt;br /&gt;&lt;br /&gt;echo ===================================================================== &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;echo. &amp;gt;&amp;gt;%LOGFILE%&lt;br /&gt;echo Automatic reboot of %COMPUTERNAME% initiated at: &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;date /t &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;time /t &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;echo. &amp;gt;&amp;gt;%LOGFILE%&lt;br /&gt;echo Calling exchange shutdown script to speed things up &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;@echo Calling exchange shutdown script first...&lt;br /&gt;@echo.&lt;br /&gt;&lt;br /&gt;@REM The exchange shutdown is quiet. Probably too quiet. &lt;br /&gt;sleep %SLEEP%&lt;br /&gt;call %STOPEXCH% 1&amp;gt;&amp;amp;2 &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;&lt;br /&gt;echo. &amp;gt;&amp;gt;%LOGFILE%&lt;br /&gt;echo Exchange should be stopped now... &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;@echo Exchange should be stopped now, initiating final shutdown... &lt;br /&gt;date /t &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;time /t &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;echo. &amp;gt;&amp;gt;%LOGFILE%&lt;br /&gt;@echo.&lt;br /&gt;echo. &amp;gt;&amp;gt;%LOGFILE%&lt;br /&gt;echo. &amp;gt;&amp;gt;%LOGFILE%&lt;br /&gt;echo Now, shutting down the server using the command: &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;echo &amp;#39;shutdown /r /t %WARNING%&amp;#39;  &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;@echo Shutting down in %WARNING% seconds...&lt;br /&gt;shutdown /r /t %WARNING%  &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>bitzie</author><pubDate>Fri, 15 Jan 2010 07:34:41 GMT</pubDate><guid isPermaLink="false">Updated Release: Shutdown_reboot.cmd to speed up the rebooting (Jan 14, 2010) 20100115073441A</guid></item><item><title>Released: Shutdown_reboot.cmd to speed up the rebooting (Jan 14, 2010)</title><link>http://sbs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=38791</link><description>&lt;div&gt;This is a batch file to shut down and reboot the SBS server.&lt;br&gt;&lt;br&gt;Put in the system32 directory so they&amp;#39;re on your path&lt;br&gt;&lt;br&gt;You will also need to download the shut down exchange script from &lt;br&gt;&lt;a href="http://sbs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=38792"&gt;http://sbs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=38792&lt;span&gt;&lt;/span&gt;&lt;/a&gt; and &lt;a href="http://sbs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=38794"&gt;http://sbs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=38794&lt;span&gt;&lt;/span&gt;&lt;/a&gt; that download site to complete the script.&lt;br&gt;&lt;br&gt;@echo off&lt;br&gt;@REM ****************************************************************&lt;br&gt;@REM Batch file to shut down and reboot the SBS server. For when it&amp;#39;s&lt;br&gt;@REM mis-behaving. Calls stopexch.cmd, then uses shutdown -r -t 5&lt;br&gt;@REM&lt;br&gt;@REM   Requires a separate stopexch.cmd and sleep.exe from the &lt;br&gt;@REM     Server 2k3 RK. &lt;br&gt;@REM&lt;br&gt;@REM  Possible enhancements:&lt;br&gt;@REM     Use command line parameters to control wait times and &lt;br&gt;@REM     shutdown warning commands. &lt;br&gt;@REM&lt;br&gt;@REM   Modified: 23/04/2009 -- pick up server name from env&lt;br&gt;@REM           : 27/10/2009 -- second date/time stamp after exchange&lt;br&gt;@REM&lt;br&gt;@REM ****************************************************************&lt;br&gt;&lt;br&gt;&lt;br&gt;@REM Ignore any sleep errors if you don&amp;#39;t have a copy of sleep on this&lt;br&gt;@REM   machine. It&amp;#39;s not critical, just for neatness.&lt;br&gt;@REM&lt;br&gt;&lt;br&gt;SET LOGFILE=C:\Shutdown.log&lt;br&gt;SET WARNING=5&lt;br&gt;SET SLEEP=2&lt;br&gt;SET STOPEXCH=%WINDIR%\system32\stopexch.cmd&lt;br&gt;&lt;br&gt;@echo Automatic reboot %COMPUTERNAME% initiated...&lt;br&gt;@echo.&lt;br&gt;&lt;br&gt;echo ===================================================================== &amp;gt;&amp;gt; %LOGFILE%&lt;br&gt;echo. &amp;gt;&amp;gt;%LOGFILE%&lt;br&gt;echo Automatic reboot of %COMPUTERNAME% initiated at: &amp;gt;&amp;gt; %LOGFILE%&lt;br&gt;date /t &amp;gt;&amp;gt; %LOGFILE%&lt;br&gt;time /t &amp;gt;&amp;gt; %LOGFILE%&lt;br&gt;echo. &amp;gt;&amp;gt;%LOGFILE%&lt;br&gt;echo Calling exchange shutdown script to speed things up &amp;gt;&amp;gt; %LOGFILE%&lt;br&gt;@echo Calling exchange shutdown script first...&lt;br&gt;@echo.&lt;br&gt;&lt;br&gt;@REM The exchange shutdown is quiet. Probably too quiet. &lt;br&gt;sleep %SLEEP%&lt;br&gt;call %STOPEXCH% 1&amp;gt;&amp;amp;2 &amp;gt;&amp;gt; %LOGFILE%&lt;br&gt;&lt;br&gt;echo. &amp;gt;&amp;gt;%LOGFILE%&lt;br&gt;echo Exchange should be stopped now... &amp;gt;&amp;gt; %LOGFILE%&lt;br&gt;@echo Exchange should be stopped now, initiating final shutdown... &lt;br&gt;date /t &amp;gt;&amp;gt; %LOGFILE%&lt;br&gt;time /t &amp;gt;&amp;gt; %LOGFILE%&lt;br&gt;echo. &amp;gt;&amp;gt;%LOGFILE%&lt;br&gt;@echo.&lt;br&gt;echo. &amp;gt;&amp;gt;%LOGFILE%&lt;br&gt;echo. &amp;gt;&amp;gt;%LOGFILE%&lt;br&gt;echo Now, shutting down the server using the command: &amp;gt;&amp;gt; %LOGFILE%&lt;br&gt;echo &amp;#39;shutdown /r /t %WARNING%&amp;#39;  &amp;gt;&amp;gt; %LOGFILE%&lt;br&gt;@echo Shutting down in %WARNING% seconds...&lt;br&gt;shutdown /r /t %WARNING%  &amp;gt;&amp;gt; %LOGFILE%&lt;br&gt;&lt;/div&gt;&lt;div&gt;&lt;/div&gt;</description><author></author><pubDate>Fri, 15 Jan 2010 07:34:41 GMT</pubDate><guid isPermaLink="false">Released: Shutdown_reboot.cmd to speed up the rebooting (Jan 14, 2010) 20100115073441A</guid></item><item><title>Created Release: Sleep.exe file needed for shutdown (Jan 14, 2010)</title><link>http://sbs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=38794</link><description>&lt;div class="wikidoc"&gt;This is the last part of the shut down script that you&amp;#39;ll need to reboot your servers faster.&lt;br /&gt;&lt;br /&gt;Combine this with &lt;a href="http://sbs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=38791" class="externalLink"&gt;http://sbs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=38791&lt;span class="externalLinkIcon"&gt;&lt;/span&gt;&lt;/a&gt; and &lt;a href="http://sbs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=38792" class="externalLink"&gt;http://sbs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=38792&lt;span class="externalLinkIcon"&gt;&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>bitzie</author><pubDate>Fri, 15 Jan 2010 07:33:29 GMT</pubDate><guid isPermaLink="false">Created Release: Sleep.exe file needed for shutdown (Jan 14, 2010) 20100115073329A</guid></item><item><title>Released: Sleep.exe file needed for shutdown (Jan 14, 2010)</title><link>http://sbs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=38794</link><description>&lt;div&gt;This is the last part of the shut down script that you&amp;#39;ll need to reboot your servers faster.&lt;br&gt;&lt;br&gt;Combine this with &lt;a href="http://sbs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=38791"&gt;http://sbs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=38791&lt;span&gt;&lt;/span&gt;&lt;/a&gt; and &lt;a href="http://sbs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=38792"&gt;http://sbs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=38792&lt;span&gt;&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div&gt;&lt;/div&gt;</description><author></author><pubDate>Fri, 15 Jan 2010 07:33:29 GMT</pubDate><guid isPermaLink="false">Released: Sleep.exe file needed for shutdown (Jan 14, 2010) 20100115073329A</guid></item><item><title>Updated Release: Shutdown_reboot.cmd to speed up the rebooting (Jan 14, 2010)</title><link>http://sbs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=38791</link><description>&lt;div class="wikidoc"&gt;This is a batch file to shut down and reboot the SBS server.&lt;br /&gt;&lt;br /&gt;Put in the system32 directory so they&amp;#39;re on your path&lt;br /&gt;&lt;br /&gt;You will also need to download the shut down exchange script from &lt;br /&gt;&lt;a href="http://sbs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=38792" class="externalLink"&gt;http://sbs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=38792&lt;span class="externalLinkIcon"&gt;&lt;/span&gt;&lt;/a&gt; that download site&lt;br /&gt;&lt;br /&gt;@echo off&lt;br /&gt;@REM ****************************************************************&lt;br /&gt;@REM Batch file to shut down and reboot the SBS server. For when it&amp;#39;s&lt;br /&gt;@REM mis-behaving. Calls stopexch.cmd, then uses shutdown -r -t 5&lt;br /&gt;@REM&lt;br /&gt;@REM   Requires a separate stopexch.cmd and sleep.exe from the &lt;br /&gt;@REM     Server 2k3 RK. &lt;br /&gt;@REM&lt;br /&gt;@REM  Possible enhancements:&lt;br /&gt;@REM     Use command line parameters to control wait times and &lt;br /&gt;@REM     shutdown warning commands. &lt;br /&gt;@REM&lt;br /&gt;@REM   Modified: 23/04/2009 -- pick up server name from env&lt;br /&gt;@REM           : 27/10/2009 -- second date/time stamp after exchange&lt;br /&gt;@REM&lt;br /&gt;@REM ****************************************************************&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;@REM Ignore any sleep errors if you don&amp;#39;t have a copy of sleep on this&lt;br /&gt;@REM   machine. It&amp;#39;s not critical, just for neatness.&lt;br /&gt;@REM&lt;br /&gt;&lt;br /&gt;SET LOGFILE=C:\Shutdown.log&lt;br /&gt;SET WARNING=5&lt;br /&gt;SET SLEEP=2&lt;br /&gt;SET STOPEXCH=%WINDIR%\system32\stopexch.cmd&lt;br /&gt;&lt;br /&gt;@echo Automatic reboot %COMPUTERNAME% initiated...&lt;br /&gt;@echo.&lt;br /&gt;&lt;br /&gt;echo ===================================================================== &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;echo. &amp;gt;&amp;gt;%LOGFILE%&lt;br /&gt;echo Automatic reboot of %COMPUTERNAME% initiated at: &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;date /t &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;time /t &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;echo. &amp;gt;&amp;gt;%LOGFILE%&lt;br /&gt;echo Calling exchange shutdown script to speed things up &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;@echo Calling exchange shutdown script first...&lt;br /&gt;@echo.&lt;br /&gt;&lt;br /&gt;@REM The exchange shutdown is quiet. Probably too quiet. &lt;br /&gt;sleep %SLEEP%&lt;br /&gt;call %STOPEXCH% 1&amp;gt;&amp;amp;2 &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;&lt;br /&gt;echo. &amp;gt;&amp;gt;%LOGFILE%&lt;br /&gt;echo Exchange should be stopped now... &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;@echo Exchange should be stopped now, initiating final shutdown... &lt;br /&gt;date /t &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;time /t &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;echo. &amp;gt;&amp;gt;%LOGFILE%&lt;br /&gt;@echo.&lt;br /&gt;echo. &amp;gt;&amp;gt;%LOGFILE%&lt;br /&gt;echo. &amp;gt;&amp;gt;%LOGFILE%&lt;br /&gt;echo Now, shutting down the server using the command: &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;echo &amp;#39;shutdown /r /t %WARNING%&amp;#39;  &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;@echo Shutting down in %WARNING% seconds...&lt;br /&gt;shutdown /r /t %WARNING%  &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>bitzie</author><pubDate>Fri, 15 Jan 2010 07:23:26 GMT</pubDate><guid isPermaLink="false">Updated Release: Shutdown_reboot.cmd to speed up the rebooting (Jan 14, 2010) 20100115072326A</guid></item><item><title>Created Release: Stopexch.cmd shut down Exchange to speed up reboot (Jan 14, 2010)</title><link>http://sbs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=38792</link><description>&lt;div class="wikidoc"&gt;This is the separate batch file that shuts down Exchange&lt;br /&gt;&lt;br /&gt;@echo off&lt;br /&gt;@REM ****************************************************************&lt;br /&gt;@REM Batch file to shut down Exchange 2007 on SBS&lt;br /&gt;@REM   Expects to be called by a separate shutdown script, &lt;br /&gt;@REM&lt;br /&gt;@REM&lt;br /&gt;@REM   Modified: 23/04/2009 -- modified to do Exchange 2007&lt;br /&gt;@REM&lt;br /&gt;@REM ****************************************************************&lt;br /&gt;&lt;br /&gt;@REM - these net stops are in order, but the /y will override anyway&lt;br /&gt;@REM    if I got it wrong. &lt;br /&gt;&lt;br /&gt;net stop &amp;quot;Microsoft Exchange Transport Log Search&amp;quot; /y&lt;br /&gt;net stop &amp;quot;Microsoft Exchange Transport&amp;quot; /y&lt;br /&gt;net stop &amp;quot;Microsoft Exchange Service Host&amp;quot; /y&lt;br /&gt;net stop &amp;quot;Microsoft Exchange Search Indexer&amp;quot; /y&lt;br /&gt;net stop &amp;quot;Microsoft Exchange Replication Service&amp;quot; /y&lt;br /&gt;net stop &amp;quot;Microsoft Exchange Mail Submission&amp;quot; /y&lt;br /&gt;net stop &amp;quot;Microsoft Exchange Mailbox Assistants&amp;quot; /y&lt;br /&gt;net stop &amp;quot;Microsoft Exchange File Distribution&amp;quot; /y&lt;br /&gt;net stop &amp;quot;Microsoft Exchange Anti-spam Update&amp;quot; /y&lt;br /&gt;net stop &amp;quot;Microsoft Exchange Active Directory Topology Service&amp;quot; /y&lt;br /&gt;net stop &amp;quot;Microsoft Search  (Exchange)&amp;quot; /y&lt;br /&gt;net stop &amp;quot;Microsoft Exchange Information Store&amp;quot; /y&lt;br /&gt;net stop &amp;quot;Microsoft Exchange System Attendant&amp;quot; /y&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>bitzie</author><pubDate>Fri, 15 Jan 2010 07:20:17 GMT</pubDate><guid isPermaLink="false">Created Release: Stopexch.cmd shut down Exchange to speed up reboot (Jan 14, 2010) 20100115072017A</guid></item><item><title>Released: Stopexch.cmd shut down Exchange to speed up reboot (Jan 14, 2010)</title><link>http://sbs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=38792</link><description>&lt;div&gt;This is the separate batch file that shuts down Exchange&lt;br&gt;&lt;br&gt;@echo off&lt;br&gt;@REM ****************************************************************&lt;br&gt;@REM Batch file to shut down Exchange 2007 on SBS&lt;br&gt;@REM   Expects to be called by a separate shutdown script, &lt;br&gt;@REM&lt;br&gt;@REM&lt;br&gt;@REM   Modified: 23/04/2009 -- modified to do Exchange 2007&lt;br&gt;@REM&lt;br&gt;@REM ****************************************************************&lt;br&gt;&lt;br&gt;@REM - these net stops are in order, but the /y will override anyway&lt;br&gt;@REM    if I got it wrong. &lt;br&gt;&lt;br&gt;net stop &amp;quot;Microsoft Exchange Transport Log Search&amp;quot; /y&lt;br&gt;net stop &amp;quot;Microsoft Exchange Transport&amp;quot; /y&lt;br&gt;net stop &amp;quot;Microsoft Exchange Service Host&amp;quot; /y&lt;br&gt;net stop &amp;quot;Microsoft Exchange Search Indexer&amp;quot; /y&lt;br&gt;net stop &amp;quot;Microsoft Exchange Replication Service&amp;quot; /y&lt;br&gt;net stop &amp;quot;Microsoft Exchange Mail Submission&amp;quot; /y&lt;br&gt;net stop &amp;quot;Microsoft Exchange Mailbox Assistants&amp;quot; /y&lt;br&gt;net stop &amp;quot;Microsoft Exchange File Distribution&amp;quot; /y&lt;br&gt;net stop &amp;quot;Microsoft Exchange Anti-spam Update&amp;quot; /y&lt;br&gt;net stop &amp;quot;Microsoft Exchange Active Directory Topology Service&amp;quot; /y&lt;br&gt;net stop &amp;quot;Microsoft Search  (Exchange)&amp;quot; /y&lt;br&gt;net stop &amp;quot;Microsoft Exchange Information Store&amp;quot; /y&lt;br&gt;net stop &amp;quot;Microsoft Exchange System Attendant&amp;quot; /y&lt;/div&gt;&lt;div&gt;&lt;/div&gt;</description><author></author><pubDate>Fri, 15 Jan 2010 07:20:17 GMT</pubDate><guid isPermaLink="false">Released: Stopexch.cmd shut down Exchange to speed up reboot (Jan 14, 2010) 20100115072017A</guid></item><item><title>Created Release: Shutdown_reboot.cmd (Jan 14, 2010)</title><link>http://sbs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=38791</link><description>&lt;div class="wikidoc"&gt;This is a batch file to shut down and reboot the SBS server.&lt;br /&gt;&lt;br /&gt;@echo off&lt;br /&gt;@REM ****************************************************************&lt;br /&gt;@REM Batch file to shut down and reboot the SBS server. For when it&amp;#39;s&lt;br /&gt;@REM mis-behaving. Calls stopexch.cmd, then uses shutdown -r -t 5&lt;br /&gt;@REM&lt;br /&gt;@REM   Requires a separate stopexch.cmd and sleep.exe from the &lt;br /&gt;@REM     Server 2k3 RK. &lt;br /&gt;@REM&lt;br /&gt;@REM  Possible enhancements:&lt;br /&gt;@REM     Use command line parameters to control wait times and &lt;br /&gt;@REM     shutdown warning commands. &lt;br /&gt;@REM&lt;br /&gt;@REM   Modified: 23/04/2009 -- pick up server name from env&lt;br /&gt;@REM           : 27/10/2009 -- second date/time stamp after exchange&lt;br /&gt;@REM&lt;br /&gt;@REM ****************************************************************&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;@REM Ignore any sleep errors if you don&amp;#39;t have a copy of sleep on this&lt;br /&gt;@REM   machine. It&amp;#39;s not critical, just for neatness.&lt;br /&gt;@REM&lt;br /&gt;&lt;br /&gt;SET LOGFILE=C:\Shutdown.log&lt;br /&gt;SET WARNING=5&lt;br /&gt;SET SLEEP=2&lt;br /&gt;SET STOPEXCH=%WINDIR%\system32\stopexch.cmd&lt;br /&gt;&lt;br /&gt;@echo Automatic reboot %COMPUTERNAME% initiated...&lt;br /&gt;@echo.&lt;br /&gt;&lt;br /&gt;echo ===================================================================== &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;echo. &amp;gt;&amp;gt;%LOGFILE%&lt;br /&gt;echo Automatic reboot of %COMPUTERNAME% initiated at: &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;date /t &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;time /t &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;echo. &amp;gt;&amp;gt;%LOGFILE%&lt;br /&gt;echo Calling exchange shutdown script to speed things up &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;@echo Calling exchange shutdown script first...&lt;br /&gt;@echo.&lt;br /&gt;&lt;br /&gt;@REM The exchange shutdown is quiet. Probably too quiet. &lt;br /&gt;sleep %SLEEP%&lt;br /&gt;call %STOPEXCH% 1&amp;gt;&amp;amp;2 &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;&lt;br /&gt;echo. &amp;gt;&amp;gt;%LOGFILE%&lt;br /&gt;echo Exchange should be stopped now... &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;@echo Exchange should be stopped now, initiating final shutdown... &lt;br /&gt;date /t &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;time /t &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;echo. &amp;gt;&amp;gt;%LOGFILE%&lt;br /&gt;@echo.&lt;br /&gt;echo. &amp;gt;&amp;gt;%LOGFILE%&lt;br /&gt;echo. &amp;gt;&amp;gt;%LOGFILE%&lt;br /&gt;echo Now, shutting down the server using the command: &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;echo &amp;#39;shutdown /r /t %WARNING%&amp;#39;  &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;@echo Shutting down in %WARNING% seconds...&lt;br /&gt;shutdown /r /t %WARNING%  &amp;gt;&amp;gt; %LOGFILE%&lt;br /&gt;&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>bitzie</author><pubDate>Fri, 15 Jan 2010 07:18:56 GMT</pubDate><guid isPermaLink="false">Created Release: Shutdown_reboot.cmd (Jan 14, 2010) 20100115071856A</guid></item><item><title>Created Release: Audit alert for logon failure (4776 event) (Nov 30, 2009)</title><link>http://sbs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=36655</link><description>&lt;div class="wikidoc"&gt;You will need to adjust the audit events to log for audit failures.&lt;br /&gt;&lt;br /&gt;To deploy the custom alert &lt;br /&gt;&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/cc721719.aspx" class="externalLink"&gt;SBS 2008 SDK&lt;span class="externalLinkIcon"&gt;&lt;/span&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Copy this XML file in this release to the %programfiles%\Windows Small Business Server\Data\Monitoring\ExternalAlerts directory on the computer that is running the Windows SBS 2008 operating system.&lt;br /&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>bitzie</author><pubDate>Tue, 01 Dec 2009 07:31:10 GMT</pubDate><guid isPermaLink="false">Created Release: Audit alert for logon failure (4776 event) (Nov 30, 2009) 20091201073110A</guid></item><item><title>Released: Audit alert for logon failure (4776 event) (Nov 30, 2009)</title><link>http://sbs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=36655</link><description>&lt;div&gt;You will need to adjust the audit events to log for audit failures.&lt;br&gt;&lt;br&gt;To deploy the custom alert &lt;br&gt;&lt;br&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/cc721719.aspx"&gt;SBS 2008 SDK&lt;span&gt;&lt;/span&gt;&lt;/a&gt;&lt;br&gt;&lt;br&gt;Copy this XML file in this release to the %programfiles%\Windows Small Business Server\Data\Monitoring\ExternalAlerts directory on the computer that is running the Windows SBS 2008 operating system.&lt;br&gt;&lt;br&gt;&lt;/div&gt;&lt;div&gt;&lt;/div&gt;</description><author></author><pubDate>Tue, 01 Dec 2009 07:31:10 GMT</pubDate><guid isPermaLink="false">Released: Audit alert for logon failure (4776 event) (Nov 30, 2009) 20091201073110A</guid></item><item><title>Updated Release: Alert for log on failure (Nov 30, 2009)</title><link>http://sbs.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=36654</link><description>&lt;div class="wikidoc"&gt;Ensure that you adjust the group policy for the default domain controller to audit for failures as well as successes before you deploy this alert.&lt;br /&gt;&lt;br /&gt;To deploy the custom alert &lt;br /&gt;&lt;br /&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/cc721719.aspx" class="externalLink"&gt;SBS 2008 SDK&lt;span class="externalLinkIcon"&gt;&lt;/span&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Copy this XML file in this release to the %programfiles%\Windows Small Business Server\Data\Monitoring\ExternalAlerts directory on the computer that is running the Windows SBS 2008 operating system.&lt;br /&gt;&lt;br /&gt;Since this file will come from the Internet you may need to right mouse click and indicate it is safe.&lt;br /&gt;&lt;br /&gt;Restart the Windows SBS Manager service.&lt;br /&gt;&lt;br /&gt;To restart the Windows SBS Manager service &lt;br /&gt;Click Start, point to Administrative Tools, and then click Services.&lt;br /&gt;&lt;br /&gt;Right-click the Windows SBS Manager service, and then click Restart.&lt;br /&gt;&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>bitzie</author><pubDate>Tue, 01 Dec 2009 07:27:26 GMT</pubDate><guid isPermaLink="false">Updated Release: Alert for log on failure (Nov 30, 2009) 20091201072726A</guid></item></channel></rss>