Sysocmgr not working on 64 bit windows

Usage and Config
1

(imported topic written by sowensby91)

I have a task that works great on 32 bit systems but dies on 64 bit systems.

I upload the txt file, it extracts then hangs. Here is the syntax of the action (the names have been changed to protect the innocent):

download http://server:port/big98.tmp

continue if { (size of it = xxxxx and sha1 of it = “xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx”) of file “big98.tmp” of folder “__Download”}

extract big98.tmp

wait {pathname of system folder}\sysocmgr /i:{pathname of windows folder}\inf\sysoc.inf /u:__Download\iis.txt /q

When BigFix tries to execute it, it launches both the 32bit and 64 bit versions of sysocmgr. When I run the command myself, substitutiong the relevance, it installs with no issues.

Any ideas?

2

(imported comment written by jessewk)

You need to use the 64 bit aware system folder inspector:

pathname of system x64 folder

That should work in both environments, provided your clients are at least at 6.0.

3

(imported comment written by sowensby91)

That did not seem to work either. I still see both the 32 bit and 64 bit versions of susocmgr.exe in the task list and IIS never gets installed.

Here is how it looks now:

download http://server:port/big98.tmp

continue if { (size of it = xxxxx and sha1 of it = “xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx”) of file “big98.tmp” of folder “__Download”}

extract big98.tmp

wait {pathname of system x64 folder}\sysocmgr /i:{pathname of windows folder}\inf\sysoc.inf /u:__Download\iis.txt /q

4

(imported comment written by jessewk)

I would try two things next:

  1. write out a file to see the exact command that is getting run

just add 'appendfile ’ in front of the ‘wait’ command. after the action has run, you’ll find a file called “__appendfile” in your operator folder on the client. You can open the file with a text editor and see if something looks strange.

  1. remove the /q and see if you’re getting an error message from the installer
5

(imported comment written by sowensby91)

Here is what was in the “__apendfile”:

wait C:\WINDOWS\system32\sysocmgr /i:C:\WINDOWS\inf\sysoc.inf /u:__Download\iis.txt /q

Removed the /q and I get a generic Windows Setup error: “The application could not be initialized.” There is a Micrsoft IIS6 FAQ page (http://www.microsoft.com/technet/community/en-us/iis/iis6_faq.mspx) that states that this error means that you need a

Components

section in your unattended answer file (I have one) and that your command points to the full path of the file.

Is there relevance language to use to include the actionsite so that I can use a full path?

6

(imported comment written by jessewk)

Yes… you can use this:

wait {pathname of system x64 folder}\sysocmgr /i:{pathname of windows folder}\inf\sysoc.inf /u:"{pathname of client folder of current site}__Download\iis.txt" /q

7

(imported comment written by sowensby91)

Thank you. That was the answer. I needed the full path of the unattended file. Thanks again for the relevance.