This section describes the environment that needs to be established and maintained for Conquest II to operate on a Microsoft Active Directory Network.
•Do a of Custom Install of Conquest II to acquire SQL scripts and deploy with SQL Server Management Studio, to:
•Either Update an existing Conquest Database
•Or Create an empty Conquest Database
•An ODBC Data Source (System DSN), created with the 32 bit ODBC Administration Tool, that uses the SQL Server Driver and has the Conquest Database selected as the Default Database. For more Details see ODBC Data Source
•Create a Conquest Administrator AD Group or User and on the SQL Server side, grant them the dbOwner database role and the ConquestAdmins database role (ordinary users/group will be granted the dbWriter and Conquest roles)
•Considerations:
•Conquest II is installed with an Executable because it predates the modern Microsoft Installer. For organisations with Conquest III, which is always installed with the Microsoft Installer to a single Web Server, it is recommended that as many Conquest Users as possible are migrated to Conquest III, to simplify future upgrades.
•Decide on the version of Microsoft Access Professional to run on:
•2010 version installed as part of Microsoft Office 2010 (recommended and suitable from Conquest II V2.57a1 onwards)
•2003 Runtime supplied in the Conquest Runtime product
•Whichever Microsoft Access component is chosen, it must be installed before Conquest II is.
•Folders and share names in the paths for Conquest II must not include characters that Microsoft has designated to be Special e.g. & < > ( ) @ ^ |
•If such characters are already entrenched in the network, create new Shares to the specific folders for Conquest files that do not include those special characters, and use them in the installation paths and also in the Conquest System Options, if necessary
•The installation program must be run with Local Administrator privilege.
•All Conquest Mobile Inspection Programs that have been downloaded to CMTPC or CMPPC from the version of the Conquest II database that is being upgraded, must first be uploaded
•Even if the release notes for CMPPC and CMTPC state that later versions of Conquest II are compatible, there might be data anomalies, should the Conquest II upgrade be made between a Download and its corresponding Upload