Jump to content

prathapml

Patron
  • Posts

    6,616
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    India

Posts posted by prathapml

  1. Is there any way to run Windows SIM where you give it the Vista product CD and an Unattend.xml file, <without> a machine image, and edit/validate the file?
    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. Just wondering if the methods listed on the first page work with Vista?
    Yes indeed, same methods for XP,2k3,vista.
    v4.45b of 7zip works fine to extract the updates.
    Winrar has been correctly extracting MS hotfixes since a long time - its just a self-extracting .CAB archive!
    I have the PROHYBRIDR version of Office 2007 and I need to install various product keys in various computers.

    But I have some questions:

    - Can I specify the path where the users save all the documents made with Office 2007 by default, like the ork 2003 do.

    - I need to make a visual basic script to run the silent installation, introducing each product key by computer.

    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.

    What I would like to be able to do is have a preinstall done (I build computers) for my customers and when you first start an office app it will ask for the serial.
    There's a very simple way to do this:

    1. First use a key to install.

    2. After install, delete this registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0\Registration (on XP & vista 32-bit)

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\12.0\Registration (on XP & vista 64-bit)

    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. 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.

  5. I have tried to integrate SP2 in WinXP x64 Trial and Win Server 2003 SP1 + R2

    But Integration is failed everytime and display message Ur Soruce Copy is Trail Can't possible.

    how slipstream in Trail copy...........?????????????????????

    If it says cant be slipstreamed into a trial copy, then thats probably what it means.....
  6. 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.

    If nuhi could provide a possibility to pause the installation for users to add the updates manually to the image, then that would be a big help I think.
    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....
  7. @spacesurfer

    Perfect! :thumbup

    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!

  8. As I have posted above,:

    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:

    Description: It is impossible to install 2007 Office release without running setup.exe.
  9. how to slipstream patches to office 2007 enterprise?
    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.

  10. Thank you cdob ! :thumbup

    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) :P

  11. I did answer it above :)

    ..... "The Setup configuration file config.xml is not valid. Run Setup again without using a Setup configuration file, or fix the configuration file."

    There is no configuration file in the Setup folders...

    Even VL editions of Office do have (and need) a config.xml

    It 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>

×
×
  • Create New...