Now it's time for the important things about our project. Ideally we would have most of our applications imported for the time we used the distribution system, as one would expect, including most applications. However, the reality is that there are always applications that are unknown. I've actually never been involved in a project where the client had 100% confidence on knowledge of the number of applications, the name, version, and vendor installation media. These are the minimum requirements for all levels of management applications.
This would be the starting point for the rest of import applications, but it is not mandatory, you can actually do it later as you see best. This is important when considering whether AppDNA would be used for the ongoing management of the application after the project phase is completed. First, you will appreciate the ability to manage applications individually, instead of having to analyze your complete stack each time you add an application. Unfortunately, many organizations consider AppDNA be useful for immediate pain on delayed migration. Guess what? Migration is not going to end, ever. Projects can be considered complete, but the process and the need remains. The project just means move to a standby mode - waiting for the next migration
When the world is changing, you need to change too .. What I mean is that users demand new deployment options because they move between different usage scenarios. For example, they want to use mobile devices instead of PCs. Then touch applications must be user friendly, which in turn create demand for more advanced operating systems. Ok, we have little distracted ...
analysis process in such is very simple for the administrator. Just choose the applications, the relevant modules and analyze! At this stage, there would be opportunity to create groups, families and suites of applications. Let's see what next and focus on analysis.
Analysis can be described shortly with the following illustrations. Although this position is on the analysis, it is important to start showing insight on what we really have in the database. In short, the data on users, user groups, organizational units, usage information, applications and operating systems. The operating systems ship with the product are versions of vanilla, but in reality, every organization has customized its OS build, as a minimum, they have group policies. While we are not reading the Active Directory group policies, they may also be changes to the construction of the operating system and can be captured. Captured OS is then imported or multiple built specific version, and used in the analysis. The end result is the realistic deployment environment from the technical point of view.
0 Komentar