Local Security Settings

This help file applies to an out-of-date version of MainBoss.
The most recent version of MainBoss is MainBoss 4.2.2.
For the latest version of this help file can be found here.

< Previous section  |  Table of Contents  |  Index  |  Next section >

If you are not using domains and you intend to use MainBoss on multiple machines, you may have to change the security settings on the computer where SQL Server is running. This is unnecessary if you're using domains.

In many cases, the security settings will already be correct by default. However, some versions of Windows do not have the correct settings. Also, if you upgrade your version of Windows, the upgrade process retains your old settings, even if they're different from the usual defaults of your new operating system.

To set up the correct settings, follow these steps on the computer where SQL Server is running:

  1. Open the Windows control panel.
In Windows 7 and 8, click System and Security, then Administrative Tools.
  • In Windows Vista and Server 2008, click Administrative Tools directly from the control panel.
    1. In the administrative tools menu, click Local Security Policy. This opens a window where you can change the security settings.
    2. In the left-hand panel of the window, expand Security Settings, then expand Local Policies, then click Security Options. MainBoss opens a list of security options you can set.
    3. Double-click on the entry for Network access: Sharing and security model for local accounts. This opens a window where you can set the option.
    4. In the drop-down list, choose the entry for Classic - local users authenticate as themselves.
    5. Keep clicking OK until you've closed all the windows.

    The alternative to Classic is that anyone logging into the computer will end up as a user called Guest (provided that Guest is enabled which is not true on many systems). Such a user would not be able to use MainBoss unless you authorized Guest as a MainBoss user...but then anyone could use MainBoss since Guest usually requires no password.

    < Previous section  |  Table of Contents  |  Index  |  Next section >