Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

  • Country


Everything posted by prathapml

  1. Yes indeed, you can do that, the same procedure works for all editions of Vista.Just to refresh my own memory, here's what I did: 1. Ran WSIM. 2. Inside WSIM, first load a *.WIM file (you'll find one on the vista disc, inside "sources" folder, named "install.wim") 3. After step2, WSIM will tell you that it wants to create a catalog file, allow it (this catalog file is not needed for anything else, so you can delete the newly created catalog when your XML is ready). 4. For step3 to succeed, you should preferably copy the *.WIM file to hard-disk, and then use it within WSIM. 5. Second, open your existing unattend.xml 6. Make changes as you see fit & save the xml. 7. If you just want to use these customizations directly (without any further action from BDD), then simply name this new file as "autounattend.xml" and place it in the root folder of your disc (that is, make an ISO image of your vista disc to ensure it stays bootable, open it in UltraISO, add the XML file, no other files need to be added or removed, now save the ISO image, burn it to disc). 8. Please note that WSIM might still fail to check a few errors, despite its validation logic. So you'd probably need 5 or 6 trial runs (of installing vista unattended) to iron out the unattended/automated installation and make it exactly the way you want it. As you'd know, describing all this makes it sound tedious, but its pretty quick actually, hoping this helps. Please do post back here, to let us know whether it worked or not.
  2. Yes indeed, same methods for XP,2k3,vista. Winrar has been correctly extracting MS hotfixes since a long time - its just a self-extracting .CAB archive! I've never heard of a PROHYBRID version of office.Yes you can specify the default-save-path for documents, it can be done when you're preparing your MSP file. As for the VBscript, you might need to make it yourself, as per your customized needs. There's a very simple way to do this:1. First use a key to install. 2. After install, delete this registry key: 3. You can do the above 2 steps in the normal way, or you can automate both of the above (to do it unattended).4. Thats all.
  3. Well, that'd be interesting! Please upload to a free hosting site (rapidshare, etc) and post link to it here. Preferably, it'll be an extractable file, and a batch-file inside it that would help us to know exactly what switches & operations it carries out.
  4. I think this used to happen with XP. WINNTBBA.DLL and WINNTBBU.DLL from I386 were the 2 files that would contain the strings & resources, that were used from setup.exe & boot-setup respectively? Just thought this piece of info might help to find a solution.
  5. No, its not strictly violating rules. His method explains how to make vista-setup think its a Business Edition & hence allows you to upgrade to ultimate.
  6. If its vista 32-bit, I might recommend this topic for reference - http://www.msfn.org/board/index.php?showtopic=90286 Place the autounattend.xml either at the root of your dvd or at the root of your USB drive. nVidia drivers aren't being automatically installed, because (as always) setup gives priority to WHQL signed drivers - and none of the nVidia-Vista drivers have the signature, except for the ones already contained on the dvd as part of Vista's own driver-set.
  7. The xml in first post is for 32-bit only. The x64 will be similar but processorArchitecture & publicKeyToken might change.
  8. If it says cant be slipstreamed into a trial copy, then thats probably what it means.....
  9. True, and betas (or test builds) will start coming out in a month.
  10. SP1 is coming quite soon now. In another month, you'll start having beta builds of SP1, which you'll then be able to integrate into base image.
  11. pkgmgr.exe (x86, version 6.0.6000.16386, 137 KB, use winrar to extract) download - http://www.mytempdir.com/1285147 spacesurfer- Thats right, i ran this command in an admin-elevated CMD window on an already-running vista ulti x86 OS. And the command + syntax seem to be perfect, i did not need to make any changes at all. (note: for some strange reason though, the cab gets extracted in the same directory as the CAB, instead of the C:\sandbox ) About integrating, i havent looked into it yet, but personally i'd rather not integrate beta versions (eg: dreamscene) into a production image. Actually, you could let vLite do its job & then add the updates manually. Or you could add in the updates & then customise down your *.WIM with vLite....
  12. @spacesurfer Perfect! Tried the above with a cab of hold-em poker, it works! Finally..... there is a proper way to get the ultimate extras installed without downloading it afresh each time u re-format! For silently installing msu, WUSA would do it. And now, a 137 KB pkgmgr.exe from WAIK does the trick for CABs! And yes, you can get the CAB from %systemroot%\SoftwareDistribution\Download - take the file before you format & then use it later!
  13. You can get a full list from - http://www.msfn.org/board/index.php?showtopic=92263
  14. war59312 has been doing a great job here - http://www.msfn.org/board/index.php?showtopic=92263
  15. For example, the PDF+XPS addin comes as an exe, it installs automatically from Updates folder. And the hotfixes & Service-Packs for o2k7 will come as an exe, which can be extracted to obtain the MSP....
  16. You dont need to find out, when a direct link to the cab-file is posted a few posts above What remains to be seen, is how to install it.
  17. Just download the update file (exe or MSP), and put it in the "Updates" folder, in the same way that you put your CUSTOM.MSP file in there for customizing setup!That way, setup will automatically install all updates it finds, when installing office. There is no other way to directly integrate files into office-2007, that i'm aware of.
  18. Thank you cdob ! I had same problem too (WinXP 64-bit SP2), now it works gsar -o -s:x46:xda:x74:x03 -r:x46:xda:xEB:x1A setupldr.bin But because of the folder structure (or god knows what), i still get a different error message after load, saying txtsetup.sif corrupted or missing, but thats easier & i think i know the reason, so can be fixed by me (i hope)
  19. thank you, updated as per your last post hmm, that'd be great.How can it be installed directly from cab? Any commands or tools to install it on vista ultimate?
  20. I did answer it above 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. Just save this as config.xml (that is if you're using Enterprise Edition, and you can modify them if needed, and if you modify it then remember to remove the comments just like how it is in Option-B-Post #2 in this topic): <Configuration Product="Enterprise"> <!-- <Display Level="full" CompletionNotice="yes" SuppressModal="no" AcceptEula="no" /> --> <!-- <Logging Type="standard" Path="%temp%" Template="Microsoft Office Enterprise Setup(*).txt" /> --> <!-- <PIDKEY Value="BCDFGHJKMPQRTVWXY2346789B" /> --> <!-- <USERNAME Value="Customer" /> --> <!-- <COMPANYNAME Value="MyCompany" /> --> <!-- <INSTALLLOCATION Value="%programfiles%\Microsoft Office" /> --> <!-- <LIS CACHEACTION="CacheOnly" /> --> <!-- <SOURCELIST Value="\\server1\share\Office12;\\server2\share\Office12" /> --> <!-- <DistributionPoint Location="\\server\share\Office12" /> --> <!-- <OptionState Id="OptionID" State="absent" Children="force" /> --> <!-- <Setting Id="Reboot" Value="IfNeeded" /> --> <!-- <Command Path="msiexec.exe" Args="/i \\server\share\my.msi" QuietArg="/q" ChainPosition="after" Execute="install" /> --> </Configuration>
  21. Hi jcarle, thank you for this information I do know that the intention was to prevent having to repeatedly enter in the same details when you install office 2007. I dont mean to hijack this topic, but for the sake of sharing info - if further info is needed on deploying office 2007 unattended, then do take a look at - http://www.msfn.org/board/index.php?showtopic=72392
  22. 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.
  23. 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

  • Create New...