Search the Community

Hello, I am trying to PXE boot surface pro 4 and for some reason it does not boot. I get the attached message. It tries to PXE over IP v4, then reaches my correct DP that has PXE and WDS, it finds the correct NBP file SMSBoot\x64\wdsnbp.com (this is specified in DHCP option), it appears to be downloading and NBP file is successfully downloaded. Then without prompting to press Enter key for PXE boot, it moves to IPV6. I have tried below but no luck Upgrade firmware to latest disable secure boot Removed DHCP option - but this time it doesn't even finds my PXE server Verified and made sure MAC address of network adapter is not registered with SCCM DB Tried docking station and no luck I can PXE boot a desktop on same network with no issues. Any suggestions would be helpful Thanks.

I just recently updated our production SCCM environment to SCCM 2012 R2 SP1, CU1. I updated MDT 2013 to Update 1 (8298) and installed the integration on my central site server. I am now having issues deploying Windows 10 to a VMware VM. After it applies drivers and boots into the operating system for the first time, I receive a pop-up message with the following: "Windows could not finish configuring the system. To attempt to resume configuration, restart the computer". Restarting the computer just brings back the same message. This is only happening with MDT integrated task sequences. I created a task sequence without MDT integration and the deployment finishes fine. I created another MDT task sequence for SCCM and it is still failing at the same point. Unfortunately, I cannot get to a CMD line when the error pops up. I try SHIFT+F10 but that doesn't work. I enabled F8 for the boot image but it is past the PE environment. I did get the logs before the OS restart and they all look fine. I updated our lab environment back in August (pre MDT 2013 Update 1 re-release) and didn't run into this issue. Any help would be greatly appreciated.

Hello, I got 2 almost the same enviroments both upgraded to the latest version of sccm. 1 can easy add OSD and there is no problem the other enviroment is refusing adding the OSD i tried already existing OSD and new ones but all fails. i get the following error massage "The spicifed unc path does not contain a valid WIM file or you do not have permissions to acces it. specify a valid path" I try to add it by netwerk share, the server and netwerk acces account got full persmision to acces the share and folders under it. the more strange is that in my other enviroment the OSD addes perfectly no problems found. ive i try to ad an application there is no problemen and that also works fine, how can i troubleshoot on what point exactly the sccm refusing to add the OSD Version 5.0.8239.1302 SCCM 2012 r2 sp1 CU2 ADK version 8.1

Hello, I am new here but I have been following windows-noob.com for a very long time. You have amazing content. I am Running SCCM 2012 R2 SP1 CU2 environment with MDT 2012 SP1 integrated plus I have WADK 10.0.10240.16384. I have build a Task Sequence below which works flawless on Dell OptiPlex 7040 and E5450. The only issue I have is when the deployment is completed. The bitlocker is not enabled and TPM says " tpm is ready for use with reduced functionality". TPM is enabled in BIOS, UEFI is selected, Secure Boot is enabled as well. Any help is appreciated on how to initiate TPM during OSD and enable bitlocker. Thanks for all the help

Hi All, Recently I have been trying to bit locker devices during OSD on a 2008r2 domain, with sccm 2012 r2 sp1. the schema has been checked and is correct (the 5 entries are present) CN=ms-FVE-KeyPackage – attributeSchema object CN=ms-FVE-RecoveryGuid – attributeSchema object CN=ms-FVE-RecoveryInformation – classSchema object CN=ms-FVE-RecoveryPassword – attributeSchema object CN=ms-FVE-VolumeGuid – attributeSchema object CN=ms-TPM-OwnerInformation – attributeSchema object The ad DC's have the bitlocker tools installed, and I can see the 'bitlocker recovery key' tab for a device in ADUC. I have a AD GPO in place on an OU where the device exists in AD But my task sequence fails at the ENABLE BITLOCKER stage towards the end of the TS. The TS was created by sccm wizard, nothing special in it as yet. If I disable the DISABLE BITLOCKER, PREPROVISION BITLOCKER and ENABLED BITLOCKER steps in the TS and build the device, then enable bitlocker manually logged on to the device, it works and saves the key to AD, I am obviously missing something here, anyone know where I should look in the logs... The device is uefi and has secureboot enabled The OS is Windows 81 x32

We just finished upgrading our SCCM Servers both our CAS and PS1 to SCCM 2012 R2 SP1. After the upgrade it seems that the new boot.wim file that is created is having issues. After the machine pxe boots and pulls down the wim file, it goes to windows is starting up then preparing network connections and then black screens and restarts. I opened up an F8 command prompt and pulled the SMSTS.log and I see an error during the TSMBootStrap.exe step. The error is Failed to download pxe variable file ... PxeGetPxeData failed with .... I have attached our SMSTS.LOG file. I verified that i have network connectivity by running IP config and then I was also able to ping our MP. I thought it might be driver related but I have tested from different dell models, Dell 9020, E3340, 7010, etc. and they all have the same problem. Any ideas/suggestions? smsts.log