<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.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>Group Policy Script Processing Behavior</title><link>http://blogs.technet.com/b/askds/archive/2010/03/23/group-policy-script-processing-behavior.aspx</link><description>Hi Everyone, Mike here. Today I am discussing the default processing behavior for Group Policy scripts. Microsoft changed the default behavior of Group Policy startup and logon scripts processing from synchronous to asynchronous starting with Windows</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Group Policy Script Processing Behavior</title><link>http://blogs.technet.com/b/askds/archive/2010/03/23/group-policy-script-processing-behavior.aspx#3320791</link><pubDate>Tue, 23 Mar 2010 19:52:06 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3320791</guid><dc:creator>David Bahm</dc:creator><description>&lt;p&gt;Thinking I just found the reason why my login scripts hadn't been running on Win7 (we haven't gone to GPP yet).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3320791" width="1" height="1"&gt;</description></item></channel></rss>