• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Windows 10 sysprep error.

Scheduled Pinned Locked Moved
Windows Problems
6
26
51.4k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J
    John Johnson @george1421
    last edited by May 17, 2016, 7:52 PM

    @george1421 The only reason for connecting to the internet is to run updates and get Adobe software, etc.

    G 1 Reply Last reply May 17, 2016, 7:58 PM Reply Quote 0
    • J
      John Johnson @george1421
      last edited by May 17, 2016, 7:54 PM

      @george1421 I am going to start from scratch and see if I can work around this.

      J 1 Reply Last reply May 17, 2016, 7:59 PM Reply Quote 0
      • G
        george1421 Moderator @John Johnson
        last edited by May 17, 2016, 7:58 PM

        @John-Johnson Just as a recommendation, for windows updates use a 2012 wsus server. And for adobe updates download them to a flash drive so you can install them. It sounds like you are building your reference image manually using audit mode?

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

        J 1 Reply Last reply May 17, 2016, 9:53 PM Reply Quote 0
        • J
          JJ Fullmer Testers @John Johnson
          last edited by Wayne Workman May 17, 2016, 2:01 PM May 17, 2016, 7:59 PM

          @John-Johnson I ran into a similar error.
          This answer is similar to the other’s but I had to run the following powershell script on every local user to get sysprep to work.

          $AppsList = "Microsoft.Bing" , "Microsoft.BingFinance" , "Microsoft.BingMaps" , "Microsoft.BingNews"`
                      , "Microsoft.BingSports" , "Microsoft.BingTravel" , "Microsoft.BingWeather" , "Microsoft.Camera"`
                      , "microsoft.microsoftskydrive" , "Microsoft.Reader" , "microsoft.windowscommunicationsapps"`
                      , "microsoft.windowsphotos" , "Microsoft.XboxLIVEGames" , "Microsoft.ZuneMusic"`
                      , "Microsoft.ZuneVideo" , "Microsoft.Media.PlayReadyClient"
          
          ForEach ($App in $AppsList)
          {
              $PackageFullName = (Get-AppxPackage $App).PackageFullName
              if ((Get-AppxPackage $App).PackageFullName)
              {
                  Write-Host "Removing Package: $App"
                  remove-AppxProvisionedPackage -online -packagename $PackageFullName
                  remove-AppxPackage -package $PackageFullName
              }
              else
              {
                  Write-Host "Unable to find package: $App"
              }
          }
          

          See this post for more info
          https://forums.fogproject.org/topic/5873/windows-10-unattend-xml-sysprep-answer-file-challenge/15

          Have you tried the FogApi powershell module? It's pretty cool IMHO
          https://github.com/darksidemilk/FogApi
          https://fogapi.readthedocs.io/en/latest/
          https://www.powershellgallery.com/packages/FogApi
          https://forums.fogproject.org/topic/12026/powershell-api-module

          J 1 Reply Last reply May 18, 2016, 1:20 PM Reply Quote 1
          • J
            John Johnson @george1421
            last edited by May 17, 2016, 9:53 PM

            @george1421 I am actually building the image on the computer model we will use it on. We have several different models. I had no issues with Windows 7 but Windows 10 has been a struggle.

            1 Reply Last reply Reply Quote 0
            • J
              John Johnson @JJ Fullmer
              last edited by May 18, 2016, 1:20 PM

              @Arrowhead-IT This actually worked for me!

              1 Reply Last reply Reply Quote 1
              • J
                John Johnson @george1421
                last edited by May 18, 2016, 1:22 PM

                @george1421 This worked. Arrowhead IT suggested the same.

                G 1 Reply Last reply May 18, 2016, 1:37 PM Reply Quote 1
                • G
                  george1421 Moderator @John Johnson
                  last edited by May 18, 2016, 1:37 PM

                  @John-Johnson just for clarity the power shell script that ArrowHead-IT posted (same as what I posted only through the link) corrected your issue? You were able to update your win10 with all of the updates from the internet and you applied the adobe updates? I just want to ensure your workflow was the same and the only thing you changed was the powershell script.

                  Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                  J 1 Reply Last reply May 18, 2016, 3:01 PM Reply Quote 1
                  • J
                    John Johnson @george1421
                    last edited by May 18, 2016, 3:01 PM

                    @george1421 said in Windows 10 sysprep error.:

                    @John-Johnson just for clarity the power shell script that ArrowHead-IT posted (same as what I posted only through the link) corrected your issue? You were able to update your win10 with all of the updates from the internet and you applied the adobe updates? I just want to ensure your workflow was the same and the only thing you changed was the powershell script.

                    Yes. I was able to lift my image to fog by using powershell as the user and removing the offending apps.

                    1 Reply Last reply Reply Quote 1
                    • J
                      John Johnson
                      last edited by May 18, 2016, 3:19 PM

                      I would say this topic is solved and I appreciate the support.

                      1 Reply Last reply Reply Quote 2
                      • J
                        John Johnson
                        last edited by Jun 25, 2016, 5:40 PM

                        I apologize for not responding for a while. I did find a solution to this. I simply made an account that I knew I would remove later. I loaded everything I needed under that account. After I was finished I created the account I wanted to keep and removed the other. All the Microsoft apps went with it. This works for me and I hope it helps…

                        1 Reply Last reply Reply Quote 0
                        • Q
                          Quazz Moderator
                          last edited by Jun 30, 2016, 10:55 AM

                          I’d just like to mention that if you clean install the latest W10 iso, this shouldn’t happen (unless you incorrectly remove certain apps)

                          1 Reply Last reply Reply Quote 1
                          • J
                            jscharfenberg
                            last edited by Nov 3, 2016, 3:58 PM

                            not sure if anyone has moved from this or not but there is a much easier way to sysprep then going through and removing the native apps. All I did was do a fresh install and have the OS offline. Go to services and disable Windows Update. Then go ahead and put it back online, install all my apps and use the SCCM 2012R2 capture ISO. Worked like a charm. It’s something in the Native App updates that kills sysprep.

                            D 1 Reply Last reply Nov 4, 2016, 2:38 PM Reply Quote 0
                            • D
                              davidedpg10 @jscharfenberg
                              last edited by Nov 4, 2016, 2:38 PM

                              @jscharfenberg

                              I run this on powershell

                              Get-AppxPackage -AllUsers | Remove-AppxPackage
                              

                              And then I use this sysprep unattend file. It works really well in my environment.

                              <?xml version="1.0" encoding="utf-8"?>
                              <unattend xmlns="urn:schemas-microsoft-com:unattend">
                              
                              <!-- Autounattend_x64_BIOS_sample.xml
                              
                              This file automates the Windows installation.
                              
                                  Before using this file:
                                   * Replace ProductKey with a product key for the edition of Windows you are installing
                                     (example: Windows 8 Pro)
                                     Note:
                                        The product key used in Microsoft-Windows-Setup\UserData\ProductKey\Key 
                                        can be used many times in different installations and is not used to activate Windows. 
                                        It is only used to choose which edition of Windows to install. 
                                        
                                        The individual product key is either specified by the user, or by setting 
                                        Microsoft-Windows-Shell-Setup\ProductKey.
                                  * Set the default language to your own:
                                    Replace "en-US" with your language code in Microsoft-Windows-International-Core-WinPE\SetupUILanguage. 
                                    For a list of languages, see http://go.microsoft.com/fwlink/?LinkId=206620.
                                  * OEMs: Replace OEMInformation with your support information
                              
                                  To use this file: 
                                     Save this file on the root of a USB flash drive with the filename: Autounattend.xml
                                     Put the Windows DVD and the USB key into a new x64-BIOS PC.
                              -->
                              
                              
                                 <settings pass="specialize">
                                     <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                                <CopyProfile>true</CopyProfile>
                                     </component>
                                 </settings>
                                 <settings pass="windowsPE">
                                     <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                                         <SetupUILanguage>
                                             <UILanguage>en-US</UILanguage>
                                         </SetupUILanguage>
                                         <InputLocale>en-US</InputLocale>
                                         <SystemLocale>en-US</SystemLocale>
                                         <UILanguage>en-US</UILanguage>
                                         <UserLocale>en-US</UserLocale>
                                     </component>
                                     <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                                         <UserData>
                                             <AcceptEula>true</AcceptEula>
                                         </UserData>
                                     </component>
                                 </settings>
                              <settings pass="oobeSystem">
                               <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                                <OOBE>
                                 <HideEULAPage>true</HideEULAPage>
                                 <HideLocalAccountScreen>true</HideLocalAccountScreen>
                                 <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
                                 <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
                                 <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
                                 <SkipUserOOBE>true</SkipUserOOBE>
                                 <SkipMachineOOBE>true</SkipMachineOOBE>
                                </OOBE>
                               </component>
                              </settings>
                              </unattend>
                              
                              1 Reply Last reply Reply Quote 1
                              • 1
                              • 2
                              • 2 / 2
                              • First post
                                Last post

                              192

                              Online

                              12.0k

                              Users

                              17.3k

                              Topics

                              155.2k

                              Posts
                              Copyright © 2012-2024 FOG Project