prathapml

You ran office2007 setup on vista silently? Was it before first-logon by any chance? That can lead to vista discarding the registry entries made by o2k7 setup, leading to this problem.I run o2k7 setup thru <SynchronousCommand> during the <oobeSystem> pass, which is working properly. Interesting! I wonder if removing the 'r' suffix & copying an \admin folder over, will allow it to work ? You must set the DisplayLevel to "none" - either thru the MSP or thru the xml. That must be because the Configuration-Product needs to be changed. The attached xml in Option-B is an example, you must compare it to your edition of office & modify accordingly. Even VL editions of Office do have (and need) a config.xmlIt might be needed to copy over that file from your CD. (or re-download from MVLS, etc) It looks like this is the only problem, so having a valid config.xml should fix it. Ah, thanks for the info, enables me to understand whats happening here. Basically, when displaylevel was none, your setup was launching, finding an invalid key, & failed silently. When you changed it to full, you were asked for a key, to be able to proceed. So therefore, you havent done anything wrong, its working as expected - the only hitch is, you forgot the part where I say replace this with your own, actual key. So just insert your key (without the dashes, according to example shown in Option-B ) and it should work.

I can confirm that it definitely works.The above problem could be due to WindowsInstaller (MSI v3.1) being corrupted - removing & reinstalling it, & also, try using only /config or /adminfile. Also, you seem to have a two-in-one, of Office 2007 standard and professional. Preferably, it must be separated - make a copy & one of the *.WW folders. If its not in %temp% then it extracts somewhere else (must be a location on C: drive). And even if the MSP doesnt work, the config.xml method will definitely work for every edition of office 2007. You can use both, the xml, & the MSP - this will give you the desired result of removing the old office versions (MSP does this) & applying further customizations (xml).Preferably, drop the MSP into "Updates" folder & then set the GP to use "/config" switch for the xml (because using BOTH /config & /adminfile, will make the WindowsInstaller get complex with one file being prioritised over the other, etc). Hi JaySwift,I believe using the *.MSI with switches doesnt work anymore - its been blocked, in fact. The SETUP.EXE file is run directly, (alongwith the barely 2 or 3 switches that you can apply to it at install-time) The setup.exe handles installation at run-time, the customizations are thru MSP, & setup-properties can be inserted thru the config.xml. Here's an excerpt from documentation LINK: Do post again to let us know how its goes, or if it gives you any further issues. We'd like to share info about what doesnt work & find out if solutions are working

No offence meant, but jcarle says exactly what my first-post says. You could follow what he says and then read this thread for further details & fine-tuning. He definitely discovered the Option-A method by himself, he has a good way of working out solutions & tools.

@boooggy: are there enough ppl asking for x64 wmp11 integration now?

Hi boooggy, For WinXP 32-bit, your wmp11 vanilla addon pack works perfectly. May i ask if you have plans of supporting XP-64 bit edition ? I have WinXP x64, with SP2 slipstreamed. wmp11-x64 - LINK | details SP2 for XP-64 - details

it gets curioser & curiouser!

http://www.msfn.org/board/lofiversion/index.php/t75486.html While looking thru a recent XPSP2 home-retail Windows CD, I noticed that its DRIVER.CAB filesize was different from the original (RTM, SP0). So then I compared an SP0+SP2 slip-streamed disc, and a new disc that comes with SP2 out-of-the-box. slip-streamed : 73.1 MB new retail disc: 60.1 MB The SP2.cab & drvindex.inf filesize remains same on both. Moreover, when doing a folder-compare, the new retail XPSP2 disc was missing a *LOT* files! But it still installs fine & seems to be normal in operation. Could this be because the files that are updated in SP2.cab have been removed from DRIVER.CAB in the newer discs? Am not quite believing that as a possible reason, would like to see if this is normal, and whether the same happens on VLK (corp) discs too. What is the filesize of YOUR driver.cab ? Why is this size-difference happening?

I use the sample autounattend.xml in first post & the regtweak posted above, & i never get prompted for the network-location

Interesting, gotta keep an eye on this! Thank you

