Jon A. wrote: We have users that log into a base PC, then go to a Terminal Server session for some of their Apps. When we create an App object in ZENworks 7 for deployment to our users, is there a way to keep it from deploying to users who are running on a Terminal Server session? We don't want the app being installed to their Terminal Server profile, we only want it to be installed on their base PC.
Have you looked at the information in the documentation regarding Terminal Server? There is a distribution rule (under Availability Settings) which looks like it's what you're asking for. Check out
this section of the doc.
To help prevent Apps from installing on Terminal Server Sessions simply add an Launch Condition (if the installation is .msi based) to the Package as follows:
That way, the installation will never take place on a Terminal Server Session.
The distribution rules listed do not prevent apps from deploying on a Windows 2000 server with Terminal Services. The version numbers for both products are the same. (5.00.2195) What you CAN do is put a registry key rule that looks to see if Terminal Services is enabled:
Value Name: ProductType
String Value = WinNT
This will prevent apps from deploying on Terminal Server. Note: This may behave differently with Windows 2003 Servers.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.