Client Push Installation

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

Client Push Installation - MSI error

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager >> Client Push Installation - MSI error

Page: [1]

Message

<< Older Topic Newer Topic >>

Client Push Installation - MSI error - 8/15/2008 9:52:07 AM

clb@pwc.dk

Posts: 1
Score: 0
Joined: 8/15/2008
Status: offline

Hope someone can help me with this nasty problem. Have used many hours trying to resolve it.

What:
ccmsetup.exe distributed via SCCM fails on some PC's with MSI-log error 1603 & 1708

Funtion in SCCM:
Client Push Installation

Exact error:
MSI (s) (7C:40) [09:50:27:312]: Note: 1: 1708
MSI (s) (7C:40) [09:50:27:312]: Product: Configuration Manager Client -- Installation operation failed.
MSI (s) (7C:40) [09:50:27:328]: Cleaning up uninstalled install packages, if any exist
MSI (s) (7C:40) [09:50:27:328]: MainEngineThread is returning 1603
Where: On Windows XP SP2

On-line article:
http://support.microsoft.com/kb/834484/en-us

I suspect a permission issue because WindowsUpdate.log request a administrator to log on. I have verified the resolution description in KB834484, but it do not change anything:

Windowsupdate.log="AutomaticUpdates Success Content Install Installation Ready: The following updates are downloaded and ready for installation. To install the updates, an administrator should log on to this computer and Windows will prompt with further instructions: - Configuration Manager Client Installation"

Post #: 1

RE: Client Push Installation - MSI error - 8/15/2008 5:26:49 PM

nrunge

Posts: 56
Score: 0
Joined: 5/20/2008
Status: offline

Does the client meet the prerequisites?

- XPSP2
-Firewall Off
-Windows File Sharing Installed

To be honest we had enough problems with clients being installed via SCCM that we deliver it though GPO when a new user logs on. It is much more consistent and takes strain off of our SCCM servers trying to install clients all the time.

< Message edited by nrunge -- 8/15/2008 5:34:01 PM >

(in reply to clb@pwc.dk)

Post #: 2

RE: Client Push Installation - MSI error - 8/21/2008 9:28:05 PM

hcortez463

Posts: 780
Score: 62
Joined: 4/8/2005
Status: offline

how are you deploying these clients.. have you checked ccmsetup.log

_____________________________

If it Helps, Please rate....

(in reply to nrunge)

Post #: 3

RE: Client Push Installation - MSI error - 8/22/2008 10:04:12 AM

nbarker

Posts: 2
Score: 0
Joined: 6/5/2008
Status: offline

Hi

I have recently deployed the SCCM 2007 SP1 client, using Client Push, to around 6,000 machines. Around 200 failed. I have managed to fix just about all of them using one of several methods (in the end I was heavy-handed and created a script that ran all the fixes, knowing one or the other would resolve the issue, and ran the script locally).

Background
SMS 2003 SP3 in a Single Site.
Vast majority of clients were XP SP2 and Server '03 SP1 or SP2 (some 64-bit), with a small number of W2K.
Did an in-place upgrade (this failed but that is another issue).
AD integration configured.
SCCM Group Policy templates installed and settings configured for Site Assignment and Client Deployment Settings.

Fixes
WMI fix - Stop WMI and dependent services, delete \\..\system32\wbem\Repository folder and all its contents.

ATL fix - run Regsvr32 atl.dll - this was the most common fix for the dreaded 1603 error.

CCMClean - Run ccmclean and install the SCCM client - some failed Client Push installations did not rollback properly and basically left the old SMS installation in a mess.

DCOM fix - Start-Run-DCOMCNFG. Access Component Services-Computer-My Computer-Properties-Default Properties. Ensure that Authentication Level = Conect and Impersonation Level = Identity.

64-Bit Fix - The SCCM GP templates do not apply the settings correctly to 64-bit machines (in the Registry they can be seen under the HKLM\Software\Microsoft\SMS\Mobile Client - they need to be under HKLM\Software\Wow6432Node\Microsoft\Microsoft\SMS\Mobile Client.

Corrupt SMS ClientIDManagerStartup.log - Corrupt ClientIDManagerStartup.logs that I could not delete or rename. Renamed the Logs folder to LogsOrig.

Other problems speak for themseleves such as unsupported OS (we had a few XP SP1 machines lurking about), machines disconnected from the network, etc.

Hope this helps.

(in reply to clb@pwc.dk)

Post #: 4