Managed applications can be collected using built-in integration to connect to System Center Configuration Database Manager or based deployments policy via Active Directory. AppDNA connects to the Active Directory database and SCCM online or offline using the client. offline client is most useful in cases where access to the target environment is limited for some reason, in general network setting limitations or user privileges.
Offline Client is single executable glazing and can be downloaded from the server AppDNA and given to someone with the necessary access to target servers. Client is running on a domain controller or a server SCCM scope. Customer then collects the required information and creates an archive, which in turn can be delivered to the AppDNA administrator to import the data to the database. The collected data includes information on application deployments, ie. SCCM collections, programs and advertisements, or their relatives coming from SCCM 2012. In addition to the various deployment configurations, SCCM 2012 provides some additional features of AppDNA perspective, ie. Incremental imports is particularly useful for managing application changes over given time.
Usually SCCM distributions are related to the machine accounts, user accounts or groups of users in Active Directory, which is essential for the management of applications within the organization. Active Directory based distributions are treated similarly by default.
These distributions may be implementing mandatory advertisements or installations, which means it is not necessarily in connection with the use of effective enforcement. As mentioned above, the rationalization of the portfolio and the development of cost optimization of view license, it would be essential to know if the applications are actually used or not. This means that using a distribution system does not make the information not relevant use rather the combination of these two systems gives the optimum starting point for the project.
Although SCCM has characteristics able to use applications, it is not used by the current version of AppDNA (6.3), which is a good reason to use SysTrack in all cases.
to import applications SCCM, there are two options.
- Use "direct import" if distributions are standard MSI files. In this case, the location of each MSI is provided by configuring SCCM programs and applications can be directly imported without capture by selecting "Use direct import MSI".
- capture applications using SCCM advertisements. This is particularly useful if the applications are not standardized MSI files (scripted installations, executables, etc ...). In this case, applications are captured using "Install Capture" feature.
After the list of supported applications is filtered and streamlined, the selected applications can be moved to more familiar "Import Applications" screen by selecting "Add to import list."
Note that direct import is not always recommended, although this may be possible. For example chained installations would be difficult to manage if the relationship is broken by importing them individually. Depending on the scenario, it should be considered if the capture of the full chain or consolidation of the MSI file is the best option for the next actions, either. Sequencing App-V.
Capture applications will be covered separately as it is about broad and can include complex technical considerations.
Active Directory data is equally important that we need to match the managed applications with users, user groups or organizational units. If your client is facing security, they would ask what kind of information we export actually from their database? Usernames, yes. Passwords, no.
As I mentioned earlier, it is all about users making them vital Active Directory information for the later stages of the project. We will use this information as a connection point to XenDesktop project, but it is also necessary for assembly applications in the organizational structure, planning the deployment of the implementation, forecasting progress, status reports, application prioritization and portfolio rationalization. I could go on forever ...
illustration below shows how the above mentioned systems functions as a basis for the management of well-structured applications.
0 Komentar