http://www.microsoft.com/technet/windowsserver/sp2.mspx Now that service pack 2 for Windows XP x64 edition is out (downloadable from above page officially), there's 2 questions: 1. If someone knows it, please post the MD5 hash of XP64-SP2 & Svr2k3-SP2. 2. Also, since i'll be using the "/integrate:" command, and there'll now be an extra SP2.CAB (addition to DRIVER.CAB), please post a batch file to merge the 2 cabs together, in the way that nLite does it. Or does nLite already do this reliably for x64?

to make ff run using default profile in its self-contained folder in ProgramFiles (instead of %appdata%), run this command: firefox.exe -profile defaults\profile Then install all the plugins, make all the customizations you want. Then pack it into any compressor or installer you want.... Atleast, thats what I do.

Plus..... You probably are wasting your time (& disk space) by integrating all of it manually. http://www.ryanvm.net/msfn/updatepack.html

Cluberti, thank you for that list! I was searching since the last few minutes for a quick at-a-glance summary of whats new (of course, hotfixes are in, but wanted to know what else...)

Hmm, do you mean this page comes up before first login, or after u login? And the above is superb then, i'd like to know about these please: when do u apply your reg settings - if u apply it before first-login, then how do u apply it? (and thru which pass?) how to integrate updates into source?

I'm back - found this about system-variable folders on vista & how they correspond to XP (it may not be much, but its notable because it gives quite a bit of info on the topic, on one page) - on link below http://trustedaccess.info/blogs/travelling...orn-Server.aspx And how to install *.MSU updates for vista silently - http://trustedaccess.info/blogs/travelling...s-silently.aspx hi maverick, below helps? ; Set the Network Location ;00000000 = Home/Work; 00000001 = Public [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\CurrentVersion\NetworkList\Signatures\FirstNetwork] "Category"=dword:00000000

incidentally, i have found the ping for n seconds + mode con command to be useful on vista, for a different purpose - and i'd like to thank gunsmokingman

Hi war59312, you are welcome (for taking charge of updates on this thread). And my inbox, hmm gotta save many of the old PM there to my HDD first... Do mail me (i think the board allows it thru "mail this user" or something like that).

Please quote only the section that you'd be referring to - pls dont quote an entire huge post......And which method do you follow? As the first post says:

I put my installers into the $OEM$ tree. And then run them thru "RunSynchronous" tag, as illustrated in the sample, after enabling auto-login once after first-boot for an admin user (note that during this first autologin, when runsynchronous commands are running, UAC isnt yet active so it all proceeds smoothly).

In vista, open CMD. type SETThe resulting output will give you all the variables that exist. There arent any extra ones.

Looks like i'm not so scared of the "UseConfigSetRoot" tag now anymore. Because i do end up using it anyways, for the sake of running automated scripts after copying files over to HDD using the $OEM$ folder path (which needs above tag). So i just delete %configsetroot% folder now at the end of my scripts. (for those who havent already read about this in the beginning of this topic, u need to use the UseConfigSetRoot tag in your xml, if u want to use the $OEM$ tree. And u can specify %configsetroot%\drivers, in your xml, to get Setup to pick up drivers automatically from dvdroot\drivers folder. I was afraid to use this feature since the entire dvd would get copied - but then realised it would get copied anyways, for the purpose i'm looking at, so cant avoid the copying of that folder) Now my recent discovery, is that i dont need to bother with the unattend.xml to set a directory to pickup drivers from! Because i can simply drop my PnPdrvrs folder into the "$OEM$\$$\inf" folder on dvd, & since its part of the DevicePath & vista searches recursively, the drivers will be installed automatically at bootup, provided your drivers are signed/WHQL. Wondering if this will work for XP too. Not quite sure if the above even makes sense at all to a beginner, but those of you who've been looking for a straight-forward way for this, might find it useful. If you want clarifications, just ask!

for me, even with drivers, the same thing happens. On my crt & LCD, & with vLite as well as nLite. A quick look thru Appearance, Effects tab hasnt changed it much yet. Still checking to see if any registry key gets set (or prevented from being set) during lite install.

leave out the topics for now. Follow the guide. If its difficult to follow the guide, then its not going to be easy to follow what someone else is saying either - unless u r simply leaving the task to them completely - by giving a list of your needs & taking the finished product.

And also, there is a guide, to help in auto-install - http://unattended.msfn.org/

I get same error with Office 2007. Remove windows installer 3.1, & reboot & then install the Windows Installer 3.1 v2.