View source for Application Management Module

In this section we like to explain you how modern Application Management with Syntaro works. 

==How To's==
===Quickstart===
# [[Syntaro_Portal_%26_Marketplace#Buy_a_module|Get a Paid or Trial Subscription]]
# [[Application Management Base Package|How to Deploy the Base Package to your Devices]]
# [[Application Management Base Script|Manage the Base Script to make package creation simple]]
# [[Application Management Create your first Package|Create your first Package]]
# [[Application Management Deploy your Package with Intune|Deploy your Package with Intune]]
# [[Application Management Uninstall your Package|Uninstall your Package]]

===Step by Step===
* [[Application Management Use External Packages|Use External Packages]]
* [[Application Management Scheduled Tasks|Scheduled Tasks]]
* [[Application Management Settings|Customize Settings on Devices]]
* [[Application_Managemnt_Test_Package|Test your Syntaro Packages]]
* [[Application Management P2 Deployment Rings|Deployment Rings & Scheduled Deployments]]
* [[Application Management Prerequisites|Prerequisites]]

===Examples===
* [[Application Management Examples|Examples]]

==System Overview==
The following diagram will show you an overview about how the Syntaro  service is working.<br><br>
[[File:ApplicationManagement1.png|none|thumb|600px]]<br>
#The users can select the apps they would like to install in the Intune Company Portal. The company portal sends the request to the Intune Service.
#The Intune service triggers the Windows 10 built-in MDM agent to enforce the new requests.
#Windows 10 MDM Agent is setting the local configuration and start Syntaro App Management to enforce it.
#Syntaro App Management is the local functionality of our Intune extension and is built on PowerShell package providers and starts the installation, update or deinstallation. This layer also gives us the advantage to work with other package Providers like RuckZuck.tools, which is a great OpenSource Package Repository.
#Our Syntaro Package Provider is handling the package logic and is using the package information you provided in your private Syntaro Package Repository. It also allows to download content over BranchCache and save Internet Bandwidth.
===Benefits===
If you use Syntaro for your modern managed workplace, then you can benefit from the following features:
*'''FileType Limitations'''<br>Microsoft Intune has limitations for application deployments. Only MSI files can be distributed and installed on Windows 10 MDM managed devices.
*'''Only Single Files'''<br>Only a single file can be distributed with Microsoft Intune. This prohibits the deployment of complex applications packages.
*'''Internet Bandwidth'''<br>During application deployment data volume that is transported via Internet is very high and might break the Internet connection.
*'''Deployment Rings for Applications'''<br>Use the deployment rings which you user for Office or Windows also for phased deployments of Applications.
*'''Prerequisites and Retries'''<br>Define actions to retry the installation for example when the applications is running or only install application when the devices meets some properties.
*'''Dynamic Configuration'''<br>Trough the usage of PowerShell for the Installation and Uninstallation you can dynamically build the configuration according to your requirements.

==Glossary==
===System Components===
[[File:ApplicationManagement2.png|none|thumb|600px]]
<ol style="list-style-type:upper-alpha">
  <li>'''Intune Company Portal'''<br>End User Interface to install applications with a store like experience.</li>
  <li>'''Intune Service'''<br>Cloud service of Intune which triggers `user requested` and `administrator defined` applications on the devices.</li>
  <li>'''Built in Windows 10 MDM client'''<br>Checks regular intervals for new requests in the Intune service and installs the Syntaro Dummy MSI Package which triggers the Syntaro Scheduled Task.</li>
  <li>'''Syntaro Base Package'''<br>The Syntaro Base Package is responsible for the installation handling on the device. It consists scheduled tasks and also installs the Syntaro Package Provider.</li>
  <li>'''Opensource PowerShell Package Providers''' like RuckZuck<br>These package providers will allow you to benefit from cloud package repositories which already contain a lot of applications, which are ready to use.</li>
  <li>'''Syntaro Package Provider'''<br>This provider will let you access your private Syntaro Package repository. This provider supports the built in Windows BranchCache.</li>
  <li>'''Package''' including Content and Installation logic<br>The package can contain as many files you need in your package and also the size can be bigger than every package you can imagine.</li>
  <li>'''Syntaro App Management Service'''<br>The cloud service which is managing the repository and is answering requests of your clients.</li>
