We have just purchased some new dell optiplex 7040 pc, 

We use MDT to deploy our os however with these new pc's we getting following message.   Invalid credentials: The network locationcannot be reached.  

When i press F8 there are not connection when i type ip config there is no ip address.

I have the imported the very latest drivers and updated my deployment share.    

I have checked the password in the boot.ini and custom.ini and they are correct, i dont think its a credential issue because I can build other pcs fine.  I have also checked the Windows PE driver injection to ensure that its checked to include all network drivers.

I using windows 2012 R2 Standard, 

workbench deployment is 6.3.8290.1000

can anybody offer any assistance.  

kind regards 

Nick 

Hi Folks,

Can any one help me please on this error.

Please click answer If it works Thanks KMI

Hey guys

Unfortunately I didn't rearm the Office 2016 licence details when capturing my image. So means I need to run the commands in a command line once the image is deployed on a machine for it to connect to our KMS

"%ProgramFiles(X86)%\Office16\OSPPREARM.exe"

then

cscript "<driveletter>\Program Files (x86)\Microsoft Office\Office15\ospp.vbs" /act

Is there anyway I can add it as a new command whilst it is getting deployed during OSD deployment? I tried adding them in the sequence as "two separate command line" but it doesn't work.

I am still prompted for license details once the image is deployed, hence I know it hasn't worked.

Should I deploy both as separate packages instead?

Hi All,

I'm Hugues, I'm working for a research center in Luxembourg. For several years, we use SCCM to deploy the operating system on our laptop, desktop,... Last week we bought a new laptop, it's a new model Dell E5470. I tried to deploy the operating system but after the boot in PXE mode, it automatically restart and I cannot choose a task sequence. I read a lot of documentations about this issue on internet, I uploaded the NIC driver Intel-I219 LM for this model on the boot image, update the distribution point but it sill doesn't work. On our other model it works,... When I do an "ipconfig" I have no IP address.

Any idea ?

Thx all

Hi,

I'm running SCCM 2012 and have recently installed the Windows 10 ADK and imported the WinPE 10 boot images. I still have the Windows 8.1 boot images on the PXE point for now whilst I test the WinPE boot images. I've injected the HP WinPE 10 driver pack NIC drivers into the x64 boot image using the SCCM console and then associated the boot image with my Windows 10 Task Sequence.

The problem I have is that oncemy HP 800 G2 reboots into the WinPE 10 boot image I have no network. The driver is not being loaded at boot. As far as I can tell the correct NIC driver has been injected though. If I bring up a command prompt inside WinPE and navigate to X:\Windows\System 32\Driverstore\Filerepository I can load the NIC driver using drvload.exe and pointing at the inf file which is in there.

Any ideas why the NIC driver is not being loaded at boot?

Thanks,

Jay

Hi,

We got a case from the user where the machine got formatted automatically from SCCM agent. And all the data is lost of the user.

Can somebody tell me why this happened and what could be the reason for this?

Regards, &amp;quot;If this thread answered your question, please click on &amp;quot;Mark as Answer&amp;quot;

I have created a pacakge to install Sas 13 on the computers out our University.  I have deployed the pacakge and made it avaiable to the systems.  But when I select to install the pacakge Software Center has a pop up window indicating  unable to make changes to your software.  This just sarted happening, I have created dozens of packages which all install but this one.  I have tried to google the error but I could not find anything.  Would anyone know why this would just start happening?

I

Thanks

I have a Task Sequence that is supposed to pickup user files, from Windows XP Pro, based on USMT and save them on the local disk, then install clean installation of Windows 7 Pro + some apps. Then restore USMT data.

I built a test Windows XP Pro VM, logged in with couple of domain accounts, created test files in each user account, then ran the TS. It installed Windows 7 Pro without reporting any issues. However, none of the settings or files from Windows XP transferred over.

I read smsts.log (you can download it here) and noticed that there were references to loadstate.log (see below), which in turn referenced scanstate.log (you candownload that here).

I am somewhat new to SCCM, therefore, any help with this analysis would be greatly appreciated.

2016-02-23 22:07:03, Info                  [0x000000] LOADSTATE.EXE Version 6.2.9200.16384[gle=0x000000b7]
2016-02-23 22:07:03, Info                  [0x000000] USMT Started at 2016/02/23:22:07:03.444
2016-02-23 22:07:03, Info                  [0x000000] Command line: C:\_SMSTaskSequence\Packages\P0100001\amd64\loadstate.exe C:\_SMSTaskSequence\UserState /ue:MININT-DUU396A\* /v:5 /c /hardlink /nocompress /l:C:\Windows\CCM\Logs\SMSTSLog\loadstate.log /progress:C:\Windows\CCM\Logs\SMSTSLog\loadstateprogress.log /i:C:\_SMSTaskSequence\Packages\P0100001\amd64\migdocs.xml /i:C:\_SMSTaskSequence\Packages\P0100001\amd64\migapp.xml2016-02-23 22:07:03, Status                [0x000000] Activity: 'MIGACTIVITY_COMMAND_LINE_PROCESSING'
2016-02-23 22:07:03, Info                  [0x000000] Drive C:\ has 20 MB free; a minimum of 250 MB is required[gle=0x000000cb]
2016-02-23 22:07:03, Info                  [0x000000] Failed.[gle=0x00000006]
2016-02-23 22:07:03, Info                  [0x000000]   A minimum of 250 MB of free space is required for temporary files[gle=0x00000006]
2016-02-23 22:07:03, Info                  [0x000000] USMT Completed at 2016/02/23:22:07:03.444[gle=0x00000006]2016-02-23 22:07:03, Info                  [0x000000] Entering MigShutdown method
2016-02-23 22:07:03, Info                  [0x000000] Leaving MigShutdown method
2016-02-23 22:07:03, Info                  [0x000000] ----------------------------------- USMT ERROR SUMMARY -----------------------------------[gle=0x00000006]
2016-02-23 22:07:03, Info                  [0x000000] * USMT error code 29: [gle=0x00000006]
2016-02-23 22:07:03, Info                  [0x000000] +-----------------------------------------------------------------------------------------[gle=0x00000006]
2016-02-23 22:07:03, Info                  [0x000000] | A minimum of 250 MB of free space is required for temporary files[gle=0x00000006]
2016-02-23 22:07:03, Info                  [0x000000] +-----------------------------------------------------------------------------------------[gle=0x00000006]

Office 365 installation hangs/stalls the OSD Task sequence despite completing the install successfully (from everything that I can tell). It appears that the right component is not getting the message to move on? I can force reboot the computer this point and I am able on login to launch every office 365 app. If I just let it sit there it will stay until the whole task sequence times out and quits.

Here is the appenforce.log that seems to show the application install went just fine!

But here is the smsts.log that has not another entry since the application install began:

Hi Team,

We have some W510 workstations for which LAN drivers are missing.

So we want to download the latest drivers for W510 model; using which we will later create driver package in SCCM 2012 R2.

can someone please let me know the location to download the drivers for W510 model ?

Thanks, S K Agrawal

Not sure what to about this one as it is kind of weird to me. We are starting the process of Windows 10 migration and at this stage I am making the task sequence in SCCM. First I install Win10 from the ISO via a USB drive to find out what drivers would be needed in SCCM. I got them all no problem and all of them installed during my first run of the TS from a USB drive.

However the bluetooth adapter is throwing an Error Code 10 STATUS_DEVICE_POWER_FAILURE. Its showing that its installed as it is not listed as an Unknown Device. When the driver is installed with windows being setup from the ISO it works fine and Windows also adds a MS Bluetooth Enumerator and MS Bluetooth LE Enumerator, both of which dont show up in the SCCM installed OS.

I am fairly certain that these being missing is what is causing the problem but I am not sure as to why it would not add them in during the TS install of Win10. The actual BT device is an Intel one and this is happening on both our Dell Optiplex 7040 and Latitude E7470. Any help is greatly appreciated!!

-Mark

In our SCCM 2012 R2 environment, I recently put together an MS Office 2013 x64 application and it is not showing up the Install Programs list when running the OSD task sequence on a system. I'm a Config Manager newbie and this is my first attempt at creating a package that can be installed by the OSD task sequence. I have verified the following criteria:

1. "Allow this application to be installed from the Install Application task sequence action without being deployed" checkbox is checked.
2. Content for the application has been fully distributed to all sites.
3. Requirements for the deployment type are set to "All Windows 7 64-bit", which is the OS used in the task sequence.
4. Installation behavior is set to "Install for system".
5. Logon requirement is set to "Whether or not a user is logged on".
6. Installation program visibility is set to "Hidden".

There is an MSO x86 app that the previous SCCM admin configured which does show up in the list, among other apps as well. I have thoroughly scoured each setting in that app to make sure that they match the ones on my MSO x64 app.  I am configuring a smaller application package (Java) to see if it's just the MSO 2013 x64 app that I created or if multiple new apps are affected.

Working to get an image of server 2008 R2 that is full patched to a new UEFI based server for a legacy application. I can manually install 2008 on this hardware if I do it via disc. I want to do it via SCCM 2012 deployment in the event I need to send an image down to it or its counterparts again. I've successfully deployed a 2012 R2 image to this server in the past as a test.

I believe my challenge has something to do with my task sequence with a 2008 OS image going to a UEFI server. I have the settings in the server to do both UEFI and Legacy. Each time I try a new deployment I use diskpart to clean disk 0. I check to make sure the server name is not in the devices collection of SCCM as well. It usually never is.

Here is what I see while it's working:

UEFI Partition disk 0
Formatting C:\
Apply operating system
Downloading wim
Applying image 1 from wim to C:\
After the progress bar comes all the way to the right, it fails the task sequence 0x8004005

Looking for some suggestions to try next from those with more experience. 

Hi all;

Selecting the same architecture of the boot image for deploying OS. Is it mandatory? For example, if I want to deploy Windows 8.1 x64, can I select x86-based boot image (as we can when we use WDS)?

Thanks

Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi,

I have been trying to upgrade Windows7 McAfee Encrypted system to Windows10 by SCCM 2012 R2 SP1 with MDT without decryption.

I have followed the steps per McAfee PC Refresh document. 

https://kc.mcafee.com/corporate/index?page=content&id=KB78376

During WinPE stage till Restore EPE MBR it's working fine but hereafter in the stage of Apply Operating System Image, the task sequence is throwing access denied error for the respective install image.

Any help or guidance on how can I fix this issue of access denied error. 

For Non-Encrypted PC the upgrade task sequence is working perfectly without additional encryption based task. 

Thanks in Advance.

Suraj

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">

During the application installation phase the TS hangs/stalls. Changing the order of applications only changes the step at which the TS hangs, but I think it rules out that it is a particular app causing the hang. When it hangs it appears that whatever app it was working on did complete the install successfully (from the appenforce.log and that I can force reboot the computer this point and I am able on login to launch the most recently installed app), so it would seem that the right component is not getting the message to move on or something important stopped running? . If I just let the target computer sit there, then it will stay on that TS step until the whole sequence times out and quits many hours later.

Here is the appenforce.log that seems to show the application install went just fine!

Here is the smsts.log that has not another entry since the application install began:

I am having a problem where not all drivers are applying for a specific model.

When I run my task sequence there are some devices in device manager that has yellow exclamation mark over them and the drivers are missing. When I update the device drivers for the device and I browse to folder \Drivers\PackageSource where model specific configmgr driver package is stored, they install fine.

I am confused as the drivers are imported and the package is applying in the task sequence but not all drivers are getting installed even though they seem to be there.