Micro$oft Windows
Sage Peachtree 2013 was crashing every time while attempting to save a Receipt entry.
This occurred only via Remote Desktop. Peachtree 2013 is installed on a Windows 10 1903 system, 8GB RAM and Intel 530 Graphics. Remote machine is a Windows 8.1 system, 4GB RAM and Intel Graphics.
Resolution was to change RDP properties to color of 24bit Color instead of 32bit and also uncheck Use Persistent Bitmapping.
Detailing the troubleshooting to resolve KB4515384 failure to install.
To mount a network location in Windows Subsystem for Linux, use the following commands.
In order to mount a Windows drive using DrvFs, you can use the regular Linux mount command. For example, to mount a removable drive D: as /mnt/d directory, run the following commands:
$ sudo mkdir /mnt/d
$ sudo mount -t drvfs D: /mnt/d
Now, you will be able to access the files of your D: drive under /mnt/d. When you wish to unmount the drive, for example so you can safely remove it, run the following command:
$ sudo umount /mnt/d
When you wish to mount a network location, you can of course create a mapped network drive in Windows and mount that as indicated above. However, it’s also possible to mount them directly using a UNC path:
$ sudo mount -t drvfs '\server\share' /mnt/share
Note the single quotes around the UNC path; these are necessary to prevent the need to escape the backslashes. If you don’t surround the UNC path with single quotes, you need to escape the backslashes by doubling them (e.g. \\\\server\\share).
WSL does not have any way to specify which credentials to use to connect to a network share. If you need to use different credentials to connect to the server, specify them in Windows by navigating to the share in File Explorer, using the Windows Credential Manager, or the net use command. The net use command can be invoked from inside WSL (using net.exe use) via interop. Type net.exe help use for more information on how to use this command.
Additional information: https://blogs.msdn.microsoft.com/wsl/2017/04/18/file-system-improvements-to-the-windows-subsystem-for-linux/
After installing Rand McNally IntelliRoute software, users may experience the error “Initialization of Client failed: Closing Application”
This problem is usually attributed to inadequate permissions for the user running the application. Please ensure that the folder that Rand McNally software was installed (generally C:\Program Files (x86)\Rand McNally) has Full Control access granted to users. Also, the Registry Key HKEY_LOCAL_MACHINE\SOFTWARE\Rand McNally on the workstation needs to grant “Full Control” to users who execute the program at the desktop level.
The above issue had to do with 64bit installation of IntelliRoute. Below is the issue I experienced with the 32bit installation of IntelliRoute.
I installed the application as an administrator and changed permissions on the Registry Key as well as the Program Files directory as noted above. However, I still received the error.
Using procmon, I tried to get some clues as to why it was crashing. I saw a hint that it looked for a file in C:\Users\%username%\WINDOWS\Sysupz.com.
Upon further investigation, this file did not exist for my test user, however it did exist in for the administrative user that I installed the application under.
To test it out, I copied the file to my test user WINDOWS folder and attempted to launch IntelliRoute and it was a success.
To copy the file to all the users on the server, I used the following command:
cd c:\users\
for /d %u in ("*") do copy c:\users\testuser\WINDOWS\Sysupz.com c:\users\%u\WINDOWS\
This seemed to resolve the issue. I’m not certain if the problems with installation are due to it being installed on a Server 2008 terminal server. That system is slated for migration to Server 2019 in December, so hopefully the IntelliRoute software will not give me problems then!
Using the following command, a computer can be joined to an existing Active Directory Domain.
netdom join %computername% /domaind:DOMAIN /userd:username /passwordd:password
PowerShell it can be accomplished with the following.
add-computer -domainname domainname -credential domainname\username -restart