FAQ

Yes, DeskAlerts fully supports Active Directory, you can export users. DeskAlerts synchronizes with Active Directory continuously. You can export multi-domain or very complicated tree structure.

You can obtain full copy of DeskAlerts and host it within your corporate network or any other host (including cloud).

DeskAlerts can be installed on server sharing resources with another applications.

Usually we recommend to create a service account in AD with the dbo rights for DeskAlerts database and run the server installation using this account (in this case, you should just check “use Windows authentication”). If you’re feeling better working with SQL accounts – it’s perfectly fine, just create a service account there with the same scope of rights (dbo for DeskAlerts db).

It’s possible that your machine isn’t in Active Directory domain. By default, DeskAlerts with Active Directory support doesn’t send messages to the outside of domain. You can change this behavior by logging into DeskAlerts Control Panel with administrator rights, going to the Settings -> Common Settings and check “Mixed authentication” under the “Active Directory” section.

We always try to make communication of clients more effective, for this reason, we have a module for sending text messages through different SMS gateways. Because many SMS providers use unique API, we can't warranty correct work with everyone, but we ready to help you with configuration. You can see examples here.

Try removing all the special characters from the number you are using to send the SMS. Furthermore, you might want to check your SMS gateway service account dashboard – most likely, they have a log of API requests here with the exact reasons why messages may not be coming through.

Yes, using API another application can send alerts via DeskAlerts, please ask sales.

Each client consumes about 100Kb per hour in an idle mode. You can adjust this value by setting pool period.

Yes, Desktop Client can be packaged as MSI file.

DeskAlerts uses 80 HTTP port and 443 HTTPS (can be changed).

This issue may be caused by the current IIS settings being too small for the intended file uploads or downloads. You can change the size limit by editing the IIS metabase.xml file. Please check our Administrator’s manual, Troubleshooting section.

Yes, DeskAlerts supports both 32 and 64-bit.

Yes, you can share it with other databases.

Skin Service is done on our side. Send the graphic mock-up of desired alert appearance to your contact person in DeskAlerts and you will get the update shortly.

Always specify the Lifetime parameter if you’re sending the alert without schedule, or the correct End Date if you’re using scheduling pattern.

The alert should be Urgent and the DeskAlerts client on this workstation should be configured to receive locked screen alerts.

In most cases, new DeskAlerts clients within one software generation (4.x.x.x, 5.x.x.x, 6.x.x.x, 7.x.x.x, 8.x.x.x, 9.x.x.x,) can be installed over the previous ones. If you’re upgrading from one generation to another, you should consider the uninstall of previous versions.

If the generations of Server and Client software are the same (version number begins with the same digit), clients will receive alerts though some newest features may not work. If the generation gap is too big, outdated clients will receive error messages prompting users to upgrade the clients.

You should perform an IIS Restart, this is a requirement for most of the server updates. And you also need to clear web browser cache

There is an option for this in System Configuration, under Active Directory settings.

No, alerts are always displayed on top of other windows. You can re-view closed alert from the client History.

Sending a message by Broadcast will send the message to ANY user/group/computer/ou instance in the sender’s audience.

Try using the latest version of Internet Explorer or Chrome to work with DeskAlerts web UI. Some older browsers may partially skip some Javascript code, causing a few elements to disappear.