As you can see in the whitepaper for App-V Integration in SCCM, it’s not possible to configure SCCM 2007 for user based targeting on Terminal Servers (RDS). As a workaround to this, some customers have written logon scripts or used third party apps like Citrix or AppSense that run multiple SFTMIME instances at user logon to publish application. While this appears to work at first, from time to time some apps may eventually fail because OverrideURL value under the Packages key in Registry that’s used by Configuration Manager 2007 will be deleted. From that point on no user on that TS will able to use app anymore. Reason “when a user logs on and starts SFTMIME.EXE PUBLISH PACKAGE via a logon script or from 3rd-party app, we try to publish app and read a specific global Registry Key on TS. If a second user logs on at the same time and gets same package then both of SFTMIME.EXE processes call SFTLIST service so now you’ve two threads trying to access same registry key at the same time. What happens is that one of the threads will get a result of INVALID, and if the key is missing or INVALID then it’ll be deleted. This behavior has been known since Windows NT 4.0: KB176906,” explain Microsoft.