Osd re-imaging

Usage and Config
1

(imported topic written by Diadem)

hello,

Need help. Trying to re-image using a captured image on IEM but process gets stuck at Determining Available Drivers. From the summary tab, i see the process fails with a 503 HTTP error. I have attached a snapshot of the same.

[-]

[+]

Download error:

“Unexpected HTTP response: 503 Service Unavailable”

Download requested on server:

URL:

http://endpointmanager.kra.go:52311/Uploads/861B0280F73693AEC3C6FD0C7BB898A1F4B73949/Win7x86_TESTTEM-PC_1411561141487.driverinfo.BFOSD

Hash:

(sha1)861b0280f73693aec3c6fd0c7bb898a1f4b73949

Size:

Next retry:

Please, its very urgent if anyone has an idea i’ll truly appreciate.

2

(imported comment written by sergio.tarchi)

Hi,

this error could be related at a Bes Root Server overload. Could you please try to restart Bes Root Server service?

Thanks.

Sergio

3

(imported comment written by Diadem)

Hi Sergio,

Thanks for timely response. I restarted the root server but nothing changed on the current re-image actions, so i started a new action which failed at the same step…i.e Determining Applicable Drivers. :frowning:

Any more ideas? Please.

Thanks.

4

(imported comment written by sergio.tarchi)

Hi,

could you please check that the file (Win7x86_TESTTEM-PC_1411561141487.driverinof.BFOSD) exists in a subfolder of Upload folder of your TEM root server? Default location is C:\Program Files (x86)\BigFix Enterprise\BES Server\wwwrootbes\Uploads.

I suggest to open a PMR to handle this issue.

Thanks.

5

(imported comment written by Diadem)

Hi Sergio,

I’ve verified and the file is there in the uploads directory.

About PMR, i already logged one which is on level 1 but still no much response. Last response was on Wednesday morning…hence the decision to seek assistance from the forum.

Thanks.

6

(imported comment written by sergio.tarchi)

Hi,

so probably the file exists in the upload directory but not on the relay where the clients try to download it from. As temporary solution I suggest to copy that file to sha1 folder of the relay where the client that you have to re-image is connected to (it could be the TEM root server computer or a lower relay in the hierarchy) renaming it with the name of its directory on Upload folder (e.g. 0deca2de52365c7a6aa6e826b70f9a716c16f346)

Default location for sha1 folder is the following if the relay is TEM root server computer:

C:\Program Files (x86)\BigFix Enterprise\BES Server\wwwrootbes\bfmirror\downloads\sha1

or the following if it’s a lower relay in hierarchy:

C:\Program Files (x86)\BigFix Enterprise\BES Relay\wwwrootbes\bfmirror\downloads\sha1

If this temporary solves, the cause of the problem (file is not automatically copied) can be better investigated via PMR.

Thanks.

7

(imported comment written by Diadem)

Hi

This seems to have worked…after copying the file to SHA1 its now running and on the target machines its showing ‘Running: Lite Touch Installation’.

Thanks alot. Will keep you informed on the developments.

Again, thanks a lot.

8

(imported comment written by Diadem)

Hi,

It worked. Two machines completed successfully. Trying on a new machine to monitor the time taken to do a clean re-image.

Thanks big time. Will open another PMR for files not copying automatically to the SHA1 folder. But will still appreciate your input on this.

Truly appreciated.