we have a very mixed environment, I spend a lot of time finding the drivers I need and embedded them in the PE but every time a new ADK or OS comes out it uses a new PE...
Is there a streamlined way to get the same drivers I needed before into the new PE?
thanks
Hi there,
I am trying to install Windows 7 on a physical machine from Configuration Manager via OSD Deployment. As soon after the computer finishes loading the boot.wim file the following error is popping up
Your PC needs to restart.
Please hold down the power button.
Error Code: 0x000000C4
Parameters:
0x0000000000000091
0x000000000000000F
0xFFFFF8011A5C4A80
0x0000000000000000
Can anybody help please
Regards
I am trying to create a new 64-bit boot.wim.
C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment>copype.cmd adm64 C:\WinPE64
ERROR: The following processor architecture was not found: adm64. Failed! You can see my command above and the error I get. I am running this on a Windows 2012 R2 Server. How come it fails when my
OS is 64-bit?
mqh7
Hello guys :-)
In my Task Sequence in SCCM 2012 R2 without MDT Im planning this:
-Restart in PXE
- CONDITION QUESTION: Do you like rename computer? IF yes GOTO xxx step (where OSDComputername will prompt new hostname) ELSE not GOTO yyy step (where task sequence goes to capture computer and network settings and proced)
Any chance of success??
I am not able to build a new x64 image for OSD deployment within CM2012. I have created a driver package for the hardware I'm testing on (a Dell 7010 desktop). I have created a new x64 boot image. I have gone through Gerry Hampson's method of creating a new .WIM file (http://www.gerryhampsoncm.blogspot.ie/2014/03/create-customised-reference-image-with.html) yet every time I build my image the following happens.
It copies down and installs the OS
it copies down and installs the drivers for the Dell 7010 desktop
It reboots
It says starting Windows.....
Then I get this error. And I can't press F8 to bring up a CMD window and get the logs.
mqh7
I am working on using PXE with SCCM 2012 and finally got my test VM to boot with the standard x86 boot image. This is the process:
1. Start up VM with no OS
2. Contacts SCCM and I press F12 to Network Boot
3. Boots into a SCCM screen and says " Windows is starting up" then " Preparing Network Connections".
4. Then all i see is a blank screen. After about a minute it will just reboot.
I found this post that discusses adding the drivers need for the boot images:
I added the entire VMware tools Driver folder to both my boot images. (All it had in there was a SCSI adapter)
Tried to redo the PXE and still get the same menages with the blank screen after that.
I am imaging about 1800 devices and about 75 at a time. On about 30% of the devices I get this error "sending with winhttp failed; 80072ee7". This happens about 75% through the Task Sequence after a reboot.
I able to ping the MP FQDN all the time.
One thing that I thought was strange is after the reboot when it detects the network adapters the USB adapter we are using is not found. Then the errors happen. And then later the adapter is found because it does upload the logs.
Logs
https://onedrive.live.com/redir?resid=94948D4E79A593A8!13901&authkey=!AE95b1J57nZh0Hs&ithint=file%2clog
https://onedrive.live.com/redir?resid=94948D4E79A593A8!13902&authkey=!AFBDM1fTGAXBhQU&ithint=file%2clog
We have a Windows 7 x86 task sequence that was working fine. No Changes Have Been Made To It!!!! I did make a copy of this and then I've modified the copy many times. The copy is for x64. But now when I try to build a x86 machine the following happens.
I am prompted for a password on the DP. I enter the password and then it copies down the Windows PE environment. (it never did that before). Then once it copies it down I am prompted with this dialog (again, we have not seen this before) If I press FINISH then the TS continues as normal but what is causing this TS Wizard dialog to appear and how do I get rid of it?
Thanks.
mqh7
I'm looking for a way to delete old computer objects from AD during OSD.
The scenario is this:
The problem is that whenever a computer is reinstalled, the old computer object in AD remains.
I've been looking at various PowerShell scripts, but I know NOTHING about Powershell, so it always ends with doing something else.
So if possible, I would like to avoid using PowerShell.
Hi ,
I have created an task sequence for OSD(Refresh i.e wipe and load) and advertised it to a collection,
When users go to the software center and click on it to install it gives below warning as a part of it,
I don't want to display this message is there any way to supress it?
he task sequence failed to install application Mozilla Firefox (en-US)(ScopeId_DF37C18A-3DCC-4C3E-87B7-BCF6704DB3F9/Application_b2c11445-6b22-4a02-96d4-69bbafcc7d92) for action (Install Applications) in the group () with exit code 617. The operating system reported error 617: You have attempted to change your password to one that you have used in the past. The policy of your user account does not allow this. Please select a password that you have not previously used.
regards
Lashkham
Hi,
Today we're running a SCCM 2012 R2 SP1 environment, integrated with MDT 2013 with ADK 8.1.
We're deploying Windows XP and Windows 7 Computers using a single SCCM MDT Integrated Task Sequence. But now it's time to support Windows 10 deployment as well, so we would like to update the system with ADK 10 and MDT 2013 update 1. According to the documentation ADK 10 supports Windows 7 and higher OS versions. Upgrading to ADK 10, will create a new boot image, but would it still be possible to continue , despite the Windows 7 and higher specs for ADK 10, to use a single Boot image/task sequence for deploying Windows XP, Windows 7 and Windows 10 all together?, or do we need to keep the old Win PE 5 (from ADK 8.1) boot image and then a separate task sequence for the Windows XP deployments?.
I haven't been able to google the right post/documentation for a thumbs up or down for this scenario, so I'm in process of building a test environment to test this upgrade and to see what happens with the compatibility with Windows XP deployments, but wouldn't mind to know if somebody already have the answers for my quest.
Kind Regards,
Jakob
I have a issue with distributing OS from SCCM to L440.
When I load the image onto the PC, it select the lan driver I217-LM, but it has to use I218-LM. I have registreted the rigth driver in the SCCM, but both drivers is installed on the server, and I can't see, how I can get the system to select I218-LM instead of I217-LM.
I hope someone can help me.
Best Regards
Alex B. Rasmussen
Support Guldmann A/S
Hi folks,
I've a custom script that fetches few TS variables from MDT database.
Script runs fine in FullOS mode, (not in Task Sequence)
However, when I've this run as part of Task Sequence and in WinPE mode, it doesn't return any value.
I've the NAA account give db_datareader/db_datawriter & public, also the boot wim has MDAC support.
cheers.
I am having an issue capturing an image and was hoping you could point me in the right direction. When I try to capture an image it keeps failing with the error “0x80070035 during the "capture the reference machine" process”.
My reference PC is a standalone HP 800G1 running Windows 7 SP1 x64 PC in a workgroup and have created the boot image iso on a DVD. I run the tsmbautorun.exe which runs sysprep and reboots the PC, then capture process starts and fails with the“image capture wizard has failed with the error code (0x80070035)" error. From the research I've done, it looks like an authentication error but I cannot see where its failing. I have tried this several times using both my credentials and the admin credentials. Obviously I am missing something somewhere and its probably something basic.
I'm trying to PXE boot a laptop from a remote DP, but when I PXE boot I can't even get an IP address. I'm not getting an error message either. When I check smspxe.log on the remote DP the last message is from a year ago saying "PXE Provider Shutdown".
I've restarted both the remote DP and main site SCCM 2012 R2. I've also tried restarting WDS service. Flow control and Loop back protection on switch is off, I've verified that the laptop is not listed in Device Assets.
We've configured a reference machine with Windows Embedded Standard 7 SP1 from the DVD, after completing the installation of the reference machine a sysprep is done (sysprep /generelize /shutdown). EWF is disabled and no ConfigMgr client is installed before the sysprep!
Next the image is captured with ConfigMgr, so it can be used in a Build & Capture or Deploy Task Sequence.
The deployment of the captured image works just fine - the Task Sequence proceeds as it should just until the 'Setup Windows and ConfigMgr'-step. The client installation failes and ccmsetup.log shows:
The Task Sequence stops, because there's no communication possible with the Managemt Point. First thing checked when logged in on the client: 'ewfmgr', and sure... DISABLED...
In order to solve the mistery, we've also tried to capture the reference machine with media. Same result.
So, why is the ccmsetup detecting an enabled EWF? I'm out of possible solutions and guesses. I'm sure the EWF is disabled pre capture, and I'm sure the EWF is disabled post deployment. Which means the EWF is enabled somewhere in the initialization fase of the OS.
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">
I have read several posts that don't truly fit my issue but I may be wrong but I need help. Let me provide as much details as I can in hopes of resolving my issue.
Network was recently segmented
SCCM 2012 R2 is a VM on x.x.0.0 VLAN 100
Desktops/Laptops are on x.x.20.0 VLAN 20
I did not have this issue prior to segmenting the network and I enabled DHCP Scope options 66 and 67, Option 60 N/A as the DNS and SCCM are not on the same server.
Option 66: FQDN of SCCM server
Option 67: smsboot\x86\wdsnbp.com
When I PXE boot the client sees the deployment server, hit F12 option and it gives error: PXE-M0F: Exiting Intel Boot Agent.
I added a second NIC to the VM and put it on the x.x.20.0 subnet and VLAN tagged 20 on there.
Still the same result. I see that the client gets an IP address from DHCP which is on the x.x.0.0 subnet, I check the Address Leases and what I see may be the issue but not 100% sure on my theory.
Instead of the normal 12 Hex MAC address it is coming up with the GUID address that I see in PXE, think this is also called the SMSBIOS GUID from what I have read.
The Client Machine is a Lenovo T540p if that makes a difference. I thought about removing the WDS feature and reading but I am hesitant on that as it applied to other issues that is not quite like mine.
Any Suggestions would be greatful, thank you!