Microsoft Windows Live Messenger 2009

Version: 14
Views: 1.4k  |  Created: 09/07/2009

Average Rating: 0
Windows Live Messenger 2009 has 1 inventory records, 1 Questions, 0 Blogs and 1 links. Please help add to this by sharing more!

Deployment Tips (6)

Most Common Setup Type
Not Determined
Average Package Difficulty Rating
Rated 0 / 5 (Not Rated) based on 0 ratings
Most Commonly Reported Deployment Method
Not Determined
or cancel
5
Command Line
Install complete live suite with the following switches:

- AppSelect:[ProductID] or ![ProductID]
- log:log_location
- NOToolbarCEIP (to not opt into Toolbar CEIP)
- NOhomepage (to not set home page defaults)
- 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)

example would be:
WLSetup-all.exe /q /NOToolbarCEIP /NOhomepage /Nolaunch /nosearch /AppSelect:Photo,Mail,Messenger
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
4
Note

To retrieve Windows Live Messenger 2009's msi, you need to install the component you need (Messenger in this case), unhide all system files and folders and go to %CommonProgramFiles%\Windows Live\.cache\ . There you will be able to find all msi which were installed on your system. Messenger.msi won't work as standalone setup, to run application successfully you will need to install other components, such as contacts.msi, crt.msi etc. depends on system.

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
4
Note
Installing just Messenger.msi & Contacts.msi works for me. To have Messenger appear in add/remove programs:

msiexec /i Messenger.msi ARPSYSTEMCOMPONENT=""

or delete the SystemComponent registry entry under Uninstall.

If you want to hold off upgrading to 14, the oem version 8 still signs in. Link in here: http://support.microsoft.com/kb/943595/en-us
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
2
Note
I'm using a .bat like this:

SET msipath=<path to msi files>
msiexec /i "%msipath%\crt.msi" /qn
ping -n 10 127.0.0.1 >nul 2>&1
REM I use this ping to avoid problems with time
msiexec /i "%msipath%\Contacts.msi" /qn
msiexec /i "%msipath%\SegoeFont.msi" /qn
msiexec /i "%msipath%\wlc.msi" /qn
msiexec /i "%msipath%\RichUpload.msi" /qn
msiexec /i "%msipath%\wllogin.msi" /qn
msiexec /i "%msipath%\WLXSuite.msi" /qn
msiexec /i "%msipath%\choiceguard.msi" /qn
msiexec /i "%msipath%\Messenger.msi" /qn

Is very important the install order of any msi file.
If you want to Uninstall option appears in Control Panel you have to copy de files wlc16D.tmp and cache.ini from one computer to the path %CommonProgramFiles%\Windows Live\.cacheThis bat is working fine for me.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
0
Note
My package is still in final testing, but so far so good.
1. Grab wlsetup-web.exe from Microsoft.

2. Run on on a "junk pc/virtual manchine" and grab the C:\Program Files\Common Files\Windows Live\.cache folder as well as the MSI logs, (MSI logs are good fore reference) after doing an install of MSN/Windows Messenger.

3. The .cache should have a nice cache.INI file describing each folder within and what they are for. Each folder has an MSI. In the end I found that the following were the only MSI's needed: contacts.msi & messenger.MSI. Contacts is the required "backend" and messenger is the MSN application; out of the original 10 MSI's triggered to install by the EXE.

4. Grab the Segeo Fonts from your computer, these are also needed. I deployed these directly as a file along with registry entries to make Segeo immediately active. Alternatively you can use the SegeoFonts.MSI from the .cache folder.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts]
"Segoe UI (TrueType)"="segoeui.ttf"
"Segoe UI Bold (TrueType)"="segoeuib.ttf"
"Segoe UI Italic (TrueType)"="segoeuii.ttf"
"Segoe UI Bold Italic (TrueType)"="segoeuiz.ttf"


5. Next I used an MSI editor to drop the version check from LAUNCHCONDITIONS on Messenger.MSI and dropped the ARPSYSTEMCOMPONENT row under properties on both MSI's so that they will show up in Add/Remove programs.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
-7
Note

If you deploy WLM 2009, you need .net framework 3.5 installed on the computer. If it's not installed, you'll get an error telling that it's not installed properly.

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment

Inventory Records (1)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

Versions

Windows Live Messenger 2009

Version

14

Questions & Answers (1)

Questions & Answers related to Microsoft Windows Live Messenger 2009

27
ANSWERS

Blogs (0)

Blog posts related to Microsoft Windows Live Messenger 2009

Reviews (0)

Reviews related to Microsoft Windows Live Messenger 2009