...
Now run the Configuration wizard using an account that has (at minimum):
DBO permissions on the database (in order to create tables, edit schemas etc.)
Local administrator rights (in order to manage local folders, services, certificates, etc.)
You may need to use the 'runas' functionality from a command line in order to impersonate a user which has these required privileges:
| Code Block | ||||
|---|---|---|---|---|
| ||||
runas /user:MyUserMyUserWithAdminPriv ConfigurationWizard.exe |
Please ensure that on the connections tab of the configuration wizard you have checked the 'Skip Sql Server sysadmin operations...'
...
If the user currently running the Configuration wizard has DBO access to the Connexion database(s) you have created, then you can use "Current User" option in the 'Database Connexions' tab:
If your current user does not have DBO access to the Connexion database(s), you can provide the credentials of a Windows/Domain account which does. Please note that this account must be valid on the current machine (meaning that if it's a Windows user, this user must exist locally. If you provide a domain user, the current machine must be joined to the domain).
