Top 10 Hard Problems Notes Administrators Face Today and How To Easily Solve Them
A Domino application and user cleanup project is something everyone should do, but most hesitate to start – much less complete – such a seemingly daunting task. The challenge is how to easily,
quickly and accurately identify which applications, which replicas and which user IDs can be safely removed from the system without inadvertently removing needed applications, replicas, mail files or
user accounts.
A Domino spring cleaning project provides benefits in two primary areas:
- By cleaning up your Domino network, you greatly improve the success rates of your Domino projects. You are able to complete major projects quickly, easily, accurately and at lower cost. Among the major tasks benefited by a pre-project cleanup are:
- Server consolidation
- Domino version upgrade
- Network merger or network division due to corporate merger, acquisition or divestiture
- By cleaning up your Domino network, operational costs are lowered by making better use of your existing server, disk and WAN resources while possibly extending the life of these same resources. With a Domino cleanup, you reduce:
- Server disk space consumption
- Time and resources required for backups and restores
- Domino server indexing overhead
- WAN consumption as unneeded replicas/mailboxes no longer consume bandwidth
- User frustration as there are fewer irrelevant databases as well as users listed in server catalogs. Users can find needed applications that much faster (and not mistakenly open obsolete applications).
Seeing that a Domino cleanup can help in multiple areas, your next question is likely: "How can I best accomplish a Domino spring cleaning?"
Domino does not provide tools to accomplish this. IBM Lotus does not have a service to accomplish this. Trying this on your own will consume substantial resources and likely result in great user discontent and lost productivity as the help desk line rings with complaints that users can no longer access their production applications or cannot log in at all. If you play it safe, you will miss many opportunities to make dramatic improvements.
Enter DYS.
DYS Analytics brings the underlying data collection, analysis, methodology and optional professional services staff to objectively and accurately identify which applications, replicas and user IDs should be removed from your system. DYS eliminates the guesswork and delivers this at such a price and timeline that you no longer need to buy more servers, more disk, more bandwidth and more user licenses to bury the problem. Continually throwing more hardware, software and network bandwidth at the problem is no longer required.
By employing enterprise-wide data collection, analysis, reporting and alerting tools – combined with a time-tested and proven application and user cleanup methodology – you ensure that your major projects stay on track at minimum cost and your operational costs are kept low.
Outlined below is an overview of an application and user cleanup methodology. Included is a summary of the issues that need to be addressed, the method DYS uses to address these and a brief outline of the project tasks. Customer micro case studies highlight the benefits of a Spring cleanup using DYS vs. the costs of doing this on your own.
There is more. If you would like to read the article in its entirety, all we ask is that you complete the form below. We will send you your free copy by email. Privacy Policy
