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.
Related
When I log in into an windows device, I can sometimes see 2 users sessions (I can see it by clicking Task Manager -> Users). One of the users has status Disconnected and the other active
Is there a way for me to see weather the user is disconnected or not in the registry?
Thank you
I don't know if there is a registry value you can check and if you find one it must be considered an unintended side effect you should not rely on.
The WTS API is the correct way to handle this.
Call WTSRegisterSessionNotification to receive notifications and/or WTSEnumerateSessionsW to find the current sessions and their states.
I used the wrong PIN on my account multiple times on the super-app, now its refusing to allow me to reset it. How do I proceed from here?
As a security measure, the account will be blocked for 24hrs and then automatically unblocked. Please avoid continuing to try logging in on that account as you can then be blocked for 7 days. For now, I would suggest that you create a new account and continue with your development work.
For Example, Policy A is updated and linked with the device.
But Policy A is not applied properly in the Device because of user intervention.
I want to Re-apply the Policy to the Device again. Is there any way to apply the policy to the device again?.
note:
I tried Device.patch. But it does not reapply policy in Device.
Nothing occurs in the Device. Because already same policy applies to the device.
With Updating Policy. we can reflect the updated policy in the Device. But there is no change in Policy,
if I try Policies.patch, Policy Object Will not get updated (Version Not change).
SO Policy is not reflecting in the Device.
could not able to update the policy without any changes.
Unfortunately, there is no way to apply the same policy on the same device without updating the policy. Also, a device can only have a single policy at any given time. Please refer to this link for applying policy to a device.
However, if it is necessary to re-apply a policy since the initial policy was not applied due to user interference, I suggest that you add a policy that will not directly affect your device. With this, the policy will be updated and can be applied to the device.
Can I use GeoCoordinateWatcher in Application_Launching to check that the phone location service is enabled or disabled? Does this affect performance?
Regards,
Panache
Don't!
Let the app launch and then decide.
You need your app to function even if the location service is disabled.
There is no time guarantee in confirming the location service is running so if you wait you may go over your allowed start up time.
Or are you just asking how to use a GeoCoordinateWatcher?
Edit:
If you want to only display this once, then just keep track of if you've displayed the prompt/message.
Also be aware that due to settings being changed while your app is tombstoned just performing the check on application launch does not guarantee that it will always be correct.
e.g.
location service disabled when app
started
App displays prompt
User presses start (app tombstoned)
uses changes settings to enable location service
user uses back button to reactivate app
app restarted (If doesn't RE-check if service enabled then would be wrong)
We are trying to trace the time a windows default printer was changed and by who or what.
Any ideas?
I don't think that is tracked anywhere. For past changes, you might be out of luck.
For future changes, you could try setting up security auditing (via regedit: Permissions->Acvanced->Auditing) on HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows and watch for changes to that key in the Security event log. The amount of security event messages may make tracking difficult, though.