Quantcast
Channel: Ivanti User Community : Discussion List - All Communities
Viewing all articles
Browse latest Browse all 15294

Node Processing Order

$
0
0

I'm hoping you guys can help me because it is driving me nuts. I'm trying to create a single configuration and execute certain nodes based on a condition. The idea of the design is I would apply some global settings to all users, and then based on conditions I might override those settings with something specific to them. This is what I was attempting to design and based from my understanding:

 

1 - Set some global variables (to be used in the conditions)

2 - Empty node, just used to contain the sub nodes

3 - Execute the child nodes for the global settings (note: Machine is an empty "Group Node", again just to help me with the hierarchy of processing)

4 - Execute the child nodes of the Machine group node

5 - Execute the nodes under the "Standard" node - these settings might override something set in Global specific to "Standard" machines

6 - Execute the child nodes under the Entity node group (again, just used for the hierarchy) and could potential override the global or machine settings to customize the experience at different geographical locations in my organization.

 

 

The nodes that have a "- #" contain a custom Powershell script that appends to a debug log just so I can see the order in which the nodes are firing. In my log I noticed that they weren't following the Hierarchy. For example, Step 6 logged before Step 2, etc.

 

There is got to be a way to process the policy config like this... or am I trying to stick a square into a round hole? Is there some log file I can look at to see what nodes were applied and when (like a gpresult)?

 

Any feedback is appreciated, I've been banging my head on this for days and can't figure out a way to validate the order in which things are processing other than what I tried by logging to a file.

 

Thanks!


Viewing all articles
Browse latest Browse all 15294


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>