Hello. I have Win 10 OSD working perfectly on computers using Legacy BIOS mode. Recently I have had to migrate all devices to UEFI BIOS mode.

OSD using UEFI mode works perfectly (exactly like in Legacy BIOS mode) when the computer being imaged has a blank disk (i.e. I run Diskpart > Select Disk 0 > Clean).

However if I want to reimage the same computer it will fail to PXE boot with Error "PXE-E18: PXE server response timeout".

If I wipe the disk, then UEFI PXE works just as it did before, and OSD works as expected.

I do not understand why it is doing this in this specific scenario.

My environment:

1. SCCM 2012 R2 SP1 standalone site on 10.10.100.112. DP with PXE is installed on this server

2. DHCP installed on DC with IP 10.10.100.10. DHCP Scope does not have Options 60, 66 or 67 which is correct since SCCM DP and DHCP server are on the same subnet.

3. OS Deployment is using ask Task Sequence based on MDT 2013 Update 1, with WDK 10. The OS Image being deployed is a Windows 10 Build 1511 Enterprise x64. The boot images are working fine and distributed to the DP's etc.

4. The computer being imaged is an HP Probook 650 G1 (very recent model) and has full UEFI BIOS enabled with all CSM modules disabled

5. The OSD Task Sequence enables Bitlocker. However I have tried this with no Bitlocker enabled with the same result.

I am stumped! Can anyone suggest something I am missing? Thanks in advance!

Hoping someone can assist with this one. I'm trying to include the installation of .NET 4.0 in our Operating System deployment task sequence but I can't get it to complete successfully. It appears to time out and the task sequence fails. However the application is installed on the target machine.

- Application installs successfully from normal application deployment and takes 5-6 minutes to complete.

Excerpts from the target machine logs:

AppEnforce.log

