The Site Settings section contains mainly settings that are used to communicate with devices where certain endpoints are. In the majority of deployments, these settings should remain default unless extra configuration has occurred on the server.
In addition to this, some basic settings that affect the user experience are configured here.
|Admin URL||URL for the admin console – This shouldn’t be changed unless the website on the server itself has been changed first.|
|STS URL||URL for the Secure Token Service. This shouldn’t be changed unless the website on the server itself has been changed first.|
|SSP URL||URL for the Self Service Portal– This shouldn’t be changed unless the website on the server itself has been changed first.|
|Companion URL||URL for Companion Clients to Checkin– This shouldn’t be changed unless the website on the server itself has been changed first.|
|Activation URL||URL for Activations– This shouldn’t be changed unless the website on the server itself has been changed first.|
|SharePoint URL||URL for Companion Clients to Access Sharepoint Details– This shouldn’t be changed unless the website on the server itself has been changed first.|
|Windows Enrollment Server||The URL for Windows 10 device connectivity – This shouldn’t be changed unless the website on the server itself has been changed first.|
|Excel Connection String||
Connection string the server uses to generate reports from the system. This is required so that the Excel documents are rendered correctly.
Removed in Silverback 20.0 Update 1
|Allow Admins to Clear Passcodes||This determines if administrators will have the ability to reset passcodes on devices.|
|Allow Admins to provision devices on behalf of users:||This determines if administrators will have the ability to provision devices on behalf of users.|
|Maximum Failed Login Attempts for Console Users||The number of failed attempts before console user’s accounts are locked out. Once locked out, another administrator will need to unlock the account.|
Change the Default Time Zone for System Users by choosing your desired Time Zone from the drop down list.
Android GCM (Google Cloud Messaging)
This determines the company information used to push to users. In most installations, the generic Silverback settings are used. If you require your own internal push settings for any reason, this is where you configure them.
|Send URL||The endpoint to send GCM Pushes to devices, this should not be changed|
|Project ID||The Project ID to be used for push, this should not be changed|
|Companion MDM Poll Interval|
Samsung License Keys
This area is dedicated for Samsung License Keys. You can enter here your corporate owned Samsung Knox Premium Licenses Key to use additional premium features for Samsung Safe devices.
|Samsung ELM License (deprecated)||This key is used to can call APIs from the Knox Standard and Knox Premium SDKs. Do not change this Key.|
|Samsung KPE Lincese||This key is used to can call APIs from the Knox Platform for Enterprise. Do not change this Key.|
|Samsung KNOX License||Enter here your Samsung KNOX Premium License key.|
This setting should not be modified. This tells Silverback which Google Play app to use for Android device enrollment.
|Google Play Enabled||Determines if Silverback should use the Google Play Companion Client, this should not be changed|
|Google Play App URL||The Google Play link fort he Companion App, this should not be changed|
This setting should not be modified
|Matrix 42 API automatic activation URL||Matrix42 related settings for the mobile portal|
|Matrix 42 API manual activation URL||Matrix42 related settings for the mobile portal|
This section should generally not be modified. These settings are static and control how iOS MDM Certificates are requested and how the server should connect to Apple to send push messages.
|Matrix42 Accounts URL||Used when generating an iOS MDM Push Certificate|
|Matrix42 Signing API URL||Used when generating an iOS MDM Push Certificate|
|APNS Port||The port to communicate with Apple for push messages|
|APNS Gateway||The Apple server to send push message requests to|
App Portal and SMS
These settings control the behavior of the App Portal for devices, and also how application information is retrieved from Apple.
|URL||The URL for devices to access the App Portal – This shouldn’t be changed unless the website on the server itself has been changed first.|
|Device App Portal Refresh Interval||While the user has the App Portal open on their device, the page will automatically refresh for them at this interval. This ensures the user’s available application list is up to date.|
|Device App Portal Managed App List Interval||While the user has the App Portal open on their device, the server will request a managed app list from the device at this interval. This ensures that the status for managed apps (Install, Uninstall, Upgrade etc.) is current.|
|iOS AppInfo URL Template||This is the URL used to retrieve app information from Apple. This should not be changed.|
Silverback integrates with SMS Providers so that user’s can receive SMS messages when they create enrollments. Currently, Silverback by Matrix42 supports the RedCoal SMS Provider for Australian customers, AerialLink v4 and MessageBird for the rest of the world.
|Send Provisioning SMS to Users||Determines if the server should send SMSs to users.|
|SMS Sender Label||If supported by the SMS Provider, this will appear as the “From:” label for the users|
|SMS Provider||Selects the SMS Provider|
|RedCoal Serial Number||The serial number for the RedCoal account – This should not be changed.|
|RedCoal SMS Keys||Authentication key for the RedCoal account, this should not be changed.|
|RedCoal Endpoint URL||The RedCoal API endpoint – This should not be changed.|
|AerialLink v4 URL||The SMS Endpoint – This should not be changed|
|AeriaLink V4 API Code||The API Code for access to sending SMS - This should not be changed.|
|AeriaLink V4 API Key||The API Key for access to sending SMS - This should not be changed.|
|AeriaLink V4 API Secret||The API Secret for access to sending SMS - This should not be changed.|
|AreiaLink Use international number format||Determines if the endpoint should expect international SMS in + format. Generally this should be left to the default settings.|
|Message Bird API URL||The URL for the MessageBird API – This should not be changed|
|Message Bird Authorization Token||The access token for connecting and sending messages – This should not be changed. In case you are as well a Message Bird customer you can change the default token to your own by Set. With restore default the default Silverback authorization Token will be used again|
|Message Bird Country Code for Local Numbers||If you want to use a local number format to send messages, enter the default country code here.|
Silverback Root Certification Authority
Silverback deploys certificates to devices that enrol. For security, an individual certificate is generated for each device. Silverback contains a Root Certificate Authority Internally that issues certificates to the devices; the settings that are set with the certificates are configured in this section.
The Certificate Deployment option, relates to certificates deployed with things such as Exchange ActiveSync.
|Certificate||Silverback Root CA certificate. This certificate must be located in the Local Computer Certificate Store.|
|Country||The country that will be placed in the certificate information for devices.|
|Organisation||The organisation that will be placed in the certificate information for devices.|
|Location||The location that will be placed in the certificate information for devices.|
|Expiry Length (years)||How long the device issued certificates should last before expiring|
Certificate Deployment Method
Enterprise Certificate – Administrators will provide a single certificate to be issued to all users for things such as Exchange ActiveSync.
Individual Client - If this is selected, a Microsoft Enterprise Certificate Authority will be contacted when a user enrols and certificate generated for that user. By default, the Certificate Authority Address is DEFAULT, which will tell the computer to automatically find the Certificate Authority. If you have the network address and instance name of the Certificate Authority, enter this here.Note that enabling this setting will automatically generate a certificate for all users in your Certificate Authority.
Corporate Certification Authority
Enter here your Corporate Certification Authority for Certificate Based Authentication. Enter your Certification Authority in the following format:
|Template Name||The template used for ActiveSync, Wi-Fi and VPN User Certificates. Please refer to our Certification Authority Integration Guides|
This section is only enabled if Individual Client certificates are enabled. This section determines certificate renewal settings.
|Renew certificates when expiry is within: (days)||When Silverback detects that a certificate it issued will expire this many days from today’s date, it will renew the certificate. For example if this setting is set to 180, and the certificate expiry is 1 year, it will automatically renew half-way through the year.|
|Exchange Certificate Template Validity||The expiry, in days for the certificate. Silverback will use this to automatically renew the certificate, if it can’t get the expiry information from the certificate itself.|
Windows 10 Certificate Settings
|Enrolment Issuing CA||The CA that will issue certificates to Windows 10 devices. This should be in the Local Computer store, and the Network Service account should have permissions to manage the private key. Please refer to our Certification Authority Integration Guides|
|CEP Enc ryption Agent||CEP Encryption Agent Certificate for certificate enrollment|
|Exchange Enrollment Agent||Exchange Enrollment Agent Certificate for certificate enrollment|
|Encryption Template||Specify here the Template for encryption purpose. Please refer to our Certification Authority Integration Guides|
|Encryption Certificate Subject Name||Specify here your Certificate Subject Name. Please refer to our Certification Authority Integration Guides|
|Signing Template Name||Specify here your Template for signing purpose. Please refer to our Certification Authority Integration Guides|
|Signing Certificate Subject Name||Specify here your Certificate Subject Name. Please refer to our Certification Authority Integration Guides|
|Agent Certificate||Select here your Agent Certificate for requesting certificates on behalf of a user. Please refer to our Certification Authority Integration Guides|
The Cloud Connector allows Silverback servers outside of your LAN to communicate with your local resources. The Cloud Connector is an outbound only session and is mutually authenticated and encrypted. This means that the Cloud Connector client must be configured to use the Silverback server’s public key, so that the server can decrypt the client traffic.
Cloud Connector Settings
|Tunnel URL||The URL for cloud connector connectivity – This shouldn’t be changed unless the website on the server itself has been changed first.|
|Send LDAP Requests through Tunnel||Whether or not LDAP Requests should be sent down the cloud connector tunnel|
|Request Client Certificates through Tunnel||Whether or not Client Certificate Generation should be sent down the cloud connector tunnel|
|Agent Cert Thumbprint||An Agent certificate may be required to request certificates on behalf of a user. This certificate should be installed in the Local Computer Certificate Store, and the Network Service should have permission to manage the private key. Then specify the thumbprint fort he certificate here.|
|Enable Traffic Log||Whether traffic information from the Cloud Connector should be logged. This should only be enabled for troubleshooting|
|Tunnel Security Principal||The local account that is running the cloud connector tunnel on the server|
|Client Certificate Thumbprint (public key)||The public key thumbprint of the cloud connector client certificate. Used to encrypt traffic sent to the cloud connector client|
|Silverback Server Tunnel Certificate (private key)||The private key thumbprint of the server’s client certificate, Used to decrypt traffic sent to the server from the client.|
This settings defines if the Exchange Protection Feature will be used with the Cloud Connector. Only enable the exchange protection here if you have a Cloud Connector present.
|Enable Exchange Protection||Whether or not Exchange Quarantine functions are sent down the cloud connector tunnel|
|Exchange Task Interval||This is the interval at which exchange protection will be executed. Note that by default this setting is quite large. This is due to the fact that if exchange protection is enabled, but not configured correctly, large amount of traffic can be generated against the Exchange Environment. If Exchange protection is configured then this setting should be reduced to the desired frequency. Ideally 1 minute.|
|Max Exchange Concurrency||Maximum number of concurrent Exchange Protection Requests to send at one time|
|Exchange Protection Max Try||Maximum number of times Silverback tries to protect the server|
|Companion Grade Period Push Message||The message to send to the user to remind them to check in|
|Queue Device Inventory on Companion Check-in||Whether the Silverback server should perform a full device inventory when the Companion Client checks in. This is useful if you allow automated unblocked, as the user will be able to rectify the problem, then scan Companion to get unblocked.|
|Companion Blocked Message||The push message sent to the user’s Companion client when they are blocked|
|Companion Unlocked Message||The push message sent to the user’s Companion client when they are unblocked|
These settings mainly govern the connection information for the database.
|Database Server Address||The network address or DNS name of the SQL server that holds the Silverback database.|
|Failover Database Server Address||If needed, you can also specify a separate server to fail-over to in the event the database server is un-reachable.|
|Database Name||The name of the Silverback database|
|Use SQL Authentication||Whether Silverback should use a defined username and password for SQL, or assume permissions for itself (e.g. if the Silverback server is granted permissions on the database, then it will authenticate as itself).|
|Username||If using SQL authentication, the username.|
|Password||If using SQL authentication, the password.|
|Web Settings Certificate||The web settings encryption certificate. This is used to encrypt the web settings in this page. If you migrate to another server you must move the certificate so this thumbprint matches a certificate that is available on the local machine for Silverback.|
Generally these could all be left enabled, this determines what device types you want to allow in your system. If you environment has very specific requirements, for example you only use iPads, the other device types can be disabled which will now allow prevent enrollment, but also remove the other device type’s settings from the console which can make managing settings easier.
Export and Import
This section allows you to export the Settings Administration settings so that you can keep a backup of these settings or move these to another server. The export and import will retain all settings, but it’s critical that the web settings encryption certificate is the same, or when uploaded, the import will not be able to be read by the server.
|Download Export||Clicking the link will download a full export of all the settings. Note that this is encrypted with the servers web settings encryption certificate.|
|Import||Upload a previously exported configuration file. This will only be readable by the server if the same web settings encryption certificate is used.|
These settings govern how the system connects to LDAP sources, and also what information should be brought back for users.
|LDAP Type||The type of LDAP Source. (LDAP, Domino, Novell)|
|LDAP Server||The network address of the LDAP Server|
|LDAP Port||The network port to use for LDAP Server connections|
|LDAP SSL||Ensure when activating that your Silverback is able to communicate proper to your Active Directory on an encrypted level.|
|LDAP Lookup Username||If needed, a Bind username for LDAP Lookups, anonymous binds will be used if this is not specified|
|LDAP Lookup Password||If needed, a Bind password for LDAP Lookups|
|LDAP Filter||Users must match this filter when using the SSP, or they cannot create enrolments, this is a fall back if the item in the LDAP Mapping section does not work.|
|LDAP Administrator Filter||Specify here your Location to the OU where your administrative accounts are located. Please note that all administrators needs to be present in this OU without sub locations.|
|Distinguished Name||The DN used for LDAP users lookup, this is a fall back if the item in the LDAP Mapping section does not work.|
|Account Field||The property of users account field.|
|Email Field||The LDAP Property used for the user’s email address|
|Certificate User Field||Determines if LDAP/S is used or not|
|Email User Field||The LDAP Property used for the user’s Email username|
|VPN User Field||The LDAP Property used for the user’s VPN username|
|LDAP Wi-Fi Field||The LDAP Property used for the user’s Wi-Fi username|
|LDAP Wi-Fi Proxy User Field||The LDAP Property used for the user’s WiFi Proxy Username|
|LDAP Wi-Fi SMIME User Field||The LDAP Property used for the user’s SMIME Certificate Username – This is used for WiFi Certificate Generation|
|LDAP Global HTTP Proxy User Field||The LDAP Property used for the user’s Proxy settings if enabled by profiles|
|LDAP First Name User Field||The LDAP Property used for the user’s First Name|
|LDAP Surname User Field||The LDAP Property used for the user’s Last Name|
|LDAP Request Page Size||How many items should return per page in LDAP request. For large LDAP Results, this can reduce issues with missing users for Tag Population|
|LDAP Referral Chasing Option||Determines if the server should “chase” referrals to other LDAP Sources|
|Number of LDAP Request Retries||How many attempts should be made for an LDAP request before the system will fail.|
|Sleep Seconds Between Filter Tasks||Setting to specify static delay between LDAP filter tasks. We recommend to keep the empty specified value.|
Custom LDAP Variables
These variables are used for System Variables when generating profiles. These are useful if you need to populate a miscellaneous value into a profile for a user that isn’t covered by the normal values above.
|Custom LDAP Var0||Custom Variable to be returned for the user|
|Custom LDAP Var1||Custom Variable to be returned for the user|
|Custom LDAP Var2||Custom Variable to be returned for the user|
In this section you can configure how user’s UPNs should map to LDAP. If your environment has multiple UPN suffixes, then these can be specified in each row. When a user enrolls and enters their username, the UPN suffix is used and matched to this list, if a match is found, the Base DN and Filter will be used to ensure the user can enroll.
A two-way transitive trust relationship between the domain configured in the LDAP section and the domains entered in the LDAP Mapping settings is required.
|UPN Suffix||UPN Suffix to match when the user enrolls|
|Base DN||BASE DN to use for lookups for this UPN Suffix|
|LDAP Filter||LDAP Filter to use for lookups for this UPN Suffix|
Profile Signing Certificate
For iOS devices, if the profile is signed, the user will see this as “trusted”. Note that the user can still install an untrusted profile, so this should be used as verification for the user only. As of iOS 8, this is less important, as the user has less visibility as to whether profiles are signed or not.
|Certificate||For iOS device enrollments, the profiles can be signed so the user sees them as “trusted”. This thumbprint should match a signing certificate installed in the Local Computer Certificate Store.|
This section contains settings that are sent to the device as part of MDM Enrolment. The URLs for Checkin and MDM should not be reconfigured unless the Silverback Websites have been reconfigured first. The VPP Service Endpoint is specific to Apple and should not be reconfigured.
|Checkin URL||URL for enrolling devices to check in for MDM functions– This shouldn’t be changed unless the website on the server itself has been changed first|
|MDM URL||URL for devices to establish MDM sessions – This shouldn’t be changed unless the website on the server itself has been changed first|
|VPP Service Endpoint||URL is used to communicate with Apple for VPP App Licensing. This should not be changed|
Block App Store
To allow you to block access to the Apple iTunes store and still allow users to install App Store Applications, a special mechanism will enable the App Store momentarily and then disable it again. While the App Store is Unblocked, Silverback will attempt to install the application according to the Max Attempts setting, sleeping for the Sleep Time in between events, until the user has installed or canceled the app installation.
During this window, the user may be able to install another application, however the Application Whitelist policy will detect this, and perform the appropriate action on the user’s device.
|Max Attempts||Number of times Silverback will attempt app installation when the App Store is blocked.|
|Sleep Time (seconds)||Amount of time in seconds between attempts that the Silverback server will wait before sending another request|
iOS Single App Mode Re-enablement Automation Workflow
For devices that are locked into Single Application Mode, these applications cannot be updated while the device is locked. This can cause issues because sometimes these apps need to be updated and it’s not viable to manually update the devices apps. The workflow is designed to remove the device from Single App Mode, update the application and then lock the device again.
Unfortunately the device does not tell the server when it’s done upgrading so the server needs to check constantly to ensure the device is locked as soon as the app is done updating. This setting determines how many times the server will “check” the device to see if the app is updated before stopping. If the applications are large or your users are in poor coverage, it’s recommended to increase this value to allow the devices adequate time to update before we attempt to lock again.
|Maximum number of times to check if application is installed before attempting to re-enable SAM.||The number of times Silverback will attempt app installation when the App Store is blocked|
Exchange User Passwords
|Include User Password in Exchange Profile||
This determines if the Exchange ActiveSync profile should include the user’s password. This password is only used if the user enrolled from the SSP with iOS and iPadOS devices, and is not used for Admin Provisioned Devices.
Limit the number of devices that can communicate with the server at any given time. These settings control the system behavior for this.
|Minimum number of devices in the system before concurrency limit is enabled||Once the number of devices that exist in the console reaches this limit the concurrency settings will be enabled. The graph in Pending Commands will not show until this number is reached|
|Period in minutes between limit flush to db||The amount of time in minutes before the device limit (defined in the Admin tab > Pending Commands section) will be saved to the database. It’s recommended to set this value to be large if you don’t intend to change the limit|
|Minutes before device count cache is cleared||The number of devices in the system is cached. This means that potentially the above limit could be exceeded before the concurrency settings are enabled. This setting defines how long until the number of devices in the system is refreshed|
|Seconds before statistics SQL query will timeout||The graph in the admin page may timeout if the request is large or the system is under load. This setting determines how long the SQL query will execute before timing out|
|Interval for getting statistics data in minutes||How often the system should get updated statistics data|
|Limit of rows for statistics request||How much data should be sampled for the statistics. The sytem will query the executed commands, sort by how long the commands took (descending) and then take this number of items for it’s statistics|
|Percentage of request limit before statistics check||The system will recalculate how many devices should be checking in, this is the percentage of the current limit that the system should wait for, before checking statistics|
Silverback has the option to cache passwords the user enters when creating enrollments. The passwords (if cached) are stored encrypted in the database and embedded into profiles sent to the user’s devices. If your company policy dictates that passwords can not be cached, then choose to never cache them. Otherwise, the passwords can be cached for a number of uses before being destroyed. If you want the users to have passwords pre-configured for them its recommended you nominate the number of uses to match the number of profiles that need the password.
If you have no concerns for the amount of time a password is cached, enter a large number and this will ensure the users shouldn’t need to ever enter a password.
|Cache User Passwords||Whether user passwords should be cached from enrollment (encrypted) and used to inject into profiles, like Exchange ActiveSync, so the user doesn’t have to enter the password|
|Cache user passwords for number of uses||
If you allow caching, you nominate how many times this password can be used before being cleared. While the passwords are encrypted, it’s still never good to leave these in the database. After this number of uses, the password will be cleared.
It’s suggested you set this to the number of settings you want to push that need a password. For example, if the user only needs the password for Exchange ActiveSync and your WiFi settings, enter “2”, this will ensure that after the user has all their needed profiles, the password will be cleared
This section displays a count for all pending commands in the system. In certain troubleshooting scenarios it might be necessary to clear these commands. This should generally be avoided because primarily it can cause a large amount of load on the system while the commands are cleared, but also that devices may lose important commands that were previously queued for them. If devices lose these commands, it might be necessary to block and unblock the device, or re-enroll the device to rectify.
|Clear Pending Commands||Clicking this will clear all of the pending commands in the system|
A Service Bus is a fully managed enterprise integration message broker and acts as a reliable and secure platform for asynchronous transfer of data and state. This technology is used to send and update information from Silverback to the UEM Console and is dedicated to replace the Silverback Data Provider inside the Software Asset and Service Management soon. Microsoft Azure Service Bus as a cloud solution as well as RabbitMQ as an open-source software for on-premises scenarios are supported.
Please refer to our Service Bus Integration Guide.
|Service Bus Type||
||Choose here either Azure or RabbitMQ as Service Bus provider|
|Connection string||e.g. Endpoint=sb://imagoverum.servicebus.windows.n...erum.uem.topic||Enter here the connection string which includes the authentication settings to send messages over the Service Bus|
Enter here your Topic for Azure Service Bus or the Exchange for RabbitMQ. Messages are sent to a topic and delivered to one or more associated subscriptions
|Subscription/Queue||e.g. matrix42.uux.subscription||Add here your create Subscription for Azure Service Bus or the Queue for RabbitMQ.|
These settings mainly govern the timing of backend events in the system. The Silverback service runs on the server constantly in the background and follows these settings. While in most cases these settings can be tuned to be as “live” as possible, if performance degradation is experienced, these settings can be tuned to even out the load on the server.
Silverback Windows Services
|Daily Inventory Start Time||Clicking this will clear all of the pending commands in the system|
|Send Daily Inventory Every (hours)||The number of hours since the last inventory task before another will be started. E.g. If the Poll Time is 6:00, and the Poll Interval is set to 1, then every hour after 6:00 a full inventory will be performed|
|Data Retention Poll Time||The time of day that the system should commence the data retention clean up. Data retention is the period in which things like Logs are kept. The clean up task can be SQL intensive, so its recommend this Poll Time is set to a quiet period for user activity|
|Clear Pending Records (minutes)||How often the system should clean up expired pending enrollments. Pending enrollments may no longer be valid, but they still exist in the system and should be cleaned up regularly|
|Check for pending emails to send every (minutes)||Emails sent by Silverback are first queued in the database. This task determines when the system will check for pending emails and send them|
|Send Inventory Requests in batches of||The daily inventory will send this many requests in a group, before waiting for the Delayed Interval (below)|
|Send Inventory Request Batches every (minutes)||The number of minutes before sending the next group of device inventory tasks. This should be configured particularly for large deployments. For example, if the Total Messages to Send is “20” and this setting is “10”, then 20 devices will be told to check in for inventory every 10 minutes at the Poll Interval|
|Refresh LDAP User Info every (minutes)||How many minutes should pass before the system refreshes user data from LDAP. This lookup refreshes user information, for example if a user married and changed the surname in LDAP, then this task would detect the change and update the user information in the console|
|Attempt pushes to removed devices for (days)||Removed devices in some scenarios may still have an MDM profile installed, for example if the device is deleted, but the MDM Profile fails to be removed. Silverback will continue to push to removed devices, to ensure that the MDM Profile is removed. It will continue for the number of days configured in this setting|
|Attempt pushes to removed devices every (minutes)||How long the system should wait before sending pushes to removed devices|
|LDAP Info Update Service Task||Whether the system should update user information from LDAP|
|Bulk Import Processing Task Interval (minutes)||Bulk import jobs (e.g. for Bulk Pending Enrollments) are queued in the database. This task will start processing the bulk jobs and this interval is how often the system will look for jobs to start|
|Data Retention Task Timeout (minutes)||The data retention task, as mentioned above can be SQL intensive, and depending on the number of users, may take a long time to execute. This timeout can be increased if the data retention job is not completing.|
|Compliance Dashboard Task Timeout (minutes)||The Compliance Dashboard, harvests data from the database to display, this can be quite SQL intensive, so in the event that this job is failing, the timeout can be increased to allow appropriate time to execute|
Epic Windows Services
|Message Companion Users to checkin every (minutes)||For Companion clients, how often the users should be told to check in via push notification. This is currently a global setting that overrides the notification settings in the Companion setting of the admin console.|
|Check for grace period violations every (minutes)||The amount of time that the system will check for grace period violations. That is, the system will check, at this interval for devices that haven’t checked in within the grace period defined in the Companion settings in the admin console.|
|Apns Port||Port for the Apple Push Notification Service|
|Apns Gateway||Server for the Apple Push Notification Service|
Batch Application Install Requests
|Send app installations in batches of||When pushing an application to a large number of devices, the system can be slowed by too many devices downloading the app at once. This setting allows you to send app installations in batches to ensure smooth load|
|Send batches every (minutes)||Defines how long the system should wait before sending the next batch of app installation pushes.|
The queuing service is an underlying service that creates an efficient way for Silverback to manage command execution. This is used by the Device Enrollment program, Samsung UMC and also for handling LDAP information processing. There are two key components for the Queue Service, the Command Queue and the Schedule Queue.
Queuing Service Settings
Command Queue is for item that should execute at a device interval and are not typically time sensitive, items are added to a queue and are checked at the defined interval.
|Service Polling Interval (seconds)||The time in seconds that the Command Queue should be checked. Only Device Enrollment Program, and Samsung UMC Commands are used by this feature. If you do not utilize either of these, then this value can be safely set to a large value.|
Scheduled Process Settings
Schedule Queue is for items that need to be processed regularly and within an expected time frame, such as LDAP information processing.
For the settings, the choice between Daily and Continuous will depend on how ‘live’ the LDAP data needs to be and the Time Interval settings will depend on the load. One scenario would be a large amount of LDAP information that takes a long time to process, for this you would ideally select Daily, and specify the time window to be early morning or late night so the server can process this when the server is not too busy.
Another scenario would be the need to have the LDAP data as live as possible. For this you would select continuous, and then adjust the “Process Task Over” time to allow for the amount of data you need to process.
|Determines which items settings you are editing. LDAP Filter is for processing LDAP Filters for Tag population, whereas LDAP Device Update is for fetching LDAP information for current users and devices.|
||Either Continuous or Daily. Continuous will process everything within the defined time frame, and then repeat when that time period has expired, continuously. Daily will execute the LDAP requests once daily, and execute over the defined start and end time.|
|Process Task Over||e.g. 240 Minutes||For the Continuous cycle, this is the time that LDAP requests will be processed within.|
|Start / End Time||
e.g. Start Time 0:00 - 23:59
e.g. End Time 0:00 - 23:59
|For the Daily cycle. This is the time window that the items should be processed each day|
|Silversync Remote Configuration Endpoint URL||The URL for the system to communicate with Silversync. This shouldn’t be changed unless the website on the server itself has been changed first|
|Silversync Security Principal||The account that Silversync should run as. Generally this shouldn’t be changed|
|M42 Push Notification Host URL||The endpoint for push notifications for Silversync clients. Generally this shouldn’t be changed.|
Emails are sent for various functions in Silverback. This may be informing a user of an enrollment, or email administrators about users violating policy. Generally an SMTP Relay that supports anonymous relaying internally would be used. If you require authentication on the proxy, please specify the username and password.
|SMTP Server||The network address oft he SMTP Server or Relay|
|SMTP Port||The SMTP Port to use|
|Username||If the SMTP server requires authentication, specify the username. If no username is provided it is assumed tob e anonymous|
|Password||If the SMTP server requires authentication, specify the password. If no password is provided it is assumed tob e anonymous|
|SSL/TLS||Whether or not the system uses SSL/TLS with SMTP|
This section governs settings surrounding the email template. At this point in time, this is essentially just who the user sees the email came from.
|Sent From||The address that should appear as the “From“ address when the user receives the email|
Windows Push Notification Services
|WNS App ID||The App ID generated when creating the fake push application for 8.1 devices.|
|WNS Package Family Name (PFN)||The PFN token generated when creating the fake push application for 8.1 devices.|
|WNS App Store URI||The URI generated when creating the fake push application for 8.1 devices.|
|WNS App Secret||The authentication token generated when creating the fake push application for 8.1 devices.|
Device Management Client
This section covers settings relating specifically to enrolments. In general these settings shouldn’t be changed.
|Use Indentation||Internal WP setting, do not change.|
|WPMDM_OmaDmRetry NumRetries||The number of initial polls after enrollment|
|WPMDM_OmaDmRetry RetryInterval||The time in between polls after enrollment|
|WPMDM_OmaDmRetry AuxNumRetries||The number of polls to attempt AFTER the first series of polls have been used.|
|WPMDM_OmaDmRetry AuxRetryInterval||The time in between polls after the first retry interval has been used.|
|WPMDM_OmaDmRetry Aux2NumRetries||After the above settings have been exhausted, this number of retries will be followed. Note that this should be set to 0, and never changed. This ensures the device will continue to check in. If this is changed to another number, the device will check in that many times, and then stop.|
|WPMDM_OmaDmRetry Aux2RetryInterval||The interval between check-ins for the above setting.|
|Exchange Profile Includes Random Password When Empty||In some scenarios, the exchange profile will fail to install if there is no password specified. This setting tells the server to insert a random password if it doesn’t have the users password. This will ensure that the profile is installed, and the user will be prompted for their password|
Windows devices inventory intervals
For Windows devices, because the checkin interval can be driven by the client, to reduce load the tasks that are performed each checkin can be limited. The settings in this table determine how often these should be queried on a device when it checks in – not how often a push will be sent to query these. For example, for Certificate List, these settings mean that if a device checks in, and it has been X minutes since the last certificate list was gathered from the device, a certificate list query will be executed.
|Queue Certificate List after||Number of minutes since the last certificate list, before it will be queued again|
|Queue Push Token Info after||Number of minutes since the last push token information query, before it will be queued again|
|Queue Device Info after||Number of minutes since the last device information query, before it will be queued again|
|Queue Security Info after||Number of minutes since the last security info check, before it will be queued again|
|Queue Installed App List after||Number of minutes since the last installed application list, before it will be queued again|
|Queue Managed App List after||Number of minutes since the last managed application list, before it will be queued again|
This section covers settings for Windows Phones, which are largely deprecated.
The EAS settings however, govern some basic settings for Exchange Protection features. In general these settings should not be changed.
|EAS Datetime Format||The date format to use for EAS Display items for Exchange ActiveSync Quarantine.|
|EAS Schema URL||The schema location for EAS – This should not be changed|
The following settings are deprecated and removed with Silverback 20.0 Update 1
For Windows devices, it’s possible to configure Assigned Access. This gives administrators greater control over the device including the ability to completely customize the home screen and what functions are available to users. There is a very large risk that if the configuration XML for this is not carefully checked, that devices can be “Bricked” and no longer usable. Because of this, this is disabled by default and must be enabled here first.
WP Marketplace Settings
These settings determine how Silverback should query the Windows Marketplace for App Information. These settings should not be changed or app lookups may not work.
|AppInfo Template URL||The lookup end point for app information – This should not be changed|
|AppIcon Template URL||The lookup end point for app icon downloads – This should not be changed|
|AppDownload Template URL||The lookup end point to search for applications – This should not be changed|
Company Hub Settings
For WP8 management and enrollment, you require a Symantec Certificate, this is covered in a separate document, however the Symantec Certificate information should be populated here.
|Enterprise ID||ID From Symantec Certificate|
|Enrollment Token||The lookup end point for app icon downloads – This should not be changed|
|Store Product ID||The lookup end point to search for applications – This should not be changed|
|Store Name||Internal Application setting, this should not be changed.|
|Company Hub App Title||Internal Application setting, this should not be changed.|
|Company Hub URL||The URL for WP8 Company Hub – This shouldn’t be changed unless the website on the server itself has been changed first.|
|Signing Certificate Thumbprint||The Symantec Certificate information should be populated here|