Remote Desktop.app != Microsoft Remote Desktop.app

kish_jayson
Contributor

I wanted to put this out there for suggestions or feedback regarding my deployment method and a minor issue I'm running into with two policies conflicting. The goal is to come up with as simple and elegant a solution is possible.

Here are the policies and groups that I have setup in the JSS:

Install_Microsoft Remote Desktop (Policy)

Trigger: Recurring Check-In
Execution Frequency: Ongoing
Packages: Microsoft Remote Desktop.pkg
Scope: deploy_Microsoft Remote Desktop (Smart Computer Group)

deploy_Microsoft Remote Desktop (Smart Computer Group)

Application Title does not have Microsoft Remote Desktop.app
and Computer Group member of Microsoft Remote Desktop (Static Group)
or Application Title has Microsoft Remote Desktop.app
and Application Version is not 8.0.25073
and Computer Group member of Microsoft Remote Desktop (Static Group)

Remove_Microsoft Remote Desktop (Policy)

Trigger: Recurring Check-In
Execution Frequency: Ongoing
Packages: Microsoft Remote Desktop.pkg
Scripts: remove_Microsoft_Remove_Desktop.sh
Scope: remove_Microsoft Remote Desktop (Smart Computer Group)

remove_Microsoft Remote Desktop (Smart Computer Group)

Application Title has Microsoft Remote Desktop.app
and Computer Group not member of Microsoft Remote Desktop (Static Group)

--

Install_Remote Desktop (Policy)

Trigger: Recurring Check-In
Execution Frequency: Ongoing
Packages: Remote Desktop.pkg
Scope: deploy_Remote Desktop (Smart Computer Group)

deploy_Remote Desktop (Smart Computer Group)

Application Title does not have Remote Desktop.app
and Computer Group member of Remote Desktop (Static Group)
or Application Title has Remote Desktop.app
and Application Version is not 3.7.2
and Computer Group member of Remote Desktop (Static Group)

Remove_Remote Desktop (Policy)

Trigger: Recurring Check-In
Execution Frequency: Ongoing
Packages: Remote Desktop.pkg
Scripts: remove_Remove_Desktop.sh
Scope: remove_Remote Desktop (Smart Computer Group)

remove_Remote Desktop (Smart Computer Group)

Application Title has Remote Desktop.app
and Computer Group not member of Remote Desktop (Static Group)

Here is the problem I'm running into:

Because one application is called Microsoft Remote Desktop.app and the other is Remote Desktop.app, the remove_Remote Desktop smart group is counting Microsoft Remote Desktop.app as within its scope. In turn the Remove_Remote Desktop policy executes every 15 minutes when the system checks in with the JSS.

Any suggestions on how to resolve this without breaking the general functionality would be greatly appreciated.

1 ACCEPTED SOLUTION

ShaunRMiller83
Contributor III

I could be wrong on this so certainly make sure to test before rolling this into production but I believe the reason you are seeing the symptoms you are describing is because you use the "has" operator in your smart groups. If I recall from training both the like and has operators in smart groups are basically the equivalent of saying contains.

If you update your smart group to something like the below in theory that should address your issue.

deploy_Microsoft Remote Desktop (Smart Computer Group)
Application Title is not Microsoft Remote Desktop.app
and Computer Group member of Microsoft Remote Desktop (Static Group)
or Application Title is Microsoft Remote Desktop.app
and Application Version is not 8.0.25073
and Computer Group member of Microsoft Remote Desktop (Static Group)

remove_Microsoft Remote Desktop (Smart Computer Group)
Application Title is Microsoft Remote Desktop.app
and Computer Group not member of Microsoft Remote Desktop (Static Group)

deploy_Remote Desktop (Smart Computer Group)
Application Title is not Remote Desktop.app
and Computer Group member of Remote Desktop (Static Group)
or Application Title is Remote Desktop.app
and Application Version is not 3.7.2+
and Computer Group member of Remote Desktop (Static Group)

remove_Remote Desktop (Smart Computer Group)
Application Title is Remote Desktop.app
and Computer Group not member of Remote Desktop (Static Group)

View solution in original post

4 REPLIES 4

ShaunRMiller83
Contributor III

I could be wrong on this so certainly make sure to test before rolling this into production but I believe the reason you are seeing the symptoms you are describing is because you use the "has" operator in your smart groups. If I recall from training both the like and has operators in smart groups are basically the equivalent of saying contains.

If you update your smart group to something like the below in theory that should address your issue.

deploy_Microsoft Remote Desktop (Smart Computer Group)
Application Title is not Microsoft Remote Desktop.app
and Computer Group member of Microsoft Remote Desktop (Static Group)
or Application Title is Microsoft Remote Desktop.app
and Application Version is not 8.0.25073
and Computer Group member of Microsoft Remote Desktop (Static Group)

remove_Microsoft Remote Desktop (Smart Computer Group)
Application Title is Microsoft Remote Desktop.app
and Computer Group not member of Microsoft Remote Desktop (Static Group)

deploy_Remote Desktop (Smart Computer Group)
Application Title is not Remote Desktop.app
and Computer Group member of Remote Desktop (Static Group)
or Application Title is Remote Desktop.app
and Application Version is not 3.7.2+
and Computer Group member of Remote Desktop (Static Group)

remove_Remote Desktop (Smart Computer Group)
Application Title is Remote Desktop.app
and Computer Group not member of Remote Desktop (Static Group)

cbrewer
Valued Contributor II

In your remove_Remote Desktop smart group, you could include application version. In this case ARD is going to be application version like "3." or like "3.7" if you want just the latest version.

kish_jayson
Contributor

"Is"… Simple. Thank you, this works quite nicely.

ShaunRMiller83
Contributor III

Happy to help and glad to hear its working for you!!