If you have Capital installed on a network, in order for the workstations to run you must also perform a network client install on each workstation.  This will prepare the station to run our programs.


The program winclient.exe contains only the components needed for a workstation to run the program from the server. It is not the entire program. If you do not have Capital installed on your server, please contact us at 517-324-9100 or email customerservice@capitalrating.com to get it.

To download Capital's network install program:

1. Click Download WinClient Now below.
   
   
2. When this dialog below pops up select Save. Should any security questions come up just click ok to each.
3. In the Save As dialog, browse to the drive and directory on your file server where Capital is installed. Once there save Winclient.exe.

Vmware Image Updated - Mac Os

Apple’s End User License Agreement (EULA) explicitly states that macOS is only authorized for installation on .

After patching, “Apple Mac OS X” appears as a guest OS option. mac os vmware image

However, the technical reality of running macOS on non-Apple hardware—often called a "Hackintosh" in a virtualized form—is fraught with friction. Apple’s End User License Agreement (EULA) explicitly states that macOS may only be installed on "Apple-branded computers." Consequently, a macOS VMware image running on a Dell or Lenovo laptop is technically a violation of the software license. While VMware is a legitimate virtualization giant, and Apple itself allows macOS Server to run virtually on Apple hardware, the gray market of pre-made images downloaded from forums and torrent sites is legally precarious. These images often bypass security checks like System Integrity Protection (SIP), leaving them vulnerable to malware. Users downloading a "ready-to-run" macOS image from an unverified source are not just risking a lawsuit; they are inviting rootkits and keyloggers into their hypervisor. Users downloading a "ready-to-run" macOS image from an

: During the first boot, you must use the Disk Utility within the VM to "Erase" and format the virtual drive to APFS before the installer can see it. leaving them vulnerable to malware.