Installation guide

and earlier. Hold a kick-off meeting for the key stakeholders in the upgrade to explain this and to
identify:
• Site requirements
• Preparations required for success
• Expectations and responsibilities
• Upgrade project milestones
Document the decisions made at the kick-off meeting and deliver these to the site’s primary project
sponsor.
Next, develop a communication plan with the PACS Administrator to ensure that project schedules,
expected changes, and other important information is effectively conveyed to affected personnel at
the site. Also inform the Agfa GSN group about any expected down times.
IMPAX data stored in AD LDS and MVF databases
(Topic number: 48414)
Part of the migration process from IMPAX 5.2 or 5.3 is to move some data from the MVF database
that resides on the IMPAX Database Server to the AD LDS (Windows Server 2008) database that
resides on the new IMPAX Application Server. This topic gives an overview of what data is transitioned
to AD LDS .
In general, user data is stored in AD LDS, while study data is stored in MVF. For example, the
following data is stored in AD LDS:
• User IDs and passwords, except for external LDAP users. For LDAP users, that information is
stored in LDAP, and a mapping to this information is stored in AD LDS.
• User permissions (operations and study status flags).
• User licenses.
• User and role preferences set in the Client Configure area settings.
• Image area user profile settings.
• User preferences for the List and Text area (such as which panels are displayed in the Text
area).
• Image area wizards and List area script wizards.
• Station, container, and station container configurations.
Among the information that remains in the MVF database is the following:
• Printer configurations
• Study keywords
• Enumerated values
AS300 Preparing to Upgrade Guide—IMPAX 4.5, 5.2, 5.3,or WEB1000 to IMPAX 6.5.3 21
Agfa Company Confidential—Subject to Non-Disclosure Obligation