<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Troubleshooting SMS/ConfigMgr</title><link>http://blogs.msdn.com/jamoyer/default.aspx</link><description>Jamie's Thoughts, Tips &amp; Tricks relevant to SMS/ConfigMgr Admins and whomever else cares to read.......</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Update Computer Account Group Membership without Rebooting</title><link>http://blogs.msdn.com/jamoyer/archive/2008/01/30/update-computer-account-group-membership-without-rebooting.aspx</link><pubDate>Wed, 30 Jan 2008 20:48:43 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7330088</guid><dc:creator>jamoyer</dc:creator><slash:comments>3</slash:comments><comments>http://blogs.msdn.com/jamoyer/comments/7330088.aspx</comments><wfw:commentRss>http://blogs.msdn.com/jamoyer/commentrss.aspx?PostID=7330088</wfw:commentRss><description>Often times when working with SMS 2003 in advanced security mode the need arises to add computer objects to active directory groups. Normally for a computer account to become aware of the group membership change a reboot is required.&amp;#160; Often it is...(&lt;a href="http://blogs.msdn.com/jamoyer/archive/2008/01/30/update-computer-account-group-membership-without-rebooting.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=7330088" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/jamoyer/archive/tags/Troubleshooting/default.aspx">Troubleshooting</category><category domain="http://blogs.msdn.com/jamoyer/archive/tags/tips/default.aspx">tips</category></item><item><title>Analyzing SMS/ConfigMgr log files the easy way!</title><link>http://blogs.msdn.com/jamoyer/archive/2008/01/28/analyzing-sms-sccm-log-files-the-easy-way.aspx</link><pubDate>Mon, 28 Jan 2008 20:27:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7290432</guid><dc:creator>jamoyer</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/jamoyer/comments/7290432.aspx</comments><wfw:commentRss>http://blogs.msdn.com/jamoyer/commentrss.aspx?PostID=7290432</wfw:commentRss><description>How do you parse log files today? Do you routinely troubleshoot issues with SMS clients? Issues such as WMI not functioning, CCMEXEC not running, Bits issues, etc. The place I always start my troubleshooting is with the client log files (C:\Windows\System32\ccm\logs)...(&lt;a href="http://blogs.msdn.com/jamoyer/archive/2008/01/28/analyzing-sms-sccm-log-files-the-easy-way.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=7290432" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/jamoyer/archive/tags/SMS+2003/default.aspx">SMS 2003</category><category domain="http://blogs.msdn.com/jamoyer/archive/tags/SCCM+2007/default.aspx">SCCM 2007</category><category domain="http://blogs.msdn.com/jamoyer/archive/tags/LogParser/default.aspx">LogParser</category><category domain="http://blogs.msdn.com/jamoyer/archive/tags/Clients/default.aspx">Clients</category><category domain="http://blogs.msdn.com/jamoyer/archive/tags/Troubleshooting/default.aspx">Troubleshooting</category></item></channel></rss>