Jamie's Thoughts, Tips & Tricks relevant to SMS/ConfigMgr Admins and whomever else cares to read.......http://blogs.msdn.com/jamoyer/atom.xmlCommunity Server2008-01-28T17:27:00Zhttp://blogs.msdn.com/jamoyer/archive/2008/01/30/update-computer-account-group-membership-without-rebooting.aspx2008-01-30T20:48:43Z2008-01-30T20:48:43ZOften 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.&#160; Often it is difficult to arrange for the scheduled downtime necessary to reboot a production server. I've used the below procedure to update the computer's security token without rebooting.&#160; This does take a bit of effort, but it doesn't involve rebooting...(<a href="http://blogs.msdn.com/jamoyer/archive/2008/01/30/update-computer-account-group-membership-without-rebooting.aspx">read more</a>)<img src="http://blogs.msdn.com/aggbug.aspx?PostID=7330088" width="1" height="1">jamoyerhttp://blogs.msdn.com/members/jamoyer.aspxhttp://blogs.msdn.com/jamoyer/archive/2008/01/28/analyzing-sms-sccm-log-files-the-easy-way.aspx2008-01-28T20:27:00Z2008-01-28T20:27:00ZHow 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) as they contain a wealth of information and usually quickly lead you down the road to problem resolution. In the past I've used simple scripts to parse the log files and that has worked fairly well, I've also fallen victim to manually...(<a href="http://blogs.msdn.com/jamoyer/archive/2008/01/28/analyzing-sms-sccm-log-files-the-easy-way.aspx">read more</a>)<img src="http://blogs.msdn.com/aggbug.aspx?PostID=7290432" width="1" height="1">jamoyerhttp://blogs.msdn.com/members/jamoyer.aspx