- Exceeded timeout of 15 minutes while waiting for process 3004 to finish.  [[[I've identified the process as dotNetFx40_Full_x86_x64.exe]]]
- WaitForRunningProcess failed. Error 0x87d00213
- CMsiHandler::CompleteEnforcement failed with 0x87d00213
- CAppProvider::CompleteEnforcement failed with error 0x87d00213
- ++++++ Failed to enforce app. Error 0x87d00213. ++++++

AppDiscovery.log

- Method EnforceApp failed with error 87D00213
- CApProvider:ExecMethodAsync failed. 87d00213

smsts.log

- Execution status received: 4 (Application failed to install )
- Install application action failed: 'Microsoft .NET 4.0'. Error Code 0x80004005

-----------------------------

- .NET 4 is built as an Application in CM.
- Allow this application to be installed from the Install Application task sequence is checked.
- Command is: dotNetFx40_Full_x86_x64.exe /q /norestart /ChainingPackage ADMINDEPLOYMENT
- Run installation and uninstall program as 32-bit process on 64-bit clients is checked.
- Detection method is Registry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319

2012 R2 SP1 CU3

Hello - I've noticed 2 things that are causing slow deployments.

• The deployment wants to install SCEP but Windows 10 won't let it so ultimately we wait longer for deployment. Anyway to fix that?
• Post deployment ConfigMgr client still does not have Policies and AV is still not up-to-date. 4 hours and defender still not updated (by itself)

Now - if my users were a patient type they could wait another 20-30 minutes and everything is right but they are not and if I could get this part to speed up a bit I would be much appreciated :-)

Ideas / Thoughts?

Thanks,

Hi All, 

            When I try to pxeboot a system, the mouse and keyboard hangs just before the password screen, before selecting the task sequence and I am not able to enter the password. Could any one please let me know what could be the reason behind it. 

This is happening suddenly with Optiplex 990 models only

Regards

Krishna C K

Hello guys, actually, PXE service is not able to start. When I have deployed task sequence on collection for first time, computer got assignment of image, but task sequence not started. I got the error on Machine:

SMS PXE LOG:

Hi everyone !

Lately im having this weird problem when i deploy windows 7 computer on my sccm 2012 environment

most of the deployment work smooth but in some deployments (something like 1 of 3) i get this error :

Hi All,

Does Anybody have a complete procedure for include Windows Update step on OSD?

I have tried adding few steps in task sequence as mentioned in this thread - https://social.technet.microsoft.com/Forums/en-US/a535e509-fc6a-483c-bf24-7e2aa064e5b7/deploying-100-of-available-software-updates-during-a-task-sequence?forum=configmanagerosd

But getting error  During Scan ,

The task sequence execution engine failed executing the action (Scan For Update 2) in the group (Install Updates 1) with the error code 44506
Action output: [ smsswd.exe ]
PackageID = ''
BaseVar = '', ContinueOnError=''
ProgramName = 'WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000113}” /NOINTERACTIVE'
SwdAction = '0001'
Set command line: Run command line
Working dir 'not set'
Executing command line: Run command line
Process completed with exit code 44506
Command line returned 44506
Invalid Verb Switch.
湉慶楬⁤敖扲匠楷捴⹨. The operating system reported error 2147943860: This operation returned because the timeout period expired. 

and during Install All Software Updates,

The task sequence execution engine failed executing the action (Install Software Updates 1) in the group (Install Updates 1) with the error code 2147943860
Action output: ... y evaluation
Policy evaluation initiated
GetIPriviledgedInstallInterface successful
Refreshing Updates
Successfully initiated RefreshUpdates operation 
Waiting for RefreshUpdates complete notification from Updates Deployment Agent
FALSE, HRESULT=800705b4 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate\installswupdate.cpp,1273)
WaitForRefreshUpdatesComplete(spInstall), HRESULT=800705b4 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate\installswupdate.cpp,1331)
RefreshUpdates(), HRESULT=800705b4 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate\installswupdate.cpp,923)
InstallUpdates(pInstallUpdate, tType, sJobID, sActiveRequestHandle), HRESULT=800705b4 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate\main.cpp,248)
Setting TSEnv variable SMSTSInstallUpdateJobGUID=
Process(pInstallUpdate, tType), HRESULT=800705b4 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate\main.cpp,302)
Timedout waiting for updates refresh complete notification. The operating system reported error 2147943860: This operation returned because the timeout period expired. 

Hi All,

I received an unusual request today and it involves setting the system drive on a Windows 20102 R2 Server to a specific drive letter other than C:.  I've tried a number of things I dug off of Google but I'm not having a whole lot of luck.  I even tried building the server from scratch and doing it that way and still no luck.  Any help will be greatly appreciated.

Thanks in Advance,

Raymond

We are using UDI with our CM2012 task sequence.   In our UDI wizard we have a software install page.  If you choose 1 particular software app then we do Not want Office 2013 to install.   So in my task sequence on the "Install Office 2013" step I added a WMI Query.

 In the KEY I have tried both with and without the leading '\' before the word software.     My issue is now no matter what software I choose from the UDI wizard Office 2013Never installs.    What is the proper registry syntax for this?  

hklm\software\ssoprovider\isxagent\[type]  if that key equals '2' do not install office.  Otherwise you can install office.

Thanks.  

mqh7

I am having a truly bizarre issue.   We have 2 options in our task sequence.   Install Windows 7 32bit or 64bit.   Both task sequences are using the same boot image.  I can build many different Dell machines. But we have 1 laptop that is a Dell Latitude E7270 that is not using our default boot image.  It for unknown reasons is using a different boot image.  I can see this when I F12 up at the bottom of the screen it is using a x64 bit boot.wim.   How?  If we only have 2 task sequences and each is using the same boot.wim how can 1 laptop use a totally different boot.wim?

mqh7

Hi All,

