This is the point where you can decide either good or bad. As I mentioned at the beginning, to decide the application delivery method is not about playing with the technical challenges, I also said that it is something where we fail often. This stage of the process is one that takes us out of that kind of thinking, this leads to something very important, users!
I know it is very difficult to manage applications in a way that you have the structure of the organization included. Excel sheet is something for SMB environments, but when you hit the organization with thousands of applications you would need an army to just update Excel files. Forget that!
Also managing modern application is constantly evolving as users demand new ways to use applications. LET'S take an example and call Jim. Jim spends much time in airplanes as his work in the global organization requires traveling between continents, it has reached a million air miles. As Jim flies much, it is constantly offline and due to its applications are physically on his laptop. Airport Bangkok Jim bought a fancy tablet PC and wants to use a business application with it while enjoying the sun in Thailand, there is no way he not accept an answer without disappointment. Thus, it must, but it can be a huge task for administrators.
Suddenly the whole scenario has changed and the application must be hosted on a server, used on a mobile connection with touch-enabled interface and potentially with limited functionality. You are thinking: "So what? in a fair application! "Multiply this scenario with 10,000 users and 1,000 applications and try to have even the minimum level user management scenario! Try it yourself with a user, if it feels easy, ask the user if he can use all devices that would and you are instantly lost.
you can easily see that someone will zero head for a while when the consultant XenDesktop walks of Jim's company gateway and begins planning the implementation XenDesktop Although I am not an expert on average XenDesktop, yet I know that the obvious question is:.
"Tell me about your usage scenarios and show me the main user groups for each scenario? "
This is how it should probably be when desktop delivery models are defined, but my wild guess is that the question is simple not so easy to answer . In fact, it would be nice to hear how it actually is?
Aha bulb! We need to stick things together.
As we started the process by importing data from System Center Configuration Manager and Active Directory, we have nearly the tools to understand it. I'm not saying AppDNA can solve the problem, but at least there are tools and the ability to take control.
We can easily organize applications to groups, suites and families and map those to the organizational structure.
So what the groups are, suites and families?
picture above gives you an idea of how to use them, but the point of view there is something very important to understand reports.
groups are relatively freely for organizing applications, it is something like Windows folders. Create a group and make applications for the group. It has no effect on the statement, it is right for the organization. If the application belongs to a group, it is still available as disaggregated element. This means that same application can belong to multiple groups.
Families are useful for closely related applications, such as "word processing applications" -family including MS Word 2010 and 2013. In the reports, the family would be displayed by the most appropriate element. This means that if at least the application marked as green, the whole family is green because there is at least one version that could be delivered. If there is no green flags for the family, would be the same amber.
Suites are something useful especially in scenarios where XenApp it is very common to have "business applications". With the business application, I mean a set of applications or facilities that are necessary to build a solution. These solutions can be very large and complex, but simply would be something like SAP. SAP is an application, but to use all the functions, you may have MS Excel, PDF reader, etc. All these applications have to work, otherwise you are not able to deliver the business application "Corporate SAP." For this reason, the RAG status is displayed by the worst case. Even if a single application of the suite is marked in red, the whole series is marked in red.
Ok, now we have the applications and the organization's control and can start planning desktop delivery models. I will not touch this area other than what I said before about the user scenarios and user groups.
From the above picture you can see that we can now map the types of desktop delivery to the organization, but also the applications included users. In addition to this, we have direct information on the number of users in each group, the number of applications within each reporting category and we could drill down to the numbers to see exactly accounts user or application names, and so on ...
After this step is time for planning migration routes. Remember, in this example, we move from the physical environment to XenDesktop (if possible). Migration Path is nothing cryptic, and in fact it isnt even any direct configuration for this, but it would be possible to define. The most important thing is that there is a plan. It can be something as simple as below.
Is there still something important we can do in this step? Oh yes!
Now is the time to reduce costs easy. If our report cards for applications that are not mapped to all users or devices, it would be good to see if we could remove this application. By removing unused applications, the workload on the next steps and especially during the daily management of the application is reduced. In addition, if the application would generate annual cost of license, it would be instant savings and it could be measured!
If you're like me, you may think about cleaning user accounts that are not related to applications. Good idea, but beware, all users not to use application! For example, cities or municipalities may have many AD accounts, but where they could keep records of all library card holders? Do they use the same applications associated with AD? Then, there are users who just do not use enterprise applications for one reason or another.
Btw, next to immerse ourselves in something very nice ...
0 Komentar