Jump to content

FireGeier

Member
  • Posts

    405
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Germany

Posts posted by FireGeier

  1. Both is working for me. I can install from DVD or USB stick. For the moment I use a stick and that is my prefered method cause it's easier to edit.

    I had problems to get the stick detected in pe pass when setting %DriversRoot% variable to install drivers. This happend cause my cmd that supposed to set the DriversRoot variable was running before the stick was recognized by system completly.

    I could imagine that you have the same kind of issue now just in a later pass... but can't tell you for sure... just thinking

    Regards,

    Martin

    EDIT:

    I've forgot to tell you the solution for my problem:

    I was putting the set command into a loop, so it's trying to set the variable now again and again till the stick is recognized. On my system this solution is causing a delay of about 4 seconds. Others gave me feedback, that they would have a delay between 10 and 15 seconds. So it's very different from system to system how long it takes, till USB stick is mounted.

    You could try to use a FOR loop executing before other applications are installed. May be that will resolve the problem.

    Example:

    cmd /c FOR /L %i IN (1,1,3000) DO ECHO Loop > NUL

    The last value inside brackets marks the end of the loop. As higher the value as longer the loop will run.

  2. Hello turbomcp!

    You need to set the %AppsRoot% variable during specialize pass! Thats is very important!

    If you should still have problems to use %AppsRoot% variable, add cmd /c in front of your command line:

    				<SynchronousCommand wcm:action="add">
    <Order>2</Order>
    <CommandLine>cmd /c %AppsRoot%Install\Java\jre-1_5_0_11-windows-i586-p.exe /s /v/qn</CommandLine>
    </SynchronousCommand>

    Regards,

    Martin

    EDIT:

    Explanation:

    Between specialize pass and oobeSystem pass the system is rebooting, so the system envrionment with environment variables is loaded again and so the added %AppsRoot% variable is present for the session.

    If you put it to the system environment in the same pass, than the environment is not reloaded to the setup process and so the %AppsRoot% variable can't be read even it is set already!

  3. Hello sp00f!

    To do a reboot you need:

    1. Based on my Application guide add the following tow synchronous commands to your xml into sepcialize pass:

    Synchronous Command 1:

    cmd /c "FOR %i IN (C D E F G H I J K L N M O P Q R S T U V W X Y Z) DO IF EXIST %i:\AppsRoot.txt SETX AppsRoot %i: -m"

    This will set the AppsRoot environment variable.

    Synchronous Command 2:

    %WINDIR%\system32\sysprep\sysprep.exe /quiet /audit

    This will boot to audit modes.

    2. Instead of inserting all Synchronous Commands to install the apps to oobeSystem pass - like described in my guide - add them to auditUser pass.

    It's important to start your command line with cmd /c! Otherwise the AppsRoot variable won't work!

    Example:

    Synchronous Command 1:

    cmd /c REGEDIT /S %AppsRoot%\Install\Regtweaks.reg

    Synchronous Command 2:

    cmd /c %AppsRoot%\Install\AcrRead\AcroRead.msi /qb

    Synchronous Command 3:

    cmd /c %AppsRoot%\Install\Firefox\Firefox_Setup_2_0_0_2.exe -ms

    etc.

    Last Synchronous Command:

    %WINDIR%\system32\sysprep\sysprep.exe /quiet /oobe /reboot

    This commands needs to be at last position always and will forward you to oobeSystem pass. Otherwise system would boot in audit mode again and again.

    Once you've insert a Synchronous Command to auditUser pass check out Properties pane in WSIM on the right and you will see, that the Synchronous Command gives you an option to set a value for Restart. Set it on Always, if you want to force a reboot after application was installed.

    3. Add AutoLogon to auditSystem pass

    Add Windows-Shell-Setup \ AutoLogon to auditSystem pass and log on the main Administrator (Administrator). Set LogonCount so that you can do enough reboots you need to do for your apps.

    If you've any further questions you're welcome to ask!

    Regards,

    Martin

    EDIT:

    Sorry... added the wrong final command line you have to use /reboot like it is now instead of /quit like it was before.

  4. @MarcJ and others how are interested:

    Update:

    After doing a lot of further test runs I still can't reproduce the problem you've having with synchronous command - doesn't matter if I use ULTIMATE or BUSINESS.

    But if I do the same app installations with synchronous command in auditUser pass instead of oobeSystem pass, than setups aborts with an error. The %AppsRoot% variable is present in that pass I've checked that using the following synchronous command:

    cmd /c SET > %AppsRoot%test_apps_root.txt

    This will write a list of environment variables to test_apps_root.txt on %AppsRoot%. This command is executed without an problems.

    But a command line like,

    %AppsRoot%Install\AcrRead\AcroRead.msi /qb

    will fail and setup is aborted.

    It's not exactly the same problem like you have, but it's simlar and the solution is very simple:

    Sure your solution with separat cmd works fine as well but the follwoing is a little bit easier:

    Instead of

    %AppsRoot%Install\AcrRead\AcroRead.msi /qb

    just use

    cmd /c %AppsRoot%Install\AcrRead\AcroRead.msi /qb

    Thats at least not much different from putting everything together in one cmd file. But it's easier to handle and in auditUser pass especialy it gives you the option to use the build in Restart command.

    Hope that'll help!

    Regards,

    Martin

  5. Hello swbchen!

    First you should set up your Automatic Updates, that they are downloaded but NOT installed automatically. Once you get the message, that there are new updates ready to be installed on your computer, you will find them in %Windir%\Softwaredistribution. You need to check the folders with the long numbers. Look for msu files.

    AFAIK, the updates are not present there for ever after you've installed them.

    Regards,

    Martin

  6. Hello sp00f!

    Than you could add the regtweaks during specialize pass using synchronous command again with reg add command:

    For example:

    	   <component name="Microsoft-Windows-Deployment" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <RunSynchronous>
    <RunSynchronousCommand wcm:action="add">
    <Description>Disable UAC</Description>
    <Order>1</Order>
    <Path>cmd /c reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v EnableLUA /t REG_DWORD /d 0 /f</Path>
    </RunSynchronousCommand>
    </RunSynchronous>
    </component>

    Martin

  7. I haven't tried out so far, but give it a try... or I will try later. But I 've read in setupact.log that sometimes an unexpected reboot happens, and setup is still going on.

    I would have an other solution but it's more complicated. You would need to integrate a .cmd into install.wim. What kind of Regtweaks you need for WPI? HKLM only or User tweaks, too?

    Regards,

    Martin

×
×
  • Create New...