upKeeper Manager 4.10

upKeeper 4.10 includes new functions and bugfixes which are listed below. FIles and more tehnical details can be found on our ftp site.

New features

These are the new features in Upkeeper version 4.10

Intune MDM sync

Devices can now be synchronized from Microsoft Intune by enabling this on the "MDM" tab in the organization settings. Note that this will also require that the API settings on the "Azure" tab is filled in correctly. See previous release documentation for 4.6 for info on how to do the setup. No additional rights are needed for this integration.

Devices imported from Intune have the following actions available:

• Lock device
• Wipe device
• Reset passcode

Applications are not handled by Intune at this moment, so the applications tab is disabled.

Azure AD user import

Azure AD users can now be imported into Upkeeper. This import requires the Graph API settings to be entered, and the checkbox "Enable automatic Microsoft Azure AD user sync" turned on.

The new job handler, called AzureAdHandler, will automatically import all users, unless the domain setting is filled in. In that case the users will be filtered by domain name (the name after @ in the user - for example, the user firstname.lastname@company.com will be imported if the domain is set to "company.com ")

In order for this import to work the following Azure permission is required: User.Read.All

All imported users will be marked with source "AzureAD" in the database. These users will be synchronized (created, updated and deleted) against Azure AD.

Note: The field "Manager" is currently not supported by the Graph API and will not be imported.

External Report system overriding

The default SSRS report system can now be overriden with an external webpage.

The flags reportUrlOverride and reportOrgIdKeyOverride can now be used inside the configuration file for the admin web. Setting reportUrlOverride inside config.[yourenvironment].json to an external URL makes upKeeper replace its default reporting system with the provided system. The key reportOrgIdKeyOverride can be used to alter what the key for organization is. The default value is organizations.

Insert new Users through HTTPPost

New users can now be added through HTTP request. These new users are not able to log in but will show up on used devices. All added users will have the Source = "Import" associated with them.

Computer issues reporting

Manual reporting of issues with computers can now be done from the detailed view inside the advanced tab. A warning will show up inside the device list if there are active issues with a device.

Customer Service System configuration

In UpKeeper Admin web, there is now a page where UpKeeper can be configured to integrate with a Customer Service System. Currently, only Zendesk is supported. To integrate with Zendesk, an organization needs to set the System setting to Zendesk, then set which email address and API key to use. They also need to specify their Zendesk Subdomain, which can be found in the Zendesk url, https://<subdomain>.zendesk.com

Zendesk integration

Organizations that have configured the Zendesk integration are now able to view their Zendesk tickets directly in UpKeeper, by clicking on the Clock icon in the admin web's left-hand menu.

Tickets with statuses New, Open, Pending and On-Hold are shown in the table, while tickets with the status Solved or Closed are hidden.

The user can create a ticket from this view by pressing the Create button. They can also edit an existing ticket by clicking on it.

When creating a ticket, the user can set the following fields:

• Requester
• Assigned Group
• Assignee
• CCs
• Tags
• Type
• Priority
• Subject
• Comment (internal or public)

When editing, the user can change the following fields:

• Assigned Group
• Assignee
• Add CCs
• Tags
• Type
• Priority
• Status
• Subject
• Comment (internal or public)

The user can also view and create tickets tied to a specific computer by navigating to the computer object and pressing Tickets. Any ticket created from this view will automatically have the computer name as a tag, except if the user removes it prior to saving the ticket. Special characters such as #, @ and ! are not allowed in tags by Zendesk and will be automatically removed upon posting the ticket. Tickets with a computer name tag will show up in the Tickets table on the corresponding computer object in UpKeeper. The user can also edit a ticket from this view.

Report: Inventory - Operating system versions

A report listing all the different operating system versions with build number and code names.

Shared applications

It is now possible to share an application among multiple organizations. This is done by opening the "Advanced" tab on the application and checking the "Is shared" box. By doing this a new tab "Sharing" is shown. On this tab a user can add organizations (if the user has access to other organizations) that will receive a read only copy of the application.

The copy is created when an organization is added to the sharing list. As long as at least one sharing copy exists, the parent application will be considered shared. It is not possible to remove the "Is shared" status as long as copies exist.

Any changes to the data on the "General" and "Advanced" tabs are synchronized to the sharing copies. A shared application cannot be deleted as long as it is shared and has child applications. In order to delete a parent sharing application all child application connections must be removed first. This is done on the "Sharing" tab by selecting the application(s) and clicking "Remove". Doing this will only remove the sharing status - the child application will still exist, but it will no longer depend or sync to the parent.

When the sharing status of an application changes, no matter if it is the parent sharing application or a child application, the package information will be reset.

Shared applications will be built to a special distribution path

\shared\{applicationId}\{packageId.wim}

Where {applicationId} is the id of the parent application, and {packageId} is the package of both the parent and the child applications.

All child applications will be given the same package and thus saving the disk space needed on the distribution point.

User devices and computers listed separately

The tab devices on the user page used to show devices if the user was imported from DuoStation, or computers if the user was imported from AD. Now there are two tabs, devices and computers - showing the corresponding items regardless of the users source.

Bug fixes

• PDB-files removed from SOS binary folders.
• Intune computer import now creates a new computer if an already imported computer was deleted in upkeeper.
• Applications with "Install in user context" will not trigger uninstall for other users/computers when reinstalling on a computer.
• Applications with "Install in user context" will install correctly for the same user on multiple computers.
• The GetHardwareDrivers call in SOS will no longer show an error if no hardware drivers were found. This also erroneously caused a "Failed to get PostCommand" error message.
• Applications with "Install in user context" enabled will no longer block other applications if no user is logged in on the computer. If no one is logged in all other applications will be given priority over applications with "Install in user context".
• Json error when importing computers from Azure has now been fixed.
• Organization filter ignored when setting standard hardware during self-register in SOS
• Removed a duplicate of the report service URL from API appsettings.config
• Fixed wrong UEFI copy path in Upkeeper SOS
• Report "Inventory - List all computers" excludes deleted computers
• Releasing the mouse in the modal for copying devices no longer closes the modal.
• The two-factor authentication window can now accept the ENTER key as a valid input.
• The Replaced By field inside the application edit view now immediately shows the replaced application when picked.
• The build number of a computer's inventory now shows correctly.
• A device can now be named the same thing as a device that had previously been deleted.
• A warning prompt now appears when attempting to delete an admin-user through the administration portion.
• Device applications no longer crashes the page if the size of the app is larger than a 32-bit integer.
• It is now possible to add a computer to an application, even if it is inherited by its group, preventing the application from being uninstalled when the group is removed.
• Company admins are no longer permitted to create new roles or delete existing roles.
• The memory leak found inside the application view in the client app has been fixed.
• Inactive groups no longer impact the detection of duplications inside batch jobs.
• File metering no longer cares about case sensitivity.