What??™s important to remember that is that for every
policy you create, you must define two CAPs??”one for PASS and one for FAIL. If you
don??™t configure a FAIL CAP, the user will receive a generic CAP failure message, if he or
she is unable to connect due to system health policy violations, rather than a NAP-specific
message which helps the user to understand and remediate the issue.
TERMINAL SERVICES REMOTE PROGRAMS
One of some users??™ biggest issues with Terminal Services is that they end up with virtually
two desktops??”one local and one remote??”when they connect to the terminal server.
Depending on how tech savvy your users are, this can cause a lot of confusion, since they
may not understand the difference between the two. All they know is that they have two
Start menus with different programs on each. Terminal Services Remote Programs solve
this problem by allowing users to access their applications remotely through Terminal
Services while making it appear as though it were a local application. This blurring of
lines between remote and local applications enhances the user experience by eliminating
the annoyances of presenting two separate desktops.
You can access applications through a number of methods: Such as via Remote Desktop
Protocol (.RDP) files with the appropriate connection information, or by adding the
application directly on the user??™s Start menu using a specially configured MSI (Windows
Installer) file.
Pages:
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355