Ok, I am now officially at wit's end. I have created yet another package that will run just fine manually, but when I test it in SCCM 2007 it bombs out. This time I packaged up Text Pad v. 5 using the packaging tips found on this website (http://itninja.com/link/internet-explorer-6-administration-kit-(online)5). I even went so far as to download a trial version of MSI Studio to duplicate everything in the instructions. Nifty tool by the way.

To make a long story short, I tested the following command using the command prompt:

msiexec.exe /i "TextPad 5.msi" ALLUSERS=1 TRANSFORMS="TextPad 5.mst" /qn /l*v %temp%\texpad.log

It ran perfectly. All giddy with excitement, I created a task sequence in SCCM 2007 with the exact same command line. I ran it, the task sequence executed as it should have. I even saw the progress meter move...everything looked like it ran correctly. NOT!

Nothing was installed, no log files were generated...nothing but fireworks. When they burned out, there was no trace that I had done anything!

The same thing happened with Visual Studio 2008 as well.

What am I doing wrong? I have tried virtually every combination possible to get the install to run. CMD and BAT files, modifying the command line, creating a basic package, crossing my eyes, etc., nothing seems to work in SCCM.

I am very open to other ideas right now if anyone has any.

Thanks a bunch :)
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
i don't know sccm yet, so this is just a guess.

could it be that the msi file is missing a full path?

"c:\temp\TextPad 5.msi" as an example.

for the log file, if %temp% has spaces in the path, the string will not be good. try merging the string between " "
Answered 12/06/2010 by: kardock
Second Degree Green Belt

Please log in to comment
0
In addition to that, how about trying it without the /qn to see if you get some dialog box that pops up with some useful information/error?
Answered 12/06/2010 by: bearden3
Purple Belt

Please log in to comment
0
I tried ensuring the full and correct path was in the command line with no luck.

I removed the /qn switch...again, nothing. The package ran, then vanished. One thing stuck out though...I was not prompted for and responses even though I made sure interaction was allowed in SCCM.

Both tries ran as expected when performing them manually. In SCCM, they mimicked a good install but neither one installed anything.

I did find the following in a log file....
The task sequence execution engine successfully completed the action (Text Pad) in the group () with exit code 0
Action output: =======================[ smsswd.exe ] =======================
PackageID = 'MAD00153'
BaseVar = ', ContinueOnError='
SwdAction = '0001'
WinHttp credentials set
Retrying download...
Http result: 405
SendResourceRequest() failed with 0x80004005
WinHttp credentials set
Retrying download...
Http result: 405
SendResourceRequest() failed with 0x80004005
Tried all the available http based locations. SMB based locations will be attempted now.
Successfully connected to "\\revimage.revenue.wi.gov\SMSPKGD$\MAD00153"
Resolved source to 'C:\_SMSTaskSequence\Packages\MAD00153'
Working dir 'C:\_SMSTaskSequence\Packages\MAD00153'
Executing command line: Run command line

C:\_SMSTaskSequence\Packages\MAD00153>C:\_SMSTaskSequence\Packages\MAD00153\msiexec.exe /i "TextPad 5.msi" ALLUSERS=1 TRANSFORMS="TextPad 5.mst" /qn /l*v C:\Windows\TEMP\texpad.log.
Answered 12/06/2010 by: mstarks67
Senior Yellow Belt

Please log in to comment
0
In SCCM, are you running the install as 'the user' or with 'administrative rights'? I'm guessing that it's running with admin rights as your log file is in C:\Windows\temp
What does it tell you in the file 'C:\Windows\TEMP\texpad.log'?
Answered 12/06/2010 by: michaelnowell
Second Degree Blue Belt

Please log in to comment
0
Why a Task Sequence and not a Package? TextPad is one MSI, it's not like you have to run anything before or afterwards but, even if you did, you can create dependencies using the Package/Program route. Just asking...

Also, FFR, there is a dedicated SMS/SCCM forum on AppDeploy.
Answered 12/07/2010 by: VBScab
Red Belt

Please log in to comment
0
If you really need the log file, put it in front of the /qn switch. We experienced similar problems witch SCCM 2007.
Answered 12/07/2010 by: mePeter
Yellow Belt

Please log in to comment
0
As VBScab mention not sure why you are using a task sequence ??? If you create this in a SCCM Package I can't see any problems with the install. As to your DP's I can see from the log file that the task is being found at \\servername\SMSPKGD$\MAD0013 have you checked on the machine that this is copied over to the working dir C:\_smsTaskSequence\packages\mad0013 ????? Also can you run the command line manually from this dir. If so I have had some issues in the past with Task Sequence but only when there was a popup from the application or some user intervention needed but even using the /qn switch it caused problems.
Answered 12/07/2010 by: langa100
Senior Yellow Belt

Please log in to comment
0
put it in front of the /qn switchLike most executables which take arguments, MSIEXEC.EXE doesn't care about what order its arguments are presented, provided the switch and its value are formatted correctly.
Answered 12/07/2010 by: VBScab
Red Belt

Please log in to comment
0
I am running the install using admin rights
Answered 12/07/2010 by: mstarks67
Senior Yellow Belt

Please log in to comment
0
even though I made sure interaction was allowed in SCCM

As far as I know you CAN NOT run programs that have the 'local interaction allowed' flag set in an SCCM task sequence...
Even worse, if you first indicate a program in a task sequence, and then change this setting for the program, I've seen SCCM just quietly 'drop through' to the next viable program.

PJ
Answered 12/07/2010 by: pjgeutjens
Red Belt

Please log in to comment
0
Good question,

