Hello all,

We just migrated our SCCM 2012 R2 environment from Vmware to Hyper-V on a new server. The old server was windows server 2008R2 and the new one is windows server 2012 R2. We kept the same computer account/ip address and did a disaster recovery procedure on the new server as a method to migrate it to the new server. The only thing we have now is that we are having issues with PXE boot. The following happens

• Client mac addr....
• client IP...10.x.x.x  mask 255.x.x.x dhcp ip 10.x.x.x.
• Gateway IP 10.x.x.x

• WDSNBP started using DHCP referral
• Contacting server 10.x.x.x (gateway 10.x.x.x)
• No response from Windows Deployment Services server
• Launching pxeboot.com...
• Press F12 for network service boot

If F12 is pressed, we directly get the following:

The Boot Configuration Data for your PC is missing or contains errors

File: \boot\bcd

Error code: 0x0000000f

The SMSPXE.log gives a lot of the following:

We tried the following:

• re-create the boot images
• Stop wds service/ rename remoteinstall\mgmt /restart wds service
• Re-create the RemoteInstall folder
• PXE boot machine on same subnet
• Granted access share/ntfs for system account on e:\ and d:\ (remoteinstall is on E)
• With process monitor I can filter out a lot of Access Denied errors on D and E during the boot

The new system is running on another system in the same datacenter (hyper-v cluster), however there is no firewall involved. Also Windows firewalls on all systems are turned off.

We also deployed a distribution point on the old vmware environment (and kept the SCCM server on hyper-v) and that works fine. A new DP on the hyper-v environment does not work. So I think it is something with Hyper-v or 2012 R2. The vmware server is 2012 (not R2).

Update: We deployed a VM on Vmware with 2012 R2 installed and deployed a DP there. That works fine. It seems that it is definitely something with Hyper-V. 

2012 R2 SP1 CU3

I'm having this weird issue not being able to install some applications during a build capture task sequence with a 0x80004005 error. 13/15 applications will install, but 2 do not (and these 2 are newly created). I have included SMSMP=primary.server.url into the Setup Windows & ConfigMgr task which others have said works for them. The 2 that do not install work perfectly fine as a package.

Has anyone figured this issue out?

Hi,

I've run a build & capture task sequence using the Windows 7 install.wim image. When I run a Deploy Windows 7 Task Sequence this is annoying installed to the D drive. I've got round this by adding the OSDPreserveDriveLetter=Falsestage o the TS and WIndows 7 is then deployed to the C Drive. However, after adfding this step the ConfigMgr client fails to install with the following error codes:

CCMSETUP.LOG

- client.msi installation failed. Error text: ExitCode: 1603

CLIENT.MSI-Product Configuration Manager Client -- Configuration failed

- Windows installer reconfigurated the product............reconfiguration success or error status: 1603

EVENTVWR-Disk Fill: Out of disk space -- Volume 'D'; required space: 90 kb; available space 0 kb.

So it seems that the configmgr client thinks that Windows is still installed on the D drive.

Any ideas on how to fix this?

Thanks,

Andrew

Has anyone had success deploying Win7 Ent x64 (using x64 boot image) to a Dell Precision 5510 with Samsung SSD (NVMe PM951)?

I have taken the cab files from Dell website and it blue screens at restart after applying the driver package and installing SCCM client. It is having an issue recognizing the disk and generates 0x0000007b blue screen shortly after the"Starting Windows" message appears. I have tried both AHCI and RAID configurations and have used both WinPE 5 and WinPE 10 boot images. 

Anyone have an idea of which driver in the Dell cab (5510-Win7-A00-C4XFD) may be causing the issue? I have tried disabling many of the drivers without success. We have about 60 other models that image successfully, so I know the TS is solid. I am having a hard time pinpointing the culprit.

Any advice or feedback would be greatly appreciated.

For a reason that I do not understand, every time we try to use an OSD sequence with a State Migration involved we get the following error:

smsts.log:

![LOG[Requesting SMP Root share config information from http://sc-cm.example:0]LOG]!><time="11:13:02.587+360" date="01-07-2016" component="OSDSMPClient" context="" type="1" thread="10196" file="smpclient.cpp:2348"><![LOG[CLibSMSMessageWinHttpTransport::Send: URL: sc-cm.example:80  CCM_POST /SMSSMP/.sms_smp?op=RootShareInfo]LOG]!><time="11:13:02.587+360" date="01-07-2016" component="OSDSMPClient" context="" type="1" thread="10196" file="libsmsmessaging.cpp:8778"><![LOG[Error. Status code 500 returned]LOG]!><time="11:13:02.610+360" date="01-07-2016" component="OSDSMPClient" context="" type="0" thread="10196" file="libsmsmessaging.cpp:9141"><![LOG[Received 1231 byte response.]LOG]!><time="11:13:02.610+360" date="01-07-2016" component="OSDSMPClient" context="" type="0" thread="10196" file="smpclient.cpp:2363"><![LOG[pReply != NULL, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osdsmpclient\smpclient.cpp,2378)]LOG]!><time="11:13:02.610+360" date="01-07-2016" component="OSDSMPClient" context="" type="0" thread="10196" file="smpclient.cpp:2378"><![LOG[SMP Root share info response is empty]LOG]!><time="11:13:02.610+360" date="01-07-2016" component="OSDSMPClient" context="" type="3" thread="10196" file="smpclient.cpp:2378"><![LOG[ClientRequestToSMP::ClientRootShareRequestToSMP failed. error = (0x80004005).]LOG]!><time="11:13:02.610+360" date="01-07-2016" component="OSDSMPClient" context="" type="3" thread="10196" file="smpclient.cpp:2429"><![LOG[ExecuteRootShareInfoRequest(sRootShareList), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osdsmpclient\smpclient.cpp,1704)]LOG]!><time="11:13:02.610+360" date="01-07-2016" component="OSDSMPClient" context="" type="0" thread="10196" file="smpclient.cpp:1704"><![LOG[ClientRequestToSMP::DoRequest failed. error = (0x80004005).]LOG]!><time="11:13:02.610+360" date="01-07-2016" component="OSDSMPClient" context="" type="3" thread="10196" file="smpclient.cpp:1882"><![LOG[Request to SMP 'http://sc-cm.example' failed with error (Code 0x80004005). Trying next SMP.]LOG]!><time="11:13:02.610+360" date="01-07-2016" component="OSDSMPClient" context="" type="2" thread="10196" file="smpclient.cpp:1590"><![LOG[FALSE, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osdsmpclient\smpclient.cpp,1644)]LOG]!><time="11:13:02.610+360" date="01-07-2016" component="OSDSMPClient" context="" type="0" thread="10196" file="smpclient.cpp:1644"><![LOG[Failed to find an SMP that can serve request after trying 4 attempts.]LOG]!><time="11:13:02.610+360" date="01-07-2016" component="OSDSMPClient" context="" type="3" thread="10196" file="smpclient.cpp:1644"><![LOG[pClientRequestToSMP->Execute(migInfoFromMP.saSMPs), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osdsmpclient\smpclient.cpp,2689)]LOG]!><time="11:13:02.610+360" date="01-07-2016" component="OSDSMPClient" context="" type="0" thread="10196" file="smpclient.cpp:2689"><![LOG[ExecuteCaptureRequestSMP failed (0x80004005).]LOG]!><time="11:13:02.611+360" date="01-07-2016" component="OSDSMPClient" context="" type="3" thread="10196" file="smpclient.cpp:2704"><![LOG[ExecuteCaptureRequestToSMP(migInfoFromMP), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osdsmpclient\smpclient.cpp,2744)]LOG]!><time="11:13:02.611+360" date="01-07-2016" component="OSDSMPClient" context="" type="0" thread="10196" file="smpclient.cpp:2744"><![LOG[ExecuteCaptureRequest failed (0x80004005).]LOG]!><time="11:13:02.611+360" date="01-07-2016" component="OSDSMPClient" context="" type="3" thread="10196" file="smpclient.cpp:2752"><![LOG[ExecuteCaptureRequest(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osdsmpclient\main.cpp,76)]LOG]!><time="11:13:02.611+360" date="01-07-2016" component="OSDSMPClient" context="" type="0" thread="10196" file="main.cpp:76"><![LOG[OSDSMPClient finished: 0x00004005]LOG]!><time="11:13:02.611+360" date="01-07-2016" component="OSDSMPClient" context="" type="1" thread="10196" file="main.cpp:124"><![LOG[Process completed with exit code 16389]LOG]!><time="11:13:02.650+360" date="01-07-2016" component="TSManager" context="" type="1" thread="9996" file="commandline.cpp:1124"><![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="11:13:02.651+360" date="01-07-2016" component="TSManager" context="" type="1" thread="9996" file="instruction.cxx:805"><![LOG[Failed to run the action: Request State Store.
Unknown error (Error: 00004005; Source: Unknown)]LOG]!><time="11:13:02.752+360" date="01-07-2016" component="TSManager" context="" type="3" thread="9996" file="instruction.cxx:911"><![LOG[Set authenticator in transport]LOG]!><time="11:13:02.754+360" date="01-07-2016" component="TSManager" context="" type="0" thread="9996" file="libsmsmessaging.cpp:7908"><![LOG[Set a global environment variable _SMSTSLastActionRetCode=16389]LOG]!><time="11:13:02.821+360" date="01-07-2016" component="TSManager" context="" type="0" thread="9996" file="executionenv.cxx:669"><![LOG[Set a global environment variable _SMSTSLastActionSucceeded=false]LOG]!><time="11:13:02.822+360" date="01-07-2016" component="TSManager" context="" type="0" thread="9996" file="executionenv.cxx:669"><![LOG[Clear local default environment]LOG]!><time="11:13:02.823+360" date="01-07-2016" component="TSManager" context="" type="0" thread="9996" file="executionenv.cxx:808"><![LOG[Let the parent group (Capture User Profile) decides whether to continue execution]LOG]!><time="11:13:02.829+360" date="01-07-2016" component="TSManager" context="" type="0" thread="9996" file="instruction.cxx:1020"><![LOG[The execution of the group (Capture User Profile) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)]LOG]!><time="11:13:02.830+360" date="01-07-2016" component="TSManager" context="" type="3" thread="9996" file="instruction.cxx:217"><![LOG[Failed to run the last action: Request State Store. Execution of task sequence failed.
Unknown error (Error: 00004005; Source: Unknown)]LOG]!><time="11:13:02.831+360" date="01-07-2016" component="TSManager" context="" type="3" thread="9996" file="engine.cxx:222"><![LOG[Set authenticator in transport]LOG]!><time="11:13:02.833+360" date="01-07-2016" component="TSManager" context="" type="0" thread="9996" file="libsmsmessaging.cpp:7908">

