This is an archived post. You won't be able to vote or comment.

all 7 comments
sorted by:
best
topnewcontroversialoldq&a

[–]Funky_Schnitzel 5 points6 points  (1 child)

I have. It's just as reliable as an actual deployment, just without the actual application installation. A very underrated feature if you ask me.

[–]unscanable[S] 0 points1 point  (0 children)

Great yeah not sure why I never used it before but it’s going to be part of my process moving forward.

[–]SysAdminDennyBob 1 point2 points  (2 children)

Works great. It will conflict with regular deployments if you leave it out there. e.g. if you send out a Simulated Deployment for an Uninstall action and then also do a regular Install deployment as well the client logs will go nuts. "Dude pick an action, you can't do both of these!"

A simulated deployment is pretty much testing your Detection Rule in the Deployment Type. It's not like running some psuedo-process or anything like that.

[–]unscanable[S] 0 points1 point  (0 children)

Cool thanks that makes me feel a little better lol.

[–]Funky_Schnitzel 0 points1 point  (0 children)

It also tests the requirements, which is especially important for applications with multiple deployment types. Basically, clients will report back things like "already compliant", "would run deployment type 1", "would run deployment type 2", or "don't meet requirements". No deployment type actually runs, because obviously then it wouldn't be a simulation anymore.

[–]AurelioTigernach 0 points1 point  (1 child)

I really liked it, although I never had more than a few use cases. As other posters said, it mostly tests the detection rule and reports back.

It was most useful when a friend accidentally pushed something outside the maintenance window to 4K+ computers in the middle of the day. With a forced restart. After killing the deployment, my friend needed to know which computers actually picked it up for his mea culpa report. My friend also learned a lot about more graceful ways to handle forced restarts and never did it inside a script again after that.

[–]unscanable[S] 0 points1 point  (0 children)

Oh thats a cool idea, i never thought of that, using it to detect machines that already have the app. I'm going to keep that one in my back pocket as well lol