slide1 n.
Skip this Video
Loading SlideShow in 5 Seconds..
Agenda PowerPoint Presentation
play fullscreen
1 / 109


169 Views Download Presentation
Download Presentation


- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Enterprise Support TrainingDragon NaturallySpeaking 9 & PDF Converter Pro 5June 12th 2008Created by Loren Cole

  2. Agenda • Product Releases • Enterprise vs. Retail • Builds vs. Service Packs • Installation • MSI Overview • Dragon NaturallySpeaking Specifics • PDF Converter Specifics • Active Directory • Systems Management Server (SMS) • Citrix • Overview: Servers, Clients, Farms • Publishing Applications • Dragon NaturallySpeaking Specifics • PDF Converter Specifics

  3. Agenda (2) • User Access Rights • Dragon NaturallySpeaking Specifics • Profiles: Layout, Upgrades, Local/Roaming, Corruption, Backups • NSAdmin • Sound Systems / Sources • Compatibility Modules / Non-Standard Windows • Speech Data / Deferred Correction • Logs • PDF Converter Specifics • Adjusting Options • PDF Overview • Application Integration • Other Issues • API • DMS Server, Client, Integration

  4. Enterprise vs. RetailBuilds vs. Service PacksMSI OverviewActive DirectorySystems Management Server

  5. Enterprise vs. Retail Builds Retail Builds: • Contain an activation component which requires the client to communicate with the activation server for licensing. • Activations are based on Serial Numbers. Each serial number can be activated on a predefined number of systems. • Special serial numbers can be used to turn off the activation component. • Contain a pipeline mechanism for receiving messages and updates. • Contain a registration mechanism for user registration. Enterprise Builds: • Do not contain activation, pipeline or registration. • Have been fully tested for deployment and Citrix. Builds vs. Updates: • New builds are available for all minor version updates. • Service packs are usually created for minor version updates, but may not contain everything available in the full build.

  6. Builds vs. Service Packs Builds vs. Service Packs: • New builds are available for all minor version updates. • Service packs are usually created for minor version updates. • Service packs contain the majority of fixes, but not all. New builds are required to address installation issues and sometimes driver issues. • Service packs are available for free to all users. • New builds are sent to Enterprise customers with valid Upgrade Maintenance contracts. • Retail customers may purchase new builds from Customer Service.

  7. Windows Installer Packages (MSI) Overview Windows Installer Packages (MSI): • Used for installing an application. • Contains scripts, the order they are executed, conditions, dialog definitions, text strings, files, etc. • Contains properties used for altering the conditions • Contain a Product Code unique to a product: • HEX Format: {403EF592-953B-4794-BCEF-ECAB835C2095} Windows Installer Transform File (MST): • Contains MSI properties • Used for passing large numbers of property adjustments to an MSI file at the same time. Windows Installer Patch File (MSP): • Used for updated an existing installation.

  8. Windows Installer – MSIEXEC (1) Msiexec.exe Windows Installer Process Used for all installation operations Parameters - Installation Type /i – Install /x – Uninstall /p – Apply MSP to existing installation /a – Create Administrative Installation Point • Unpacks all files to a specified location. • Reduces network traffic caused by decompression Parameters – Adjustments MSI File or Product Code /q – Silent Installation • b – shows progress and message dialogs • n – suppresses all dialogs • + – shows finish dialog

  9. Windows Installer – MSIEXEC (2) Parameters – Adjustments (cont’d) TRANSFORMS – Used for passing MST files. ALLUSERS – Changes availability to users • 0 – Available for only user who installed • 1 – Available for all users /lv – Verbose Log – Follow by log path/filename All MSI Properties can be altered by passing adjustments Examples: • msiexec.exe /i “<path>\Dragon NaturallySpeaking 9.msi” SERIALNUMBER=“A209A-XXX-XXXX-XXXX-XX” ALLUSERS=1 /qb+ /lv “C:\DNSInstall.log” • msiexec.exe /i “<path>\PDF Professional 5.msi” TRANSFORMS=“<path>\1033.mst”;<path>\admin.mst” ALLUSERS=1 /qn /lv “C:\PDFInstall.log” • msiexec.exe /x {20ECF3EE-4F7B-40ED-98E7-8CA63FC69F14}

  10. Viewing / Editing MSI Files ORCA • Part of the Windows SDK for Windows Installer Packages • Available for download from many different web sites • Allows viewing, editing and saving MSI file tables. Note:It is very easy to destroy an installation package. Make sure to test any MSI changes in a test environment before rolling out in production.

  11. Dragon NaturallySpeaking Specifics (1) Dragon NaturallySpeaking Settings: • ADDLOCOL – Can be used to install specifics features; comma delimited list. Use “ADDLOCAL=ALL” to install all components. • ADVERTISE – The opposite of ADDLOCAL. Specify which features to not install; comma delimited. • SERIALNUMBER – Used to pass the serial number – use quotes. • INSTALLDIR – Used to specify a different installation directory. • DEFAULTSINI – Allows passing of a “NSOptions.ini” file to change the default options of all user profiles. • ROAMINGUSERINI/ROAMINGUSEROPTIONS – Used for changing roaming user settings. See TN 5758 for details. • SETDEFAULTS/SETADMINS – Will display the Options dialog and/or Administrative Settings dialog during installation. Adjustments will impact all users.

  12. Dragon NaturallySpeaking Specifics (2) Dragon NaturallySpeaking Settings (cont’d): • DNS does not provide a tool for creating an MST settings file. • We typically recommend the Microsoft Office Resource Kit for creating MST files. • Available as a free download from Microsoft’s website. • Additional information can be found in the IT Administrators Help file. It is only available from the Start menu after installing the application. Prerequisite: • ISScript1050.msi must be installed prior. • Required by applications packaged with InstallShield Developer Studio 10.5. • Provides the InstallShield Scripting Runtime needed to run the custom installation scripts.

  13. PDF Converter Specifics PDF Converter Settings: • Creating an administrative installation point will allow you to select all installation options available. • During the administrative installation, an “Admin.mst” file will be created. • Admin.mst – contains all options selected including the serial number. • Admin.mst can be passed to the installer using the TRANSFORMS parameter. • Additional information can be found in the documentation provided with the installation files (CD or Download). Prerequisite: • VCRedist must be installed prior. • Required by applications built with Visual C++ .NET 2005 • Provides the Visual C++ 2005 Runtime required by the application. • Available for x86 (32-bit) and x64 (64-bit) installations: • <CD>\Prerequisite

  14. Active Directory Active Directory: • Is available as a free add-on to Microsoft Windows Server OS (2000, 2003, 2008). • Testing has only been done on Windows 2000 and 2003, although there should be no issue deploying through Windows 2008. • Active Directory provides an easy way to manage a Domain, as well as the computers and users within it. • The main focus of deploying software is through Group Policy Object. Group Policy Object (GPO): • GPOs are used to alter the state of a computer or a users environment. • GPOs can be used to alter appearance, permissions, deploy software and run scripts. • We only test and support deployment of software through Computer defined GPOs. • GPOs are applied using the Windows SYSTEM account.

  15. Active Directory Interface Interface: • Provides a look at all users and computers that have been added to the Domain. • Organizational Units (OUs) are used to organize groups of users/computers. • GPOs are applied to OUs.

  16. Creating a GPO (1) Group Policy Objects: • Are added to the properties of an OU.

  17. Creating a GPO (2) Group Policy Objects (cont’d): • GPOs define Computer and User configuration adjustments. • GPO adjustments apply to all users/computers in the OU (and sub-OUs). • Computer policies occur before login; User policies occur during login. • Add a new package under software installation to deploy. When prompted, select the “Advanced” option to change settings.

  18. Creating a GPO (3) Group Policy Objects (cont’d): • The name and support information can be adjusted. • It is possible to have the package automatically uninstalled from clients, if the client is moved to another OU.

  19. Creating a GPO (4) Group Policy Objects (cont’d): • Packages can be created for MSP files to upgrade an existing package. • MST files can be added as Modifications to alter MSI packages. • MST files are the only way to provide adjustments.

  20. Systems Management Server (SMS) Systems Management Server (SMS): • Is a Microsoft management application. • It can be used standalone or to extend the functionality of Active Directory. • It provides a lot more functionality and adds reporting. • We currently support SMS v2 and 2003 (v3). System Center Configuration Manager 2007 (SMS v4) has not been tested. • SMS setup consists of a Server, Database and a Client. • Software deployments occur through the use of Packages and Advertisements to Collections of computers or users. Collections: • Collections are similar to OUs in Active Directory. • Client’s pass information to the server. • Passed information can be used to customize collections (All Windows XP Systems). • Additional collections can be created to further organize computers and/or users.

  21. Packages (1) Packages: • Are used to define any adjustment to a client system. • Define Access Accounts for accessing the package. • Define Distribution Points that hold the program. • Define Programs which will be run on the client system.

  22. Packages (2) Packages (cont’d): • Details as well as the program icon can be set • A source directory provides the location of the program files. Note that the client must be able to access the UNC or Mapped Drive exactly as shown.

  23. Packages (3) Packages (cont’d): • Adjustments to the shared folder can be made. • The priority can be changed on updating the package on distribution points.

  24. Package Program (1) Package Program: • Command line can be set for running the program. • Can be run when a user is logged in, when no one is logged in or both. • User rights and interaction can be set.

  25. Package Program (3) Package Program (cont’d): • Can set another package to run first, as well as how many times to run it. • Import the Product Code for easier management.

  26. Advertisements (1) Advertisements: • All packages must be advertised to a client, unless they are run by another package that is advertised. • Advertisements can be used to allow a user the choice to run a program or force a program to be run.

  27. Advertisements (2) Advertisements (cont’d): • Specify the package, program and collection to advertise. • Can set the advertisement start time, expire time and priority. • Can set the advertisement as mandatory, forcing the program to run.

  28. Advertisements (3) Advertisements (cont’d): • Specify whether the program runs from the distribution point or if the client will download the source files and run them locally. • Specify whether the client should check a remote distribution point.

  29. Citrix MetaFrame Presentation Server 4.5

  30. Citrix MetaFrame Presentation Server (1) Citrix MetaFrame Presentation Server (MPS): • Provides clients access to applications installed on a server. • Applications are installed on a server and published to clients. • Clients use software to connect to the server: • ICA Client • Web Client • A Citrix Farm can be implemented, which makes use of several servers that are managed as one to distribute the load. • We currently support Citrix MPS 3, 4 and 4.5. • We currently support Citrix ICA Client 8, 9, 10. • The web client has not been tested. • “Thick” clients refer to systems which function without a server. • “Thin” clients refer to systems that require a server to be functional. Most make use of embedded flash memory for boot tasks and runtime storage.

  31. Citrix MetaFrame Presentation Server (2) Citrix MetaFrame Presentation Server (MPS): • Uses the main Presentation Server Console for administrating the servers/farms. • MPS 4.5 introduces a new Access Management Console for administrating applications.

  32. Citrix MetaFrame Presentation Server (3) Citrix MetaFrame Presentation Server 4.5 (MPS 4.5): • Access Management Console provides a better overview of the current state of the server/farm.

  33. Publishing Applications (1) Publishing Applications: • Setup through PSC (v3,4) and AMC (v4.5) – interface is similar. • Can specify the name as well as quickly disable an application.

  34. Publishing Applications (2) Publishing Applications (cont’d): • Select type for publishing (can only be changed on initial setup). • Applications must be published as type: Application

  35. Publishing Applications (3) Publishing Applications (cont’d): • Location of the EXE being published. Must be the same on all servers. • Isolate will block the application from working with other applications.

  36. Publishing Applications (4) Publishing Applications (cont’d): • Add all servers the application is available from.

  37. Publishing Applications (5) Publishing Applications (cont’d): • Select all users or groups of users that can access the application.

  38. Publishing Applications (6) Publishing Applications (cont’d): • Change the icon and automatically add the application to the client’s desktop and/or start menu.

  39. Publishing Applications (7) Publishing Applications (cont’d): • Enable audio between the server and client. • Encrypt the data being sent between the client and server.

  40. Publishing Applications (8) Publishing Applications (cont’d): • Adjust the resolution and color of the application sent to the client. • Seamless window uses the client system’s display properties.

  41. ICA Client (2) ICA Client: • The ICA Client needs to be installed on the client system. • The Program Neighborhood can be modified to access the server. • Any applications available to the user will be displayed on login.

  42. ICA Client (2) Application Set Settings: • Adjust the communication method for connecting to the server. • Enable/Adjust the sound settings. • Adjust the colors and window size of the application being displayed on the client. • Adjust the login settings for connecting the client to the server.

  43. Dragon NaturallySpeaking Specifics (1) Dragon NaturallySpeaking Requirements: • Has far greater requirements for a server and network than typical applications. • A server that can handle 200 instances of Microsoft Word, would only be able to handle 6-10 DNS users. • Network bandwidth requirement of 1.3 Mbps dedicated during dictation. • Latency is another factor and can be quite high from remote points. •

  44. Dragon NaturallySpeaking Specifics (2) Connection Setup: • Legacy Audio must be turned on when publishing the application. • Two policies must be enabled on the server for sound. • Policies can be created on the server in the PSC.

  45. Dragon NaturallySpeaking Specifics (3) Connection Setup (cont’d): • Microphone support must be enabled for Client Devices. • The Client microphone must be enabled for audio input.

  46. Dragon NaturallySpeaking Specifics (4) Connection Setup (cont’d): • Sound quality must be enabled for the client system. • High sound quality must be allowed for the client system.

  47. Dragon NaturallySpeaking Specifics (5) Connection Setup (cont’d): • High sound quality must be enabled on the Client system. • A patch must be installed on the Client system. Citrix Audio Patch (vddns): • Provides Dragon the ability to adjust the sound settings on the Client system. • Required for proper communication between the sound system on the Client and Dragon running on the server. • Can be distributed through Citrix by publishing as Content. Must be run on each Client individually. • Must be the same version or higher than Dragon. • Will only work with ICA Client 8 and 9 out of the box. • TN 5761 contains the latest version that will work with ICA Client 10. • Log file: C:\Program Files\Citrix\ICA Client\vddns.log • Additional information can be found in the IT Administrators Help file. It is only available from the Start menu after installing the application.

  48. PDF Converter Specifics PDF Converter Specifics: • Standard application requirements. • Does not require any special policies or client adjustments. • Only the main application processes can be shared. Printer Setup: • Citrix can automatically add printers to a client system, making them available to locally installed applications. • If printers are installed on the Citrix server, they must be shared. • The ScanSoft PDF Create virtual printer cannot be shared. • The PDF Create printer will be available to applications running on the Citrix server. It cannot be made available to applications running on the Client systems.

  49. User Access RightsFile Locations Windows Registry

  50. User Access Rights User Access Rights: • DNS and PDF fully support all standard Windows User Types. • Restricted (Normal) Users are fully supported. • Administrators may further lock down a user profile which can cause problems with the software. Read Access Rights: • User Profile must have Read access to: • %ProgramFiles% • %SystemRoot% • %AllUsersProfile% • Hkey_Local_Machine – registry keys • User Profile must have read/write access: • %userprofile% • Hkey_Current_User – registry keys