Jump to content


Master-VodaWagner

Established Members
  • Posts

    14
  • Joined

  • Last visited

Everything posted by Master-VodaWagner

  1. Hi All, I am on the Tech Preview 1708 release and there is only a single SCCM server with a remote SQL database I cannot upload the entire logs on here but I have installed clients on 90% of my companies estate but I have 3 computers that are troublesome. 1 x Windows Server 2016 and 2 x Windows 10 Enterprise The client was installed from Windows Updates, but looking in the ccmsetup.log I can see these 2 errors Failed to persist AAD on-boarding info. Error 0x87d00217 Failed to get client version for sending state messages. Error 0x8004100e Apart from those 2 everything else in the log looks fine and I see a successful install for client.msi. Any Ideas?
  2. So I have a service plan which applies to a single device, the update have been downloaded to the DP and under Monitor > Deployments I can see the update has targeted the right device But the device is in a state of Unknown, Client check passed/Active. Now the client is active and talks to SCCM and just today downloaded an update to Office 365 but not the feature update to 1703 Win10. Any thoughts?
  3. Hi all, I got a single VM which is being a pain in the backend, it stumbles at the staging boot image and yet other VMs using the same task have worked perfectly. I've tried the following steps so far to troubleshoot - Rebuilt the VM, changed the MAC, created a new HDD, cleansed the HDD in WinPE. The VMs are Gen2 on HyperVisor 2016, UEFI, TPM etc Here is the snippet from the smsts.log file Launch mode read from environment variable: 'PXE'.' TSPxe 12/05/2017 08:30:09 1532 (0x05FC) BootpackageID: DC100023 AssociatedWInPE: DC100014 SourceVersion: 8 AssociatedSourceVersion: 8 TSPxe 12/05/2017 08:30:09 1532 (0x05FC) WinPE associated with task sequence does not match boot media. TSPxe 12/05/2017 08:30:09 1532 (0x05FC) Installing WinPE associated with task sequence DC100017:0. TSPxe 12/05/2017 08:30:09 1532 (0x05FC) TSUEFIDrive: TSPxe 12/05/2017 08:30:09 1532 (0x05FC) Staging boot image DC100014 TSPxe 12/05/2017 08:30:09 1532 (0x05FC) bFoundRawDisk == true, HRESULT=8007000f (e:\cm1702_rtm\sms\framework\tscore\bootimage.cpp,315) TSPxe 12/05/2017 08:30:09 1532 (0x05FC) Unable to find a raw disk that could be partitioned as the system disk TSPxe 12/05/2017 08:30:09 1532 (0x05FC) BootImage::GetSystemDisk(iSystemDisk), HRESULT=8007000f (e:\cm1702_rtm\sms\framework\tscore\bootimage.cpp,488) TSPxe 12/05/2017 08:30:09 1532 (0x05FC) ValidateSystemPartition(), HRESULT=8007000f (e:\cm1702_rtm\sms\framework\tscore\bootimage.cpp,1062) TSPxe 12/05/2017 08:30:09 1532 (0x05FC) Failed to prepare the system partition for staging. The system cannot find the drive specified. (Error: 8007000F; Source: Windows) TSPxe 12/05/2017 08:30:09 1532 (0x05FC) BootImage::PrepareForStaging(sLocalDataPath), HRESULT=8007000f (e:\cm1702_rtm\sms\framework\tscore\bootimage.cpp,783) TSPxe 12/05/2017 08:30:09 1532 (0x05FC) Failed to validate for boot image staging TSPxe 12/05/2017 08:30:09 1532 (0x05FC) StageBootImage() failed. 0x8007000f. TSPxe 12/05/2017 08:30:09 1532 (0x05FC) TS::Boot::BootImage::StageBootImage( pAssociatedWinPE->GetPackageID(), TsBootProgress, pv, hCancelEvent), HRESULT=8007000f (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2256) TSPxe 12/05/2017 08:30:09 1532 (0x05FC) Failed to stage WinPE. Code(0x8007000F) TSPxe 12/05/2017 08:30:09 1532 (0x05FC)
  4. Did you find a fix for this, I am in a similar issue. Although my Windows 10 Enterprise ISO was en-gb language installed
  5. bit of a bummer if the organisation wants to block the windows store....
  6. Yes, I've encountered this when I attempted 1703 but went back to 1607 for now
  7. Hi all, My Windows 10 TS was working perfectly, got my language pack issue resolved and imaged 4 HyperV VMs perfectly. Tried to image a further 4 this evening and all new VMs I create will PXE boot until the splash screen "Preparing Network" and then it restarts. I get the below errors in the SMSTS.log GetSelectedTaskSequence(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2531) TSPxe 02/05/2017 19:41:29 1076 (0x0434) There are no task sequences available to this computer.. Please ensure you have at least one task sequence advertised to this computer. Unspecified error (Error: 80004005; Source: Windows) TSPxe 02/05/2017 19:41:29 1076 (0x0434) RunWizardForPXE(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2869) TSPxe 02/05/2017 19:41:29 1076 (0x0434) oTSMediaWizardControl.Run( sMediaRoot, true, sTSLaunchMode ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1110) TSPxe 02/05/2017 19:41:29 1076 (0x0434) Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1258) TSPxe 02/05/2017 19:41:29 1076 (0x0434) Exiting with return code 0x80004005 TSPxe 02/05/2017 19:41:29 1076 (0x0434) Execution complete. TSBootShell 02/05/2017 19:41:29 840 (0x0348) hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,493) TSBootShell 02/05/2017 19:41:29 840 (0x0348) m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,335) TSBootShell 02/05/2017 19:41:29 840 (0x0348) this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,561) TSBootShell 02/05/2017 19:41:29 840 (0x0348) ::RegOpenKeyExW (HKEY_LOCAL_MACHINE, sKey.c_str(), 0, KEY_READ, &hSubKey), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,831) TSBootShell 02/05/2017 19:41:29 840 (0x0348) RegOpenKeyExW is unsuccessful for Software\Microsoft\SMS\Task Sequence TSBootShell 02/05/2017 19:41:29 840 (0x0348) GetTsRegValue() is unsuccessful. 0x80070002. TSBootShell 02/05/2017 19:41:29 840 (0x0348) I've deleted all Unknown computers from SCCM, WinPE can ping the SCCM box fine but I cannot figure out what to do next, please advise as I am nearly tearing my hair out. Many thanks
  8. I have applied the MDT approach using this guide and accepted the standard unattend.xml settings etc but when I want to select or install the GB language pack the install fails with error code: 0x80070002 <--- I cannot seem to find any additional log files to help with this error My unattend.xml script is: <?xml version="1.0" encoding="UTF-8"?> -<unattend xmlns="urn:schemas-microsoft-com:unattend"> -<settings pass="oobeSystem"> -<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="amd64" name="Microsoft-Windows-International-Core"> <InputLocale>en-GB</InputLocale> <SystemLocale>en-GB</SystemLocale> <UILanguage>en-GB</UILanguage> <UILanguageFallback>en-US</UILanguageFallback> <UserLocale>en-GB</UserLocale> </component> -<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="amd64" name="Microsoft-Windows-IE-ClientNetworkProtocolImplementation"> <HKLMProxyEnable>true</HKLMProxyEnable> <HKLMProxyServer>IP:PORT</HKLMProxyServer> </component> -<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="amd64" name="Microsoft-Windows-Shell-Setup"> -<OEMInformation> <Manufacturer>ORGNAME</Manufacturer> <SupportHours>0900-1700</SupportHours> <SupportPhone>NUMBER</SupportPhone> </OEMInformation> -<OOBE> <ProtectYourPC>1</ProtectYourPC> <HideEULAPage>true</HideEULAPage> <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE> <HideOnlineAccountScreens>true</HideOnlineAccountScreens> <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen> <HideLocalAccountScreen>true</HideLocalAccountScreen> </OOBE> </component> </settings> -<settings pass="windowsPE"> -<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="amd64" name="Microsoft-Windows-Setup"> -<UserData> -<ProductKey> <WillShowUI>OnError</WillShowUI> <Key>KEY</Key> </ProductKey> <AcceptEula>true</AcceptEula> <FullName>ORGNAME</FullName> <Organization>ORGNAME</Organization> </UserData> </component> </settings> <cpi:offlineImage xmlns:cpi="urn:schemas-microsoft-com:cpi" cpi:source="wim://<SERVERFQDN>/install_files/install.wim#Windows 10 Enterprise"/> </unattend>
  9. Hi all, I get the following errors when I attempt to download any Server 2016 updates from MS in SCCM Failed to download content id X. Error: Invalid certificate signature X is the package content id for any of the server 2016 updates I've tried to download from MS via the internet
  10. Hi All, Currently on 1702 of SCCM, when I right click my Windows 10 Enterprise OS and choose Update Schedule, the list of updates is empty even though it has downloaded the Creators Update patch. Any thoughts?
  11. Hey all, Very new to SCCM but loved the really nice build guides on this website. Basically I need to help in figuring out how to implement the following on New Build Laptops/Desktops/Servers etc. We will use a CSV file to import the ComputerName, MAC Address etc for multiple devices, I have PXE booting working and can deploy Windows 10 Enterprise easily to any device and at the moment have the prompt for OSDComputerName to manually enter the details per device. How can I automate that so it pre-populates the ComputerName based on the details it has for the device in SCCM? Hope I've explained it easily, Many Thanks
×
×
  • 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.