Hello, I'm tryin to deploy with GPO the new version but it seems a little bit different than we use to. Has anyone had any success with it?

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

0
The description of your problem is too vague. Does it deploy or not? What does a verbose log tell you?

BTW, you're aware that there's a specific GPO forum here http://www.appdeploy.com/messageboards/tt.asp?forumid=10

0
Bumping an old thread. WLM has fallen in the priority list but with the mandatory upgrade that will come soon, I have to deploy the new version soon.

I grabbed the MSI i got from the downloaded file from the generic Windows Live thing installer.

Verbose logging give me

=== Verbose logging started: 2009-08-31 16:42:10 Build type: SHIP UNICODE 3.01.4000.4039 Calling process: \??\C:\WINDOWS\system32\winlogon.exe ===
MSI (c) (80:6C) [16:42:10:046]: User policy value 'DisableRollback' is 0
MSI (c) (80:6C) [16:42:10:046]: Machine policy value 'DisableRollback' is 0
1: 2905 2: C:\WINDOWS\system32\appmgmt\MACHINE\{bca2b1da-a5e5-483c-a4ee-ea33f7e04941}.aas
MSI (c) (80:6C) [16:42:10:062]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (c) (80:6C) [16:42:10:062]: DoAdvertiseScript is returning: 1603
=== Verbose logging stopped: 2009-08-31 16:42:10 ===

There are a couple other MSI associated with WLM (Live Sign In Assistant and Live Essentials). Those 2 are working when deployed in GPO but the main application (Live Messenger) isnt...

When manually installing with the msi while logged, it's still not working.

0
When manually installing with the msi while logged, it's still not working. !!! Would it be an idea, do you think, to ensure it installs manually before attempting a deployment?

Try to install using an administrator account and log that install. Any error in that scenario will provide clues as to why your deployment is failing.

Having said that, sometimes deployment of packages will install fine manually can still fail, sometimes with very little clue in the log (as you've already seen). In these cases, you *generally* get more meaningful clues from looking at any 'MSInstaller' entries in the Event Log.

0
My previous post looked like a noob post. :D

Installer completed successfully when logged in, but when launching application, it fails. I don't have the exact error message (Working in french) but it says that the application could not be launched because the settings were not set propoerly. I could paste my log file, but I highly doubt it will provide something useful.

What really surprise me, is the so little information I can find about WLM 2009. I guess everyone will wake up when MS pushes its mandatory update in 2 weeks.

0
when launching application, it failsIf I said "ProcMon", would you be able to figure out how best to proceed? :)

0
Yeah, installation now work with the MSI while loggued in. I found out that it requires .net framework 3.5 to work... Damn MS not specifying this anywhere!

Anyway, the installation still not working. It's not even trying in the boot sequence before the Ctrl-Alt-Del. I see the "Installing the software" thing, but for like 0.1 second...

I'll check what I can find with ProcMon.

Thanks.

0
Alright did some test yesterday. Using procmon i was able to see that the machine reads the GPO, but still cannot do anything to even try install the application. Before Ctrl-Alt-Del its not even displaying the application names. It looks to me that it doesnt even try to install.

When I checked the scripts file located in the SYSVOL under Policies/GUID/ the .AAS script file has 0 bytes.

Any other clue? Why it fails to create the script file? Incorrect MSI file format, missing table, value?

0
GP screws you over like that every now and again. What you'll probably also find is that when you run the Deployment Wizard, the report will show the GPO as 'Empty'.

Delete the GPO - not just the link, the entire GPO - and recreate it.

BTW, AppDeploy has a separate GP forum.

0
Finally found a way to make it work. I followed artini advice on the WLM 8 appdeploy page.

2) You need to add a populated AdvtExecuteSequence table to the package. The easiest method is to export the AdvtExecuteSequence table from the sequence.msi sample package included in the Windows Installer SDK. Then use the import table functionality to import the advtExecuteSequence table into the messenger package.

CostInitialize 800
CostFinalize 1000
InstallValidate 1400
InstallInitialize 1500
CreateShortcuts 4500
RegisterClassInfo 4600
RegisterExtensionInfo 4700
RegisterProgIdInfo 4800
RegisterMIMEInfo 4900
PublishComponents 6200
MsiPublishAssemblies 6250
PublishFeatures 6300
PublishProduct 6400
InstallFinalize 6600

Once this package is fixed up, you should be able to add it for deployment (note that you have to fix the package before you configure it for deployment).

Then open Property table and Modify IAGREE to "Yes" then add the following rows:

SETHOMEPAGE = "No-SetMyHomePage"

I didn't have to modify the MsgrFeat located in the Feature table.

Last thing, yes I know I misplaced the topic. Maybe some admin can move it to the proper location?

Thanks

0
Using this method, http://support.microsoft.com/kb/943595/en-us what does config.txt look like for installing Messenger 2009 only? This seems to still install everything:

 p=A26D7C8B-875D-48E2-BED1-7168268D022A*0&s=0&h=0&c=0&m=EN-US&t=0 

wlsetup-all.exe /silent /configfile:"config.txt"

0
I used P=A26D7C8B-875D-48E2-BED1-7168268D022A*0&s=0&h=0&c=0&m=EN-US&t=1 like you inside my config file