I've been able to trace this back to a corresponding error in smpisapi.log:

<![LOG[========== BEGIN: HttpExtensionProc ==========]LOG]!><time="14:49:06.347+360" date="01-07-2016" component="smpisapi" context="" type="0" thread="3016" file="smpisapi.cpp:404"><![LOG[Query string to parse: 'op=RootShareInfo'.]LOG]!><time="14:49:06.347+360" date="01-07-2016" component="smpisapi" context="" type="1" thread="3016" file="smpisapi.cpp:139"><![LOG[Attempt to call SMPDecryptAndVerify failed (0xc000a000)]LOG]!><time="14:49:06.363+360" date="01-07-2016" component="smpisapi" context="" type="3" thread="3016" file="smprequesthandler.cpp:412"><![LOG[SMPRequestHandler::ExtractSMPRequestMsg failed. error = (c000a000).]LOG]!><time="14:49:06.363+360" date="01-07-2016" component="smpisapi" context="" type="3" thread="3016" file="smprequesthandler.cpp:429"><![LOG[SMPRequestHandler::HandleMessage for StoreOp ROOTSHAREINFO failed with server errorcode 99]LOG]!><time="14:49:06.363+360" date="01-07-2016" component="smpisapi" context="" type="3" thread="3016" file="smprequesthandler.cpp:322"><![LOG[Returning status "500 Internal Server Error"]LOG]!><time="14:49:06.363+360" date="01-07-2016" component="smpisapi" context="" type="1" thread="3016" file="smpisapi.cpp:230"><![LOG[========== END: HttpExtensionProc ==========]LOG]!><time="14:49:06.363+360" date="01-07-2016" component="smpisapi" context="" type="0" thread="3016" file="smpisapi.cpp:482">

