396 results found

1. Munki Integration : On-Demand installation

   I wish that the Munki "OnDemand" key that is planned for a PkgInfo is exposed in the declaration of a package in SimpleMDM. That would offer to trigger the installation of a package as needed without an instal / remove cycle.

   2 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   completed  ·  0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Expose assignment count for custom profiles via API

   The internal API for profile search https://a.simplemdm.com/admin/profiles.json returns the number of groups and devices assigned to a profile as groupCount and deviceCount.

   Exposing this information to the customconfigurationprofiles "list all" endpoint would make it possible to add a scheduled job to cleanup profiles with 0 installs, so the UI doesn't get clogged up with outdated profiles.

   4 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   completed  ·  0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Enable Remote Desktop per enrollment instead of globally

   The new feature to enable remote desktop automatically is great, but we only want to enable it on a certain enrollment, not on all machines.

   5 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   completed  ·  0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Add the ability to mark some custom attributes as "secret"

   We're looking at pushing things like wifi passwords to devices using profiles and custom attributes... as we aim to use MIST's multiple PSK option - https://www.mist.com/documentation/multi-psk/

   Each device will have their own wifi password pushed as a custom attribute - but these are effectively passwords. It would be awesome if they could be tagged as secret (like a lot of CI/CD tools allow you to do) and we could log that an admin had viewed them (in the same way unlock PIN and Activation Lock Key access is logged now

   2 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   completed  ·  AdminEric McCann (Admin, SimpleMDM) responded

   When editing a custom attribute via Configs > Attributes, you can now select "Mark as secret". When checked, this will prevent users with "Custom attributes marked as secret" permissions disabled for their user role from seeing the values stored for these attributes.

5. Add ClickUp as a shared app.

   Would like to have ClickUp added the shared app library. Thanks!

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   completed  ·  0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Implement "SetAutoAdminPassword" to allow DEP created admin account password rotation

   SetAutoAdminPassword allows changing the password of a local admin account that was created by Setup
   Assistant during DEP enrollment via the AccountConfiguration command. It is available in macOS v10.11 and
   later. This would be useful to allow admin password rotation. Ideally this would also available via the API.

   11 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   completed  ·  Anonymous responded

   This is now supported (with some limitations). Documentation is available here: https://help.pdq.com/hc/en-us/articles/5626064805659-macOS-Account-Setup-and-Admin-Passwords

7. Add Slack universal installer to Shared Apps

   I found that Slack has a universal installer available on their website, but only the Intel version is in the Shared Apps library. It would be nice to be able to push the universal version from Shared Apps instead/in addition.

   (link here, under the "Distribute Slack" section: https://slack.com/help/articles/360035635174-Deploy-Slack-for-macOS)

   Thank you!

   7 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   completed  ·  1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Add schedule to script jobs

   Scripts and jobs to run them are a fantastic addition but the jobs are single use at that this stage.

   The ability to schedule jobs seems like the next logical iteration.

   Keep up the good work SimpleMDM

   27 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   completed  ·  AdminEric McCann (Admin, SimpleMDM) responded

   Script Jobs can now be scheduled within the admin interface.

9. Add Scripts and Script Jobs to API

   Feature Request: Add Scripts and Script Jobs to API

   Currently the "Scripts" and "Script Jobs" functionality is only supported when using the SimpleMDM web console via a browser.

   • Scripts: https://a.simplemdm.com/admin/scripts
   • Script Jobs: https://a.simplemdm.com/admin/script_jobs

   With the goal to support custom advanced automation for our machine provisioning processes and integration with other configuration management systems, we need the ability to:

   Requirements:

   • Create/Update (Upload) and Delete Scripts
     • Support multipart/form-data by default (similar to other SimpleMDM APIs)
   • List and Get Scripts, including:
     • Script ID
     • Script name
     • Full script contents
     • Created/Updated timestamps
   • Create Script Jobs
   • List Script Jobs
   • Get Job Status
   • Get Job Log / Results / Output

   Desirable bells & whistles premium options:

   • Query / Filter Script Jobs via Script Jobs List API. Available Filters might include:
     • Script Name
     • Script ID
     • Target ID(s) (Device ID(s), Device Group ID(s), Assignment Group ID(s))
     • Target Type(s) (Devices, Device Groups, Assignment Groups)
     • Created Timestamp
     • Updated/Modified Timestamp
     • Script Status (Pending, Completed, Failed)
   • Support Base64 encoding for Script Content when Creating/Updating scripts
   • API endpoint to get "raw" (application/octet-stream? Base64 encoded text/plain?) output of the script stdout/stderr Something like: GET https://a.simplemdm.com/api/v1/job/response/{job_id}
     • Currently the web console embeds the Script output as a JSON-escaped field in the "Metadata.job_response" field

   Why we need this functionality:

   We use SimpleMDM in addition to SaltProject for fleet management. Most of our fleet configuration is driven by Salt, however having the ability to use the native macOS MDM for management and automation will greatly benefit our ability to serve our users. The combination of Scripts (with Attribute Support!) and Jobs could be a game changer --if-- we could programatically interact with it. Some scenarios where this is valuable:

   • Initial Device Provisioning: When a new Device is enrolled in SimpleMDM, we want to take additional actions via the "device_enrolled" webhook event with a Script Job to do just-in-time provisioning.
   • Device Status Change Events: We already pull all SimpleMDM logs via API. We want to take advantage of

   Example scenarios:

   1. Upload A Bash Shell Script

   Request (POST)
   curl https://a.simplemdm.com/api/v1/scripts/ \
   -F "[email protected];filename=myscript.sh" \
   -F attributesupport=true \
   -u {APIKEY}:

   2.1. Execute myscript.sh against a single device

   Request (POST):
   curl https://a.simplemdm.com/api/v1/jobs/ \
   -d scriptname=myscript.sh \
   -d target={deviceid} \
   -d target_type=device

   Response:
   HTTP/1.1 200
   {
   "data": {
   "type": "job",
   "id": "abcde123456",
   "attributes": {
   "scriptname": "myscript.sh",
   "created": "2022-03-03T01:23:45Z",
   "createdby": "[email protected]",
   "target_type": "device",
   "target": "device-id-xxxx1234",
   "status": {
   "pending": 1,
   "completed": 0,
   "failed": 0
   },
   "devices": [
   {
   "id": "device-id-xxxx1234",
   "status": "pending"
   }
   ]
   }
   }
   }

   2.2. Execute myscript.sh against a device group

   Request (POST)
   curl https://a.simplemdm.com/api/v1/jobs/ \
   -d scriptname=myscript.sh \
   -d target={devicegroupid} \
   -d targettype=device_group

   1. Get Job Status:

   Request:
   curl https://a.simplemdm.com/api/v1/job/{JOB_ID} \
   -u {API_KEY}

   Response:
   HTTP/1.1 200
   {
   "data": {
   "type": "job",
   "id": "abcde123456",
   "attributes": {
   "scriptname": "myscript.sh",
   "created": "2022-03-03T01:23:45Z",
   "createdby": "[email protected]",
   "targettype": "device",
   "target": "device-id-xxxx1234",
   "status: {
   "pending": 0,
   "completed": 1,
   "failed": 0
   },
   "devices": [
   {
   "id": "device-id-xxxx1234",
   "status": "completed",
   "logid": "wxyz0987"
   }
   ]
   }
   }
   }

   1. Get Job Output

   Request:

   curl https://a.simplemdm.com/api/v1/job/log/{LOG_ID} \
   -u {API_KEY}

   Response:

   {
   "data": {
   "type": "log",
   "id": "ec481e3a74a44f588f95bab03f9b76e5",
   // ... standard job attributes?
   "metadata": {
   "name": "myscript.sh",
   "job_status": "0",
   "stdout": "<<Base64 Encoded stdout>>",
   "stderr": "<<Base64 Encoded stderr>>"
   }
   }
   }

   Feature Request: Add Scripts and Script Jobs to API

   Currently the "Scripts" and "Script Jobs" functionality is only supported when using the SimpleMDM web console via a browser.

   • Scripts: https://a.simplemdm.com/admin/scripts
   • Script Jobs: https://a.simplemdm.com/admin/script_jobs

   With the goal to support custom advanced automation for our machine provisioning processes and integration with other configuration management systems, we need the ability to:

   Requirements:

   • Create/Update (Upload) and Delete Scripts
     • Support multipart/form-data by default (similar to other SimpleMDM APIs)
   • List and Get Scripts, including:
     • Script ID
     • Script name
     • Full script contents
     • Created/Updated timestamps
   • Create Script Jobs
   • List Script Jobs
   • Get Job Status
   • Get Job Log /… more
   8 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   completed  ·  Anonymous responded

   This has been implemented. Please see our documentation for more information:

   • Scripts API: https://simplemdm.com/docs/api/#scripts
   • Script Jobs API: https://simplemdm.com/docs/api/#script-jobs

   
   

   If there are additions/changes you would like to see, please submit a new suggestion. Also, thank you for the very detailed description!

10. API: get application identifier

    In order to list the machine on which an application is installed, I intend to use /apps/{APP_ID}/installs

    Right now it is impossible to get the application identifier "APP_ID" from the API.
    The /apps endpoint returns a very limited list of known applications (probably from the catalog, but it's not very clear).

    The only way to get this APP_ID is to go through the admin web interface, go to the "Apps" section, and copy the identifier from there.

    As far as I can tell, the API is missing this feature currently.

    2 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    completed  ·  AdminEric McCann (Admin, SimpleMDM) responded

    The APP_ID for an app can be obtained from the Apps List All endpoint here: https://api.simplemdm.com/#list-all

    
    

    As it stands, we recommend using this endpoint to get a list of IDs. However, this endpoint only returns apps in your account's Catalog. If there is some additional functionality you are looking for, please submit a new suggestion.

11. Add Nextcloud client to shared apps

    Adding Nextcloud client (is a Dropbox alternative and much more) to shared apps. It can be found here: https://nextcloud.com/install/

    2 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Permit override of receipts or installs keys in Munki pkginfo

    Related to this feature request: https://suggestions.simplemdm.com/forums/204404-suggestions/suggestions/40986322-fully-support-the-munki-pkgingo-plist

    As per the documentation (https://help.pdq.com/hc/en-us/articles/6430464122907-Custom-PkgInfo-for-Munki-apps) the following keys are not permitted to overridden by the user:

    installs
    receipts

    I believe the intent of the restriction on these in the manifest is to prevent installation issues, but these keys are vitally important to fix the installation of packages that include sub packages that are not always installed.

    Without being able to override these options, some packages that include a large amount of sub packages that are not always installed (for example, architecture specific ones) will get stuck in a state where Munki believes they are not installed and will continue to re-install the package each time an auto-update cycle runs.

    Please permit the administrator to modify these keys so they can specify specific things Munki should check for to determine if a package is installed, otherwise some vendor package files simply cannot be deployed using SimpleMDM managed Munki without being repackaged by the administrator, and that is far from convenient or simple.

    Related to this feature request: https://suggestions.simplemdm.com/forums/204404-suggestions/suggestions/40986322-fully-support-the-munki-pkgingo-plist

    As per the documentation (https://help.pdq.com/hc/en-us/articles/6430464122907-Custom-PkgInfo-for-Munki-apps) the following keys are not permitted to overridden by the user:

    installs
    receipts

    I believe the intent of the restriction on these in the manifest is to prevent installation issues, but these keys are vitally important to fix the installation of packages that include sub packages that are not always installed.

    Without being able to override these options, some packages that include a large amount of sub packages that are not always installed (for example, architecture specific ones) will get stuck in a state where Munki believes… more

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    completed  ·  Anonymous responded

    We have added the ability to set the "receipts" key in the custom PkgInfo. From what I currently understand, this should solve most scenarios, but if the "installs" key is also necessary for your use-case (or any other PkgInfo keys), please submit a new suggestion and/or email us at [email protected] and let us know. Thanks!

13. add ability to upload custom icons

    When creating custom apps, it would be nice if we could upload a custom icon with it.

    11 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    5 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    completed  ·  AdminEric McCann (Admin, SimpleMDM) responded

    Custom icons can now be uploaded for custom apps & nopkgs that are deployed using SimpleMDM's hosted Munki integration. When enabled, the Managed Software Center will display the provided custom icon. 

    
    

    Please note: Once the app is installed, the application will still use whichever icon was specified in the pkg/dmg. Additionally, custom pkgs that are only eligible for deployment via the MDM protocol do not currently support custom icons. This would require the pkg itself to be modified.

14. Add blender to shared apps
    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    completed  ·  1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. Allow admins to set 'Remote Desktop Enabled' for all devices

    A freshly built macOS 12.1 machine can only have Remote Desktop / screen sharing enabled using MDM. Currently, this can only be done on a per machine basis using 'Enable Remote Desktop' option or API call. It would be great if we could: -

    1. Set 'Remote Desktop Enabled' at a global level for all macOS devices that are in SimpleMDM.

    2. Have the ability to set it on multiple machines at once by ticking the box next to the device and setting from the 'Actions' menu.

    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    completed  ·  Anonymous responded

    Remote Desktop can now be enabled/disabled on multiple devices at once via the main Devices page, as well as enabled automatically when a device enrolls. To enable this for enrollments, see the option under Enrollments > Settings.

16. Support a device's local time for Software Update Policy for iOS profiles

    Currently the start hour and end hour for the profile is based on the account's time zone in the settings. Since we operate devices around the globe, we'd like to easily set one time frame for all devices across our sites. E.g. 7pm to 7am and a checkbox enabled for "Use device's local time".

    4 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    completed  ·  AdminEric McCann (Admin, SimpleMDM) responded

    This option is now supported within the Software Update Policy for iOS profile.

17. Devices API should indicate if phone is in lost mode

    The following API
    
GET https://a.simplemdm.com/api/v1/devices

    Lists detailed information about the device status under attributes.

    We would like to see an additional attribute for when the device was placed in lost mode and if the device is currently in lost mode.

    For example:
    
{
"is_in_lost_mode": true,
"lost_mode_active_at": "2021-07-13T16:00:54.000-07:00",
}


    Since we have a large fleet of devices, we periodically place some of that fleet into lost mode if they go missing, using your existing API.

    We would like to build out reporting which would require having lost mode information available in the API.

    4 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    completed  ·  Anonymous responded

    The "lost_mode_enabled" key has been added to the Devices API.

    
    

    The Logs API can be used to get "lost_mode.enabled" logs to see when the device issued a response indicating that it received the "Enable Lost Mode" command successfully.

18. Add Notion to shared apps

    https://www.notion.so/help/notion-for-desktop

    9 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    completed  ·  1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. Add Handbrake to macOS shared apps.

    I would like to see Handbrake offered as a macOS shared app. Thanks!

    2 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. Specify package install order during prestage

    The prestage_installer pkg that gets used when more than one pkg is assigned to a device group doesn't currently have a method to specify installation.

    Some vendors supply their products as multiple packages and some have dependencies of one being installed before another (see: jamf Connect trying to run the installed app if it doesn't detect a LaunchAgent on disk that is installed by another .pkg). For reasons like this, being able to guarantee the order of pkg installation is key.

    This request is to implement a way to specify the order of installation from the portal that is used by the prestage_installer script.

    The prestage_installer pkg that gets used when more than one pkg is assigned to a device group doesn't currently have a method to specify installation.

    Some vendors supply their products as multiple packages and some have dependencies of one being installed before another (see: jamf Connect trying to run the installed app if it doesn't detect a LaunchAgent on disk that is installed by another .pkg). For reasons like this, being able to guarantee the order of pkg installation is key.

    This request is to implement a way to specify the order of installation from the portal that is used… more

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    completed  ·  1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close