Fixlet Problem

Content Authoring
1

(imported topic written by SimonJuul)

Hi All.

I was hoping some help here, i really have no idea why this fixlet is not installing, even though it is saying “completed” in the console.

Here is the Fixlet, hope someone can help a Brother out :wink:

//Prefetch Bluestar

prefetch BluStarClientSetup.exe.tmp sha1:b7cdd810ee5eb5b331a2649362e63bc7b347f48b size:66064762
http://xxx.xxx:52311/Uploads/b7cdd810ee5eb5b331a2649362e63bc7b347f48b/BlustarforPC3.1.tmp
sha256:a98892e613cb181ea8d184c8084a644eaa654d976419a9ea6a93b6b6b6b58f6a

//Udpak filer

extract BluStarClientSetup.exe.tmp

//Installer filer

wait __Download\BluStarClientSetup.exe /s /v%22/qn%22

2

(imported comment written by Tim.Rice)

What happens if you use …

waithidden __Download\BluStarClientSetup.exe /s /v"/qn"

Did you write this as a Fixlet or as a Task?

Have you looked at the Client log files? Any errors?

3

(imported comment written by SimonJuul)

Hej Tim.

Thank you for giving your time.

Lets just start by saying, that i am new to the hole Endpoint manager.

Never the less i have locked at the logs, and it just tells me that

Command failed (Thread execution failed (2)) waithidden __Download\BluStarClientSetup.exe /s /v"/qn"

and the same with a wait __

I have made it via the Wizard, so i am thinking it is a task.

I hope for your respons

4

(imported comment written by Tim.Rice)

Does the Target machine meet the Pre-requisites?

  • Microsoft Visual C++ 2008 SP1 Runtime.

  • Microsoft Visual C++ 2010 SP1 Runtime.

  • Microsoft .NET Framework 4.0 Full.

These were taken from …
http://gts.aastra.com/publish/mx-one/TeleSys/Version5/ServicePack/fw/BluStar/ReleaseNotes%20BS%202.0%20PC%20SP2.htm

5

(imported comment written by jgstew)

As Tim already indicated, I think it should be " instead of %22

Also, this error seems to suggest that the client is having an issue finding “__Download\BluStarClientSetup.exe”.

I would double check that this file exists as it should and try running it from the command line directly to see what happens. Also try it using PSExec.

6

I had something similar happen last week, with a BroadCom BASP installer. I think that there is something odd with command-line parsing for particular InstallShield-based installers, where BESClient gives this error if the command-line parameters contain doublequote characters; but I’m not at all certain on that count and I will probably not be putting much more effort in to it.

In my case, we worked-around the problem by using appendfile to create a batch file to contain the installation command, and using waithidden to execute the batch.