Issues on "Create Deployment Media"

[rgfdic]

Hello Everyone,

I am trying to test OSD in Bigfix, and one step that is giving me problems is the creation of the boot media (Create Deployment Media). I see the following error in the client log.

"Command succeeded delete “C:\Windows\system32\RelayDownloader64.exe” (group:105,action:107)
Command succeeded copy __download/RelayDownloader64.exe “C:\Windows\system32\RelayDownloader64.exe” (group:105,action:107)
Wow64 redirection disabled. action uses wow64 redirection false (group:105,action:107)
Command succeeded delete “C:\Windows\sysnative\RelayDownloader.exe” (group:105,action:107)
Command succeeded copy __download/RelayDownloader.exe “C:\Windows\sysnative\RelayDownloader.exe” (group:105,action:107)
Command succeeded delete “C:\Windows\sysnative\RelayDownloader64.exe” (group:105,action:107)
Command succeeded copy __download/RelayDownloader64.exe “C:\Windows\sysnative\RelayDownloader64.exe” (group:105,action:107)
Wow64 redirection enabled. action uses wow64 redirection true (group:105,action:107)
Command succeeded parameter “RBAGENT” = “rbagent64.exe” (group:105,action:107)
Command started - download now as rbagent64.exe https://192.168.2.10/agents/rbagent64.exe (group:105,action:107)
At 08:47:49 -0700 -
Report posted successfully
At 08:47:53 -0700 - actionsite (http://serverFQDN:52311/cgi-bin/bfgather.exe/actionsite)
Command failed (Can’t download file ‘General transport failure.
SOCKET CONNECT (winsock error -8)’) download now as rbagent64.exe https://192.168.2.10/agents/rbagent64.exe (group:105,action:107)
At 08:47:53 -0700 -
"
Any help will be appreciated.

[Gianluca]

Hello,

have you verified if the https link is able to download the file?
Have you any firewall or security tool active that could block the communication?

The issue seems to be not easy. I suggest to open a PMR in order to investigate the error more deeply.
Please consider that the problem determination can be helped if they are reported details as the Site level, MDT bundle version, The Bare Metal server version, The image os type (Win7, win10 and so on), the architecture of the image if x64 or x32, if the image is cloned or if it is a setup. Or if you have noticed that the issue starting occurring after that a particular change happened in your environment.
Moreover, in these cases are required the *.trc and *.log files in the C:\Program Files\Common Files\IBM Tivoli folder of the Bare Metal server.
The error could be related to the available memory, you could even check if the free ram is reducing during the download on the bare metal server.

[Gianluca]

Me again,

in addition to my previous update please consider that you could have run a particular scenario following the following steps:

1. In the Bundle and media mananger panel a particular MDT Bundle creator (computer with WADk or Waik installed locally)
2. then you pressed “Create Deployment Media” to create a network media
3. then you selected one of your available Bare Metal Server, but not coincident with the selected MDT Bundle creator.
4. in the OS Deployment server section of the “Create Deployment Media” panel you could have selected a Server IP that is not reachable from the selected MDT Bundle creator computer.

Try to verify is it work correctly the http link reported in the log messages: “https://192.168.2.10/agents/rbagent64.exe” from the MDT Bundle creator computer.

[sryn]

Just in case someone searches for the same fault and finds this like I did, the WIndows firewall on the OSD server had no exception for HTTP/S. I don’t know if this is normally configured as part of the Deploy Bare Metal Server, I added a rule allowing ports 80 and 443 and then the Create Media task completed.