Deploying Sage 300 Workstation without shared drives

In our current antiquated Accpac, we are using a shared mapped drive to store some Accpac DLLs for customized reports. Moving forward, we are planning to upgrade to either version 2014 or 2016 of Sage 300. Meanwhile, there has been recent corporate IT security policy that stops the use of all shared folders (due to SMB protocol, and moving all the current shared documents to SharePoint).

Question - must a shared folder be required? Can't we do a full client installation on every user's computer?

Since we can't use shared folders, we can't deploy Sage 300 as a client/server app (ie. Workstation). Web portal/screens/Sage300c are all out as well since they can't do customized screens and reports (We also want to add a Asset Management module from Norming). So, what's left is just the Remote Desktop Services option, which we aren't really keen.

I've been trying to build up justification to stick to the Workstation order. All of our users' computers are Windows 7 (moving to Windows 10 by the end of the year). Perhaps I could somehow propose enabling only SMBv2 or v3 (more secure?), and having the shared folder (shared as "hidden" from the server), and also to use UNC paths instead of an explicit mapped drive.

Comments, suggestions? Thanks!

  • 0
    You still need a shared folder for common files - there is no way around that, but you can use a hidden share. Mapped drives are so 20th century, no one uses them anymore. Full client installs is a dumb idea, stick with workstation setups - less maintenance and other issues.
    Use Customization Directories for custom reports - look in Administrative Services, Customization Directories.
  • 0 in reply to 49153
    I suppose a hidden share could work. But is that hidden shared folder still accessible via SMB protocol? Yes, Workstation setup is still my preferred method as I really do not want to go down the RDP path.
    I don't have a copy of the installation guide, but am I right to guess that the UNC path of the hidden share will be specified in the Customization Directories settings in Administrative Services?
  • 0 in reply to JohnAA
    You do have a copy of all the manuals - you just don't know it. Click Help, Documentation and open the ENG folder.
    We're talking Windows networking here right - all Windows shares are SMB protocol.
    You are NOT going to be able to run Sage 300 without any Windows share in a client/server setup - that is the reality. The only option to run Sage 300 without a share would be by using terminal server.
  • 0 in reply to 49153
    What I have is a very old version of Accpac (v5.*). Not sure if the documentation applies to Sage 300 2014? Anyway, now it looks like the only way to go is RDP. Shared drive is a complete no-no even if it's hidden. Even with terminal server/RDP, I believe a shared folder on the server is still required for customized reports/screens/DLL, yeah?
  • 0 in reply to JohnAA
    So which hair brained twit came up with the idea of not using shares? He/she needs to be retrained. That is ridiculous, in the 20+ years of working with Sage I've never come across such a stupid idea.
    You're all over the place, you need to focus. V5 documents apply to v5, Sage 300 2014 documents apply to Sage 300 2014.
    If you are running Sage 300 on a terminal server and all users access Sage 300 on that TS then no shares are required.
  • 0 in reply to 49153
    Also if you have the Sage 300 2014 or 2016 install then the manuals are in the Docs folder, you can extract the ISO file using 7Zip (www.7-zip.org)
  • 0 in reply to 49153
    RDP is our only option now. Slipped my mind that we have a trial version of Sage 300 2014 installed. Shall go look for the manuals there.