<?xml version="1.0" encoding="UTF-8"?>
<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/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>SoloDig &#187; Troubleshooting Tips</title>
	<atom:link href="http://solodig.com/category/troubleshooting-tips/feed" rel="self" type="application/rss+xml" />
	<link>http://solodig.com</link>
	<description>The joy of helping</description>
	<lastBuildDate>Thu, 13 May 2010 07:41:12 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>How to view(read) the smsts.log and other log files when PE boot fails in running the task sequence</title>
		<link>http://solodig.com/troubleshooting-tips/how-to-view-the-smsts-log-and-other-log-files-when-pe-boot-fails-in-running-the-task-sequence</link>
		<comments>http://solodig.com/troubleshooting-tips/how-to-view-the-smsts-log-and-other-log-files-when-pe-boot-fails-in-running-the-task-sequence#comments</comments>
		<pubDate>Sat, 12 Dec 2009 12:38:48 +0000</pubDate>
		<dc:creator>Eskon</dc:creator>
				<category><![CDATA[Troubleshooting Tips]]></category>
		<category><![CDATA[SMSTS.LOG]]></category>

		<guid isPermaLink="false">http://solodig.com/?p=249</guid>
		<description><![CDATA[when I advertise the TS on computers ,it failes because of various reasons and could not able to identify the reason for the faliure.So i decied to look into the SCCM default report for the particular Task sequence.the report doesnt give you all the full information just the task name where it failed.So later someother day fould [...]]]></description>
		<wfw:commentRss>http://solodig.com/troubleshooting-tips/how-to-view-the-smsts-log-and-other-log-files-when-pe-boot-fails-in-running-the-task-sequence/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SMS 2003 Client log files helps more in troubleshooting the issues</title>
		<link>http://solodig.com/troubleshooting-tips/sms-2003-client-log-files-helps-more-in-troubleshooting-the-issues</link>
		<comments>http://solodig.com/troubleshooting-tips/sms-2003-client-log-files-helps-more-in-troubleshooting-the-issues#comments</comments>
		<pubDate>Thu, 16 Jul 2009 05:32:47 +0000</pubDate>
		<dc:creator>Eskon</dc:creator>
				<category><![CDATA[Troubleshooting Tips]]></category>

		<guid isPermaLink="false">http://eskonr.wordpress.com/?p=150</guid>
		<description><![CDATA[Below are the basic log files (more understandable way) that are helpful in troubleshooting the client issues if there are any application instllation failure/inventory and other issues.This information has been compiled from Microsoft Knowledge Base Article 867490 A list of windows update error codes can be found here. CAS.log .&#8221;CAS&#8221; means &#8220;Content Access Service&#8221;. In this Log [...]]]></description>
		<wfw:commentRss>http://solodig.com/troubleshooting-tips/sms-2003-client-log-files-helps-more-in-troubleshooting-the-issues/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Troubleshoot SMS/SCCM clients that had issues with WMI</title>
		<link>http://solodig.com/troubleshooting-tips/troubleshoot-smssccm-clients-that-suffer-with-wmi</link>
		<comments>http://solodig.com/troubleshooting-tips/troubleshoot-smssccm-clients-that-suffer-with-wmi#comments</comments>
		<pubDate>Wed, 10 Jun 2009 03:24:03 +0000</pubDate>
		<dc:creator>Eskon</dc:creator>
				<category><![CDATA[Troubleshooting Tips]]></category>
		<category><![CDATA[WMI Issues]]></category>

		<guid isPermaLink="false">http://eskonr.wordpress.com/?p=9</guid>
		<description><![CDATA[Here is the basic script which can be used to run on systems where you have issues with wmi.This can be run on many systems with the help of psexec(microsoft provided) command. Start copying into notepad and save it as xxxx.bat *************************************Script Start************************************* @echo off Title WMI Repair %windir%\system32\wbem\winmgmt /clearadap %windir%\system32\wbem\winmgmt /kill %windir%\system32\wbem\winmgmt /unregserver %windir%\system32\wbem\winmgmt [...]]]></description>
		<wfw:commentRss>http://solodig.com/troubleshooting-tips/troubleshoot-smssccm-clients-that-suffer-with-wmi/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
