x Want to participate? Join the group to interact
Options
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 3 replies
  • Subscribers 97 subscribers
  • Views 2212 views
  • Users 0 members are here
Browse Forums
Announcements
151
topics
113
replies
General Discussion
5k
topics
13k
replies
Payroll & Tax
633
topics
892
replies
Reporting and Analytics
573
topics
1k
replies
Service Alerts
1
topics
0
replies
Software Development Kit (SDK)
435
topics
672
replies
Year End
83
topics
128
replies
BFoster

Sage 50 2019 installation problem in an Active Directory domain environment

SOLVED
Posted By

Hi,

I'm the IT system administrator for my company.  We have several people using Sage 50 US over a Windows Active Directory domain network.  Our company data is on a Windows 2012r2 server and the network share is mapped to the W drive for users.

I need to install the Sage client on a new Windows 10 domain joined machine but the network install method (ClientInstall.bat) is not working.  It just opens a command window and sits there for 15 minutes with no activity.

I resorted to doing the manual installation approach using the installer downloaded from the Sage website.  (https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=93912&sliceId=1&cmd=&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl&micrositeID=MS_Agent)

I am logged in as a domain administrator and can open the contents of the Sage company share (W:)

When I run setup.exe (as administrator) everything goes fine until I get to the screen shown in the screenshot below:

The dropdown menu for 'Select a mapped drive' is empty and does not show Drive W: even though when you go to Windows File Explorer the Sage drive is mapped correctly and everything shows fine.

My firewall is off.  I can ping our sage server just fine.

Any help or advice is greatly appreciated!

Top Replies

Parents
  • 0

    Update:  I figured out a workaround for this.  Even though our Sage share is already mapped to drive letter W with group policy, I mapped the share to a second drive letter (S) using the 'Find a Computer' button.  This pulled up the standard Windows drive mapping window.  It then let me continue with the installation, having the same share mapped to two different drive letters.  When I got through the installation Sage opened and showed the S drive.

    Closing and re-opening Sage allowed me to find the original share, mapped to W.  I think at that point it is probably safe to unmap the S drive and use the original mapped drive (W).

Reply
  • 0

    Update:  I figured out a workaround for this.  Even though our Sage share is already mapped to drive letter W with group policy, I mapped the share to a second drive letter (S) using the 'Find a Computer' button.  This pulled up the standard Windows drive mapping window.  It then let me continue with the installation, having the same share mapped to two different drive letters.  When I got through the installation Sage opened and showed the S drive.

    Closing and re-opening Sage allowed me to find the original share, mapped to W.  I think at that point it is probably safe to unmap the S drive and use the original mapped drive (W).

Children

*Community Hub is the new name for Sage City