"WLSetup.exe" /silent /configfile: "\\path\to\config\file\config.txt"

FYI the wlsetup.exe that you download from that link contains Windows Live Messenger 8 with the newest version of Windows Live Messenger being 14.0.8089.726

1
So you're using the OEM version 8 from here?

http://g.live.com/1rewlive/en/WLSetup.exe

I was going to http://download.live.com/Messenger to download version 14. My old version 8.1.178.0 is not allowed to sign in anymore; that oem ver 8.5.1302.1018 is allowed to sign in. A space before config.txt seems to be mandatory. The /configfile option is ignored with version 14, but the /silent option works. I guess I'll hold off on jumping 6 versions with all its extra baggage for now. :)

0
What I did was download version 14 to my work machine and follow the instructions here http://itninja.com/link/windows-live-essentials-(wave-3)-qfe-2-standalone-messenger-and-other-apps-installers-download-«--my-digital-life so that I could create a deploy package for the rest of the machines using version 14.

1
Found a solution, after much searching, here is the solution. I take no credit for the answer, so here is the link to the original post.

/AppSelect:[ProductID] or ![ProductID]
/log:log_location
/NOToolbarCEIP (to not opt into Toolbar CEIP)
/Nolaunch (blocks all applications from running automatically after your installation is complete)
/NOMU (to opt the computer into Microsoft Update)
/nosearch (to not set search defaults)
/q (for a silent/unattended install)

Here is my command that I use to install:

WLSetup-all.exe /q /NOToolbarCEIP /NOhomepage /Nolaunch /nosearch /AppSelect:Photo,Mail,Messenger

Cheers!

0
Here are the complete list of products to use for the "AppSelect" switch in Windows Live Essentials 2011:
(source: log files)
• companion
• silverlight
• familysafety
• mail
• messenger
• moviemaker (installs the Photo gallery as well!)
• olc
• wlsync
• writer
• bingbar
• idcrl32/idcrl64

Use the command line as shown above.

0
Very nice, thanks, but where do I get the full installation file (wlsetup-all.exe) for Live essentials 2011?

BR Mike

ORIGINAL: hubertlam

Here are the complete list of products to use for the "AppSelect" switch in Windows Live Essentials 2011:
(source: log files)
• companion
• silverlight
• familysafety
• mail
• messenger
• moviemaker (installs the Photo gallery as well!)
• olc
• wlsync
• writer
• bingbar
• idcrl32/idcrl64

Use the command line as shown above.

0
I hope you know that Live Essentials isnt Windows XP compatible. I was able to distribute a working version using the Windows XP release. I ran the Windows Live Messenger installation and extracted the MSI file than I deployed it with GPO. You need 2 package, Windows Live Messenger (of course) and the Windows Live Communication Platform.

Good luck

0
We run windows 7 x64

Also I have tried to use the msi-files collected from Cache-folder during wlsetup-web.exe
but I get a DLL-error message.
So thinking of going with the complete package instead using the switches described above, but can't
get a hold of the file.. :/

2
ORIGINAL: imrumpf

Found a solution, after much searching, here is the solution. I take no credit for the answer, so here is the link to the original post.

/AppSelect:[ProductID] or ![ProductID]
/log:log_location
/NOToolbarCEIP (to not opt into Toolbar CEIP)
/Nolaunch (blocks all applications from running automatically after your installation is complete)
/NOMU (to opt the computer into Microsoft Update)
/nosearch (to not set search defaults)
/q (for a silent/unattended install)

Here is my command that I use to install:

WLSetup-all.exe /q /NOToolbarCEIP /NOhomepage /Nolaunch /nosearch /AppSelect:Photo,Mail,Messenger

Cheers!

This baby works like a charm, only the Messenger and nothing else (just an additional live call shortcut). Only problem is, that this version is not supported anymore. When trying to log in, it requires for new version installation. Such bullshit! I hate live 2011!!!

0
Hmm, I got online with build 14.0.8117.416 (2009 version)

0
That sounds great! Where do I get it?

ORIGINAL: yannara

Hmm, I got online with build 14.0.8117.416 (2009 version)

0
Just google around the web with this version number, you should find it. Some links are forwarding you to 15.xxx build version, and that would be 2011 sucker.

0
Is there any way to do a silent install without a reboot? It's the one managed installation in KACE that is forcing a reboot.

0

0
ORIGINAL: imrumpf

Found a solution, after much searching, here is the solution. I take no credit for the answer, so here is the link to the original post.

/AppSelect:[ProductID] or ![ProductID]
/log:log_location
/NOToolbarCEIP (to not opt into Toolbar CEIP)
/Nolaunch (blocks all applications from running automatically after your installation is complete)
/NOMU (to opt the computer into Microsoft Update)
/nosearch (to not set search defaults)
/q (for a silent/unattended install)

Here is my command that I use to install:

WLSetup-all.exe /q /NOToolbarCEIP /NOhomepage /Nolaunch /nosearch /AppSelect:Photo,Mail,Messenger

Cheers!

Can you make a start-up script with that command, then I can use the scritp to deploy via GPO. But I want the script can check if the product not exist then do installing; otherwise do nothing.
It look like the script which for deploying MS Office 2010, but after modified some lines, mine still not work :(

0