[wpkg-users] Special install command not working

[Mike Burgener]

I still run in to that issue, however its a newer version of that 
product. all other packages work, tried using cmd /c "echo yes | 
\\whale\wpkgsoftware\arm\ARM_RVDS_40\rvds_4_0_stn_sp2\dist_362_all-all\s
etupcli.exe install  --level "Full" --source 
\\whale\wpkgsoftware\arm\ARM_RVDS_40\rvds_4_0_stn_sp2\dist_362_all-all  
--target "C:\Program Files\ARM" --env system"

Tried putting in a .cmd, .bat not working as well, but running when 
logged in a testmachine in a cmd or via "execute" works.

Any ideas?

> -----Original Message-----
> From: Mike Burgener
> Sent: Freitag, 13. Februar 2009 11:27
> Cc: wpkg-users at lists.wpkg.org
> Subject: Re: [wpkg-users] Special install command not working
> 
> Rainer Meier wrote:
> > Hi Mike,
> >
> > Mike Burgener wrote:
> >> Hmm, it works on a non domain-member machine, so I think it cannot
> be
> >> a permission problem, for me it looks like the installer does not
> get
> >> the "yes" when run by wpkg.
> >
> > Credentials and access rights is not a thing which only
> > exists in domains. Also workgroups and stand-alone machines
> > use credentials. For example if you create a share on XP
> > professional, then you can access the share only if you use
> > the same user on the remote machine (username and password is
> > the same). Actually in such cases the following accounts are 
involved:
> >
> > Machine A (publishing the share):
> > MACHINEA\user (using password X)
> >
> > Machine B (accessing the share):
> > MACHINEB\user (using password X)
> >
> > So if you access the share from machine B then Windows will
> > first try to  use "MACHINEB\user" account. Unfortunately this
> > will not work since it's a local user. Depending on Windows
> > configuration it will then try to use "user" only which
> > succeeds if on machine A there is a user called "user" too.
> >
> > If both fail Windows will also try to use the "Guest" account
> > with no password. Unfortunately this account is disabled by default.
> >
> > You might just try to enable the guest account and allow
> > access to the share by Guest. This case Windows will always
> > succeed to access the share. No matter which local user is
> > currently logged on (SYSTEM in case of WPKG).
> >
> > br,
> > Rainer
> 
> This easier Version of .cmd does not work as well.
> 
> echo yes |
> 
\\server\wpkgsoftware\arm\ARM_RVDS_3.1\Utilities\Installer\2.2\127\win_
> 3
> 2-pentium\wh.exe install  --level "RVCT Only" --source
> \\server\wpkgsoftware\arm\ARM_RVDS_3.1\  --target "C:\Program
> Files\ARM"
> --env system
> regedit /s \\server\wpkgsoftware\registry\license_server_rvds31.reg
> 
> 
> 
-----------------------------------------------------------------------
> --
> wpkg-users mailing list archives >>
> http://lists.wpkg.org/pipermail/wpkg-users/
> _______________________________________________
> wpkg-users mailing list
> wpkg-users at lists.wpkg.org
> http://lists.wpkg.org/mailman/listinfo/wpkg-users