</ol>

===Others===
* '''Syntaro Base Script'''<br>The Syntaro Base Script can be used to provide a set of functions to all of your packages. BaseVISION provides you with a really good one which can be copied from [https://github.com/ThomasKur/SyntaroApplicationManagementBaseScript/blob/master/SyntaroAppManagementHelper_001.ps1 GitHub].
* '''Syntaro Dummy MSI Package'''<br>The Syntaro Dummy MSI Package is a generated MSI file per Package, you define in our system and can be deployed with Intune to the devices. This placeholder MSI is also triggering the Scheduled Task to install the package instantly.

==General Packaging Pages==
Additional information about packaging an application you can find on those websites:

*[http://www.Appdeploy.com Appdeploy]<br>
*[http://www.Itninja.com ITNinja]<br>
*[https://github.com/OneGet/oneget/ Oneget on Github]<br>

== Device Management ==

=== Introduction ===
As of Syntaro release 1811, it is now possible to delete devices manually and set up a rule to delete devices that appear inactive, decommissioned, or unresponsive for a period of time of your choosing.
This will cleanup for example devices that are registered double in your device list. This way you won't unnecessary reach your device quota.

=== Deleting Devices ===
{| class="wikitable"
|- style="vertical-align:top;"
|[[File:double devices.png|none|thumb|300px]]
| Click on "Devices" in the "Application Management" blade. This will open a new blade with a list of all the devices which are/were connected. In this case you can see that "SYNTEST8" is double in the list. You can make the difference between them by looking at the date that they were last connected.
|- style="vertical-align:top;"
|[[File:delete_double_device.png|none|thumb|300px]]
| When you want to delete a device, simply click on the "bin-button".
|- style="vertical-align:top;"
|[[File:confirmation_delete_device.png|none|thumb|300px]]
| Once you have clicked on the bin-button, a window will appear to confirm your action. Once you click "Yes", the device will be deleted permanently. 
|}

=== Device List Cleanup ===
{| class="wikitable"
|- style="vertical-align:top;"
|[[File:Device_settings.png|none|thumb|300px]]
| Click on "Device Settings" in the "Application Management" blade. This will open a new blade when you can check the option that will soft delete devices after a period of time. Soft because the Device will not be permanently deleted from the device list, but will be hidden.
|- style="vertical-align:top;"
|[[File:show_hidden_devices.png|none|thumb|300px]]
| The deletion of the device is soft, because the device will not be permanently deleted from the device list, but will be hidden. Click on "Devices" in the "Application Management" blade. Here you can check the box that will show not only the connected devices but also the the ones who were deleted after the amount of time that you set.
|- style="vertical-align:top;"
|[[File:set_device_disconnection.png|none|thumb|300px]]
| Check the box and choose after how many days you want the deletion to be set. Minimum is 30 days. Click "Save" and it's set!
|}

== User Notifications ==
=== Introduction ===
We have a new feature that gives you the option to send notifications to your users. 
For example: An application is being installed, but before it gets installed, the user first needs to close Outlook.
Now you will be able to send the user a notification that they have to do that. 
Through a powershell script that you can update in the base script we provide, it will be possible to create this. 
The following diagram will show you an overview about how the new Syntaro service works.<br><br>
[[File:UserNotificationSystemOverview.jpg|none|thumb|600px]]<br>

=== Available Options ===
{| class="wikitable"
|- style="vertical-align:top;"
|<syntaxhighlight lang="powershell">
C:\Users\%userprofile%\source\repos\Syntaro.Appmanagment.UserCommunication>
-title "MyTitle"
-Message "MyMessage"
</syntaxhighlight>
| With this powershell script it will be possible to send a notification with your own title and message 
|- style="vertical-align:top;"
|[[File:Message window ok.png|none|thumb|300px]]
| This will be the result that the user will see
|- style="vertical-align:top;"
|[[File:Install window.png|none|thumb|300px]]
| You can also expand this notification by giving the user 2 options: "Install now" or "Remind me later"
|- style="vertical-align:top;"
|<syntaxhighlight lang="powershell">
C:\Users\%userprofile%\source\repos\Syntaro.Appmanagment.UserCommunication>
Invoke-PostponeMessage
-userMessageTitle "My Title"
-userMessage "My Message"
</syntaxhighlight>
| Here an example of how you can create that window
|- style="vertical-align:top;"
|[[File:Remindme window.png|none|thumb|300px]]
| When the user chooses "Remind me later", a new window will open up, where the user can pick a time for when he or she wants to be reminded
|- style="vertical-align:top;"
|<syntaxhighlight lang="powershell">
C:\Users\%userprofile%\source\repos\Syntaro.Appmanagment.UserCommunication>
Invoke-ProcessMessage
-processName "Outlook"
-autokillApplication
</syntaxhighlight>
| When you want to create a notification so that the user has to close an application, you can add this script (example). If the user closes the application, the answer that will be send is "true". When the user doesn`t response, it will send "false".
|- style="vertical-align:top;"
|[[File:Autokill Option.png|none|thumb|300px]]
| The user will then get this notification. If the user doesn`t respond to the notification, the application will be killed after a default time of 120 seconds
|}

===More information and MSI download===
You can find more information and the MSI you need for it to work here on GitHub:
https://github.com/baseVISION/SyntaroUserCommunication

== Trouble Shooting==
=== Log Collector===
If you have a machine that is not working correctly we have a little tool that collects Syntaro related information of that device.<br>
The tool is a simple small exe file that you can execute with regular user rights.<br><br>
You can download the exe from here:<br>
[https://github.com/baseVISION/Syntaro_Appmanagement_Log_Collector/releases/download/v1.0/Log_Collector.exe Log Collector]
<br><br>
That Information will be copied to a new folder in the current user's temp folder. In that folder, you can review all the information that got collected.
The folder will also include a file called "_CollectedLogs.zip".
If you want to open a support case with us that is related to software installation on clients, please also send us that Zip-File.<br><br>
If you get the Message "Windows protected your PC"  please click on "more options" and then select "Run anyway"

=== New Version of Package doesn't get installed===
Our experience showed, that if a new version of a package does not get installed, one registry key will be the culprit most of the times.
To solve this issue we can reset this "NotFoundInRepo" registry key which resolves the problem in most cases. Underneath you will find the steps to reset this registry key by yourself.

{| class="wikitable"
|- style="vertical-align:top;"
|[[File:AppManagement_NotFoundInRepo_001.png|none|thumb|300px]]
| First you will have to navigate to the Syntaro Appmanagement registry keys. You will find them under Computer\HKLM\SOFTWARE\Syntaro\ApplicationManagement\. Now in its subfolders, you will have to find the folder named after the ID of your package that is not being installed correctly. The registry key "Name" will help you distinguish the different packages.
|- style="vertical-align:top;"
|[[File:AppManagement_NotFoundInRepo_002.png|none|thumb|300px]]
| The "NotFoundInRepo" key will be situated in the folder of your package. If the value in this key is equal to 5 or higher, this registry key is causing the problem. Simply setting its value back to 0 will normally solve the issue. After resetting the key, please rerun the Syntaro Full Installer and the Syntaro Updater Scheduled Tasks.
|}

The function of this key was meant to minimize the time the scheduled task needs to complete. If a package cannot be found in the repository the key would count up by 1. This has the outcome, that if this key reaches the value 5, the scheduled task stops trying to install this package to save time and performance. To reduce the situations where this key could be count up in terms of a network connection issue, please download the latest Base Package from the Syntaro Portal and deploy it through Intune to your machines.<br><br>

If you have a lot of packages or devices where this happened you could also create a package to reset those values.
How you can create such a package is described here:
[[Application_Management_Tutorial:_Reset_NotFoundInRepo_registry_value]]

=== RuckZuck Packages are not getting installed===
Roger Zander discontinues the support for version 1 of RESTAPI. As a consequence, versions of the OneGet Packageprovider prior to 1.7 are not working anymore. If you still have older versions installed on your clients, you will get plenty of errors when trying to install your RuckZuck packages through the scheduled task. <br><br>
To solve this issue, you have to update the corresponding client app over Intune. A detailed step-by-step tutorial can be found [https://docs.microsoft.com/en-us/intune/lob-apps-windows#step-5-update-a-line-of-business-app here].