Sage 100

Will the March 2020 Common Components change Elliot spoke about in the last round table fix the issue where users have to run Sage elevated? Or is it just a fix for installing the client? 

I have an IT guy asking why users have to run the client as an Admin, and I never know how to answer it other than "Because Sage does what they want...and maybe have lazy programmers? I don't know, let me find out for you" - then just hope they forget. I know I have seen several threads about this, but for the life of me can't find any of them using the search. Help!? How do you respond to this question?

------------------------------
Michelle Forsey
Eide Bailly, Inc.
801-456-5470
------------------------------

My experience is when asked Sage replies the same way --- "  I don't know, let me find out for you" - then just hope they forget.  "

I have found it exceptionally difficult to get any substantial documentation out of Sage when required by IT.

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
------------------------------

Giving full control (NTFS) to the local workstation folder (C:\Sage\...) often helps.  SI needs something extra buried in Program Files somewhere.  Of course there is the Paperless registry entry too, which is often wiped out.

I'm also curious what is being fixed.

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

Original Message:
Sent: 12-31-2019 12:37
From: Wayne Schulz
Subject: Sage 2020 Common Components change

My experience is when asked Sage replies the same way --- "  I don't know, let me find out for you" - then just hope they forget.  "

I have found it exceptionally difficult to get any substantial documentation out of Sage when required by IT.

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
------------------------------

I'll find out.  The Dev team members that I've worked with for our roundtables have been pretty responsive.  We may not always like what they say but I usually get some answer.

------------------------------
Moira Goggin
Executive Director
90 Minds, Inc.
------------------------------

Original Message:
Sent: 01-06-2020 18:27
From: Kevin Moyes
Subject: Sage 2020 Common Components change

Giving full control (NTFS) to the local workstation folder (C:\Sage\...) often helps.  SI needs something extra buried in Program Files somewhere.  Of course there is the Paperless registry entry too, which is often wiped out.

I'm also curious what is being fixed.

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


Original Message:
Sent: 12-31-2019 12:37
From: Wayne Schulz
Subject: Sage 2020 Common Components change

My experience is when asked Sage replies the same way --- "  I don't know, let me find out for you" - then just hope they forget.  "

I have found it exceptionally difficult to get any substantial documentation out of Sage when required by IT.

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990

Here are the replies:

The change is to no longer require elevated permissions in order to run the Workstation Synchronization (Workstation Sync) that is usually required on all workstations after installing a PU or when launching Sage 100 on a machine for the first time.

This was accomplished by moving the location of the Sage\Common Components from C:\ProgramFiles\CommonFiles to C:\ProgramData.

To clarify, this applies to Workstation Synchronization. Sage 100 Workstation Setup will still require Administrative rights.

------------------------------
Moira Goggin
Executive Director
90 Minds, Inc.
------------------------------

Original Message:
Sent: 01-06-2020 18:34
From: Moira Goggin
Subject: Sage 2020 Common Components change

I'll find out.  The Dev team members that I've worked with for our roundtables have been pretty responsive.  We may not always like what they say but I usually get some answer.

------------------------------
Moira Goggin
Executive Director
90 Minds, Inc.
------------------------------


Original Message:
Sent: 01-06-2020 18:27
From: Kevin Moyes
Subject: Sage 2020 Common Components change

Giving full control (NTFS) to the local workstation folder (C:\Sage\...) often helps.  SI needs something extra buried in Program Files somewhere.  Of course there is the Paperless registry entry too, which is often wiped out.

I'm also curious what is being fixed.

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


Original Message:
Sent: 12-31-2019 12:37
From: Wayne Schulz
Subject: Sage 2020 Common Components change

My experience is when asked Sage replies the same way --- "  I don't know, let me find out for you" - then just hope they forget.  "

I have found it exceptionally difficult to get any substantial documentation out of Sage when required by IT.

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990

Thank you for digging into that Moira! I appreciate the clarification.

------------------------------
Michelle Forsey
Eide Bailly, Inc.
801-456-5470
------------------------------

Original Message:
Sent: 01-14-2020 14:30
From: Moira Goggin
Subject: Sage 2020 Common Components change

Here are the replies:

The change is to no longer require elevated permissions in order to run the Workstation Synchronization (Workstation Sync) that is usually required on all workstations after installing a PU or when launching Sage 100 on a machine for the first time.

This was accomplished by moving the location of the Sage\Common Components from C:\ProgramFiles\CommonFiles to C:\ProgramData.

To clarify, this applies to Workstation Synchronization. Sage 100 Workstation Setup will still require Administrative rights.

------------------------------
Moira Goggin
Executive Director
90 Minds, Inc.
------------------------------


Original Message:
Sent: 01-06-2020 18:34
From: Moira Goggin
Subject: Sage 2020 Common Components change

I'll find out.  The Dev team members that I've worked with for our roundtables have been pretty responsive.  We may not always like what they say but I usually get some answer.

------------------------------
Moira Goggin
Executive Director
90 Minds, Inc.


Original Message:
Sent: 01-06-2020 18:27
From: Kevin Moyes
Subject: Sage 2020 Common Components change

Giving full control (NTFS) to the local workstation folder (C:\Sage\...) often helps.  SI needs something extra buried in Program Files somewhere.  Of course there is the Paperless registry entry too, which is often wiped out.

I'm also curious what is being fixed.

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


Original Message:
Sent: 12-31-2019 12:37
From: Wayne Schulz
Subject: Sage 2020 Common Components change

My experience is when asked Sage replies the same way --- "  I don't know, let me find out for you" - then just hope they forget.  "

I have found it exceptionally difficult to get any substantial documentation out of Sage when required by IT.

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990