Have you ever found yourself in need of more than just one domain? Are your production and test domains separated into two different forests? Or maybe you use a disaster recovery domain in which a trusted relationship does not exist between the production domain and DR site? If you are a managed service provider (MSP), you might have a dozen domains and need a tool capable of multi-tenant server monitoring.
Previous versions of SysKit had functionality, but using it was a little bit messy and not as intuitive as you might like. You had to have an agent installed on a server in every domain in order to collect data from all of them, and all domains had to have trusted relationships between them. With SysKit’s new multi-tenant server monitoring support, it is easy to handle use cases such as these. In the course of this blog post we will show you how you can accomplish these tasks using SysKit.
Here are a couple of use cases where having a multi-tenant server monitoring ability might come in handy.
1. Monitoring multiple domains
If you just want to monitor servers from multiple domains and you don’t want complications with untrusted domains and multiple logon accounts, you’re in luck. Now you can avoid having to take countless steps and run complicated scripts. After you install SysKit, all available domains are automatically discovered and are ready to be monitored. In case you need to add untrusted domains, you can do that manually by entering the domain name or domain controller or just the IP address of the remote active directory domain controller.
2. Using a specified service account for each domain
It’s not uncommon in multiple-domain environments for each domain to have its own set of specified domain admins and for users from other domains to be prohibited from accessing its servers. Having that in mind, we’ve added the ability to specify credentials for each of the domains in your environment using a simple, easy-to-use interface. SysKit handles all the authentication challenges behind the scenes, so you don’t have to worry about it.
3. Monitoring untrusted domains
Another problem with monitoring multiple domains occurs when domains don’t have trusted relationships between each other. Basically, this means that users from one domain can’t see or access servers in another because there is no trust between them. This is a common occurrence for managed service providers (MSPs). Every MSP has a number of clients, all with independent infrastructures, and it’s crucial to ensure that clients can’t see or access each other’s domains or the MSP’s domain. A common-use approach for accessing domains in these scenarios is using separate credentials for each client domain. And since untrusted domains cannot be discovered automatically, monitoring them was not supported. Our multi-tenant server monitoring support fixes that problem and allows you to monitor servers even in untrusted domains. The only thing you have to do is manually add an untrusted domain using its fully qualified domain name or the IP address of its domain controller and the user credentials for accessing the servers in it.
We’ve also made several adjustments to our existing interface to make working with servers from multiple domains easier. For instance, we’ve modified all our reports to use the fully qualified domain name rather than just a server name, so there will be no confusion regarding the server’s domain. Also, you can use our existing feature, Global Report Views, to make working with multiple domains even easier. This feature allows you to filter report data by various properties, such as server name. Using this filtering, you can create a view for each of your domains where each view contains only the servers in the selected domain. In other words, each view can serve as a logical group to separate your servers by groups. And best of all, they are featured across the entire SysKit application and can be applied to all reports.