Jump to content


RichMawdsley

Established Members
  • Posts

    12
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by RichMawdsley

  1. Ok, lets cross a few scenarios off, try the following;

     

    1) Rebuild a current Win7 machine which is currently not working via Software Center.. Do this via PXE which is working.. shortly after it completes, can you run the TS again from Software Center?

    2) Rebuild a current Win7 machine which is currently not working via Software Center.. Do this via PXE which is working.. Once it completes, ensure its fully up to date (wsus) and let your standard required apps install as normal. Then, can you run the TS again from Software Center?

     

    If Scenario 1 works then you know your image is OK and nothing inside it from when it was captured is causing the issue.

    If Scenario 2 works then you know your image is OK, WSUS is installing anything which is breaking it, and neither are your applications.

    If Scenario 1 works but 2 doesn't, well then you can point the finger towards updates or applications.

     

    From what you've said above, I would except Scenario 1 to work.

     

    Also, during your Task Sequence, can you confirm the command line you are using to install the SCCM client?

     

    Rich

  2. Interesting.

     

    I know I've suggested this previously elsewhere but not sure you did it.. I'd suggest creating a brand new Windows 7 machine completely separate from your current image, fully update it, then manually install the SCCM client and go through the process of running the Task Sequence.

     

    I suspect this may be something to do with either how your Windows 7 image was captured (not properly cleaned up to give its own identity), or something installed in your Windows 7 image.

     

    Rich

  3. I hate Java. It has caused me the biggest headaches when mass deploying. Their installer is utterly S***.

     

    When deploying it through SCCM, it gets even worse and as you have said, it throws random errors and is literally random.

     

    However, below are the scripts I use which work for me deploying to 10k machines. A lot of blood and tears went into these (even if it is basic) and it's the only way I could get them to work. These use a config file aswell (read their website) and puts the exception.sites file in place. It also ensures updates are disabled and start menu cleaned. These are for x86 version so mirror for x64 also changing relevant parts.

     

    This script should only be run when no versions of Java are installed:

    @ECHO OFF
    REM Red Wedding
    taskkill /F /IM javaw.exe
    taskkill /F /IM jqs.exe
    taskkill /F /IM jusched.exe
    del "C:\Program Files (x86)\Common Files\Java" /S /F /Q
    REG DELETE "HKLM\SOFTWARE\Wow6432Node\JavaSoft" /f
    
    REM Copy Config File Locally and Rename
    XCOPY "%~dp0Config.cfg" "%systemdrive%\ProgramData\Oracle\Java\java.settings.cfg*" /R /H /Y
    
    REM Install Java
    msiexec /i "%~dp0jre1.8.0_60.msi" INSTALLCFG="%~dp0Config.cfg" REPAIRMODE=0 AUTO_UPDATE=0 EULA=0 INSTALL_SILENT=1 NOSTARTMENU=1 SPONSORS=0 /q /L C:\apps\java86.txt
    
    REM Create Dir Structure
    MD "%systemroot%\Sun\Java\Deployment\"
    
    REM Copy Config Files
    XCOPY "%~dp0deployment.config" "%systemroot%\Sun\Java\Deployment\deployment.config*" /R /H /Y
    XCOPY "%~dp0deployment.properties" "%systemroot%\Sun\Java\Deployment\deployment.properties*" /R /H /Y
    
    REM Copy Site Exceptions
    xCOPY "\\SERVERSHARE\Java\exceptionsites\exception.sites" "%systemroot%\Sun\Java\Deployment\exception.sites*" /R /H /Y
    
    REM Disable Updates Completely
    REG ADD "HKLM\SOFTWARE\Wow6432Node\JavaSoft\Java Update\Policy" /f /v EnableJavaUpdate /t REG_DWORD /d 0
    REG ADD "HKLM\SOFTWARE\Wow6432Node\JavaSoft\Java Runtime Environment\1.8.0_60\MSI" /f /v AUTOUPDATECHECK /t REG_SZ /d 0
    REG ADD "HKLM\SOFTWARE\Wow6432Node\JavaSoft\Java Runtime Environment\1.8.0_60\MSI" /f /v JAVAUPDATE /t REG_SZ /d 0
    REG ADD "HKLM\SOFTWARE\Wow6432Node\JavaSoft\Java Runtime Environment\1.8.0_60\MSI" /f /v JU /t REG_SZ /d 0
    
    REM Cleanup
    RD "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Java\" /S /Q
    del "C:\Program Files (x86)\Common Files\Java" /S /F /Q
    

    I also found, that should there even be a trace of Java on the machine, then installing via SCCM will fail. So I made the below scripts to kill Java.

     

    Java 6 and below:

    wmic product where "name like 'Java(TM)%%'" call uninstall /nointeractive
    
    RD "C:\Program Files\Java\jre6" /S /Q
    RD "C:\Program Files (x86)\Java\jre6" /S /Q
    REG DELETE "HKLM\SOFTWARE\Wow6432Node\JavaSoft\Java Runtime Environment" /f
    REG DELETE "HKLM\SOFTWARE\JavaSoft\Java Runtime Environment" /f
    
    Exit /B 0
    

    Java 7:

    wmic product where "name like 'Java 7%%'" call uninstall /nointeractive
    
    RD "C:\Program Files\Java\jre7" /S /Q
    RD "C:\Program Files (x86)\Java\jre7" /S /Q
    REG DELETE "HKLM\SOFTWARE\Wow6432Node\JavaSoft\Java Runtime Environment" /f
    REG DELETE "HKLM\SOFTWARE\JavaSoft\Java Runtime Environment" /f
    
    Exit /B 0
    

    Java Completely

    wmic product where "name like 'Java%%'" call uninstall /nointeractive
    
    RD "C:\Program Files\Java" /S /Q
    RD "C:\Program Files (x86)\Java" /S /Q
    RD "C:\ProgramData\Java" /S /Q
    REG DELETE "HKLM\SOFTWARE\Wow6432Node\JavaSoft" /f
    REG DELETE "HKLM\SOFTWARE\JavaSoft" /f
    RD "%systemroot%\Sun\Java\Deployment\" /S /Q
    RD "%systemdrive%\Microsoft\Windows\Start Menu\Programs\Java\" /S /Q
    RD "%systemdrive%\ProgramData\Oracle\" /S /Q
    
    Exit /B 0
    

    Hope they help.

     

    Rich Mawdsley

  4. Excellent post as always.

     

    I would suggest adding a note about the issues with the latest ADK v1511 tho. I've just hit this issue after installing it. Only workaround is to uninstall ADK v1511 and install the RTM version.

     

    http://blogs.technet.com/b/configmgrteam/archive/2015/11/20/issue-with-the-windows-adk-for-windows-10-version-1511.aspx#pi168308=2

     

    From Software Center, launch a task sequence that uses a Windows PE v10.0.10586 boot image. When the computer restarts into Windows PE, it will fail when “Initializing hardware devices” with the error: “Windows PE initialization failed with error code 0x80220014.”

     

    At this time, we do not recommend that Configuration Manager customers use the 1511 version of the Windows 10 ADK.

     

    Although I personally had this error in a build and capture pxe scenario, and others have reported it on bare metal installs too.

     

    Rich Mawdsley

    • Like 1
  5. Figured out my own problem!

     

    Incase anyone else has the issue:

     

    I had the 'Request State Store' step in my Restore TS set as 'Capture state from the computer' as a pose to what it should be set as; 'Restore state from another computer'.

     

    All works fine now!

     

    -First post was always going to be something I'd done wrong wasn't it! :P

  6. Afternoon All,

     

    I'm in the process of setting up USMT on our systems and have it working fine in a WINPE TS.

     

    However I'm now trying to capture 1 machine and restore it on separate one via separate Capture and Restore TS in Windows.

     

    I firstly create the association in SCCM for the source and destination computers, stating all user accounts to be transferred.

     

    Then run the Capture on PC 1 which works fine and I can see status in SCCM changes to 'In Progress'.

     

    Then I run the Restore on PC 2 and it fails with the log file saying the store path is invalid.

     

    I manually check and the store path its going to is '815A23998209*SNIP*', which does exist but its empty.. However I can see that the store path for the captured machine is actually '0B10473D648A0*SNIP*'.

     

    So PC2 is looking for its own captured information and not realising I've made an association already and its not pointing to the correct PC1's captured info.

     

    Hope that makes sense and someone can help as I've hit a brick wall! Any Ideas?

     

    Thanks,

     

    Rich

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.