For what its worth, the health checks for the SMP are completely normal:

<![LOG[========== BEGIN: HttpExtensionProc ==========]LOG]!><time="14:50:24.342+360" date="01-07-2016" component="smpisapi" context="" type="0" thread="3016" file="smpisapi.cpp:404"><![LOG[Query string to parse: 'op=healthcheck'.]LOG]!><time="14:50:24.342+360" date="01-07-2016" component="smpisapi" context="" type="1" thread="3016" file="smpisapi.cpp:139"><![LOG[Creating state store - W:\USMT\SMPSTOREW_<usmt folder>$\<migration hash>.]LOG]!><time="14:50:24.342+360" date="01-07-2016" component="smpisapi" context="" type="1" thread="3016" file="smprequesthandler.cpp:1408"><![LOG[Creating Migration Status Parent Directory - W:\USMT\SMPSTOREW_<usmt folder>$\MigrationStatus.]LOG]!><time="14:50:24.342+360" date="01-07-2016" component="smpisapi" context="" type="1" thread="3016" file="smprequesthandler.cpp:1482"><![LOG[Statestore - W:\USMT\SMPSTOREW_C5BFB3A4$\MigrationStatus exists.]LOG]!><time="14:50:24.342+360" date="01-07-2016" component="smpisapi" context="" type="2" thread="3016" file="smprequesthandler.cpp:1494"><![LOG[Creating Migration Status Child Directory - W:\USMT\SMPSTOREW_<usmt folder>$\MigrationStatus\<migration hash>.]LOG]!><time="14:50:24.342+360" date="01-07-2016" component="smpisapi" context="" type="1" thread="3016" file="smprequesthandler.cpp:1512"><![LOG[Returning status "200 OK"]LOG]!><time="14:50:24.436+360" date="01-07-2016" component="smpisapi" context="" type="1" thread="3016" file="smpisapi.cpp:230"><![LOG[========== END: HttpExtensionProc ==========]LOG]!><time="14:50:24.436+360" date="01-07-2016" component="smpisapi" context="" type="0" thread="3016" file="smpisapi.cpp:482">

Seems to be a lot of post regarding issues with NIC drivers with later Dell (And other vendor) models. I am using SCCM 2012R2 CU2 and older builds work fine. However, the Dell E7270 can pxe but briefly displays the config manager screen before rebooting. This is information I am given as the tester is in a different country from myself.

These symptoms I would think are due to the driver missing from the boot image (Windows 10 ADK 1511). I imported the latest l217-LM driver into the boot image but same thing. Anyone had any success with importing a certain driver for these adapters?

We just applied CU3 to our SCCM 2012 R2 SP1 system. After the update, PXE boot for management point fails with error 0xc000000f. The PXE boot for this management point was working before the update. I tried reinstalling the management point however no change.

Hi, guys

Recently. the company I am working for are looking at getting the vendor to do the majority of the imaging.

The plan is spilt the Task Sequence into 2 parts. Offsite and then onsite. I have the OSDComputerName variable prompting for the hostname.

Booting from a USB device as a test, the entire Task Sequence completes - application installing, domain join etc. However when testing with USB during the first half, then plugging in the network cable for the second half doesn't work - doesn't do domain join etc. 

Has anyone done this before and has an example or ideas on best practices and how I should be doing this?

 Hi 

 i 'm looking to forward give an exam 70-243 but i'm not getting exact study materiel to pass an exam and get certified

 please if anyone can help how to and where to get study materiel to pass that examination, i went through Microsoft online 

but it has lengthy of stuff   

How do I include an unattend.xml in a boot image for ConfigMgr? For USB media, it is easy - copy it to the root of the media. How do I do that for the boot image used for PXE boot?

Thanks,

Jeff

