Systems Management

SCCM installs software (actually runs package's programs) using a Local System account, if you've set Program's 'Run mode' to 'Run with administrative rights'. If installation is msi-based and it has been executed as per user, the missing shortcuts are actually in Local System's "profile":
[blockquote][font="courier new"]"%systemroot%\system32\config\systemprofile\Start Menu"
[/blockquote]To be sure that installation is done per machine, add ALLUSER=1 at the msiexec command line, like this:
[blockquote][font="courier new"]msiexec.exe /i package.msi /qb ALLUSERS=1
[/blockquote][font="courier new"][font="times new roman"]Legacy installations (setup.exe) may also behave the same way or may have some other problems related to the fact that installation is done by Local System.
--
Mikko Järvinen

Did you test if all the above mentioned applications installs /qb or /qn switches manually?

- Is the client installed on the, er, client machines?
- Use the console to see if the target's have "received" the application's advertisement.
- Also, the client has a bunch of log files. http://msmvps.com/blogs/lduncan/pages/17901.aspx

ORIGINAL: goldeneye

Did you test if all the above mentioned applications installs /qb or /qn switches manually?



Hi goldeneye,

Mostly we face the above issues with the silent installation( response / unattended file) so /qn or /qb will not used in this case.

We call the setup.exe n the unattended file in the vbscript. And while installing the appln manually by double clicking the vbscript works fine as per the source.

But while deploying it thro sccm, in the log , we cud find exit code=0 , installed successfully.
All that we could find in the client machines is jus one or two files of the relative application.

So is there any parameters to be changed in the command line options to deploy the appln which uses unattended file or response files?

ORIGINAL: VBScab

- Is the client installed on the, er, client machines?
- Use the console to see if the target's have "received" the application's advertisement.
- Also, the client has a bunch of log files. http://msmvps.com/blogs/lduncan/pages/17901.aspx


Hi,

S the SCCM Client has been installed in all the client machines.
After advertising the program, while checking the status in Execmgr.log in the client machine, we get exit code=0, successfully installed.

But in the client machines jus one or two files have been installed, no arp entry, no shortcuts too .
So what shud be done in this case?

Alice,

Please make the followings checks.
1.Try installing only the .msi and .mst files using the cmd line's msiexec /i...........
2. If there are loose files along with the .MSI file then Select download and run when you advertise the application.
3.Check if there ane any CA in the MSI which will stop installing application silently,comment them and then try to install..
4.While creating a SMS package please make sure that there is no extra space provided or any other human error.
5. Try creating a log file /l*v %windir%/debug/ABC.log and check this log file rather then checking "Execmgr.log" This will help you trace the exact error.
6. If you installing application using .bat or .vbs then make sure you provide the correct pacth in the same.

Cheers

ORIGINAL: goldeneye

Alice,

Please make the followings checks.
1.Try installing only the .msi and .mst files using the cmd line's msiexec /i...........
2. If there are loose files along with the .MSI file then Select download and run when you advertise the application.
3.Check if there ane any CA in the MSI which will stop installing application silently,comment them and then try to install..
4.While creating a SMS package please make sure that there is no extra space provided or any other human error.
5. Try creating a log file /l*v %windir%/debug/ABC.log and check this log file rather then checking "Execmgr.log" This will help you trace the exact error.
6. If you installing application using .bat or .vbs then make sure you provide the correct pacth in the same.

Cheers


Cant follow the points from 1st to 3rd as it is silent installation.
no space was there as mentioned in the 4th point.
Tried created log file, the log file jus has the following informations like company name of the appln, ... few properties n then the exit code...
The log file wasnt step by step process so this log file was not so useful for analyzing the installation process.
The correct path was provided.

To explain u the exact problem we are facing, i wud like to explain u a scenario:

Actually in our team we packaged both SQL 2000 Developer Edition Server & Client thro silent installation.
We created a setup .iss (unattend file) for silent installation and the command to invoke this .iss file is:
setupsql.exe -s -f1 setup.iss --->which was working fine manually but thro sccm ,it wasnt
so we changed the parameters setupsql.exe k=SMS -s -m -SMS -f1 setup.iss , using this cmd, SQL 2000 DE Client was deployed successfully in SCCM.

When we tried the same parameters for SQL 2000 Developer Edition Server , it dint work.
So are u ppl aware of the sms parameters for deploying the applns thro SCCM

When I deployed SQL 2000 via SCCM 2007 I used the following command line within a VBscript wrapper:

SQL2000\X86\SETUP\SETUPSQL.EXE -s -SMS -f1 setup.iss -f2c:\software\SQL2k.log

The other problem I encountered was with the default TEMP and TMP environment variables. To fix this I also included a function to set both temp variables to be "C:\Temp".

Hope this helps

If the ultimate delivery mechanism is an MSI (or collection of MSIs) - as is the case with the SQL Server flavours - I prefer to use those MSIs directly and avoid answer files. Besides any other consideration, you can apply any changes you require using transforms against those MSIs.

ORIGINAL: Pudsey

When I deployed SQL 2000 via SCCM 2007 I used the following command line within a VBscript wrapper:

SQL2000\X86\SETUP\SETUPSQL.EXE -s -SMS -f1 setup.iss -f2c:\software\SQL2k.log

The other problem I encountered was with the default TEMP and TMP environment variables. To fix this I also included a function to set both temp variables to be "C:\Temp".

Hope this helps




Hi Pudsey,

Thanks for ur reply. But cud u explain it more detaiily as im newbie to sccm?
Im ok with command line option. but dint get u wat ever u said abt TEMP concept....[:(]

ORIGINAL: VBScab

If the ultimate delivery mechanism is an MSI (or collection of MSIs) - as is the case with the SQL Server flavours - I prefer to use those MSIs directly and avoid answer files. Besides any other consideration, you can apply any changes you require using transforms against those MSIs.


Its always good to use the vendor msi's itself....
Since applns like SQL, DB2 .... are reg Database........ our team opted for answer file method....
Will try pushing with the vendor msi's also....
Thanks for ur reply VBScab

I cannot remember the exact error I was getting but I think it was something about the filename being too long. This is because the usual temp path “C:\Documents and Settings\<UserName>\Local Settings\Temp”, when combined with the extended file names extracted by the installer, exceeds 255 characters when fully expanded. To fix this you set the temp paths to be something short like “C:\Temp”.

A shorthand version of the VBScript I used to set the variables:

Function SetVar ' Sets TEMP and TMP Variables

Set objEnvVar = objShell.Environment("PROCESS")
objEnvVar.Item("TMP") = "C:\TEMP"
objEnvVar.Item("TEMP") = "C:\TEMP"

End Function

I then set them back using:

Function ResetVar ' Resets TEMP and TMP Variables

Set objEnvVar = objShell.Environment("PROCESS")
objEnvVar.Item("TMP") = "C:\DOCUME~1\%USERNAME%\Local Settings\Temp"
objEnvVar.Item("TEMP") = "C:\DOCUME~1\%USERNAME%\Local Settings\Temp"

End Function


Hope this helps

Puds