<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Conditional-Triggers - Tag - byteben</title><link>https://byteben.com/tags/conditional-triggers/</link><description>Conditional-Triggers - Tag - byteben</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>ben@byteben.com (Ben Whitmore)</managingEditor><webMaster>ben@byteben.com (Ben Whitmore)</webMaster><lastBuildDate>Mon, 04 Mar 2013 00:00:00 +0000</lastBuildDate><atom:link href="https://byteben.com/tags/conditional-triggers/" rel="self" type="application/rss+xml"/><item><title>Leveraging OU Membership Conditions with the Registry in AppSense Environment Manager</title><link>https://byteben.com/bb/leveraging-ou-membership-conditions-with-the-registry-in-appsense-environment-manager/</link><pubDate>Mon, 04 Mar 2013 00:00:00 +0000</pubDate><author>ben@byteben.com (Ben Whitmore)</author><guid>https://byteben.com/bb/leveraging-ou-membership-conditions-with-the-registry-in-appsense-environment-manager/</guid><description><![CDATA[<p>So I have quickly learned that I can satisfy a lot of my &ldquo;membership&rdquo; conditional triggers by referencing a registry key rather than looking up the Active Directory. This is especially useful on &ldquo;Computer-Start-up&rdquo; triggers. In my experience, when the computer boots, the network is not always ready by the time we kick off a conditional trigger for Computer Group Membership. If the network is not ready and we try to look-up our AD on &ldquo;Computer Start-up&rdquo; then that condition will fail. So how can we get around this?</p>]]></description></item></channel></rss>