x Want to participate? Join the group to interact
  • State Verified Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 132 subscribers
  • Views 1081 views
  • Users 0 members are here
Browse Forums
Announcements
271
topics
260
replies
Databases and Operating Systems
764
topics
2k
replies
Financials Suite
1k
topics
3k
replies
General Discussion
2k
topics
10k
replies
Operational Suite
852
topics
2k
replies
Reporting and Analytics
1k
topics
3k
replies
Reports, Macros, and Customizations
877
topics
3k
replies
Sage CRM for Sage 300
183
topics
415
replies
Matt Baer

Stuck splash screen on Server 2019 published app. Can it be disabled?

SOLVED
Posted By

Hi I'm publishing Sage 300 using Windows Server 2019 Remote Desktop published app.   

It works great, except there is a documented bug with this version of RD whereas splash screens persist in the foreground and do not disappear.     This issue did not exist with previous versions of Windows,  seems to be just Server 2019.    

We've tried nearly every suggestion online to fix this behavior and it is by no means specific to Sage.    However, as a work around I found that older versions of Sage could disable the splash screen by modifying a registry key but this no longer exists.   I tried manually creating the key but had no effect.

Has anyone else experienced this hanging splash screen or know of a way to disable it on modern versions of Sage 300?

Thank you,

Matt

  • +1
    verified answer

    I just tried it on Sage 300 2022 and it worked for me. Were you adding to HKEY_CURRENT_USER?  Here's what I use in my .reg file:

    Windows Registry Editor Version 5.00

    [HKEY_CURRENT_USER\Software\ACCPAC INTERNATIONAL, INC.\ACCPAC\DESKTOP]
    "Splashscreen"="NO"

  • 0 in reply to Team Equation

    Thanks for rejuvenating the thought process.   I did get it to work on a local "workstation setup" install, wow it was so much faster!

    Also got it to work on the RD server by modifying the HKEY_USERS hive for a particular user.   After doing so the published app did remove the splash screen, but once the user logged off the actual RD server, the registry key was removed.

    Still trying to figure out how the registry works for users that don't have established accounts and have only ever opened up a published app.   We're playing with adding keys via GPO, if we figure it out I'll post the solution, getting closer!

  • 0 in reply to Matt Baer
    SUGGESTED

    Ok, we have had great success.    Created a GPO that only applies to the RD server.  The GPO runs a logon.vbs script when users launch the published app.  

    It registers the shell32.dll which creates the appropriate registry entries for the user without launching all the extra stuff like tray icons that comes with explorer.exe.    The script code we used for the logon.vbs was

    Set objShell = WScript.CreateObject("WScript.Shell")
objShell.Run("regsvr32.exe /s /n /i:U %SystemRoot%\System32\shell32.dll")

    The GPO also adds the registry keys and value that Team Equation referenced above in order to disable the splash screen.

    Now, even though a user has never connected to the RD server, the app launches with no splash screen and does not run extra taskbar tray programs.   So far so good!!!

*Community Hub is the new name for Sage City