(imported topic written by delichty91)
Some quick stats to start with:
- TEM Version: 8.1.617
- Server/Console OS: Windows Server 2008 SP2
- Client OS: Windows 7 SP1
I have a client that has never been able to successfully complete a fixlet. Each attempted fixlet results in a status of “Download Failed”. Tasks process perfectly fine, it is only fixlets that do not seem to work (anything that downloads content and executes it).
One example is the Fixlet to ugprade the TEM Client to 8.1.617 (this is the fixlet I used to do some troubleshooting with). I have included the entire Action Script from Fixlet “Updated Windows Client - Tivoli Endpoint Manager version 8.1.617.0 Now Available!” below. Before issuing this action to the client, I performed a manual restart of the computer (just for good measure). Once the restart was completed, I verified that the BES Client and BITS services were running.
The action I issued to troubleshoot this was ID 1137. The file was downloaded and cached onto the TEM Server without issue. I verifeid this via the Download Status Report. Action 1137 shows up within the “Ready” section of that report. The detail shown on this report for this action is as follows.
Action: 1137
url 1: http://software.bigfix.com/download/bes/81/BigFix-BES-Client-8.1.617.0.exe
To further troubleshoot this issue, I opened the action URL http://mytemserver:52311/bfmirror/downloads/1137/0 from this client. The page loads fine and returns a simple “A” (this seems to be normal/correct). Then, I brought up the download URL http://mytemserver:52311/bfmirror/downloads/1137/1 from this client. It downloaded the installer and I was able to run it without issue (after renaming it to 1.exe of course). I confirmed that the client is now running 8.1.617 of the TEM Client.
I pulled all of the details out of the TEM Client Log that pertains to action 1137, and have attached them to this post (too much detail to include in the post itself). I see mulitple attempts by the TEM Client to check on the status of the download, but no indications of why it was unable to download the cached content from the TEM Server.
As another step, I ran the task to change the TEM Client Communication Method to use winsock.dll instead of the Monikers API. After this action was completed, I manually restarted the BES Client service on this machine. I then issued another fixlet to test, and the behavior remained precisely the same.
Any direction or assistance you could provide in tracking down and resolving this issue would be greatly appreciated.
BEGIN full action script
continue if {name of operating system is not “Win2000” or not exists running application “mmc.exe”}
prefetch BESClientUpgrade.exe sha1:b91da55056468bb4f5335ef2b21e6f1a48bdb0cd size:8044032 http://software.bigfix.com/download/bes/81/BigFix-BES-Client-8.1.617.0.exe
regset "
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\windows\Installer
" “Logging”=“voicewarmupx”
delete __Local\Get\BESClientUpgrade.exe
// If the next line fails, there is not enough free space to complete this action
continue if {8044032 < free space of drive of client folder of current site}
move __Download\BESClientUpgrade.exe __Local\Get\BESClientUpgrade.exe
// The following line may show as Failed if the command executes a restart of the client - This is normal behaviour on success
wait __Local\Get\BESClientUpgrade.exe /s /v"/l*voicewarmup “{location of client}\besclientinstall.log” REBOOT=ReallySuppress MSIRESTARTMANAGERCONTROL=Disable /qn"
END full action script