Re: Client fails installation

Thanks for the information..

"Terry Matthews" wrote:

> You'll get a better (and more) response if you post in sms.admin or
> sms.general, sms.installer is actually for a tool called "SMS Installer" a
> repackaging tool.
>
> From looking at your log though everything is the same as mine... creator
> owner and all except the msi error 1729.
>
> From looking on the internet there's a million articles on msi and error and
> 1729.
>
> One is from a guy who says after he upgraded from MSI 2.0 to MSI 3.1 he
> started getting these errors? Have you upgraded versions?
>
> Anyway take a look on the internet see if any of those articles help, then
> post to sms.admin or sms.general.
>
> Good luck,
> Terry
>
>
> "Dean" <Dean@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:6D9AB84C-A7C3-4E8E-B85A-D3D523CAF76D@xxxxxxxxxxxxxxxx
> > Hello All,
> >
> > I am having a problem with clients being installed on both Windows XP SP1a
> > machines and Windows 2000 SP4 machines.
> >
> > The SMS server pushes the client, and appears to work but i get the same
> > error in each machine as shown below:
> >
> > Product: SMS Advanced Client -- Configuration failed.
> >
> > I also get the following information in the client.msi.log file:
> >
> > Property(S):
> > SmsSoftwareDistributionCacheSize.8AE6A59B_5597_4D75_9BFD_7F566BF56500 =
> > 250
> > Property(S): CcmAdministratorsGroupName = Administrators
> > Property(S): CcmUsersGroupName = Users
> > Property(S): CcmCreatorOwnerAccountName = CREATOR OWNER
> > Property(S): PrimaryVolumePath = C:
> > MSI (s) (2C:2C) [11:00:46:100]: Note: 1: 1729
> >
> > It appears to me that the SMS client is trying to be installed by the
> > creator owner but we have used a domain admin account to install the
> > client
> > by default.
> >
> > Any help would be appreciated.
> >
> > Thanks,
> > Dean
>
>
>
.

Relevant Pages

  • RE: Deployment and Setup woes
    ... Windows Installer compares the version of the files, ... see topic File Versioning Rules in the MSI SDK. ... Make sure you always change the PackageCode whenever you rebuild your setup. ... > NOT installed on the client computer, ...
    (microsoft.public.dotnet.framework.setup)
  • RE: Deployment and Setup woes
    ... Windows Installer compares the version of the files, ... see topic File Versioning Rules in the MSI SDK. ... Make sure you always change the PackageCode whenever you rebuild your setup. ... > NOT installed on the client computer, ...
    (microsoft.public.dotnet.languages.vb)
  • RE: Deployment and Setup woes
    ... Windows Installer compares the version of the files, ... see topic File Versioning Rules in the MSI SDK. ... Make sure you always change the PackageCode whenever you rebuild your setup. ... > NOT installed on the client computer, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Windows Installer rerunning client.msi
    ... i wonder if the account logged in while the MSI tries to repair has enough rights to do so? ... ccmexec.exe is the actual sms client binary and not the installer, that would be client.msi or ccmsetup.exe which can be used to invokes it. ...
    (microsoft.public.sms.admin)
  • Re: Client install error
    ... version of Windows Installer. ... I encounter an error upon manual installation of sms client( ... Setup was unable to compile the file SmsClient.mof ...
    (microsoft.public.sms.admin)
Loading