[wpkg-users] WPKG client service script error on clean
mangoo at wpkg.org
Sat Feb 27 13:13:46 CET 2010
>> 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 drops connections right on the beggining of the download, or after some Kb are downloaded. And the download is extremly slow. I think you should check this out.
Again, works here - most likely a problem on your side.
But someone else could recommend if it works for them or not.
> \> > 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 file, or else .msi package install will fail?
>> I think instead of wasting time on creating a transform file (too bad AD does not let you specify MSI parameters)
>> you can just run a AD script:
>> cscript \pathtowpkg.js /install:wpkg
>> Easy enough.
> Sorry, but I do not know whats does this accomplishes? Installs the client? Or runs the WPKG normal cycle?
> 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.
As AD is not able to handle MSI parameters (although it is advertised
that "it handles MSI"), or install exe and such, this was one of
motivations to write WPKG.
From experience, you'll have to decide if you want to use AD to deploy
packages or WPKG.
If you decide to use both, you'll likely to get confused one day, when
WPKG will install some package, then AD will remove it, then WPKG will
install it, and so on.
If you want seamless upgrades using MSI and parameters, Microsoft
recommends you to migrate to SMS.
More information about the wpkg-users