We are creating task sequences for all of our software installs. Due to the large variety of different image builds we have, it is easier to copy existing task sequences into new image builds. Utilizing task sequences just makes it easier. We do not advertise many packages to our users unless they are third-party updates. It is much easier to chain sequences together in a task sequence as well.

langa100,
with regards to the downloaded installations, they run correctly using the command line from the C:\_smsTaskSequence folder. This is what baffles me.
When the sequence is executed, everything looks and runs correctly but nothing gets installed. There is no log file generated for reference either. The maunal install using the cached files installs correctly including the log files.
Answered 12/07/2010 by: mstarks67
Senior Yellow Belt

Please log in to comment
0
I had only allow user interaction when testing the package installation. I wanted to see where the problem might have occurred. The task serquence has no option to allow user interaction.
Answered 12/07/2010 by: mstarks67
Senior Yellow Belt

Please log in to comment
0
Checked the windows application logs? Tried it with /qb or /qb! switch? Seems to me that something fails and since you are using /qn, you can not see what. I noticed recently that sometimes long path´s do not resolve correctly, when you use SCCM.
Answered 12/07/2010 by: admaai
Orange Senior Belt

Please log in to comment
0
Just a quick thought but have you tried without the ALLUSERS property?
Answered 12/08/2010 by: langa100
Senior Yellow Belt

Please log in to comment
0
Executing command line: Run command line

C:\_SMSTaskSequence\Packages\MAD00153>C:\_SMSTaskSequence\Packages\MAD00153\msiexec.exe /i "TextPad 5.msi" ALLUSERS=1 TRANSFORMS="TextPad 5.mst" /qn /l*v C:\Windows\TEMP\texpad.log.


msiexec.exe location is system32 and in above log it is being executed from C:\_SMSTaskSequence\Packages\MAD00153\msiexec.exe which might be an issue. copy paste above cmd line with same pth and see how it goes.
Answered 12/08/2010 by: srini
Yellow Belt

Please log in to comment
0
I did. My last test was to create a batch file and run that from the command line. In the batch file was the following line:

msiexec.exe /i "TextPad 5.msi" TRANSFORMS="TextPad 5.mst" /qn /l*v %temp%\texpad.log

I ran this setup as a package and as a task sequence. Both appeared to run correctly and success was recorded in the log files. The installation still failed. I went to the cached folder for SCCM on the target machine and ran the batch file manually and Text Pad was installed without any problems.

I am starting to think that this problem has something to do with permission settings. I know it is something very simple, but that "something" is eluding me. I can execute the batch file properly but the SCCM execution fails...very strange.
Answered 12/08/2010 by: mstarks67
Senior Yellow Belt

Please log in to comment
0
Do the old "run a command prompt via Task Scheduler" trick to get a command prompt running as the local System user, then repeat the install. This emulates as closely as possible how SCCM would install. You might want to ProcMon the process, too.
Answered 12/08/2010 by: VBScab
Red Belt

Please log in to comment
0
Good News everyone...

I have solved the problem. I decided to eliminate the TRANSFORM installation completely. I ended up modifying the textpad.msi file directly, in particular, incorporating the registry key related to our license into the .msi file. I then created a new software package from the definition and voila'. I was able to successfully push the install out using SCCM and it installed perfectly. Something about TRANSFORM installs doesn't seen to sit well with SCCM.

Thanks to everyone for the great tips and assistance. I will probably be back...

Mike
Answered 12/08/2010 by: mstarks67
Senior Yellow Belt

  • SCCM has no problem with transforms. VBSCAB is correct in this is no job for a task sequence. One problem you were probably having is running a per-user installation with admin rights. This runs a a local system account and has no access to any users profiles including any logged in user. It's generally not a good idea to modify vendor MSIs as many here will attest. An MST is almost always a safer method. At least you got it worked out though.
  • I second and third about transforms. SCCM has no issue with them. When I have to use a task sequence in a program I create the program under the package then I use the Install Software component in the TS. Also, you don't have to do msiexec /i blah.msi TRANSFORMS=blah.mst /qb. I just point it to the msi file, add the TRANSFORMS=blah.mst then leave it. CM adds the other stuff for you. Hope this made sense.
Please log in to comment
0
I may be out in left field here, but did you try...

a) using explicit paths and wrapping it in quotes - for example, in your command line use:
msiexec.exe /i "C:\_SMSTaskSequence\Packages\MAD00153\TextPad 5.msi ALLUSERS=1 TRANSFORMS=C:\_SMSTaskSequence\Packages\MAD00153\TextPad 5.mst /qn /l*v C:\Windows\TEMP\texpad.log"

b) simply removing the spaces from your msi and mst filenames?
Answered 12/08/2010 by: snootworks
Yellow Belt

Please log in to comment
0
You're missing at least 2 quote marks in your response. Did you mean:msiexec.exe /i "C:\_SMSTaskSequence\Packages\MAD00153\TextPad 5.msi" ALLUSERS=1 TRANSFORMS="C:\_SMSTaskSequence\Packages\MAD00153\TextPad 5.mst" /qn /l*v %SystemRoot%\TEMP\textpad.log
Answered 12/08/2010 by: VBScab
Red Belt

Please log in to comment
0
Bloody hell... first post on the board and I make a copy/paste error. *shame*
Answered 12/08/2010 by: snootworks
Yellow Belt

Please log in to comment
0

nm old post

Answered 05/08/2012 by: Estes
Second Degree Blue Belt

Please log in to comment
0

nm old post

Answered 05/08/2012 by: Estes
Second Degree Blue Belt

Please log in to comment
Answer this question or Comment on this question for clarity