Re: SOS ! - Workgroup clients - MSI Packages - Error 1619

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Shehzad Khoja [MSFT] (srkhoja_at_online.microsoft.com)
Date: 01/31/05 

Date: Mon, 31 Jan 2005 13:19:08 -0800

1 - Have you specified network access account? Is that not working?
2 - In some cases (if you share ExecMgr.log I can confirm) you will have to
put \\%SRV_SITE%\Sources\SETUP-Microsoft_Visio_Viewer_2002 (without
environment variable) as program's startin directory.

Hope this helps. 

-- 
This posting is provided "AS IS" with no warranties, and confers no rights.
"DC" <DC@discussions.microsoft.com> wrote in message 
news:BB3A0D78-37CF-4E4A-9674-1584D29F7500@microsoft.com...
> Hello,
>
> Here is the situation I face :
>
> My client uses a single SMS site server which assumes all roles (MP, DP, 
> RP,
> SLP) in the architecture.
>
> His central site is managed by an Active Directory.
> He has 50 distant sites where clients are members of workgroups (1 per
> distant site).
>
> Each client computer holds a system variable calles SRV_SITE which set the
> netbios name of machine that contain software sources.
> Each workgroup has its own SRV_SITE (site server).
> This machine is typically a Windows 2000 workstation and each of them has
> the same share. Synchronisation between main sources and distant copies is 
> in
> place. So the client wishes to keep this mecanism BUT he does not want to
> install and SMS distribution point at each location.
> This means that the SMSPKGD$ folder will not contain the Windows Installer
> software sources.
> At least the installation command which could be :
>
> msiexec.exe /i
> \\%SRV_SITE%\Sources\SETUP-Microsoft_Visio_Viewer_2002\vviewer.msi /qb!
>
> This type of command work perfectly fine on domain clients but it fails on
> workgroup ones.
> The program assignment is well sent to the SMS workgroup clients, well
> started but the Windows Installer error 1619 is returned. I know that this 
> is
> due the "NT AUTHORITY\System" context in which packages are executed.
>
> Here is how a standard package is configured :
>
> SMS Server name : SMS2003
> Packages share : Packages$
>
> Example : Visio viewer 2002 (Windows Installer based installation)
>
> Data source : none
> Access accounts : none except generic Admins, users and guests
> Distribution points : none
>
> General tab :
> Program name : Installation
> Program command line :
> \\SMS2003\Packages$\Commandes\SETUP-Microsoft_Visio_Viewer_2002\install.cmd
> Content of install.cmd file : msiexec.exe /i
> \\SMS2003\Packages$\Sources\SRC-Microsoft_Visio_Viewer_2002\vviewer.msi 
> /L*
> C:\VVIEWER.LOG ACCEPTEULA=1 /qb!
> Startup folder : none
> Execution: normal/standard
>
> Environment tab :
> Execution mode 1 : whether a user is logged or not
> Execution mode 2 : Execute with administration rights AND grant users to
> interact with program
>
>
> That's all for the program. Assignment is totally standard.
>
> I have also published the command line (CMD.EXE) to workgroup clients in
> order to act as NT AUTHORITY\System.
> I shelled the installation command line and of course it failed. I did the
> same with the RUNAS /NETONLY command and it worked.
> But when I include this sequence in a script it fails.
>
> Coudl anyone provide me help because I want to keep the Windows Installer
> products sources on the SRV_SITE machines ?
>
> Thanks in advance for your help.
>
> Best regards,
>
> David Chatel
> France
>

Relevant Pages

  • SOS ! - Workgroup clients - MSI Packages - Error 1619
    ... My client uses a single SMS site server which assumes all roles (MP, DP, RP, ... This means that the SMSPKGD$ folder will not contain the Windows Installer ... This type of command work perfectly fine on domain clients but it fails on ...
    (microsoft.public.sms.swdist)
  • Re: MS04-025 Error
    ... Your clients must have access to the distribution point. ... but the execution cannot begin because either the files are missing ... >> file not listed in the command line which earlier i have browsed. ...
    (microsoft.public.sms.swdist)
  • Re: Vista - User Directory
    ... installer, and parts of the code are not compiled in, e.g., #ifndef DEMO_VERSION allows ... Fundamentally, software-only schemes are ... most of my consulting clients are small companies. ... triggering the UAC. ...
    (microsoft.public.vc.mfc)
  • Re: [opensuse] Post installation queries (FIRST successful installation of Linux)
    ... way to manage users on opensuse is with yast. ... You use the 'passwd' command to change the passwords from the command line. ... By default, if you su to root, you can change/reset any user password simply ... the installer do that to me, so others will need to chime in on how to fix ...
    (SuSE)
  • Re: XNews using hugh amounts of CPU
    ... If Yottanews is anything like his beta service ... Support with regards to Yottanews beta server. ... I would like to test it with as many clients as possible. ... non-standard command it will just disconnect you. ...
    (news.software.readers)