HP EliteBook 745 Sure Recover User Guide - Page 15

Provisioning your target systems, Troubleshooting

Page 15 highlights

NOTE: If you use IIS as your hosting solution, you must configure your MIME entries to include the following extensions, all configured as "application/octet-stream:" ● .mft ● .sig ● .swm ● .wim Provisioning your target systems You can provision your target systems using the HP Client Management Script Library, HP Client Security Manager (CSM)/Sure Recover or the Manageability Integration Kit (MIK) (https://www.hp.com/go/ clientmanagement). Provide the following information for this provisioning: 1. The URL address of the manifest file hosted in the previous section (http://your_server.domain/path/ custom.mft) 2. The public key used to verify the signature file created previously (for example, C:\staging\my-recovery- public.pem). Troubleshooting If you receive a message about the custom recovery process failing security validation, check the following: 1. Manifest must be UTF-8 without BOM. 2. Check file hashes. 3. Ensure that the system was provisioned with the public key corresponding to the private key used to sign the manifest. 4. IIS server mime types must be application/octet-stream. 5. File paths within the manifest must include the full path to the topmost directory containing the image as seen from a client system. This path is not the full path where the files are saved at the distribution point. Provisioning your target systems 9

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24

NOTE:
If you use IIS as your hosting solution, you must
configure
your MIME entries to include the following
extensions, all
configured
as "application/octet-stream:"
.mft
.sig
.swm
.wim
Provisioning your target systems
You can provision your target systems using the HP Client Management Script Library, HP Client Security
Manager (CSM)/Sure Recover or the Manageability Integration Kit (MIK) (
go/
clientmanagement
).
Provide the following information for this provisioning:
1.
The URL address of the manifest
file
hosted in the previous section (http://your_server.domain/path/
custom.mft)
2.
The public key used to verify the signature
file
created previously (for example, C:\staging\my-recovery-
public.pem).
Troubleshooting
If you receive a message about the custom recovery process failing security validation, check the following:
1.
Manifest must be UTF-8 without BOM.
2.
Check
file
hashes.
3.
Ensure that the system was provisioned with the public key corresponding to the private key used to
sign the manifest.
4.
IIS server mime types must be
application/octet-stream
.
5.
File paths within the manifest must include the full path to the topmost directory containing the image
as seen from a client system. This path is not the full path where the
files
are saved at the distribution
point.
Provisioning your target systems
9