I'm having some trouble booting into PXE.
I've recently configured PXE and have built my first task sequence.
My test machine boots in to PXE and completes the TS with no problems, but when I try to boot other machines (of the same model) they throw the "PXE-E53: No boot filename received" error.

The machines that I am trying to boot have not had the SCCM client installed previously, but are in my device collections.
I have ticked "Enable unknown computer support" in the DP properties and the TS is set to "All Platforms".

I'm new to SCCM so am quickly running out of ideas. I know my PXE server is running correctly because my test machine has no issues. My only guess is that it's not working because there has not been a client present on the machine, but I thought that's what the above settings were for.

Thanks in advance!

Jackson 

I have intresting scenario here which amazes me little bit, since I´m working with OSD over 6 years now, but it´s never late to learn new tricks :)

I´m using Intel generic NIC package to be able to install only NIC drivers on new model and then gather rest of the drivers with vendor utility (we´re trying to avoid downloading different packages via browser).

This is the driver-pack I´m talking about: https://downloadcenter.intel.com/download/18713/Network-Adapter-Driver-for-Windows-7-

1. If I install Win7 with using only those drivers in CM driver package, during first native OS start I get endless black screen error which wines about missing files in inf, and that inf is some of those extracted files in driver package.

2. If I then, with the same model, install Win7 without any drivers, login and plug USB stick containing _exact_ same driver folder and files, it picks up a little bit different sys/inf file, and works fine without dying on me with black screen loop.

So what´s happening? Why plug-and-play mechanism is different in CM TS and manual seeking and injection? 

I have been successfully installing Office 365 click to run (2013/2016) but now I have ramdomly install failures on both Win7 and Win10. It does not happen every time but most of the time.

If I don't set a timeout in the program the installation never finish. The CPU is 100% with svchost.exe taking all the juice. 

When I log into windows I actually have Office installed but I'm not sure if it's installed correctly.

Office logs:

The last row goes on and on without ever ending if I don't set a timeout.

I use MDT integration with package/program roles together with UDI wizard to choose office installation during OSD.

Any help is appreciated. 

Hi,

I received below "Not Found" pop up and unable to edit my task sequence.  Only that task sequence experiencing this issue not the others.  Any suggestion?

Brian

I am trying to test PXE booting on devices that only have UEFI and no CSM support.
We are running Windows Server 2008 R2 in our environment.

On the DHCP server, we have option 66 and 67 set. If I change option 67 to SMSBoot\x86\wdsnbp.com and boot a traditional BIOS system (non UEFI) the SCCM server responds and gives me the option to hit F12 and PXE boot. This works without issue and can deploy images.

I then change option 67 to SMSBoot\x64\wdsmgfw.efi and use a machine that is pure UEFI (meaning UEFI without any legacy support / CSM). The system appears to successfully download the wdsmgfw.efi and font file via TFTP as shown in the WDS logs. However, it then goes to the next sreen where it is trying to contact the WDS server. AFter retrying for a while it will error out with error 0x102 which I believe translates to ERROR_TIMEOUT

The SMSPXE.log repeats the following:
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName="" ServerRemoteName=""><Machine><ClientID>8908f9c4-c345-49ba-b137-af7b0b983584</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="GAS20043" OfferIDTime="7/24/2013 3:12:00 PM" PkgID="GAS00037" PackageVersion="" PackagePath="<a href="http:///SMS_DP_SMSPKG$/GAS00038">http://<IVE REMOVED  THIS>/SMS_DP_SMSPKG$/GAS00038" BootImageID="GAS00038" Mandatory="0"/></ClientIDReply>
 SMSPXE 7/24/2013 7:14:58 PM 7724 (0x1E2C)
00:50:56:01:00:82, DF6A0C42-F909-B518-7B44-3150B662200B: found optional advertisement GAS20043 SMSPXE 7/24/2013 7:14:58 PM 7724 (0x1E2C)
Looking for bootImage GAS00038 SMSPXE 7/24/2013 7:14:58 PM 7724 (0x1E2C)

