General Consultant Discussion

 View Only
  • 1.  Do you have a boilerplate request for IT requesting VPN, account setup when you perform upgrades?

    Posted 06-28-2023 09:02

    It would be helpful to have one boilerplate list of Windows accounts and their related security that we could give to IT at the start of an upgrade or new implementation. As it stands now, I mostly ask for an administrator account and hope that I get it. 

    This is even more important when dealing with Sage Premium since a couple of accounts are needed through the implementation.

    Something like: 

    SAGE CONSULTANT

    • An account  that is a local admin domain user with no time restrictions on usage though you may set it to expire on mm/dd/yy which is when the work is scheduled to be completed and accepted.
    • Full access to the Sage server(s)

    SAGE 100

    • Sage 100 runs as a service - for that, we require a local admin domain service account - this should not expire or require password changes unless those expirations/changes will be maintained by IT
    • For Sage 100 Premium we require either the SA account or an equivalent for both the source ( existing ) and destination ( upgrading to ) SQL server

    Something like this, though, I'm sure that I've missed a bunch of stuff or characterized some accounts incorrectly. Getting a high-level account from very small companies is usually not that tough. The problem is that (a) small companies are leaving Sage 100, and (b) big companies aren't going to provide high-level access without some justification.

    Does anyone have something similar that they maintain?



    ------------------------------
    Wayne Schulz
    wayne@s-consult.com
    Schulz Consulting
    (860) 516-8990
    Moodus, CT
    ------------------------------


  • 2.  RE: Do you have a boilerplate request for IT requesting VPN, account setup when you perform upgrades?

    Posted 06-28-2023 09:29
    Edited by Brett Zimmerman 06-28-2023 09:29

    Generally-speaking I typically request "administrator-level remote access to both the current and new Sage 100 servers, ideally unattended (e.g. VNP/RDP), or if needed we can just use my logmein-unattended, although I would still need a logon".



    ------------------------------
    Brett Zimmerman
    Net at Work
    Greater Boston Area
    ------------------------------



  • 3.  RE: Do you have a boilerplate request for IT requesting VPN, account setup when you perform upgrades?

    Posted 06-28-2023 09:56

    I usually do the same. On bigger installs, there can be several accounts the IT department may need to create. I will just work on such a list if nobody has something already done. Thanks! 



    ------------------------------
    Wayne Schulz
    wayne@s-consult.com
    Schulz Consulting
    (860) 516-8990
    Moodus, CT
    ------------------------------



  • 4.  RE: Do you have a boilerplate request for IT requesting VPN, account setup when you perform upgrades?

    Posted 06-28-2023 10:16

    For the Sage 100 service account you may want to specify that this account should not be given permissions to login remotely for security purposes.



    ------------------------------
    Gary Feldman
    I-Business Network
    Marietta GA
    16786270646
    http://www-i-bn.net
    ------------------------------



  • 5.  RE: Do you have a boilerplate request for IT requesting VPN, account setup when you perform upgrades?

    Posted 06-28-2023 12:34

    Each one is different, depending on the version / upgrade details.  Here are a few points from the top of my head:

    • Local admin to the new Sage server.
    • A "service account" with local admin permission, and a non-expiring password.
    • A remote connection method that allows us to reconnect after server reboot.
    • SQL "sa" account for Premium (both source and destination instances). 
      • (Plus a bunch of other non-permission details related to SQL setup).
    • Access to where the old Sage is installed (if on a different machine).
    • An Admin level Sage 100 login (and ideally the "administrator" password).
    • Access to any network paths used in Sage (like if Paperless files are stored on a file server).


    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------