Hi Lukasz,
one way to do this is to keep a testing copy of all WPKG files and setups and
make your test clients use this instead of the production files. This way you
get a completely separate base dir and %SOFTWARE%. You can test different
packages, profiles, to some extent hosts, different
ycdwbycid wrote:
I checked the events log and you might have got me there...
WNetAddConnection2-> A specified logon session does not exist. It may
already have been terminated.
16/10/2009 12:15:18WpkgService Error None1 N/A
ZEUS-DT
WNetAddConnection2-> A specifi
Hi all,
What is the best way to thes updates to the already deployed packages?
We have quite few packages at the top level of profiles hierarchy
(covering nearly all of the machines).
Remving package from there and putting it in the test profile would be
disasterous. What i have been doing so fa
On Wed, 21 Oct 2009 15:43:54 +0100 Hugo Monteiro
wrote:
you could also install like this:
WLSetup.exe /AppSelect:Messenger /q
and WLSetup.exe could be the full offline installer.
HM>
I didn't knew this uninstall possibility,
Thanks!
--
Jean-Jacques Moulis
Jean-Jacques Moulis wrote:
On Wed, 21 Oct 2009 10:26:13 +0100 Hugo Monteiro
wrote:
HM> The procedure starts to install the components, but stops at the
HM> installation of dw20shared.msi, which apparently is the Microsoft
HM> Application Error Reporting Tool.
HM> Can someone shed some ligh
Hello list,
I've tried every way i could find, through google, to install the latest
version of Windows Live Messenger, without luck.
One of the methods i followed was installing the software locally, in
one workstation, and then copying the .msi files found in the .cache
directory. I then tri
