Is there a maximum time from when a policy is patched to when a device syncs the newly patched policy? As an example if a device is provisioned and active then powered off, the policy assigned to this device is patched, 45 days later the unit is powered on, will there be any problem applying the policy to the device?
If the device does not check in for 45 days, the user token on the device expires, so it may disappear from the API. The default expiry time for device data is 30 days, if that’s older than 30 days it will be removed from the database.
Related
I am trying to troubleshoot a Windows 10 Pro system. This is complicated by the fact that the system event log is flooded by a set of identical information level messages about TPM every minute.
The messages are:
The TPM has been cleared. Reason: ByPPI.
The Ownership of the Trusted Platform Module (TPM) hardware on this computer was
successfully taken (TPM TakeOwnership command) by the system.
The TBS device identifier has been generated.
The TPM was successfully provisioned and is now ready for use.
I found a TPM-Maintenance task in the task scheduler that seems to run every minute.
Can someone explain why Windows is clearing the TPM once a minute? Is that necessary? Can I safely disable the TPM-Maintenance task to prevent this flood of messages?
Thanks!
Devices enrolled to the policy are not getting updated on device patch(changing policy) or doing any change on applied policy(like disable the status bar, disable camera). The device needs a manual reboot several times to pickup up a real-time state from google and sync. Can you please advise on the issue.
This issue about policy sync up is already fixed.
I have a PC as a mikrotik router at home, and also i have many power failures because the electricity network is undergoing maintenance ant this may last for months, and I noticed that what it's shown at the user profile is not updated instantly by the downloads(mega Bytes) at the active users, and after an electricity cut off, everything at the active user just resetted (I mean downloaded megabytes), and nothing is recorded.
How can I update it instantly or at least every hour, any ideas?
Several solutions to keep track of volatile data after a reboot:
Use a Radius server with accounting (data use will be automatically sent to the radius server and logged in database)
Use mikrotik API to query the "Mb used" from an external device and log it on a file.
Write a mikrotik script to query the data you need and log it into a file or on a non-volatile area (for example, comment on user)
During the teamwork development process that shares the same instance of Vagrant I always had trouble relaunching Vagrant Share due to it's session expiration. Documentation says that it's currently 1 hour (even though sometimes it worked only for 10-15 minutes). Is it possible to remove or extend session expiration time?
Currently (June 2016) the expiration time has been extended even more to 8 hours based on VagrantCloud's documentation:
Share sessions expire after a short time (currently 8 hours), but can
also be expired manually by ctrl-c from the sharing machine or via the
web interface.
However it doesn't seem to be any option to set the expiration interval yourself. And I don't believe it will ever be. The purpose of vagrant share is to share your work for a limited time just for your client to have a look or for your partners to do some testing and come back with feedback, not mid-term hosting.
It is not currently possible to change the vagrant share session expiration timeout.
What KPI(Key Performance Indicators) should we keep in mind while testing a mobile app or what can be the KPIs for a successful mobile app?
KPIs for Apps on mobile devices:
Application time running without connection to permanent power (battery) (App + device + OS)
Frequency of connections to server (every 5, 10, 30 minutes)
Num bytes needeed for App data packet to server.
storage capacity for app data
logging capacity before roll over
time intervall app can fully work whitout connection to server
Unclear if these are KPIs:
remote updateable (full update, difference update)
capable to migrate app data persisted with old app version to new one.
encryption of app data.
KPI's to measure Success of Mobile App
Downloads
Active Users - monthly and daily
Revenue per User
Acquisition Cost
Retention Rate
User Experience - App Launch time/ Social Shares / Pages visited
Session Time