7.4

Table Of Contents

Getting Started

This section will help you get started with PlanetPress Design

Environment Considerations

This page is intended to provide technical information about the environment in which PlanetPress Suite is intended to run.

Terminal Server/Service

PlanetPress Suite does not support Terminal Server (or Terminal Service) environment as possible under Windows 2000, 2003

and 2008. This is to say, if Terminal Service is installed on the server where PlanetPress Suite is located, unexpected behav-

iours may occur and will not be supported by our company. Furthermore, using PlanetPress Suite in a Terminal Service envi-

ronment is probably an infringement of our End-User License Agreement.

Terminal Service is not to be confused with "Remote Desktop" used in conjunction with the "Remote Desktop" options of all

Windows operating systems. Remote Desktop, when used to connect to a PlanetPress Server in a non-simultaneous setting, is

perfectly acceptable. However, it has been reported that PlanetPress may lock up when access through Remote Desktop con-

nections.

VMWare/ESX

PlanetPress Suite supports VMWare Workstation, VMWare Server, VMWare Player and VMWare ESX infrastructure envi-

ronments as software installed on the Guest operating system. However, note that only PlanetPress version 7.1.3 and higher

support VMotion under ESX. Also note that copying (duplicating) your VMWare Guest Machine and using it simultaneously con-

stitutes an infringement of our End-User License Agreement.

Note that while VMWare ESX, Workstation, Server and Player (from VMWare, Inc.) are supported, other virtual environments

(such as Microsoft Virtual PC, Parallels, Xen and others) are not supported at this time.

32-Bit or 64-Bit?

PlanetPress Suite version 7.1.3 and higher support 64-Bit operating system. However, our application remains 32-bits in this

environment, which means that for all intents and purposes there is no difference between those two environments as far as

PlanetPress Suite is concerned.

Network Considerations

Mapped Drives

This section only applies when sending documents to the PlanetPress Suite Workflow Tools and when using mapped

drives in your PlanetPress Talk scripts or in any variable property that refers to a mapped drive path.

Mapped drives (for example, drive X: leading to \\server\public\)are always user-specific and are created at logon. This

means that mapped drives are typically not available by the PlanetPress Suite services when running a live configuration. Fur-

thermore, while the mapped drives are not shared, they are still limited to one map per computer, meaning if one user maps

the X: drive, a different user (or a service)will not be able to map it again.

Getting Started