Hello,
For the start let me thank the developers and maintainers of this project,
as it is very usefull. I am newbie here, therefore pardon for my incompetence.
I have started depolyment of WPKG from scratch. If I understand correctlly,
there are two separate modes of the execution - serve
Hi Rainer,
> Hi Vasaris,
>
> On 26.02.2010 16:51, Vasaris wrote:
> >After this, I uploaded settings.xml file to the target workstation,
> > which I have preprared and exported from the additional workstation, where
> > WPKG client was installed manually. It is
>> I see you're not using a path-user setting but instead the machine account. I
>> personally never tried it but remember that there were some discussions that
>> in
>> certain cases it does not work properly. Tomasz can comment on this, he
>> knows by
>> heart I think.
>
> This should generally
Hi
> Hi,
>
> >> Andrew: I assume the client was joined to the domain?
> >
> > Yes it is. It is Windows 2000 native domain.
>
> Hmm, maybe this points us to the problem. As Tomasz said the machine account
> authentication is not working well with Samba domain controllers. Samba is
> emulating a
Hi,
> On 27.02.2010 09:41, Vasaris wrote:
>
> >> You can also try http://wpkg.org/files/client/beta/1.3.14/ - although
> >> there were almost no changes in machine account handling code.
Sorry, but the server is now experiencing some sort of problems. I cannot
down
> I try join windows xp to domain with netdom.exe. When I run package I get
> error: "Multiple connection...".
> Is someone who tried to join windows to a domain and can help me?
Simple - try another user account with administrative privileges in the domain.
This is known Windows XP problem. For
> Vasaris wrote:
>
> > P.S. I cannot download beta from http://wpkg.org/files/client/beta/1.3.14/.
> > Server is malfunctioning - drops connections, does not send the whole file
> > (only few tens of Kb).
>
> You sure the problem is not on your end? It works f
> Again, works here - most likely a problem on your side.
> But someone else could recommend if it works for them or not.
Would be nice. I tried visual traceroute to wpkg.org server, it seems, that
there is are no problems. Therefore maybe only my route is bad.
> > Sorry, but I do not know whats
Hi,
One question more question. For now in Windows AD Software deployment, one
can define MSI package deployment, based on computer accounts membership in
certain security groups.
WPKG uses computers lists, packages list and etc. Is it possible to use AD
security group membership inform
> Vasaris wrote:
>
> >>> I would rather stick to MSI packages, as they allow seemless upgrade,
> >>> when new version is out. If it is not possible, I think, that server-mode
> >>> deployment is better then.
> >> If you have "wpkg" p
Thanks for explanation. It prety sums up everything.
> There is a patch attached to some Bugzilla entry adding AD-Integration to
> wpkg.js. However it never made its way into the official wpkg.js yet. I
> planned
> to integrate such support into a future release of WPKG but I did not have
> time
> On 27.02.2010 14:14, Tomasz Chmielewski wrote:
> > No, one folder is enough.
> > If WPKG Client is already installed, wpkg.js will just skip its
> > installation.
>
> Just as an additional clarification: Make sure WPKG client is assigned to each
> profile - else WPKG will try to remove the WPKG
> On the other side if there is no AD support this will just enforce admins to
> duplicate some information which is supposed to be quite static. So the
> drawbacks seem not to be a no-go criteria to me.
>
> However with an architectural change I would like to achieve certain
> decoupling
> betwe
> > Heh, now I have a joke. After unsuccessfull first deployment of 1.3.9
> > client, I have tried 1.3.14 beta (I finaly was able to download it via 3rd
> > provider). It did not worked. Everything was failed here:
> > http://bugzilla.wpkg.org/show_bug.cgi?id=182.
> >
> > And now, back to the 1.
> > I have deployed WPKG client on the other workstation. Depolyment went well,
> > no errors. And it does not have WSH "success audit" entries overfill. Maybe
> > you know whats is the problem here, and in such case may you please give me
> > some hint how to disable this behaviour? :-)
>
> Un
Hi,
Now after some time, I would like to report some issues:
1. .msiI upgrade scenario does not work in Active Directory environment
(IntelliMirror). For example .msi package with client 1.3.9 is set to upgrade
to 1.3.14 beta. The upgrade fails, and the screen show "Removing WPKG 1.3.9
> On 02.03.2010 12:25, Vasaris wrote:
>
> > 4. 1.3.14 is broken. It does not reads settings.xml file on the client
> > side. I have custom settings.xml to install on the shutdown instead of the
> > startup, custom messages localizes in Lithuanian - does not work any
> > I beg my pardon, but start it where/under what circumstances?
>
> Double click on wpkginst.exe in %PROGRAMFILES%wpkg - it will launch a setting
> window.
Do I have to do that on the client workstation, experiencing issues?
> Sorry, can't help you here, I never transformed a msi file as it's
> On 02.03.2010 13:54, Vasaris wrote:
> >> Double click on wpkginst.exe in %PROGRAMFILES%wpkg - it will launch a
> >> setting window.
> >
> > Do I have to do that on the client workstation, experiencing issues?
>
> Well, yes.
I did so. The settings, which
> Subscribe to wpkg-announce list, you will be notified of any stable releases.
Thanks, I will do that.
> > Do you mean, that 1.3.14 => 1.3.14+ upgrade will be fixed? Or from
> > pre-1.3.14 => 1.3.14?
>
> 1.3.14 => 1.3.14+.
OK.
> pre-1.3.14 => 1.3.14 will still work in most cases, but you'
> > You mean, to test out? I would gladly help, because I am interested in
> > support of AD/GP way of the WPKG service-client deployment.
>
> Sponsor, like in $$$.
Depends how much? ;-)
> Or donate your time and write a fix yourself.
as .msi file is built every time, I have to know, what tool
put the wrong path. Does that means, that the client is left in the unsupported
state, until is logged on by admin and fixed bad config by hand? Or special
script has to be made, to re-deploy on-top?
>
> More or less (or use psexec, or winexe).
> Same if i.e. you deploy a workstation, but it was
> On 02.03.2010 16:47, Vasaris wrote:
> > put the wrong path. Does that means, that the client is left in the
> > unsupported state, until is logged on by admin and fixed bad config by
> > hand? Or special script has to be made, to re-deploy on-top?
>
> So how do
23 matches
Mail list logo
