<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.2.2" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>

<channel>
	<title>KevinTM</title>
	<link>http://blog.kevintm.com</link>
	<description>"Bridging the Gap Between Fantasy and Reality"</description>
	<pubDate>Tue, 08 May 2012 15:37:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.2</generator>
	<language>en</language>
			<item>
		<title>Symantec Backup Exec System Recovery Hangs at 95% (resolved)</title>
		<link>http://blog.kevintm.com/?p=563</link>
		<comments>http://blog.kevintm.com/?p=563#comments</comments>
		<pubDate>Tue, 08 May 2012 15:37:19 +0000</pubDate>
		<dc:creator>kevintm</dc:creator>
		
		<category><![CDATA[Techie]]></category>

		<guid isPermaLink="false">http://blog.kevintm.com/?p=563</guid>
		<description><![CDATA[Per symantec tech article TECH141655.
Problem.  Symantec Backup intermittently hangs at 95% and does not complete.
- typically occurs when multiple machines are backing up to the same destination folder (NAS or network share)
Workaround is to unregister RPAM on each machine that is having the issue.
RegSVR32.exe /U &#8220;C:\Program Files(x86)\Common Files\Symantec Shared\rpAccess\RPAM.dll&#8221;
if recovery pointed need to be [...]]]></description>
			<content:encoded><![CDATA[<p>Per symantec tech article <a href="http://www.symantec.com/docs/TECH141655">TECH141655</a>.</p>
<p>Problem.  Symantec Backup intermittently hangs at 95% and does not complete.<br />
- typically occurs when multiple machines are backing up to the same destination folder (NAS or network share)</p>
<p>Workaround is to unregister RPAM on each machine that is having the issue.</p>
<blockquote><p>RegSVR32.exe /U &#8220;C:\Program Files(x86)\Common Files\Symantec Shared\rpAccess\RPAM.dll&#8221;</p></blockquote>
<p>if recovery pointed need to be mounted for restoring data.  The dll will need to be registered.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.kevintm.com/?feed=rss2&amp;p=563</wfw:commentRss>
		</item>
		<item>
		<title>Renew SSL self-signed certificate in SBS 2008</title>
		<link>http://blog.kevintm.com/?p=562</link>
		<comments>http://blog.kevintm.com/?p=562#comments</comments>
		<pubDate>Thu, 03 May 2012 00:51:08 +0000</pubDate>
		<dc:creator>kevintm</dc:creator>
		
		<category><![CDATA[Techie]]></category>

		<guid isPermaLink="false">http://blog.kevintm.com/?p=562</guid>
		<description><![CDATA[With Small Business Server 2008, you have the option to use a third party SSL certificate or the default self-signed SSL certificate. By default the self-signed certificate is valid for two years, but how to you renew it without interrupting OWA, Outlook, and Exchange? When the certificate is expired, Outlook 2007/2010 will give you an [...]]]></description>
			<content:encoded><![CDATA[<p>With Small Business Server 2008, you have the option to use a third party SSL certificate or the default self-signed SSL certificate. By default the self-signed certificate is valid for two years, but how to you renew it without interrupting OWA, Outlook, and Exchange? When the certificate is expired, Outlook 2007/2010 will give you an error message when opening, that the certificate is not valid. Here are the steps to fix it.</p>
<p>1. Goto the Windows SBS Console, click on Network Tab, then Connectivity Tab<br />
 2. Click on the certificate icon, then click the “view certificate properties” in the right pane. In the General tab of the new window, it will show the dates that the self-signed certificate is valid for.<br />
 3. In the “Connectivity Tasks” area, click “setup your Internet address”, go through the wizard to renew your self-signed SSL certificate.<br />
 4. When you now check the certififcate properties, you will see that it is now valid for another two more years.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.kevintm.com/?feed=rss2&amp;p=562</wfw:commentRss>
		</item>
		<item>
		<title>How to Block Facebook Using Hosts File.</title>
		<link>http://blog.kevintm.com/?p=561</link>
		<comments>http://blog.kevintm.com/?p=561#comments</comments>
		<pubDate>Wed, 11 Apr 2012 14:04:14 +0000</pubDate>
		<dc:creator>kevintm</dc:creator>
		
		<category><![CDATA[Techie]]></category>

		<guid isPermaLink="false">http://blog.kevintm.com/?p=561</guid>
		<description><![CDATA[Not to be used typically in a corp settings.  However, I deal with a lot of small business users.  Sometimes, a user likes to be on facebook just a little bit to much and it conflicts with work.  
1) open the hosts file. Hosts file location:

Windows XP, Vista and Windows 7 (open [...]]]></description>
			<content:encoded><![CDATA[<p>Not to be used typically in a corp settings.  However, I deal with a lot of small business users.  Sometimes, a user likes to be on facebook just a little bit to much and it conflicts with work.  </p>
<p>1) open the hosts file. Hosts file location:</p>
<blockquote><p>
Windows XP, Vista and Windows 7 (open notepad as administrator. Then open the file in the following location)<br />
C:\WINDOWS\system32\drivers\etc\hosts
</p></blockquote>
<blockquote><p>
Windows 2000<br />
C:\WINNT\system32\drivers\etc\hosts
</p></blockquote>
<blockquote><p>
Windows 98/ME<br />
 C:\WINDOWS\hosts
</p></blockquote>
<p>2) Add the following lines.</p>
<blockquote><p>
# Block Facebook<br />
127.0.0.1 www.facebook.com<br />
127.0.0.1 facebook.com<br />
127.0.0.1 static.ak.fbcdn.net<br />
127.0.0.1 www.static.ak.fbcdn.net<br />
127.0.0.1 login.facebook.com<br />
127.0.0.1 www.login.facebook.com<br />
127.0.0.1 fbcdn.net<br />
127.0.0.1 www.fbcdn.net<br />
127.0.0.1 fbcdn.com<br />
127.0.0.1 www.fbcdn.com<br />
127.0.0.1 static.ak.connect.facebook.com<br />
127.0.0.1 www.static.ak.connect.facebook.com
</p></blockquote>
<p>3) Save</p>
<p><a href="http://cariblogger.com/2010/07/how-to-block-facebook-using-hosts-file/">Source</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.kevintm.com/?feed=rss2&amp;p=561</wfw:commentRss>
		</item>
		<item>
		<title>How to Hide a User from the Welcome Screen</title>
		<link>http://blog.kevintm.com/?p=560</link>
		<comments>http://blog.kevintm.com/?p=560#comments</comments>
		<pubDate>Tue, 03 Apr 2012 23:41:45 +0000</pubDate>
		<dc:creator>kevintm</dc:creator>
		
		<category><![CDATA[Techie]]></category>

		<guid isPermaLink="false">http://blog.kevintm.com/?p=560</guid>
		<description><![CDATA[1) While being logged in an administrator with local admin rights.&#160; Start –&#62; run –&#62; Regedit (run as administrator)   2) HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon    3) Create a key called SpecialAccounts (plural)    4) Create a sub-key called UserLIst (singular)    \Winlogon\SpecialAccounts\UserList    5)Create a DWORD (32bit) [...]]]></description>
			<content:encoded><![CDATA[<p>1) While being logged in an administrator with local admin rights.&#160; Start –&gt; run –&gt; Regedit (run as administrator)   <br />2) HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon    <br />3) Create a key called SpecialAccounts (plural)    <br />4) Create a sub-key called UserLIst (singular)    <br />\Winlogon\SpecialAccounts\UserList    <br />5)Create a DWORD (32bit) value with the same value as the user you want to hide.    <br />6) Set Value to 0</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.kevintm.com/?feed=rss2&amp;p=560</wfw:commentRss>
		</item>
		<item>
		<title>Create a self-signed certificate for the Remote Desktop Gateway Server</title>
		<link>http://blog.kevintm.com/?p=558</link>
		<comments>http://blog.kevintm.com/?p=558#comments</comments>
		<pubDate>Fri, 23 Mar 2012 17:39:20 +0000</pubDate>
		<dc:creator>kevintm</dc:creator>
		
		<category><![CDATA[Techie]]></category>

		<guid isPermaLink="false">http://blog.kevintm.com/?p=558</guid>
		<description><![CDATA[More or less. You should only use self-signed certificates for testing or lab purposes.  I found these steps very helpful when setting up a 2008 Foundation box and testing Remote Desktop Gateway Services with it.

To create a self-signed certificate for the Remote Desktop Gateway server
On the RD Gateway server, open Remote Desktop Gateway Manager. [...]]]></description>
			<content:encoded><![CDATA[<p>More or less. You should only use self-signed certificates for testing or lab purposes.  I found these steps very helpful when setting up a 2008 Foundation box and testing Remote Desktop Gateway Services with it.</p>
<blockquote><p>
To create a self-signed certificate for the Remote Desktop Gateway server<br />
On the RD Gateway server, open Remote Desktop Gateway Manager. To open Remote Desktop Gateway Manager, click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Gateway Manager.</p>
<p>In the Remote Desktop Gateway Manager console tree, right-click the local RD Gateway server, which is named for the computer on which the RD Gateway server is running, and then click Properties.</p>
<p>In the results pane, under Configuration Status, click View or modify certificate properties.</p>
<p>On the SSL Certificate tab, click Create a self-signed certificate, and then click Create and Import Certificate.</p>
<p>In the Create Self-Signed Certificate dialog box, do the following:</p>
<p>In the Certificate name box, verify that the correct fully qualified domain name (FQDN) is specified for the self-signed certificate, or specify a new name. The FQDN must match the DNS name that the client uses to connect to the RD Gateway server, unless you are using wildcard certificates or the SAN attributes of certificates.</p>
<p>To store the root certificate in a specified location so that you can manually distribute the root certificate to clients, verify that the Store the root certificate check box is selected, and then specify where to store the certificate. By default, this check box is selected and the certificate is stored under the %Windir%\Users\<Username>\Documents folder.</p>
<p>Click OK.</p>
<p>If you selected the Store the root certificate check box and specified a location for the certificate, a message will appear stating that RD Gateway has successfully created the self-signed certificate, and confirming the location of the stored certificate. Click OK to close the message.</p>
<p>Click OK again to close the RD Gateway server Properties dialog box.</p>
<p><a href="http://technet.microsoft.com/en-us/library/cc730805.aspx">source link</a>
</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://blog.kevintm.com/?feed=rss2&amp;p=558</wfw:commentRss>
		</item>
		<item>
		<title>DRAC 4/i login issue resolved</title>
		<link>http://blog.kevintm.com/?p=557</link>
		<comments>http://blog.kevintm.com/?p=557#comments</comments>
		<pubDate>Tue, 21 Feb 2012 15:32:17 +0000</pubDate>
		<dc:creator>kevintm</dc:creator>
		
		<category><![CDATA[Techie]]></category>

		<guid isPermaLink="false">http://blog.kevintm.com/?p=557</guid>
		<description><![CDATA[I purchased a replacement DRAC card for a PE1850.  I was struggling getting logged in to the damn thing even after resetting the DRAC to default&#8217;s via Open Manage on the server as well as resetting the settings via the management utility via boot up.  Turns out the problem was that it wasn&#8217;t [...]]]></description>
			<content:encoded><![CDATA[<p>I purchased a replacement DRAC card for a PE1850.  I was struggling getting logged in to the damn thing even after resetting the DRAC to default&#8217;s via Open Manage on the server as well as resetting the settings via the management utility via boot up.  Turns out the problem was that it wasn&#8217;t completely reset to defaults.  </p>
<p>Solution. On the server with the DRAC installed.  I logged in as an administrator.  Right click on &#8220;command prompt&#8221; and selected, &#8220;Run as Administrator&#8221;.<br />
c:\windows\system32>  racadm racresetcfg<br />
Now the DRAC is completely reset back to factory defaults with the login root calvin.<br />
Changed the ip address and all is good now.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.kevintm.com/?feed=rss2&amp;p=557</wfw:commentRss>
		</item>
		<item>
		<title>Win 7 x86 RAM issue resolved.</title>
		<link>http://blog.kevintm.com/?p=556</link>
		<comments>http://blog.kevintm.com/?p=556#comments</comments>
		<pubDate>Mon, 13 Feb 2012 02:46:49 +0000</pubDate>
		<dc:creator>kevintm</dc:creator>
		
		<category><![CDATA[Techie]]></category>

		<guid isPermaLink="false">http://blog.kevintm.com/?p=556</guid>
		<description><![CDATA[Enabling PAE
Windows automatically enables PAE if DEP is enabled on a computer that supports hardware-enabled DEP, or if the computer is configured for hot-add memory devices in memory ranges beyond 4 GB. If the computer does not support hardware-enabled DEP or is not configured for hot-add memory devices in memory ranges beyond 4 GB, PAE [...]]]></description>
			<content:encoded><![CDATA[<p>Enabling PAE<br />
Windows automatically enables PAE if DEP is enabled on a computer that supports hardware-enabled DEP, or if the computer is configured for hot-add memory devices in memory ranges beyond 4 GB. If the computer does not support hardware-enabled DEP or is not configured for hot-add memory devices in memory ranges beyond 4 GB, PAE must be explicitly enabled.<br />
To explicitly enable PAE, use the following BCDEdit /set command to set the pae boot entry option:<br />
bcdedit /set [{ID}] pae ForceEnable<br />
IF DEP is enabled, PAE cannot be disabled. Use the following BCDEdit /set commands to disable both DEP and PAE:<br />
bcdedit /set [{ID}] nx AlwaysOff<br />
bcdedit /set [{ID}] pae ForceDisable<br />
Windows Server 2003 and Windows XP:  To enable PAE, use the /PAE switch in the boot.ini file. To disable PAE, use the /NOPAE switch. To disable DEP, use the /EXECUTE switch.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.kevintm.com/?feed=rss2&amp;p=556</wfw:commentRss>
		</item>
		<item>
		<title>How to Distribute Self Signed Certificates in SBS 2008/2011</title>
		<link>http://blog.kevintm.com/?p=555</link>
		<comments>http://blog.kevintm.com/?p=555#comments</comments>
		<pubDate>Mon, 13 Feb 2012 02:03:07 +0000</pubDate>
		<dc:creator>kevintm</dc:creator>
		
		<category><![CDATA[Techie]]></category>

		<guid isPermaLink="false">http://blog.kevintm.com/?p=555</guid>
		<description><![CDATA[Since the certs are now CA based, they can no longer be simply installed via the web browser like they were in sbs 2003.
You must install them with the client app the server generates.
Typically this can be found on the server in c:\users\public\public downloads.    if the public folder is shared it is [...]]]></description>
			<content:encoded><![CDATA[<p>Since the certs are now CA based, they can no longer be simply installed via the web browser like they were in sbs 2003.<br />
You must install them with the client app the server generates.<br />
Typically this can be found on the server in c:\users\public\public downloads.    if the public folder is shared it is usually \\servername\</p>
<p>source: http://blogs.technet.com/b/sbs/archive/2008/09/30/how-do-i-distribute-the-sbs-2008-self-signed-ssl-certificate-to-my-users.aspx</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.kevintm.com/?feed=rss2&amp;p=555</wfw:commentRss>
		</item>
		<item>
		<title>Old 2003 NTBackup Script remodified.</title>
		<link>http://blog.kevintm.com/?p=554</link>
		<comments>http://blog.kevintm.com/?p=554#comments</comments>
		<pubDate>Wed, 25 Jan 2012 03:21:43 +0000</pubDate>
		<dc:creator>kevintm</dc:creator>
		
		<category><![CDATA[Techie]]></category>

		<guid isPermaLink="false">http://blog.kevintm.com/?p=554</guid>
		<description><![CDATA[1st issue.  Create a new full .bkf file for each day instead of append or replace.

@for /f &#8220;Tokens=1-4 Delims=/ &#8221; %%i in (&#8217;date /t&#8217;) do  @set dt=%%i-%%j-%%k-%%l
@for /f &#8220;Tokens=1&#8243; %%i in (&#8217;time /t&#8217;) do @set tm=-%%i
@set tm=%tm::=-%
@set dtt=%dt%%tm%
@echo Copying backup set:  %dt%.
@echo Please wait&#8230;
@C:\WINDOWS\system32\ntbackup.exe backup systemstate C:, D: &#8220;D:\backup set.bks&#8221; /a /d [...]]]></description>
			<content:encoded><![CDATA[<p>1st issue.  Create a new full .bkf file for each day instead of append or replace.</p>
<blockquote><p><i><br />
@for /f &#8220;Tokens=1-4 Delims=/ &#8221; %%i in (&#8217;date /t&#8217;) do  @set dt=%%i-%%j-%%k-%%l<br />
@for /f &#8220;Tokens=1&#8243; %%i in (&#8217;time /t&#8217;) do @set tm=-%%i<br />
@set tm=%tm::=-%<br />
@set dtt=%dt%%tm%<br />
@echo Copying backup set:  %dt%.<br />
@echo Please wait&#8230;<br />
@C:\WINDOWS\system32\ntbackup.exe backup systemstate C:, D: &#8220;D:\backup set.bks&#8221; /a /d &#8220;Backup %dt%&#8221; /v:no /r:no /rs:no /hc:off /m normal /j &#8220;%dt%&#8221; /l:s /f &#8220;<b>\\backups\Backups\_2003-web\</b>Backup %dt%.bkf&#8221;<br />
</i></p></blockquote>
<p>2nd issue. Delete old backups so space does not fill up on the Backup NAS or USB hard drive. *requires forfiles or robocopy*</p>
<blockquote><p><i><br />
net use t: &#8220;<b>\\backups\Backups\_2003-web</b>&#8221;</p>
<p>forfiles -p t:\ -m *Sun* -d -120 -c &#8220;cmd /c echo purged @FILE on %date% >> t:\purgelog.txt&#8221;<br />
forfiles -p t:\ -m *Mon* -d -7 -c &#8220;cmd /c echo purged @FILE on %date% >> t:\purgelog.txt&#8221;<br />
forfiles -p t:\ -m *Tue* -d -7 -c &#8220;cmd /c echo purged @FILE on %date% >> t:\purgelog.txt&#8221;<br />
forfiles -p t:\ -m *Wed* -d -7 -c &#8220;cmd /c echo purged @FILE on %date% >> t:\purgelog.txt&#8221;<br />
forfiles -p t:\ -m *Thu* -d -7 -c &#8220;cmd /c echo purged @FILE on %date% >> t:\purgelog.txt&#8221;<br />
forfiles -p t:\ -m *Fri* -d -7 -c &#8220;cmd /c echo purged @FILE on %date% >> t:\purgelog.txt&#8221;<br />
forfiles -p t:\ -m *Sat* -d -7 -c &#8220;cmd /c echo purged @FILE on %date% >> t:\purgelog.txt&#8221;</p>
<p>forfiles -p t:\ -m *Sun* -d -120 -c &#8220;cmd /c Del @FILE&#8221;<br />
forfiles -p t:\ -m *Mon* -d -7 -c &#8220;cmd /c Del @FILE&#8221;<br />
forfiles -p t:\ -m *Tue* -d -7 -c &#8220;cmd /c Del @FILE&#8221;<br />
forfiles -p t:\ -m *Wed* -d -7 -c &#8220;cmd /c Del @FILE&#8221;<br />
forfiles -p t:\ -m *Thu* -d -7 -c &#8220;cmd /c Del @FILE&#8221;<br />
forfiles -p t:\ -m *Fri* -d -7 -c &#8220;cmd /c Del @FILE&#8221;<br />
forfiles -p t:\ -m *Sat* -d -7 -c &#8220;cmd /c Del @FILE&#8221;</p>
<p>net use t: /delete /y<br />
</i></p></blockquote>
<p>Change the bold text to match your backup drive.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.kevintm.com/?feed=rss2&amp;p=554</wfw:commentRss>
		</item>
		<item>
		<title>PSConfig Arg</title>
		<link>http://blog.kevintm.com/?p=553</link>
		<comments>http://blog.kevintm.com/?p=553#comments</comments>
		<pubDate>Mon, 23 Jan 2012 17:17:04 +0000</pubDate>
		<dc:creator>kevintm</dc:creator>
		
		<category><![CDATA[Techie]]></category>

		<guid isPermaLink="false">http://blog.kevintm.com/?p=553</guid>
		<description><![CDATA[After running a sharepoint sp1 update on a 2011 sbs, backups stopped working.  Try this to fix it. 
1. Open an Administrative command prompt.
2. Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
3. Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
Source
]]></description>
			<content:encoded><![CDATA[<p>After running a sharepoint sp1 update on a 2011 sbs, backups stopped working.  Try this to fix it. </p>
<p>1. Open an Administrative command prompt.<br />
2. Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN<br />
3. Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures</p>
<p><a href="http://blogs.technet.com/b/sbs/archive/2011/05/24/you-must-manually-run-psconfig-after-installing-sharepoint-2010-patches.aspx">Source</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.kevintm.com/?feed=rss2&amp;p=553</wfw:commentRss>
		</item>
	</channel>
</rss>

