Improve company productivity with a Business Account.Sign Up

x
?
Solved

SCCM problem with some packages

Posted on 2008-06-24
3
Medium Priority
?
1,136 Views
Last Modified: 2013-11-21
Hi,

We have recently upgraded from SMS 2003 to SCCM 2007.  Everything seems to have gone smoothly and working fine but we have a few packages that are not msi's and are actually scripts that it runs.  Some of these scripts arent working even though SMS reports the package installed successfully.  The scripts that "fail" are ones that copy a file from a server to the local pc.  I have read that with SCCM there are 2 types of security modes and if you chose Advanced it uses the local system account to run packages and not a user account.  If we change the package to run as the user and only when a user is logged in then the script works, however, we dont want our packages to only run when a user is logged in and the user wont have rights to install software on the pc.

Has anyone come across this issue before and know of a solution?
0
Comment
Question by:oldhammbc
  • 2
3 Comments
 
LVL 29

Assisted Solution

by:matrixnz
matrixnz earned 400 total points
ID: 21864470
So are the installs completely silent?  Is there any need for user input?  In general legacy apps work fine, never had an issue with them personally, you may want to check the C:\Windows\System32\CCM\Execmgr.log for the installation and see exactly what commands are running.

I have had problems with applications that call another application, basically you execute a file which than calls another executable before exiting, since SMS is only looking for the first call(exe) it shows it's been launched successful, however the second file launches but under the users context and than fails, this won't be shown inside the logs.  Have found this especially with Installshield Setup.exe which can call ISScript.msi prior to calling the main MSI file.

Cheers
0
 
LVL 8

Accepted Solution

by:
oldhammbc earned 0 total points
ID: 21905588
We have managed to fix it.  The problem was that all the packages had been moved to a cluster share which as it turns out did not have Kerberos authentication enabled.  We have now enabled this and everything seems to work fine.
0
 
LVL 8

Author Comment

by:oldhammbc
ID: 22633673
We have managed to fix it.  The problem was that all the packages had been moved to a cluster share which as it turns out did not have Kerberos authentication enabled.  We have now enabled this and everything seems to work fine.
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Problem Description: Actually I found the below issue with some customers after migration from SMS 2003 to SCCM 2007 and epically if they change site code, some clients may appear in the console with old site code, plus old sites still appearing …
Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration. My first tip is around source server preparation. No migration is an easy migration, there is a…
The video will let you know the exact process to import OST/PST files to the cloud based Office 365 mailboxes. Using Kernel Import PST to Office 365 tool, one can quickly import numerous OST/PST files to Office 365. Besides this, the tool also comes…
Watch the video to know how one can repair corrupt Exchange OST file effortlessly and convert OST emails to MS Outlook PST file format by using Kernel for OST to PST converter tool. It can convert OST to MSG, MBOX, EML to access them. It can migrate…

606 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question