I am trying to add machine variable from CAS and it fails. If I do it from primary site it works fine....on CAS it gives me following error... The user has full administartive privillage on both the servers CAS and Pri

I use ConfigMgr 2012R2 CU4 with MDT 2013U1.

When I create USB boot media from the Configmgr console and use that USB stick to boot an EFI machine, there is a 30 second delay/menu presented to choose to boot Windows Setup.  The USB stick does not present a menu or a dely when booting a machine that is booted in legacy BIOS.

During my task sequence I have to do many reboots into WinPE so this 30 second delay adds up to 4 or 5 minutes --- so  I would really like to get rid of it...  But I dunno how.

Is there a way to remove that delay from the  Windows Boot Manager in my Boot WIM? 

Hi all.

I need to be able to run a Powershellscript before the Format and partition disk step in a PXEbooted OSD Task Sequence.

I must run some verifications(powrshellscript) before disk erase starts and if precheck fails I don't want to end up with a client that is formated....

Problem is if disk is encrypted with bitlocker, or maybe the disk is blank there is no partition except X: ramdrive to store SCCM packages on. I want to run a "Run Powershell Script" step, but that requires that I store my script in a package that needs to be cached on the client before being able to execute the script. No fixed disk means nowhere to cache package unfourtenately.

By default my package do not seem to be allowed to cache to X: for some strange reason?

I managed to get the packages cached to ramdrive X: by setting the Task Sequence variable "SMSTSLocalDataDrive" to X:\, script started and displayed my Powershell WPF GUI and everything worked as expected. However, this method invoked other problems, diskpart failed and the OSImage was attempted to download to ramdrive. I did not manage to change SMSTSLocalDataDrive to C: after it was set, this is by design according to technet.

Any ideas how to solve this? I just need to cache one small script package on X:, run powershellscript, partition and format disk and then use fixed disk(C:) from there as usually.

Any other ideas how to solve this differently, i prefer not to map a network drive and run the script from there, but maybe that is the only option?

I tried this on a SCCM CB and 2012 R2 SP1 , both with MDT 2013 U2 integrated, same behaviour.

I am trying Inplace upgrade Task Sequence to upgrade Windows 7 SP1 Enterprise computers.

I build a TS using Inplace upgrade wizard from SCCM Console on SCCM 1511.

Imported Windows 10 Enterprise from ISO. Clients has been updated with latest version

Experiencing various issues.

After running InPlace upgrade TS from Software Center, TS quits with in a minutes and software center closed as well without any errors. No errors shows in SMSTS.log, TSAgent.log

Upon re-launch of Software Center Available Software and Installation Status Tab shows nothing.

Tried run actions from Configuration Manager Client in Control Panel, no luck

Reinstalled Client and finally TS shows back again.

Interesting aspect - After about 15-30 minutes I found InPlace upgrade Task Sequence kicks back on couple of machines and upgrades to windows 10 successfully

Anybody experiencing similar issues or any advise to check any specific log file

Requesting assistance.

RJ

RJ09

We upgraded our Primary site server to CM2012 1602.    Then we were not able to build any machines via OSD. I removed the DP role from our primary site server and re-added it. Now, the Task Sequence can't find any packages. Do I actually need to right click every package we have and choose distribute content?   I would hope/pray that is not the fix :-)

Any help would be great since we can't build any new machines right now and we need too

mqh7

I am the admin of our SCCM 2012 R2 SP1 CU2 environment. We are using the ADK 1511 version and I have read that adding MDT 2013 to that will allow me to upload multiple boot images that are independent of the ADK version installed on the SCCM Server.

I am looking for confirmation that this is true.

I would imagine the process would be as simple as uploading a new boot media, and choosing one from an ADK installed on my own system. Previously I tried this in SCCM without MDT and I got an error.

Thanks in advance!

Portland Public Schools / Systems Administrator II

In Windows 10 OSD we have never had an actual mouse cursor that is visible, even after updating to 1602.  It is however visible in Windows 7 OSD.

The mouse and USB devices are installed, and you can actually click and interact with the mouse, but the cursor is not visible.  

This makes troubleshooting during OSD a massive pain, especially when navigating the task manager.

Is there any fix for this issue?