The problem is with Windows 8.x or Windows 10 clients handling drive mappings differently than previous Windows versions. The reply posted earlier by Butch has one workaround; that method is summarized below: The issue that you are seeing is bug 36317. Please edit the following registry key to match the mapped drive: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\DynamicsSL\INSTALLDIR HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\DynamicsSL\ParentDirectory HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Solomon\Solomon IV Tools For Visual Basic\ParentDirectory Another client install approach is to first map the SL drive using the following steps: 1. Open a command prompt ‘as administrator’. From Windows 8 start menu type COMMAND. Right mouse click on ‘Command Prompt’ and select ‘Run as administrator’ 2. Map the drive share NET USE S: \\computername\sharename /PERSISTENT:YES 3. Run setup from the workstation folder CD APPLICATION\WRKSTN SETUP 4. Follow the usual prompts 5. Close the command prompt when completed 6. Open the command prompt without administrator From Windows 8 start menu type COMMAND. Select the ‘Command Prompt’ Entry. 7. Map the drive share NET USE S: \\computername\sharename /PERSISTENT:YES To verify try running Dynamics SL from the icon places on the Windows 8 menu as well as the Database Maintenance icon placed in control panel/Administrative Tools Note: to remove the network mapped drives will require removing both the Administrator privileged and the standard access mappings. Mapping the SL network drive in a network login script or group policy would require a similar set of steps.
↧