Presently a login/password must be entered during the installation of Sage 100. This can present a problem for remote consultants who do not have the credentials and are working on the initial staging of the installation.
Frequently the IT departments may not share local admin level logins, may not want to create a separate login for the consultant. If the consultant does have a login and password to the network that account may expire rendering it unusable for integration engine purposes.
The Integration Engine login and password portion of the install should allow for a "SKIP" steps so that this option can be bypassed and Sage 100 completely installed without the consultant needing to possess the network login and password at the time of initial installation.
by: Wayne S. | over a year ago | Integration
Comments
It would be even better if the CRM service and installing the module could be completely bypassed!
At least 95% of the time the Integration Engine sits unused, and it is simple to do such an install later (if the customer actually _wants_ to use Sage CRM).
Why are we _forced_ to install it on every server (causing complications in more than a few special circumstances, like Wayne's above)?
Agree 100%. Another reason is the amount of time it takes to explain to the client's IT person why Sage is requiring a windows login and password to create a service that it's not going to use.
If a "Skip" options can't be added, then at least create the service using the Local System account so no login is needed during the installation.