OSD: Perform Post-Install Tasks | Keeps failing

Hi All,

I am trying to install an OS Deployment Server, which I have done numerous times and it keeps failing on the ‘Perform Post-Install Tasks’ action.

Here is the action log:
Completed //Stop IBM Web Interface Extension service and set it to manual start
Completed waithidden cmd /C "net stop remboagent & sc config remboagent start= demand"
Completed parameter “AGENTFOLDER” = "{following text of first “%22” of preceding text of first “\rbagent” of (value “ImagePath” of key “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RemboAgent” of registry as string)}“
Completed parameter “READYTESTPATH”=”{(parameter “AGENTFOLDER”)}\updateidlescheme.log"
Completed regdelete “[HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\OSDControl]” "Install"
Completed waithidden cmd /C "{preceding texts of firsts “%00” of (value “ImagePath” of key “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RemboAgent” of registry as string)} -d -v 4 rad-updateidlescheme > “{parameter “READYTESTPATH”}” 2>&1"
Completed if {not exists file (parameter “READYTESTPATH” of action) whose (not exists lines whose (it as string contains “Resource temporarily unavailable”) of it)}
Completed parameter “waitTime” = "{now}"
Completed pause while {((now) - time (parameter “waitTime”)) < 300second}
Completed waithidden cmd /C "{preceding texts of firsts “%00” of (value “ImagePath” of key “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RemboAgent” of registry as string)} -d -v 4 rad-updateidlescheme > “{parameter “READYTESTPATH”}” 2>&1"
Completed if {not exists file (parameter “READYTESTPATH” of action) whose (not exists lines whose (it as string contains “Resource temporarily unavailable”) of it)}
Completed pause while {((now) - time (parameter “waitTime”)) < 600
second}
Completed waithidden cmd /C "{preceding texts of firsts “%00” of (value “ImagePath” of key “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RemboAgent” of registry as string)} -d -v 4 rad-updateidlescheme > “{parameter “READYTESTPATH”}” 2>&1"
Completed //Abort post install action, server is taking longer than 10 minutes to become responsive
Failed continue if {exists file (parameter “READYTESTPATH” of action) whose (not exists lines whose (it as string contains “Resource temporarily unavailable”) of it)}
endif
endif
parameter “BMSERVERVERSION” = "{version of file (matches (regex “.:.+exe”) of (value “ImagePath” of key “HKLM\SYSTEM\CurrentControlSet\Services\RemboServer” of registry as string))}“
if {(parameter “BMSERVERVERSION”) > version “7.1.111.19023”}
parameter “updatebehaviorslogpath”=”{(parameter “AGENTFOLDER”)}\updatebehaviors.log"
if {(parameter “BMSERVERVERSION”) > version “7.1.117.00000”}
waithidden cmd /C "{preceding texts of firsts “%00” of (value “ImagePath” of key “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RemboAgent” of registry as string)} -d -v 4 rad-updatebehaviors add 7 > “{parameter “updatebehaviorslogpath”}” 2>&1"
else
waithidden cmd /C "{preceding texts of firsts “%00” of (value “ImagePath” of key “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RemboAgent” of registry as string)} -d -v 4 rad-updatebehaviors 7 > “{parameter “updatebehaviorslogpath”}” 2>&1"
endif
endif
parameter “GSPPATH” = "{value “DataDir” of key “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RemboServer” of registry as string & “\global\gsp”}"
if {exists folder (parameter “GSPPATH”)}
waithidden cmd /C "{preceding texts of firsts “%00” of (value “ImagePath” of key “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RemboAgent” of registry as string)} -d -v 4 rad-mkgenericsysprof > “{(parameter “AGENTFOLDER”)}\mkgenericsysprof.log” 2>&1"
endif

Troubleshooting:

  • Uninstalled OS Deployment Server, Removed Relay, Cleaned up Registry, File System, Removed SQL - Still does it.

The computer is just idling throughout the process. I am not sure what I am doing wrong here.

Anyone else seen this behaviour?

Thanks
Regards,
Stefano

The install process stops because the rad-updateidlescheme command has failed. This is the very first interaction that is performed after all the different pieces are installed. Hence is very probable that a problem in the installation will manifest itself with a failure at this point.
Seen once linked to the datasource.
Ununstall the OSD server. Do not remove the relay.
Run "Bare Metal Server Clean Up Post Uninstall or Install Failure " fixlet 134.
Check on the system and make sure that AutoDeply datasource has been removed. If not remove it manually.
Retry and good luck.
Antonio

Thanks Antonio, I will give that a go. I have definitely tried running that ‘Base Metal Server Clean up Post Uninstall or Install Failure’ fixlet after uninstalling. I will check that AutoDeploy datasource has been removed as well though.
I will keep you posted.

Regards,
Stefano

Hi Antonio,
Your suggestion to delete the ODBC System entry for AutoDeploy, resolved my issue - the OSD Server install succeeds, all the way up until it tries to update the driver manifest:

Completed cmd.exe /C echo Skipping OS driver manifest import (already at right version) [AGTRC:0]>> “{parameter “ManifestImportlogpath”}” 2>&1
Completed EOF
Completed delete runrbagent.bat
Completed move __createfile runrbagent.bat
Completed endif
Completed waithidden runrbagent.bat
Completed // If the synchronization has not been triggered by an update, we must reset the registry key before updating it to be sure to read the status of the last synchronization
Completed if {(value “SyncTimeManifest” of key “HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\OSDControl” of registry as integer)|0 = 1439889223790}
Completed regset “[HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\OSDControl]” “SyncTimeManifest”="0"
Completed endif
Completed // End action if previous command failed before we store a success key in registry
Completed if {exists file (parameter “ManifestImportlogpath” of action) whose ((number of lines whose (it as string contains “[AGTRC:0]”) of it) equals 3)}
Completed regset “[HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\OSDControl]” “SyncTimeManifest”="1439889223790"
Completed endif
Failed continue if {(value “SyncTimeManifest” of key “HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\OSDControl” of registry as integer)|0 >= 1439889223790}

The SyncTimeManifest registry entry is never created. I have seen this before and reinstalls of the OSD Server have resolved it, but since I have already done this, I have run out of ideas.

I am sure others have seen this…

Thanks!

Still not luck with this. I have raised a PMR with IBM and will update this thread with the results of their findings, in hope that this assists others if they come across this.

-Stefano

Have you tried manually creating :
creating “[HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\OSDControl]” “SyncTimeManifest”=“1439889223790”

The failures were caused by us running Trend Micro OfficeScan on our OSD Servers. The following article got us working again. Known issue with Trend OfficeScan - http://www-01.ibm.com/support/docview.wss?uid=swg1IV72635

-Stefano