MusicMaster Blog

by Jerry Parker, Director of Operations

If you manage a lot of users in MusicMaster CS, like schedulers, librarians, admins, or engineers, you already know the pain of maintaining separate logins. Accounts have to be created, rights assigned, and eventually disabled when someone leaves. That’s a lot of manual work and plenty of room for error.

With MusicMaster CS, you can connect user authentication directly to Windows Active Directory. No more juggling separate logins. Users simply sign in with their normal network credentials. IT controls the credentials, while MusicMaster CS handles the access and role mapping automatically. You can even restrict access so that only users with valid Active Directory credentials can open MusicMaster CS, reducing administrative load and keeping everything centralized.

In plain English, Active Directory integration gives you a simpler, centralized way to manage user access, onboarding, and departures, all from within IT’s existing directory tools.

Why integrate with Active Directory?

Here’s why connecting MusicMaster CS to Active Directory is a smart move:

• Centralized authentication: Your IT team adds a new hire to Active Directory. Their credentials automatically grant access to MusicMaster CS as soon as the user is mapped to a corresponding MusicMaster CS User and Role set.
• Automatic offboarding: When someone leaves the company, disabling the account in AD immediately blocks access to MusicMaster.
• Stronger security posture: Password complexity rules, lockouts, two-factor authentication, and all your other directory-level security settings can apply to MusicMaster CS access.
• Audit and compliance: MusicMaster CS shows who is logged in and when, while AD handles authentication, lockouts, and password aging.
• Together, these benefits mean fewer surprises, cleaner audit trails, and complete alignment between IT policy and programming workflow.

What It Looks Like in Practice

• In Active Directory, your IT team creates and manages user accounts and resource access.
• In MusicMaster CS, each user is mapped directly to their Active Directory account.
• You assign the appropriate MusicMaster CS role to match the user’s privileges.
• When they log into Windows with their AD credentials, access to MusicMaster CS is granted automatically.
• (Optional) Enable fail-over authentication, so MusicMaster CS can still present a login box if AD is unavailable.

Results: No more local passwords. No more “I forgot my MusicMaster login.” No more mystery accounts.

Planning Tips

• Decide whether you’ll allow or disallow direct MusicMaster CS logins.
• Lock down permissions in MusicMaster roles, not AD groups.
• Keep at least one internal “super-admin” account as a safety valve if AD becomes unavailable.

The Result

• You free yourself from user administration in multiple systems and align MusicMaster with the same security enforcement your organization uses everywhere else.
• Your schedulers get one password.
• Your IT team gets central control.
• You get cleaner security and simpler onboarding and departure processes.

It’s a small change with a big payoff.

Requirements

• Configure your MusicMaster CS Server(s) to enable LDAP/Active Directory
• TEST your LDAP connectivity
• Add users normally, and assign roles and stations
• Decide whether to allow fail-over login
• Click the “Select External Account” button in the User Edit screen.
• Choose the correct user account and save your work.

That’s it! When a user logs into Windows with their AD credentials and opens MusicMaster CS, access is granted automatically. All local settings, profiles, screen layouts, and other user preferences are preserved exactly as before.

Configuring MMCS Server:

Right-click on your tray app, and access “Server Configuration.”

Choose the User Authentication Tab, and enter details for your LDAP Server.

(Don’t forget to specify the server by IP and PORT)

Once your server details are entered, click “Test” to validate the connection.

If you get a success message, the MMCS Server is configured correctly. Repeat for each of your MMCS Servers. Once all MMCS servers have LDAP enabled, your server configuration is complete!

Configuring MMCS USER accounts:

Select the “Gear” dropdown, choose “Manage Users and Accounts” to access the users and roles.

Next, choose a pre-defined user (or you can create a new one), right-click the intended user and choose “Edit.”

Next, choose “Select” to fetch “external Accounts” from LDAP/Active Directory:

The system will return a list of all Active Directory Users. Simply select the appropriate user and choose “OK” to map the MusicMaster CS User to the Active Directory User. Once mapping is complete, the user will be fully qualified for MMCS Access via their Windows logon credentials, allowing gated access to MMCS via Active Directory!

(Note: the checkbox “Show Accounts Already assigned to another MMCS user” will allow you to review any current MMCS/AD mappings saved in the system)

Final Thoughts

Integrating with Active Directory takes just a few minutes to configure but delivers lasting benefits. It centralizes access control, improves security, and eliminates duplicate user management. Once it’s in place, you’ll wonder how you ever managed without it.

Once configured, AD integration turns user management into a background task. Your IT policies handle authentication, your MusicMaster CS roles handle permissions, and the two stay in sync. It’s clean, reliable, and built for enterprise-grade operation.

It’s another example of MusicMaster CS quietly doing the heavy lifting in the background, so your team can focus on what really matters: great programming.

If you’d like help planning or testing your setup, our support team is ready to assist. We’ll walk you through the setup and best practices, and ensure you get it right the first time!