Microsoft Windows NT 4.0 Guide Manuel d'utilisateur

Naviguer en ligne ou télécharger Manuel d'utilisateur pour Serveurs Microsoft Windows NT 4.0 Guide. Windows NT® Server Manuel d'utilisatio

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 35
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 0
Windows NT® Server
Server Operating System
Using and Developing Applications
Compatibility Scripts with
Windows NT® Server 4.0,
Terminal Server Edition
White Paper
Abstract
Microsoft® Windows NT® Server 4.0, Terminal Server Edition, is a new technology that gives the
Windows NT Server operating system the capability to serve 32-bit Windows® operating system-
based applications to terminals and terminal emulators running on personal computer and other
computer desktops. The Terminal Server environment is, by definition, a thin client architecture
where all application processing occurs centrally on the server. Because Terminal Server terminal
emulator clients will be available for many different desktop platforms (Macintosh, UNIX, and
others), Terminal Server provides access to 32-bit Windows-based applications from virtually any
desktop, and provides a bridging technology for organizations that are transitioning to a pure 32-
bit desktop environment.
This paper provides guidelines for using and developing Applications Compatibility Scripts for the
Terminal Server environment. This is a highly technical document and a thorough understanding
of Windows NT Server 4.0 and Windows NT Server 4.0, Terminal Server Edition will be important
for understanding the information in this document. For a more information about
Windows NTServer 4.0, Terminal Server Edition see
http:\\www.microsoft.com\ntserver\terminalserver
®
Vue de la page 0
1 2 3 4 5 6 ... 34 35

Résumé du contenu

Page 1 - Windows NT® Server

Windows NT® ServerServer Operating SystemUsing and Developing ApplicationsCompatibility Scripts withWindows NT® Server 4.0,Terminal Server EditionWhit

Page 2

Application Compatibility Scripts for Windows NT Server, Terminal Server Edition 6The files and directories an application uses can also cause proble

Page 3 - CONTENTS

Applications Compatibility Scripts for Windows NT Server, TerminalServer EditionA third method is to contact the application vendor. They may be abl

Page 4

Application Compatibility Scripts for Windows NT Server, Terminal Server Edition 8Inaccessible files due to file security:Some applications store fil

Page 5 - INTRODUCTION

Applications Compatibility Scripts for Windows NT Server, TerminalServer EditionResolution: If you use “change user /install” or “All users begin wit

Page 6

Application Compatibility Scripts for Windows NT Server, Terminal Server Edition 10Microsoft Windows applications can create objects (such as Events,

Page 7 - COMPATIBILITY

Applications Compatibility Scripts for Windows NT Server, TerminalServer EditionFinally, if the application is being developed in-house, the best met

Page 8 - REGISTRY SETTINGS

Application Compatibility Scripts for Windows NT Server, Terminal Server Edition 12These values are set under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\W

Page 9

Applications Compatibility Scripts for Windows NT Server, TerminalServer EditionMulti-User Object Manager not to decorate objects created by this app

Page 10 - Resolution:

Application Compatibility Scripts for Windows NT Server, Terminal Server Edition 14For optimum application compatibility, when users log in they shou

Page 11

Applications Compatibility Scripts for Windows NT Server, TerminalServer EditionApplication tuning tasks must occur at two different times: when the

Page 12

© 1998 Microsoft Corporation. All rights reserved.The information contained in this document represents the current view of MicrosoftCorporation on th

Page 13

Application Compatibility Scripts for Windows NT Server, Terminal Server Edition 16The Application Scripts use one final component to assist in optim

Page 14

Applications Compatibility Scripts for Windows NT Server, TerminalServer Editionfor a single character, but it is still recommended. Otherwise younee

Page 15 - Server Edition

Application Compatibility Scripts for Windows NT Server, Terminal Server Edition 18This example changes the text #ROOTDRIVE# to the valueof the RootD

Page 16 - COMPATIBILITY FLAGS

Applications Compatibility Scripts for Windows NT Server, TerminalServer EditionSyntax:CACLS filename [/T][/E][/C][/G user:perm][/R user [...]][/P us

Page 17

Application Compatibility Scripts for Windows NT Server, Terminal Server Edition 20/r Uses search strings as regular expressions. This switch is notr

Page 18 - UTILIZING LOGON

Applications Compatibility Scripts for Windows NT Server, TerminalServer EditionHKEY_CURRENT_USER\Software\Microsoft\Office\8.0CommonFileNewLocalTemp

Page 19 - CONFIGURATION

Application Compatibility Scripts for Windows NT Server, Terminal Server Edition 22• For key names, leading and trailing space characters are ignore

Page 20

Applications Compatibility Scripts for Windows NT Server, TerminalServer Edition• This syntax means that you can't create a value with leading

Page 21 - 2. ACSR.exe

Application Compatibility Scripts for Windows NT Server, Terminal Server Edition 24The amount of work it will take to bring an application in line wi

Page 22 - 4. CACLS.exe

Applications Compatibility Scripts for Windows NT Server, TerminalServer EditionPlease refer to http://www.microsoft.com/win32dev under Guidelines fo

Page 23 - 5. FINDSTR.exe

INTRODUCTION ... 1Terminal Server Extends the Multi-user Capabilities of Window

Page 24 - [-b] textFiles

Application Compatibility Scripts for Windows NT Server, Terminal Server Edition 26USRLOGON.CMD@Echo OffRemRem This is for those scripts that don&apo

Page 25

Applications Compatibility Scripts for Windows NT Server, TerminalServer EditionRem added to UsrLogn2.Cmd when the Installation script is run.RemIf N

Page 26

Application Compatibility Scripts for Windows NT Server, Terminal Server Edition 28@Echo OffRemRem Verify that %RootDrive% has been configured and se

Page 27

Applications Compatibility Scripts for Windows NT Server, TerminalServer EditionIf Exist %SystemRoot%\System32\OleAut32.Dll cacls%SystemRoot%\System3

Page 28 - CONCLUSION

Application Compatibility Scripts for Windows NT Server, Terminal Server Edition 30regini MsWord97.key > Nul:Rem If original mode was execute, cha

Page 29 - FOR MORE

Applications Compatibility Scripts for Windows NT Server, TerminalServer EditionAPPENDIX C: FLOWCHART OFUSRLOGON.CMD

Page 31

Applications Compatibility Scripts for Windows NT Server, TerminalServer EditionMicrosoft® Windows NT® Server 4.0, Terminal Server Edition, is a new

Page 32 - MSWORD97.CMD

Application Compatibility Scripts for Windows NT Server, Terminal Server Edition 2files and databases stored on file servers throughout a distributed

Page 33

Applications Compatibility Scripts for Windows NT Server, TerminalServer EditionWhy Do Application Compatibility Issues Exist?Ideally, applications w

Page 34

Application Compatibility Scripts for Windows NT Server, Terminal Server Edition 4Applications keep configuration information in a system database ca

Page 35 - CHART OF

Applications Compatibility Scripts for Windows NT Server, TerminalServer EditionResolution:Terminal Server handles this situation by providing an ins

Commentaires sur ces manuels

Pas de commentaire