(imported topic written by SystemAdmin)
I consider backup of Extender for iOS.
I saw the following page.
Isn’t the registry information on Extender also required?
(imported comment written by SystemAdmin)
From my experience thus far, that link gives all the pieces you need in order to get your Management Extender back up and functional and to retain the device ID and registration information
for your mobile devices
.
If you want, you could possible backup the RegCount, ComputerID, and ReportSequenceNumber from
HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\GlobalOptions
to restore the identity of the Management Extender itself to the TEM server (so that it retains the same computer ID and same action history) – but it isn’t required to resume functionality. Likewise, you could preserve any BES specific settings you’ve made to the relay, but that could be recreated from information from the TEM Server.
- Tim
(imported comment written by SystemAdmin)
Hello Tim,
Thanks for your replyng.
As an asked background, I had found the following problem.
- Since there was administrator authority fault in a iOS device unit, although the iOS apps was again installed on the iOS device, administrator authority did not change.
- I thought that it meant that this needs to back up the registry key and value of Extender for iOS.
Since I have not checked by the component of the newest Extender for iOS yet, after the problem of the component of Extender for iOS is resolved, I am going to carry out.
With the fault of the component of Extender for iOS, when I applied FixletID94 to Extender for iOS, I checked that the phenomenon from which FixletID194 becomes the completion of correction and have continued “Not Relevant”.