Any idea what may be going on?

Hi all,

I'm tyring to get PXE to work. The setup is like this now;

- IP Helpers to dhcp, DP and terminal server in the client VLAN.

When booting into PXE, the client gets an IP but then gives PXE-E32: TFTP open timeout. This is the smspxe.log:

Prioritizing local MP http://DP.

Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16830119" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>

D0:BF:9C:**:**:**, D730017F-38AE-11E4-*: device is in the database.	SMSPXE	10/05/2016 16:17:00	6012 (0x177C)

Prioritizing local MP http://DP.

Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16830119" ServerName=""><Machine><ClientID>GUID:73C35A63-7A0F-4844-*</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="P0120FEA" OfferIDTime="28/04/2016 14:38:00" PkgID="P010039A" PackageVersion="" PackagePath="http://DP/SMS_DP_SMSPKG$/P010039B" BootImageID="P010039B" Mandatory="1"/></ClientIDReply>

D0:BF:9C:**:**:**, D730017F-38AE-11E4-*: using advertisement P0120FEA

Prioritizing local MP http://DP.

Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16830119" ServerName=""><Machine><ClientID>GUID:73C35A63-7A0F-4844*</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="P0120FEA" OfferIDTime="28/04/2016 14:38:00" PkgID="P010039A" PackageVersion="" PackagePath="http://DP/SMS_DP_SMSPKG$/P010039B" BootImageID="P010039B" Mandatory="1"/></ClientIDReply>

D0:BF:9C:**:**:**, D730017F-38AE-11E4-*: using advertisement P0120FEA	

--> I don't know if it matters but the PkgID in the line "Client boot action reply" seems very weird, since we don't have a pkg with an ID P010039A.

Kind regards,

Sander.

Dear  Expertz,

I am facing a issue while I was deploying a TS in PXE, it shows contacting to the server for a long time....... and nothing happensKindly give an idea what might go wrong in SCCM, I am using SCCM 2012 SP1

Hello,

I have used the Scheduled Updates Wizard with settings "continue on error" and "update DP"

1.) Ok it ran in a few minutes and saw message that it failed to update the DP. I performed a manual "Update Distribution points.

2.) Noticed that there was a long list of updates but I'm wondering if the Wizard reviewed what already existed in the wim image?

3.) Wonder if some of the updates listed where automatically not done and were superseded by others in the checked list?

4.) Is there some log generated for this event in sccm?...in otherwords what got applied to this wim?

5.) Is there a log in the wim that can be checked after image is dropped?

6.) Not sure if in "Programs and Features" that "View Windows Updates" is the complete source list of all the KBs applied?   In Windows XP I could check in c:\Windows and check the hidden KBs to see what was installed? Where can I do this in Windows Explorer in Windows 7?

Thanks!

I'm running SCCM 2012 R2 SP1 CU3 - trying to deploy Windows 10 enterprise LTSB to Dell, Optiplex 7010's and 9020's

I've been running into a few issues on my physical machines when deploying Windows 10 Enterprise LTSB. During the OSD process the clients will successfully complete the tasks for deploying the OS and applying drivers, but seem to to get stuck on the "Setup Windows and ConfigMgr" step. Once they arrive at this step they seem to take a long time on the "Getting Ready" screen, around of 20-30 minutes.

This does finally complete and when they reboot into the windows login screen I've noticed that they aren't joined to the domain, and the site settings for the ConfigMgr Client aren't setup ( I don't see this behaviour on my virtual machines, as they always join the domain and install the client as they should). The other weird thing is that in the Deployment Status, it reports back as a success - which clearly isn't the case. 

When I log into the computers and go into Device Manager, I don't see any components needing or missing drivers.

I'm stumped as to why on a VM this process runs fine, but once I switch to a physical machine it won't join the domain or install the client 

Has anyone encountered this issue?

Thanks for any help you can provide.