Operations | Monitoring | ITSM | DevOps | Cloud

We are pleased to announce we have closed our Series D round of funding, led by Tiger Global with participation from existing investors IVP, CRV, Redpoint Ventures, Sequoia, and Greylock Partners. In this round, we raised $150M, bringing our total raised to over $400M. This new fundraising round further validates the value we provide to customers.

Earlier this month, we were delighted to have been awarded Gold for IT Department of the Year at the American Business Awards®. Last year (2021) was a transformative year for N-able and the award was received for the IT Department’s ability to spin off, revamp, and rebuild a whole IT infrastructure for a brand-new public company and be fully operational within an impressive timeline of only 10 months.

We are super excited to announce a major milestone in our company history. 10 years ago, iLert started with a simple mission: help companies to increase their uptime and deliver a seamless digital experience. Every feature in iLert is built to help you to respond to critical alerts faster and increase your uptime.

In the previous blog, we outlined the critical barriers faced by leaders and probable success factors in Digital first implementation, and how an experienced technology partner & fusion team can enhance the success further. In this blog, we will provide the perspectives of having the right strategy & framework in place across people, process, product, and data for an end-to-end transformation. iOPEX point of view - Digital first

Many CXOs believe that Web3 will power the next paradigm shift and transform the world. As a result, they are accelerating their learning curve to spot opportunities and leapfrog to next-gen business models that will catapult their organizations to new heights. But is there really an urgency to explore what Web3 can offer?

Incident management is the process followed by the area of IT service management to respond to a service disruption, in order to restore it to normal as quickly as possible, minimizing the negative impact on the business. An incident is a single unplanned event that generates a service disruption, whereas a problem is a cause or potential cause of one or more incidents, as defined by ITIL incident management guidelines.

There are various options when it comes to understanding the available IT Operations Management (ITOM) software tools. Especially because, unlike with IT service management (ITSM) say, there are different interpretations of what ITOM software is or includes. This variety is reflected in the Gartner Research view of the ITOM software category, where it has created multiple ITOM software Magic Quadrants rather than simply one.

Over the next couple of weeks (don't know exactly how many posts will turn out of this) I will blog about how we have developed our documentation site. The site is built on top of MkDocs, a custom theme, and a bunch of Markdown files. In this first post, I'll introduce you to MkDocs and help you get a basic site set up.

Microservices are a popular architectural style for building applications that are resilient, highly scalable, independently deployable, and able to evolve quickly. But a successful microservices architecture requires a different approach to designing and building applications. A microservices architecture consists of a collection of small, autonomous services. Each service is self-contained and should implement a single business capability within a bounded context.

Do new users created on one domain controller (DC) of an Active Directory (AD) environment, ever get erroneously deleted only after a few minutes by DCs of other sites within an AD forest? Do changes made in a particular AD site ever get rewritten by DCs in other sites? Can AD objects be erroneously identified? Can more than one AD user account, for example, with all its associated attributes, be a replica of another user account?