You can also try http://wpkg.org/files/client/beta/1.3.14/ -
although there were almost no changes in machine account handling code.
I will do that for sure. I would like to clarify - do I have to make
the trasform with the Properties table additional record, pointing to
settings.xml
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 work, but I
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 Windows 2000 domain (no
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.
I will do that for sure. I would like to clarify - do I have to make the
trasform with the Properties table additional
On 27.02.2010 10:45, Rainer Meier wrote:
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.
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 Windows 2000
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
download beta-client, as the server
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 fine for me from
several IPs around the world.
Vasaris wrote:
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
download beta-client, as
I can confirm that the download works okay from Australia.
In terms of software deployment we'd love to stick to simply deploying msi
packages using group policy but this just isn't a practical position for
most of us. Given the variety of software delivery options employed by
vendors we looked
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 fine for me from
several IPs around the
Vasaris wrote:
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 fine for me from
several IPs around
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
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 package defined (including WPKG Client), it will install WPK
Client.
OK. I understood.
Hi Tomasz,
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 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 client
On 27.02.2010 19:43, Vasaris wrote:
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
-Original Message-
From: wpkg-users-boun...@lists.wpkg.org [mailto:wpkg-users-
boun...@lists.wpkg.org] On Behalf Of Vasaris
Sent: Saturday, February 27, 2010 3:54 AM
To: Rainer Meier
Cc: wpkg-users@lists.wpkg.org
Subject: Re: [wpkg-users] WPKG client service script error on clean
Hi Vasaris,
On 27.02.2010 19:43, Vasaris wrote:
The only problem I have now, that I cannot disable WSH Success Audit
entries in the Windows Application Log. It fills everything up. I have
cheched everywhere, and it seems, that there is no any /debug /verbose
parameters anywhere, and
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.3.9 client,
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 -
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 as follows:
I hope you also imported the configuration
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 as follows:
I hope you also
On 26.02.2010 18:15, Rainer Meier wrote:
(...)
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
24 matches
Mail list logo
