web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested Answer

SL 2018 install question

(0) ShareShare
ReportReport
Posted on by 134

Hi all, we currently have SL 2018 CU1 installed using Windows Authentication and also have a Remote Desktop Services (terminal server) server that user's use with the client installed. The RDS server is Server 2016. Basically when I set this RDS server up, I installed it in terminal server install mode. Does anyone know if this is still required? The issue I'm having is that user's are being prompted for their SL credentials on every new login to the server. When they log onto the server, their solomon.ini is being replaced with a new copy. This new copy is coming from the System32 folder. Thanks in advance.

I have the same question (0)
  • Suggested answer
    Erich Strelow F Profile Picture
    16 on at

    Sorry to say that the initial login prompt appears by design. You can leave the password field blank and choose a company. After that, further logins to SL skips the user prompt. You probably already guessed that one.

    You can tweak this behavior by the way of setting up centrally managed home folders or through login scripts.The home folders is the more complete solution, since it gives you extra control over your user profiles and behaviors, but it requires skills and infrastructure that's beyond my league. Check out https://support.microsoft.com/en-us/help/816313/how-to-assign-a-home-folder-to-a-user to further investigate this.

    To setup login scripts, you can create a command-line script similar to this:

    set slprofile=%userprofile%\appdata\roaming\microsoft dynamics sl
    set server=
    set sysdb=
    set defcompany=
    if not exist "%slprofile%" (
       mkdir "%slprofile%"
       echo [System32 Database] > "%slprofile%\solomon.ini"
       echo DatabaseType=MS >> "%slprofile%\solomon.ini"
       echo Database=%sysdb% >> "%slprofile%\solomon.ini"
       echo Server=%server% >> "%slprofile%\solomon.ini"
       echo [Company] >> "%slprofile%\solomon.ini"
       echo CompanyID=fcompanyÞ¥ >> "%slprofile%\solomon.ini"
       echo UserID=%username% >> "%slprofile%\solomon.ini"
    )
    

    Store this as a file like "setup-solomon.cmd" in a way it will be readable by all users.

    Then setup a login script through task scheduler, referencing the file.

    You must setup both the username and the initial company in order to avoid the login prompt.

  • CFROTON Profile Picture
    4,710 on at

    Hello Krogerss,

    Hmmm.. why there’s a Solomon.ini file in the system32 folder.  The only places that a Solomon.ini file should reside is in the SL root and in the user profile… I wonder if they rename/remove the .ini does the issue persist?

    Best Regards,

    Jana MacDonald

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 664 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 522 Super User 2025 Season 2

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 303 User Group Leader

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans