E7250 will not PXE Boot with SCCM 2012 R2

Just received our new version Dell laptop the E7250. We are using SCCM 2012 R2 OSD to build our computers. We currently have 6 Dell computers (2 desktops 7010 and 790 and 4 laptops 6410, 6420, 6430 and 5440) that are using the same WIM file. Never had a problem with the network drivers until now with the E7250. It loads the WIM file but as soon as it says "preparing network connection" it fails. I hit F8 and try an IPCONFIG and I don;t see an IP address. So I'm thinking Network Driver issue, so I add the network driver to the Boot image and still can't get past "Preparing Network Connections". Any ideas?
Thanks

I got the same issue, both the Dell and Intel drivers only have Intel L217-LM drivers, the Latitude E7250s I've got need L218-LM drivers. I've tried older versions of the family driver package from Intel, but no good.
Perhaps its not the driver packages but rather SCCM 2012 R2 that doesn't pick up the 218 drivers in the packages, but I'm stuck.

Similar Messages

Type 2 Virtual Machine in Hyper-V will not PXE boot with WDS

Hi
Bit of a wierd scenario this but I'm doing a bit of a lab experiment kind of thing. The setup is as follows:
VMWare Workstation 10 with Windows Server 2012 R2 running as a virtual machine. In VMW10 I have a NAT network interface and a Bridging interface set to load with the virtual machine. These seem to work fine (although the NAT doesn't seem to want to connect
to the internet but that's why the bridging one is there in addition).
Server 2012 is configured with the following roles:
ADDS, DHCP, DNS, Hyper-V, Printer, WDS
I have correctly configured WDS to work on the same machine as DHCP and I can get PXE boot working with WDS on a Type1 Virtual Machine in Hyper-V using the Legacy Network adapter. My problem is when I try and PXE boot on a Type2 Virtual Machine (this type
is new in R2 and should eliminate the need for a legacy network adapter) using the same network interface that I used for the Type1 machine, I get an IP address from DHCP but WDS doesn't seem to respond. Instead I get the "PXE-E16: No Offer Received"
message. I have tried just about everything I can think of and spent the whole day trying to figure out why this is the case but came up with nothing. Has anyone else encountered this or can anyone shed any light on the matter?
Many thanks in advance

"VMWare Workstation 10 with Windows Server 2012 R2"and "Server 2012 is configured with the following roles: ADDS, DHCP, DNS, Hyper-V, Printer, WDS"
Hyper-V is not supported to be run as a VM. It is a Type 1 hypervisor, which means it works on the bare metal. You have it running as a VM on a Type-2 hypervisor, so it has no access to the bare metal. Yes, VMware may have made it so some
things work in that environment, but it is not a supported (or tested) environment for Hyper-V.
.:|:.:|:. tim

Machines cannot PXE boot using SCCM 2012 DP

There are a lot of posts about PXE boot, but I can't find the common thread to tie them all together. My test machines cannot PXE boot.
My lab environment is very simple:
10.10.0.0/24 subnet
10.10.0.10 = W2k8 R2 DC, DHCP, DNS
10.10.0.11 = SCCM2012 (on W2k8R2 with SQL Server 2008 SP3 and CU4)
All machines are Hyper-V virtual machines connecting through the same virtual network.
Setup the PXE service from DP properties. I let SCCM install WDS. WDS in Server Manager does not have a server node, but the WDS service is running. DP PXE tab is configured as follows:
"Enable PXE support for clients" is checked
"Allow this distribution point to resond to incoming PXE requests" is checked
"Enable unknown computer support" is checked
"Require a password when computers use PXE" is not checked
"User device affinity" is set to "Allow user device affinity with automatic approval"
PXE is configured to respond on all network interfaces
The PXE server response delay is 0 seconds
The DHCP server has options configured as follows:
Option 66: 10.10.0.11
Option 67: smsboot\x86\wdsnbp.com
Both DP and MP on SCCM server are configured for HTTP.
Both x86 and x64 boot images have been distributed to DP. The media was updated after PXE was enabled on the DP.
Both x86 and x64 boot images have "Deploy this image from the PXE service point" enabled on the Data Source tab of their properties.
I have tried both unknown computer task sequence and a computer import task sequence (old computer association). They all end in abortpxe.com
Complete PXE response is as follows:
=================================================================
PXE Network Boot 03.23.2009
(C) Copyright 2009 Microsoft Corporation, All Rights Reserved
CLIENT MAC ADDR: 00 DD CC BB AA 00 GUID: 532D27E3-A184-4D27-A822-30A8B6F4A39D
CLIENT IP: 10.10.0.106 MASK: 255.255.255.0 DHCP IP: 10.10.0.10
GATEWAY IP: 10.10.0.5
Download WDSNBP...
Architecture: x64
WDSNBP started using DHCP Referral.
Contacting Server: 10.10.0.11 (Gateway: 0.0.0.0)
The detalis below show the information relating to the PXE boot request for
this computer. Please provide these details to your Windows Deployment Services
Administrator so that this request can be approved.
Pending Request ID: 6
Contacting Server: 10.10.0.11
TFTP Download: smsboot\x64\abortpxe.com
PXE Boot aborted. Booting to next device
===========================================================
From the smspxe.log:
]LOG]!><time="16:31:39.445+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:6402">
<![LOG[Client Identity: {C9929C4D-735A-4973-8659-4D3D5D5E4F92}]LOG]!><time="16:31:39.445+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:6428">
<![LOG[Set enterpirse certificate in transport]LOG]!><time="16:31:39.480+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9207">
<![LOG[Set media certificate in transport]LOG]!><time="16:31:39.505+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9220">
<![LOG[Set authenticator in transport]LOG]!><time="16:31:39.505+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Set authenticator in transport]LOG]!><time="16:31:39.533+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[PXE::CBootImageManager::FindMatchingArchitectureBootImage]LOG]!><time="16:31:39.553+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="bootimagemgr.cpp:1736">
<![LOG[PXE::CBootImageManager::FindMatchingArchitectureBootImage]LOG]!><time="16:32:00.963+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="bootimagemgr.cpp:1736">
<![LOG[Set enterpirse certificate in transport]LOG]!><time="16:32:01.008+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9207">
<![LOG[Set media certificate in transport]LOG]!><time="16:32:01.027+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9220">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:01.027+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:01.084+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777218" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID=""
LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
]LOG]!><time="16:32:01.108+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:6402">
<![LOG[Client Identity: {C9929C4D-735A-4973-8659-4D3D5D5E4F92}]LOG]!><time="16:32:01.108+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:6428">
<![LOG[Set enterpirse certificate in transport]LOG]!><time="16:32:01.151+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9207">
<![LOG[Set media certificate in transport]LOG]!><time="16:32:01.174+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9220">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:01.174+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:01.209+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[PXE::CBootImageManager::FindMatchingArchitectureBootImage]LOG]!><time="16:32:05.230+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="bootimagemgr.cpp:1736">
<![LOG[Set enterpirse certificate in transport]LOG]!><time="16:32:05.290+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9207">
<![LOG[Set media certificate in transport]LOG]!><time="16:32:05.325+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9220">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:05.325+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:05.366+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777218" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID=""
LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
=============================================================================================
I've been hammering this for about 10 hours now (or to be honest, it's been hammering me) and it must be something very simple I'm missing. I have a feeling that I'm doing something I used to do in 2007 and whatever that is, it does not work in
2012.
If I connect using boot media, Task Sequences execute perfectly.
TIA,
Tom

Option 66: 10.10.0.11
Option 67: smsboot\x86\wdsnbp.com
Pending Request ID: 6
Contacting Server: 10.10.0.11
TFTP Download: smsboot\x64\abortpxe.com
PXE Boot aborted. Booting to next device
<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777218" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
Those options are fine when using DHCP options. They must be configured right because ConfigMgr does send a reply to the client ("abortpxe"). It basically tells you that ConfigMgr knows the MAC address and/or SMBIOSGUID of the client, but cannot find
a deployment for it.
Just find ResourceID 16777218 in the console (you might have to add the ResourceID column) and double check if there's an deployment available (properties of the client with resourceID 16777218).
Torsten Meringer | http://www.mssccmfaq.de
Your answer really helped me. I was searching for 2 days trying to find a computer in Config Manager. Your suggestion to "Just
find ResourceID 16777218 in the console (you might have to add the ResourceID column) and double check if there" was the trick to finding the computer in Config Manager. Thanks for all of your help
Gregory Campbell System Administrator

Toshiba L755 is the only one that will not PXE BOOT

I have a few host on my network which it has VMWare 10 installed, successively performed deployment into those machines(Hosts and created VM"s). Now, I do have also a Toshiba L755-S5258 that will not complete the process, it does not give any
errors. The following is the messages it gives.
Client MAC ADDR: xx xx xx xx xx xx GUID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXX
Client IP:XXX.XXX.X.XX MASK: XXX.XXX.XXX.x DHCP IP: XXX.XXX.X.X
Gateway IP: XXX.XXX.X.X
Downloaded WDSNBP...
Press F12 for network service boot
Windows Deployment services: PXE boot Aborted.
PXE-MOF: Exiting Intel PXE ROM
This si the only unit that does not follow through with the deployment
Note that I've deleted other machines that I successively deployed to from the Known Computers on Active Directory User and Computers, with not good results
Please any one help me decipher this headache

Hi,
Are your using the WDS for the Windows deploy? A network boot program (NBP) is the first file that is downloaded and executed as part of the network boot process and it controls
the beginning of the boot experience (for example, whether or not the user must press F12 to initiate a network boot). NBPs are specific to both the architecture and firmware of the client. You must accounting the screen press F12 to allow the system boot
from the WDS. The VMware® workstation PXE booting issue please ask your software vendor.
The related KB:
Managing Network Boot Programs
http://technet.microsoft.com/en-us/library/cc732351(WS.10).aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Setup of PXE boot for SCCM 2012

I have setup SCCM Server on a test network with IP 192.168.9.10. I have also setup a DC which is running AD, DNS and DHCP and its IP is 192.168.9.2
On what server do I install WDS and how do I configure WDS/DHCP to point SCCM 2012 to enable PXE boot

If the client is in the same subnet as the PXE enabled DP no further network configuration is necessary. If it isn't you have to configure
1. IP Helper on your switch/router to direct the request to the PXE enabled DP (preferred)
OR
2. Add DHCP Scope option to direct the request to the PXE enabled DP
See how to do it here
http://www.gerryhampsoncm.blogspot.ie/2013/02/sccm-2012-sp1-step-by-step-guide-part_9487.html
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Will SCOM 2012 R2 co-exist with SCCM 2012 SP1

Hi. Sorry if the answer is obvious, but I need to ask...
Will SCOM 2012 R2 coexist with SCCM 2012 SP1?
We currently have SCOM 2007 R2 installed and we'd like to upgrade.
We installed SCCM 2012 close to 2 years ago and upgraded to SP1 last summer.
We had SCOM 2007 R2 integrated with SCVMM 2008 R2, but have upgraded to SCVMM 2012 SP1 recently - so there is nothing setup between SCOM and SCVMM.
There is currently nothing setup between SCOM and SCCM.
We're a single forest, single domain shop. Ideally, we'd like or System Center products to "work together", thus the question about the 2012 SP1 and R2 mix.
Thanks for any input. I appreciate your time and expertize. Joe.

Hi,
I concur with Alexey, a side note SCCM and SCOM do not use the same SQL Server.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

My mac book pro will not fully boot up. I have the grey background with the apple sign and the timer going round...but 20 minutes later still no desktop

My mac book pro will not fully boot up. I have the grey background with the apple sign and the timer going round...but 20 minutes later still no desktop

You could try doing a hard shut down (holding the power button or yanking the battery) and then doing a safe boot by holding the shift key at startup:
http://support.apple.com/kb/HT1455
Also, not sure if this applies in your case, but I've had that happen when there's a USB drive inserted either in the computer or a connected external keyboard. I did a hard shut down, removed the drive and it went through a normal start up.

Working in adobe illustrator - computer crashed - will not soft boot or reset PRAM - should i reinstall from CD snow leopard 10.6.3? I have an extra hard drive in my MAC with time machine on it set to do auto back ups. How do i recover ?

working in adobe illustrator - computer crashed - will not soft boot or reset PRAM - should i reinstall from CD snow leopard 10.6.3? I have an extra hard drive in my MAC with time machine on it set to do auto back ups. How do i recover ?

Well first you have to figure out what is wrong with the machine and solve that problem first.
Your post is very vague on what occured, and there are many types of "crashes" it really depends upon what see on the screen and what the hardware does, we can't see it to tell you, so you have to tell us.
I suggest you run through these user tips and provide more information about your hardware.
Disconnect the TimeMachine drive for now
..Step by Step to fix your Mac
Help us to help you on these forums
Create a data recovery/undelete external boot drive
If this is going way over your head, there are local PC/Mac techs that will assist you for a fee, Apple only does hardware repairs and is advised to use them if you discover it is, especially if under warranty/AppleCare.
Hard drive and RAM upgrades can be handled yourself or by a outside tech in many older models of Mac, but don't expect Apple to cover the new parts.
Install/upgrade RAM or storage drive in Mac's

Deploying CC Enterprise Applications With SCCM 2012

Hi all,
We are using CC Packager to package up individual applications (Photoshop, InDesign etc) and are having trouble deploying the applications once packaged. To deploy, we are using SCCM 2012 and are deploying to Windows 7 x64 clients. It appears that the install begins on the client, then hangs, never to finish.
We are running the MSI with the REBOOT=ReallySuppress and MSIRESTARTMANAGERCONTROL=Disable commands, but with no luck.
This has us really stumped. The applications seem to package fine, yet just won't install. If we manually run the installer, we can see it begin installing, then the progress bar goes backwards and the installation ends without displaying any sort of message.
Also, as an FYI, we have followed this guide closely in our attempts: http://helpx.adobe.com/creative-cloud/packager/deploying-packages-sccm.html
Has anyone experienced a similar problem? Any ideas?
Thank you in advance.
Ryan

Windows 7 x64 Clients
Deploying with SCCM 2012
I have called Adobe before and was told that the application package needs to be on a local drive on the computer. The package cannot be installed if the package is sitting on the network. My installation for a adobe creative cloud package fails to install when I try to install the application from the software center. At some moment the installation searches to ensure it is on a local disk. Not sure how this happends. If you place the installation package on a drive on your computer the package will install, although it will take time depending on how many applications you have packaged.
Another problem that you might have is having users log out of the applications without admin previlages.
I have yet to find a solution for these two problems, I could really use some help from someone who has sucessfully deployed a creative cloud package to a user.
Thank you

Remote WSUS integration with SCCM 2012

Hi,
We are currently having WSUS already in place for Patching , but not used at all its just installed.
can remote WSUS be integrated with SCCM 2012 server which is on different server ? what is the best practice ? is it to have WSUS on same server as Primary server?
or I decommission it and install a new WSUS on same server as SCCM server.
what steps have to be taken care if remote WSUS is integrated ? any documents or steps to be taken care .
Thanks in Advance

When you install SUPs, they automatically configure the underlying WSUS instance to sync from an upstream server based upon your ConfigMgr hierarchy.
A couple of notes here though:
- You generally shouldn't use an existing instance of WSUS for ConfigMgr. Once integrated into ConfigMgr, WSUS should no longer manage approvals, update binary downloads, or update binary distribution as these are all handled by ConfigMgr separate from WSUS.
Using an existing WSUS instance where this was the case can be problematic at best and will cause unexpected behavior and results.
- Clients do not choose SUPs based upon boundaries or location so using a remote SUP is typically not beneficial and in many cases will cause additional network load. The exception to this is if the SUP is within a secondary site.
Jason | http://blog.configmgrftw.com | @jasonsandys

I heard some promote use of "Terminal Services(RDS)", rather than App-V application with SCCM 2012 even if you have SCCM licens.

Hi,
I heard some promote use of "Terminal Services(RDS)", rather than App-V application with SCCM 2012 even if you have SCCM licens. The reason you dont need to repackage\test the application on an client OS...
I don't agree and I have not Heard this Before, just that you use TS for some scenario.
Or is it more likely that "Terminal Services(RDS)", take over the applikation administration?
/SaiTech

Surely this all depends on your environment. There's nothing wrong with creating RemoteApps to push to client devices. Maybe you have an environment where RDS is widely used.
Why not leverage both solutions and target App-V's at RDS servers and then create App-V based RemoteApps that users can run at home as part of a home working solution via RDWeb.
Creating apps via RDS will be an admin overhead yes but then so is creating App-V packages in SCCM.
I don't agree with the arguement re: 'you dont need to repackage\test the application on an client OS...' as
App-V allows you to run on multple O/S types.
To be honest both technologies have their pros and cons.
Cheers
Paul | sccmentor.wordpress.com

WinPE 5 802.1x Support with SCCM 2012 R2

Please see updated information a few posts down.
I am trying to get 802.1x support working to deploy windows 7-8 machines using MDT2012. I have checked IEEE 802.1x network authenication protocol under features of the deployment share properties. I am trying to follow the guide on the deploymentguys.
I have my files on the boot image and can do a net start dot3svc, we are not using certificates at the moment for our 802.1x so I am skipping that line. doing a netsh lan add profile filename="X:\8021x\ Local Area Connection.xml " interface="Ethernet2"
does work. I am having a problem with the third step when I run the following command netsh lan set eapuserdata filename=x:\8021x\Wired-WinPE-UserData-PEAP-MSChapv2.xml allusers=yes interface="Ethernet2" All i get is error setting
user data for interface ethernet2, the operation is not supported.
How does one get 802.1x working in WinPE 4.0?
Heres the latest updated in this first post so you dont have to scroll way to the bottom to get the latest relevant information:
So here's the current situation and hopefully someone has seen it before.
My boot image has the prestart command set to x:\8021x\configure8021x.cmd. If i make a USB boot media this command will run and work with an 8021x wire plugged in. If I PXE boot with a non8021x
wire plugged in this command will run. If I PXE Boot with an 8021x
wire plugged in it does not run the command. If the boot image gets staged from the windows software center it
also will not run my command.
Does anyone know why the staged boot image and booting from PXE are not running my prestart command? It seems that during PXE and staged boot that the network initializes BEFORE it runs any prestart commands?

Well progress on this issue has been made. So why I was getting the operation not supported is because I was exporting our corporate 8021x LAN profile which gets put in place by group policy, which i assumed would work. So i unjoined the windows
7 machine from the domain and was then able to modify the LAN profile to be what is exactly in the documentation with images.
Then the above command works and I no longer get the operation is not supported and I am able to move on to the next steps which is to create a script file which contains the net start and the netsh commands i was using above to test it. Great!
Now my next issue comes up when the instructions tell me to modify the winpeshl.ini file which it says is located at X:\windows\System32\Winpeshl.ini. So I mount the boot.wim file that I did earlier and I browse to the location in question however
the first thing I notice is that when I open the winpeshl.ini file to go to modify it I expect to see:
[LAUNCHAPPS]
“%SYSTEMDRIVE%\sms\bin\i386\TsBootShell.exe”
Instead what I find is it says:
[LAUNCHAPPS]
%Windir%\system32\netstart.exe, -prompt%SYSTEMDRIVE%\sources\recovery\recenv.exe
So I thought ok I will create a copy of this file and rename it to winpeshl.ini.bak and then modify it to say what It says it should be in the instructions which is:
[LAUNCHAPPS]
winpeinit.exe
%SYSTEMDRIVE%\Windows\System32\wscript.exe, %SYSTEMDRIVE%\8021x\Configure8021xUser.wsf
“%SYSTEMDRIVE%\sms\bin\i386\TsBootShell.exe”
Next I unmount the boot.wim file and overwrite the copy I had. Next I update the distribution points and PXE boot a test machine. What I see next is
what I dont understand. Upon booting and hiting F8 to get to a command line I cd into x:\windows\system32\ and notice that I do indeed still have my winpeshl.ini.bak file so I open the winpeshl.ini file I had thought I modified earlier and low and behold
it contains this which is different when I look at it when I mounted the wim file:
[LAUNCHAPPS]
“%SYSTEMDRIVE%\sms\bin\i386\TsBootShell.exe”
So something is modifying this file and setting it this way effectively overwriting what I put in so that my script can run and configure the 8021x user settings.
Is there some updated documentation somewhere, how do I proceed from here??
The next steps after this would be to modify the unattend.xml file at a certain location to run the Configure8021xUserWindows.wsf script which does the winpe script just instead
of running from X: it runs from C: as it says in the documentation. But I can't move on to test this yet without getting the winpe part working.

T61s, T60s & older model unable to PXE boot to SCCM (MAC address problem)

Hi,
We have a series of T60, T61 & older machines that are unable to PXE boot to SCCM. The T400 & X series & other newer models can boot just fine.
After checking further, we realised that only a certain range of MAC addresses are unable to pxe boot i.e
00-1A-XXXXXXX
00-1C-XXXXXXX
range.. all the other range of MAC addresses are fine to boot via network.
The error when doing network boot is "bad or missing discovery server list"
Also, we are running on SCCM 2012 at the moment. Our branch office who is running SCCM 2008 can have all the machines - regardless of models & brand boot just fine.
Any ideas? Much appreciated.

did it obtain IP address from DHCP server? is DNS server address is configured in DHCP scope? can you ping using IP address?
if drivers are proper will suggest to update it in boot media & enable command line support to make it easy for deployment & troubleshooting.
Prashant Patil

Deploy UDI Windows 10 with SCCM 2012 R2 and MDT 2013 Update 1

Hi,
Trying use "User-Driven Installation" with
SCCM 2012
R2 CU4 and MDT
2013 Update 1 for deploy Windows
10.
Created MDT Task Sequences with
template "Client Task sequence"
and Deployment Method "User-Driven Installation".
When I try to deploy I have error like:
Failed to run the last action: Error in the task sequence. Execution of task sequence failed.
The operation cannot be completed because other resources are dependent on this resource. (Error: 00001389; Source: Windows)
ZTI deployment failed, Return Code = 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Unable to create WebService class InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Command line returned 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Process completed with exit code 5001 TSManager 22.04.2015 11:36:57 1160 (0x0488)
Part smsts.log
!--------------------------------------------------------------------------------------------! TSManager 22.04.2015 11:36:57 1160 (0x0488)
Expand a string: WinPEandFullOS TSManager 22.04.2015 11:36:57 1160 (0x0488)
Executing command line: smsswd.exe /run: cscript "%deployroot%\scripts\ztierrormsg.wsf" TSManager 22.04.2015 11:36:57 1160 (0x0488)
[ smsswd.exe ] InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
PackageID = '' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
BaseVar = '', ContinueOnError='' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
ProgramName = 'cscript "C:\_SMSTaskSequence\WDPackage\scripts\ztierrormsg.wsf"' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
SwdAction = '0001' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Set command line: Run command line InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Working dir 'not set' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Executing command line: Run command line InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Process completed with exit code 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Microsoft (R) Windows Script Host Version 5.12 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Copyright (C) Microsoft Corporation. All rights reserved. InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Microsoft Deployment Toolkit version: 6.3.8216.1000 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
ZTI deployment failed, Return Code = 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Unable to create WebService class InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Command line returned 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Process completed with exit code 5001 TSManager 22.04.2015 11:36:57 1160 (0x0488)
!--------------------------------------------------------------------------------------------! TSManager 22.04.2015 11:36:57 1160 (0x0488)
Failed to run the action: Error in the task sequence.
The operation cannot be completed because other resources are dependent on this resource. (Error: 00001389; Source: Windows) TSManager 22.04.2015 11:36:57 1160 (0x0488)
MP server http://sccm.domain.com. Ports 80,443. CRL=false. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting authenticator TSManager 22.04.2015 11:36:57 1160 (0x0488)
Set authenticator in transport TSManager 22.04.2015 11:36:57 1160 (0x0488)
Sending StatusMessage TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting message signatures. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting the authenticator. TSManager 22.04.2015 11:36:57 1160 (0x0488)
CLibSMSMessageWinHttpTransport::Send: URL: sccm.domain.com:80 CCM_POST /ccm_system/request TSManager 22.04.2015 11:36:57 1160 (0x0488)
Request was successful. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Set a global environment variable _SMSTSLastActionRetCode=5001 TSManager 22.04.2015 11:36:57 1160 (0x0488)
Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 22.04.2015 11:36:57 1160 (0x0488)
Clear local default environment TSManager 22.04.2015 11:36:57 1160 (0x0488)
Let the parent group (Gather Logs and StateStore on Failure) decides whether to continue execution TSManager 22.04.2015 11:36:57 1160 (0x0488)
The execution of the group (Gather Logs and StateStore on Failure) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager 22.04.2015 11:36:57 1160 (0x0488)
Failed to run the last action: Error in the task sequence. Execution of task sequence failed.
The operation cannot be completed because other resources are dependent on this resource. (Error: 00001389; Source: Windows) TSManager 22.04.2015 11:36:57 1160 (0x0488)
MP server http://sccm.domain.com. Ports 80,443. CRL=false. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting authenticator TSManager 22.04.2015 11:36:57 1160 (0x0488)
Set authenticator in transport TSManager 22.04.2015 11:36:57 1160 (0x0488)
Sending StatusMessage TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting message signatures. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting the authenticator. TSManager 22.04.2015 11:36:57 1160 (0x0488)
CLibSMSMessageWinHttpTransport::Send: URL: sccm.domain.com:80 CCM_POST /ccm_system/request TSManager 22.04.2015 11:36:57 1160 (0x0488)
Request was successful. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Executing command line: X:\WINDOWS\system32\cmd.exe /k TSBootShell 22.04.2015 11:37:31 696 (0x02B8)
The command completed successfully. TSBootShell 22.04.2015 11:37:31 696 (0x02B8)
Successfully launched command shell. TSBootShell 22.04.2015 11:37:31 696 (0x02B8)

MDT Updates for Windows 10 Technical Preview Build 10041
Если Вам помог чей-либо ответ, пожалуйста, не забывайте жать на кнопку "Предложить как ответ" или "Пометить как ответ".
http://zalozny.com.ua

PowerPC G5 will not soft boot

My 2.3GHz dual core PPC G5 running 10.4.8 will not soft boot that is shut down using the restart and shutdown menu. I have to hard boot it to get it to shut down (holding down the power button on the front of the G5). I have rebooted with the shift key in safe mode with no luck helping with this shutting down the computer glitch. Any ideas would be appreciated.

Sounds as though, if you have a place to put a full computer content clone,
that is something you should try to do; if at all possible. Or use a second
computer to facilitate accessing this ailing one in FireWire Target Disk Mode
and work on saving whatever you can (to another drive; a bootable clone)
so later on, you can wipe the hard disk drive and or replace it; should this
odd issue really only be a failing hard drive or corrupted data on a drive,
all your stuff may not be a total loss.
The original boot-installer disc (DVD) should have the Apple Hardware Test
on it; some of those installers require you to boot while holding Opt key
down in order to see the startup manager menu with AHT option, & etc.
There are others who require a different key to be pressed to access AHT.
Do you have a new replacement hard disk drive on hand so you can put
a new HDD inside the computer, format it, and install a completely new
OS X, to test the computer's hardware from? That may be a home option.
Good luck & happy computing!

E7250 will not PXE Boot with SCCM 2012 R2

Similar Messages

Maybe you are looking for