Jump to content


Search the Community

Showing results for tags 'PXE'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
    • Windows 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Official Forum Supporters
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Windows Server General
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests

  1. I'm trying to set up a task sequence to deploy Windows 10 via PXE. We have SCCM 2012 SP2 CU4 running on Server 2012 (not R2), with WDS 6.5.9200.16384, ADK 10.1.14393.0, and MDT 6.3.8443.1000. It's s single site and single server. I'm building the image from the official v1607 Enterprise ISO in a VM, entering System Audit Mode and doing some minimal config, and then using a freshly-built SCCM Capture Media ISO to handle the sysprep and image capture. Once captured, I create a basic (non-MDT) task sequence and deploy it as available to the unknown computers group for media and PXE only. If I have the task sequence join the domain and install the Configuration Manager client, everything works fine. I end up with an inaccessible defaultuser0 account on the machine, but I can log in with a domain account and do what I need to do / give it to a user. However, if I have the task sequence not join the domain, then I can't log into the machine after the image is deployed. It does the specialize pass and then does the "checking for critical updates" step, reboots, and then it gets to a login screen for "defaultuser0" and I can't log in. I've checked on the source VM after another fresh build from the installation ISO, and the defaultuser0 account seems to get created as part of the Windows 10 Enterprise v1607 installation. Even if I delete this account before capturing the image, the defaultuser0 account shows up after deployment. (We do everything in system audit mode and do not create any accounts.) I've tried setting the options within the task sequence to enable the admin account and set the password, but it's still not enabled and I can't do anything. If I try restarting in safe mode or enabling the command prompt, the only account listed/selectable is "defaultuser0" and I can't log into it at all. I've also tried adding net user command line steps to the task sequence to add a new local user and add it to the local administrators group, but this causes the task sequence to fail with 0x00000002. The task sequence that doesn't join the domain also does not install configuration manager - this task sequences is for machines that will be off the domain and off the network and not centrally managed. My guess is these steps can't run in the WinPE environment, but I was unable to find any relevant info in the smsts log. If I could get the task sequence / capture media to trigger the standard OOBE, I think that would work fine for our purposes. But I don't know how I can do that. The capture media doesn't seem to have any options I can control for the sysprep step. Could I just remove the "Apply Windows Settings" step in the task sequence entirely to achieve the same result? Again, we're not using MDT because this is a simple, bare bones image and task sequence. Our goal is to PXE boot and install Windows 10 Enterprise with updates and a few applications pre-installed. For domain-joined machines, they get policy after booting into the OS and get all the other stuff that they get. For machines off the domain, all we need is access to a local admin account so we can log in and do a light touch config, depending on each user. If this isn't possible without MDT, then we'll look at creating the MDT packages and task sequences. Thanks.
  2. I was wondering if anyone could give me some advice. I've come across a problem which Im struggling to get past. We have an sccm distribution point which has PXE enabled. Whenever a machine tries to PXE for some reason WDS just doesn't respond. Eventually it just times out. Where shall I begin :S any help would be awesome.
  3. I'm trying to set up a task sequence to deploy Windows 10 via PXE to both UEFI and BIOS clients. We have SCCM 2012 SP2 CU4 running on Server 2012 (not R2), with WDS 6.5.9200.16384, ADK 10.1.14393.0, and MDT 6.3.8443.1000. It's s single site and single server. PXE booting to BIOS clients seems to work fine. When PXE booting UEFI client, it loads the boot file and then throws out 0xc0000225 complaining about \Windows\Syetem32\boot\winload.efi . We're deploying the task sequence to the "Unknown Computers" group, and we only care about x64 clients. The task sequence has an x64 boot image, and is the last task sequence deployed. Do I have to do something special to allow both BIOS and UEFI clients to boot successfully at the same time (and using the same task sequence)? I came across this video which sets up policies and defines different files to load based on vendor class, but I haven't tried any of it yet. We're using SCCM and not WDS directly, so I wasn't sure if it was appropriate. Our DHCP server is the same as the SCCM site server, as well. The only DHCP options I have set are 003 (Router), 006 (DNS Servers), 015 (DNS Domain Name), and 060 (PXEClient). Thanks.
  4. So I find today that in trying to test a new TS that when booting PXE, I get an error screen from WDS that just only displays the error code 0xc000000f. Digging around, I've found some that say it's a WDS problem and another that says it's an SSL issue because the MP is SSL but the DP is not. One article states that if the MP is SSL, the DP also has to be using the PKI Cert as well instead of the self-signed. Another article mentions no problems with the DP being non-SSL. This is what I'm seeing in SMSPXE.log PXE::MP_GetList failed; 0x80070490 SMSPXE 5/16/2017 2:50:13 PM 5520 (0x1590) PXE::MP_LookupDevice failed; 0x80070490 SMSPXE 5/16/2017 2:50:13 PM 5520 (0x1590) PXE::MP_GetList failed; 0x80070490 SMSPXE 5/16/2017 2:50:13 PM 5520 (0x1590) PXE::MP_ReportStatus failed; 0x80070490 SMSPXE 5/16/2017 2:50:13 PM 5520 (0x1590) PXE Provider failed to process message. Element not found. (Error: 80070490; Source: Windows) SMSPXE 5/16/2017 2:50:13 PM 5520 (0x1590) Just looking for some insight on where to go with this.
  5. Hi guys, I'm actually struggling with a question. With Config Manager 1606, is there any way to have multiple boot images available, and be able to selct one during PXE? Regardless of all my attempts one boot image is automatically selected (the last distributed) I would be glad to read your ideas
  6. Hello! I'm currently having an issue deploying windows 10 via PXE. Its running SCCM 1606. The client will boot up get an IP and contact the WDS server but it wont find the WinPE image. The image is on the server. I've already removed and redistributed it. I've removed the PXE role from the DP and readded. I've even removed the DP role and readded it. The Boot Image is set to "Deploy this Boot image...". Still gives the same error. I am able to deploy the OS when I create deployment media. Then I'm just putting the boot image on a CD and still pulling down the OS. Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16792882" ServerName=""><Machine><ClientID>GUID:37705003-F519-4C59-9592-73B0F3E03976</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="WAL20010" OfferIDTime="10/20/2016 9:46:00 AM" PkgID="WAL0002D" PackageVersion="" PackagePath="http://WAL-SCCM-OSD1.ad.edc.org/SMS_DP_SMSPKG$/WAL00027" BootImageID="WAL00027" Mandatory="0"/></ClientIDReply> SMSPXE 10/20/2016 10:12:19 AM 2264 (0x08D8) 00:21:CC:64:94:F8, 70E6BA01-5125-11CB-80F6-BC22C629C2EE: found optional advertisement WAL20010 SMSPXE 10/20/2016 10:12:19 AM 2264 (0x08D8) Looking for bootImage WAL00027 SMSPXE 10/20/2016 10:12:19 AM 2264 (0x08D8) Any help would be greatly appreciated.
  7. PXE had been working, installed update today for the latest hotfix regarding KB4016483. After this update, PXE is no longer working and gives a BCD error when trying to boot. Hopefully someone has an answer for this as it is getting frustrating. The Windows Boot Configuration Data (BCD) file from the PXE Server does not contain a valid operating System entry. Ensure that the Server has boot Images installed for this architecture. File:\Tmp\x86x64{abc123}.bcd Error code: 0x0c0000098 I’ve read that this was a problem in 2012 and all suggest removing the pxe setting to remove WDS and then selecting it back to have WDS install itself again. I’ve repushed my boot images out there and I can see them in C:\RemoteInstall\SMSImages. SMSPXE.log shows the following few lines: InstallBootFilesForImage failed. 0x80004005 Warning: Failed to copy the needed boot binaries from the boot image C:\RemoteInstall\SMSImages\COP00005\boot.COP00005.wim. The operation completed successfully. (Error: 00000000; Source: Windows) Failed adding image C:\RemoteInstall\SMSImages\COP00005\boot.COP00005.wim. Will Retry.. Unspecified error (Error: 80004005; Source: Windows)
  8. Running into an issue that I cannot wrap my head around. We recently switched from HTTPS to HTTP and now clients will not talk to remote MPs or DPs on Secondary Sites. Talking back to MP on Stand Alone Primary works fine. I have revoked certs from CA and removed certs from servers but all of my Secondary sites are having issues with MPs and DPs (no PXE Boot Filename Received). Also removed Secondary Site, WDS, WSUS, all prereqs and reinstalled. Tried PXE booting to WDS + MDT 2013 and that works, but once SCCM PXE boot is turned on, I get the error. Boot images are distributed to DPs and Task Sequences have correct boot image assigned. Has anyone run into this type of problem before? Everything looks fine the mpsetup.log and mpcontrol.log files. MPControl.log STATMSG: ID=5460 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_MP_CONTROL_MANAGER" SYS=KEL-APPS.******.****** SITE=KEL PID=2840 TID=5188 GMTDATE=Mon Mar 13 16:23:37.001 2017 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 Successfully performed Management Point availability check against local computer. Applied D:P(A;CIOI;GA;;;SY)(A;CIOI;GA;;;BA)(A;CIOI;GR;;;LS)(A;CIOI;GR;;;S-1-5-17) to folder C:\Program Files\Microsoft Configuration Manager\Client SSL is not enabled. Call to HttpSendRequestSync succeeded for port 80 with status code 200, text: OK Sent summary record of SMS Management Point on ["Display=\\KEL-APPS.******.******\"]MSWNET:["SMS_SITE=KEL"]\\KEL-APPS.******.******\ to \\KEL-APPS.******.******\SMS_KEL\inboxes\sitestat.box\7d1dtt14.SUM, Availability 0, 733641724 KB total disk space , 681200880 KB free disk space, installation state 0. Http test request succeeded. STATMSG: ID=5460 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_MP_CONTROL_MANAGER" SYS=KEL-APPS.******.****** SITE=KEL PID=2840 TID=5188 GMTDATE=Mon Mar 13 16:28:37.013 2017 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 Successfully performed Management Point availability check against local computer. SMS_MP_CONTROL_MANAGER 3/13/2017 12:28:37 PM 5188 (0x1444)
  9. Hi All, I am unable to PXE boot from one of the site.This is first time we are trying to use PXE in this site. IP helper is enabled and WDS IP address is added in the IP helper. All other sites are working fine with PXE method.Only this site has issue. Below is the error message during PXE boot.I have attached the error screen shot PXE-T04: Illegal operation error PXE-E36: Error received from TFTP server PXE-MOF: Exiting Intel PXE-ROM Operating System not found Any help is much appreciated !! Thanks, Karthik
  10. Hello, I was able to PXE boot successfully and its able to pickup my WDS Server. I am not able to launch Task Sequence to begin deploying images? All I get is command prompt and it sits there? X:\windows\System32>wpeinit X:\windows\System32> cursor blinking? Help? TaskSequcenProvider log from C:\Program Files\Microsoft Configuration Manager\Logs <![LOG[setting status complete: status code = 0x0; ]LOG]!><time="04:29:19.994+300" date="01-18-2017" component="TaskSequenceProvider" context="" type="1" thread="5344" file="exterror.cpp:128"> <![LOG[[PID: 5220] Invoking method SMS_TaskSequence.ExportXml]LOG]!><time="04:29:20.451+300" date="01-18-2017" component="TaskSequenceProvider" context="" type="1" thread="5344" file="wmiprovider.cpp:333"> <![LOG[[PID: 5220] Done with method SMS_TaskSequence.ExportXml]LOG]!><time="04:29:20.453+300" date="01-18-2017" component="TaskSequenceProvider" context="" type="1" thread="5344" file="wmiprovider.cpp:352"> <![LOG[setting status complete: status code = 0x0; ]LOG]!><time="04:29:20.453+300" date="01-18-2017" component="TaskSequenceProvider" context="" type="1" thread="5344" file="exterror.cpp:128"> <![LOG[[PID: 5220] Invoking method SMS_TaskSequence.LoadFromXml]LOG]!><time="04:29:20.524+300" date="01-18-2017" component="TaskSequenceProvider" context="" type="1" thread="5344" file="wmiprovider.cpp:333"> <![LOG[[PID: 5220] Done with method SMS_TaskSequence.LoadFromXml]LOG]!><time="04:29:20.532+300" date="01-18-2017" component="TaskSequenceProvider" context="" type="1" thread="5344" file="wmiprovider.cpp:352"> <![LOG[setting status complete: status code = 0x0; ]LOG]!><time="04:29:20.532+300" date="01-18-2017" component="TaskSequenceProvider" context="" type="1" thread="5344" file="exterror.cpp:128"> <![LOG[[PID: 5220] Invoking method SMS_TaskSequence.LoadFromXml]LOG]!><time="04:29:28.724+300" date="01-18-2017" component="TaskSequenceProvider" context="" type="1" thread="5344" file="wmiprovider.cpp:333"> <![LOG[[PID: 5220] Done with method SMS_TaskSequence.LoadFromXml]LOG]!><time="04:29:28.731+300" date="01-18-2017" component="TaskSequenceProvider" context="" type="1" thread="5344" file="wmiprovider.cpp:352"> <![LOG[setting status complete: status code = 0x0; ]LOG]!><time="04:29:28.731+300" date="01-18-2017" component="TaskSequenceProvider" context="" type="1" thread="5344" file="exterror.cpp:128"> <![LOG[[PID: 5220] Invoking method SMS_TaskSequence.ExportXml]LOG]!><time="04:29:43.187+300" date="01-18-2017" component="TaskSequenceProvider" context="" type="1" thread="5344" file="wmiprovider.cpp:333"> <![LOG[[PID: 5220] Done with method SMS_TaskSequence.ExportXml]LOG]!><time="04:29:43.192+300" date="01-18-2017" component="TaskSequenceProvider" context="" type="1" thread="5344" file="wmiprovider.cpp:352"> <![LOG[setting status complete: status code = 0x0; ]LOG]!><time="04:29:43.192+300" date="01-18-2017" component="TaskSequenceProvider" context="" type="1" thread="5344" file="exterror.cpp:128"> <![LOG[[PID: 5220] Invoking method SMS_TaskSequence.ExportXml]LOG]!><time="04:29:48.819+300" date="01-18-2017" component="TaskSequenceProvider" context="" type="1" thread="5344" file="wmiprovider.cpp:333"> <![LOG[[PID: 5220] Done with method SMS_TaskSequence.ExportXml]LOG]!><time="04:29:48.821+300" date="01-18-2017" component="TaskSequenceProvider" context="" type="1" thread="5344" file="wmiprovider.cpp:352"> <![LOG[setting status complete: status code = 0x0; ]LOG]!><time="04:29:48.822+300" date="01-18-2017" component="TaskSequenceProvider" context="" type="1" thread="5344" file="exterror.cpp:128"> <![LOG[[C67EB48 PID:5220] Received shutdown request from WMI]LOG]!><time="04:30:29.884+300" date="01-18-2017" component="TaskSequenceProvider" context="" type="1" thread="5344" file="wmiprovider.cpp:399"> <![LOG[[FFD9EB48 PID:96] Initializing provider for namespace root\sms\site_GM1]LOG]!><time="04:31:24.783+300" date="01-18-2017" component="TaskSequenceProvider" context="" type="1" thread="4820" file="wmiprovider.cpp:90"> <![LOG[[FFD9EB48 PID:96] Initialization of provider for namespace root\sms\site_GM1 succeeded]LOG]!><time="04:31:24.783+300" date="01-18-2017" component="TaskSequenceProvider" context="" type="1" thread="4820" file="wmiprovider.cpp:107"> <![LOG[[PID: 96] Invoking method SMS_TaskSequence.ExportXml]LOG]!><time="04:31:24.787+300" date="01-18-2017" component="TaskSequenceProvider" context="" type="1" thread="6516" file="wmiprovider.cpp:333"> <![LOG[[PID: 96] Done with method SMS_TaskSequence.ExportXml]LOG]!><time="04:31:24.801+300" date="01-18-2017" component="TaskSequenceProvider" context="" type="1" thread="6516" file="wmiprovider.cpp:352"> <![LOG[setting status complete: status code = 0x0; ]LOG]!><time="04:31:24.801+300" date="01-18-2017" component="TaskSequenceProvider" context="" type="1" thread="6516" file="exterror.cpp:128"> <![LOG[[FFD9EB48 PID:96] Received shutdown request from WMI]LOG]!><time="04:32:32.918+300" date="01-18-2017" component="TaskSequenceProvider" context="" type="1" thread="6512" file="wmiprovider.cpp:399"> <![LOG[[5483EB48 PID:6536] Initializing provider for namespace root\sms\site_GM1]LOG]!><time="04:35:08.086+300" date="01-18-2017" component="TaskSequenceProvider" context="" type="1" thread="6480" file="wmiprovider.cpp:90"> <![LOG[[5483EB48 PID:6536] Initialization of provider for namespace root\sms\site_GM1 succeeded]LOG]!><time="04:35:08.086+300" date="01-18-2017" component="TaskSequenceProvider" context="" type="1" thread="6480" file="wmiprovider.cpp:107"> <![LOG[[PID: 6536] Invoking method SMS_TaskSequence.ExportXml]LOG]!><time="04:35:08.087+300" date="01-18-2017" component="TaskSequenceProvider" context="" type="1" thread="4108" file="wmiprovider.cpp:333"> <![LOG[[PID: 6536] Done with method SMS_TaskSequence.ExportXml]LOG]!><time="04:35:08.098+300" date="01-18-2017" component="TaskSequenceProvider" context="" type="1" thread="4108" file="wmiprovider.cpp:352"> <![LOG[setting status complete: status code = 0x0; ]LOG]!><time="04:35:08.098+300" date="01-18-2017" component="TaskSequenceProvider" context="" type="1" thread="4108" file="exterror.cpp:128"> <![LOG[[5483EB48 PID:6536] Received shutdown request from WMI]LOG]!><time="04:35:59.666+300" date="01-18-2017" component="TaskSequenceProvider" context="" type="1" thread="6840" file="wmiprovider.cpp:399">
  11. Hello, I have recently encountered extremely slow download of the Image.wim files while in PXE environment. I have verified that IIS is not being limited and in monitoring the switch port the server is connected to I have getting on between 8-10% utilization of the 1GB port and the Server Resource monitoring is showing a max network at 100Mbps. The Image.wim file is 8.2GB and is taking roughly 6-7 hours to download. This is not a question about TFTP transfer of the Boot.wim and have in placed the Reg change to increase the block size. I have verified IIS default site has no limit on transfer. Client BITS settings are not enabled on Default Client settings. Current Environment of Distribution Point Virtual Server running on ESXi 6.0 Windows Server 2012 R2 Standard OS SCCM 1606 Distribution Point Role 8.0 GB RAM Virtual Server running on ESXi 6.0 VMXNET3 Ethernet Adapter: Speed 10.Gbps, Driver version: 1.6.6.0 VMware tools version 10.0.0.3.000743 I have attached an SMSTS,log which verifies the proper Distribution Point is being contacted for the content. This log shows the Image.WIM download starting at 10:22 AM and the Apply Operating System not starting until 5:05PM. This may be a VMware/Server issue, but wanted to verify this could not be related to SCCM prior to sending this issue up the ladder. If anything other information is needed please let me know, I have been searching the internet and I am leaning towards the VMXNET3 adapter and VM tools upgrade. Thanks for any help. smsts DP.log
  12. Recently upgrade SCCM 2012 R2 to 1607. Ever since I have been unable to PXE boot Elite x2 1012 G1 tablets. I can do Probooks no problem. This UEFI thing is really messing me up. Nothing changed in DHCP. The Distribution Point is a 2012 R2 server, so I know that support PXE for UEFI. I am using Realtek USB FE Family Controller v 10.13.1115.2016 in the x64 Boot Image. The Boot Image version is 10.0.14393.0. I see the NBP file being downloaded successfully, quickly blips to another message, and goes back to the BIOS screen. I am using the USB dongle N7P47AA. Any advice? Is anyone doing this successfully? Thank you.
  13. have a situation where at a couple of sites that if you configure the machine for UEFI and attempt to PXE boot it only works the first time. Though if you take the computer to a different VLAN it will again PXE boot one time, but subsequent PXE boots fail. However if you configure the computer for BIOS it can PXE boot all day long. We also then have a site where they can not PXE boot at all if the machine is configured for UEFI. Though we have a number of sites that PXE boot with BIOS or UEFI without any problems whatsoever. The only correlation we have been able to make is that locations using Juniper EX4300 switches have the problem, where sites still using older EX4200 do not have the issue. Though we did find one site today that was experiencing the issue on an EX4200. We even opened an incident with Juniper and they have not been able to provide resolution and our networking team keeps pointing their fingers at the DPs, but all of our DPs are configured identically. We are on 1602 ip helpers/forwarders DHCP Scope options Option 66: 10.x.x.x Option 67: Boot\x64\wdsnbp.com edit - sorry title should have been "Can only UEFI PXE once, no longer PXE boots afterwards"
  14. I have SCCM deploying Windows 8.1 via a task sequence using x64 boot image but it only works when i set BIOS to legacy. This is an issue as we have some newer PCs which use TPM 2.0 and require UEFI. When i change bios to UEFI, i cannot PXE boot. I get the message 'Start PXE over ipv4' then it moves onto 'Start PXE over ipv6', but never actually PXE boots and just loops. Can anyone help?
  15. Hi, I have upgrade my environment (one primary server 7 distribution point, all server are server 2012 R2 standard) to Version 1606 Console version: 5.08412.1307 site version 5.0.8412.1000. Only after that my Eufi and legacy boot doesn't work any more, Error message on y distribution point is: RequestMPKeyInformation: Send() failed. SMSPXE 10/5/2016 1:09:38 PM 2920 (0x0B68) Failed to get information for MP: http://servername. 80004005. SMSPXE 10/5/2016 1:09:38 PM 2920 (0x0B68) reply has no message header marker SMSPXE 10/5/2016 1:09:38 PM 2920 (0x0B68) PXE::MP_LookupDevice failed; 0x80004005 SMSPXE 10/5/2016 1:09:38 PM 2920 (0x0B68) RequestMPKeyInformation: Send() failed. SMSPXE 10/5/2016 1:09:38 PM 2920 (0x0B68) Failed to get information for MP: http://servername. 80004005. SMSPXE 10/5/2016 1:09:38 PM 2920 (0x0B68) reply has no message header marker SMSPXE 10/5/2016 1:09:38 PM 2920 (0x0B68) Failed to send status message (80004005) SMSPXE 10/5/2016 1:09:38 PM 2920 (0x0B68) Failed to send the status message SMSPXE 10/5/2016 1:09:38 PM 2920 (0x0B68) PXE::MP_ReportStatus failed; 0x80004005 SMSPXE 10/5/2016 1:09:38 PM 2920 (0x0B68) PXE Provider failed to process message. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 10/5/2016 1:09:38 PM 2920 (0x0B68) What have I done: untick the enable PXE checkbox on the distribution point. Answer yes that you want to remove the Windows Deployment service. remove boot images from your distribution point After 5 minutes delete %windir%\temp check with server manager. If WDS is done uninstalling there is a reboot pending. Reboot. check if the remote install folder is located on your system. If it is delete it. If it fails to delete due to permission issues with the SMSTempBootFiles path, delete all folders except that one and then rename the remote install folder something else. reboot Add the PXE point again by checking the box on the distribution point properties. Check the distrmgr.log and see if the remote install folder reappears.. Replicate the boot image to the DP again. After that create a new Boot image with the latest ADK 10 version and distribute it to the distribution point But still the same error, have somebody an idea? Thanks a lot already..
  16. Hello all, I hope I can lay this out clearly so someone can understand what's happening here and help out. We've had OS Deployment working for a couple of years now with no real issues. We have about 30 offices nation wide. We have a single Site and a Distribution Point at each location. The DPs are PXE enabled. They are all virtualized except two, which are located IN ADDITION to the primary DP VMs in our two largest offices. Both of these locations have multiple subnets. They both had speed issues on day one when we enabled OSD. After much troubleshooting and trying every suggestion we tried, we finally got "regular speed" by installing a physical DP on the subnet that the local IT staff were on. Two weeks ago we upgraded the WAN circuits in the 2nd office. We replaced the router and all switches. Because this location now houses our disaster recovery site, we rejiggered the network and added a new subnet that is now where all the clients are located. Now we have the same issue we had when we setup OSD. It took over 30 hours to image a single system. We have moved the physical DP to the new subnet, but PXE is not working now. I can get PXE working, so I'm really curious about the slow deployment across subnets in the same office. Our setup: HQ, 31 Subnets, virtual Site Server & DP, physical DP** on ITs subnet 31 remote offices with a single subnet and VM DP 1 remote office with 3 subnets a VM DP and a Physical DP** on client subnet ** Without 2nd DP imaging takes more than a day.
  17. Hi, Our main site has multiple locations, and a few of them within the US support and deploy our images from the main office via SCCM 2012 R2 SP1 CU3. We have been troubleshooting some network issues recently, that I believe we have cleaned up now. However during some deployment testing, we are experiencing some inconsistent results that I hope someone may have an answer or idea of where to look. -Created 4 VMs setup for OSD (testing/troubleshooting) all of the VMs are set for PXE. -All machines boot up and get to the PXE menu and populate the available task sequences with no issues. -Our guy has reported that he started the same task sequence to all the VMs at same time manually, where they all will download the boot image as so, and move forward onto the imaging process. -Anywhere from 2 out of the 4, to 3/4 of the VMs startup just fine and run the task sequence to completion. The other 1-2 (depending on the test run, it varies) will reboot and then launch within winPE and start the task sequence. I could be wrong here, but I believe usually when a TS reboots it is because the boot image from the PXE or boot media differs from the boot image assigned to the TS which makes sense. Though, given nothing is different from one VM to the other, the TS is the same...which has me scratching my head. My other theory(keyword theory) is our user is experiencing this upon the boot up itself while downloading the boot image from the bios menu. VM 2 is requesting this boot image that maybe "busy" at that very second due to VM 1 requesting it as well, forcing sccm to use another available boot image? - more than likely wrong here, nor does that really make sense to me, I'm just picking straws at this point. Has anyone run into this, or seen it before? Any thoughts, things to try? Thank you
  18. Hi Guys, I've been building my Win10 image lately and for some reason SCCM refuses to complete any OSD Task Sequences successfully (on Win 10, or our old Win8.1 TS). It seems to be failing to setup the SCCM Client and then rebooting to a half built OS. smsts.log is here: https://pastee.org/7dkq5 I don't have a CCMSetup.log, it doesn't get that far. Any ideas? The key line that seems to stick out for me is: <![LOG[The action (Setup Windows and Configuration Manager) requested a retry]LOG]!><time="13:16:09.927-60" date="08-14-2015" component="TSManager" context="" type="1" thread="1260" file="engine.cxx:271"> <![LOG[Reboot to local harddisk]LOG]!><time="13:16:09.927-60" date="08-14-2015" component="TSManager" context="" type="1" thread="1260" file="engine.cxx:469"> I've been trying to work this out for the past few days now and I'm tearing my hair out Thanks!!
  19. Having an issue with one of our DP's. It will pxe boot and get to the loading files screen, the progress bar hangs loading the boot.wim. Will sit there for hours and never get to the next step.. I have this same boot.wim on 3 other DP's and no issues with it. Any ideas? Things I have done: Removed the image removed pxe rebooted numerous times enabled pxe distribute the boot.wim back to the DP. Nothing works. 2012 R2 SP1 CU3
  20. Hey Everyone, When I've run in to hitches in the past this has been a great place to find information related to the problems I've experienced, so I'm hoping someone can help me out with the problem I'm currently having. I've been working on getting Operating System Deployment functioning on the newly-implemented SCCM server in my organization by following the instructions in Anyweb's guide. However I'm encountering an issue at the PXE boot portion of this. The SCCM 2012 server is virtualized, but is not using infiniband. The boot images have been successfully distributed, are checked with the "Deploy this boot image from the PXE-enabled distribution point" option. The distribution point itself has PXE support enabled, along with all of the other options for unknown computers, responding to PXE requests, requiring a password, etc. The WDS role was installed after setting this up, as per usual. There were a few indications of possible issues in the distmgr.log now that I look back at it (I presume if it's in red it's failure/error?) and I'll attach that in a moment. But I wasn't looking for anything but the WDS at the time. Anyway, so WDS is installed and since the DHCP server is not on the same host so I've set the appropriate DHCP options for PXE clients to access this. Attempting to PXE boot from a physical machine on another subnet simply results in the PXE client getting the DHCP address and then starting the TFTP, but then immediately exiting with "PXE-M0F: Exiting Intel Boot Agent" and proceeds to the next boot device. Not wanting to complicate things by traversing subnets just yet, I took that out of the equation and added a VM on the same subnet as the server. When I tried to PXE boot from that client it starts the TFTP process and then returns PXE-T01: The Specified file was not found, PXE-E3B: TFTP Error - File Not Found, PXE-M0F: Exiting Intel PXE ROM, etc. Taking a step back, I have attempted to troubleshoot the TFTP process and see what the hang-up here is. Checking the SMSPXE.log shows that it finds the image (though there are some errors here that don't make sense "Failed to copy the needed boot binaries from the boot image. The operation completed successfully. Error: 00000000"), after these errors it seems to find the images, load the required API, open the image, read the image file and then subsequently validate it. I check the REMINST folder for the appropriate files, they're there. So maybe the TFTP process is failing? On another system on the same subnet, I attempted to use the TFTP client to grab one of the PXE files from the SCCM server using the same information I supplied to the DHCP options. The only result is a long pause and a "TImeout occurred, Connect request failed" message. Trying the same command from the SCCM server itself grabs the file just fine. I try again from the TFTP client on a remote machine and attempt to grab a file that I know doesn't exist on the SCCM server. No pause, it errors out immediately saying "Error on server : The specified file was not found. Connect request failed". So, this confirms to me that it is at least communicating with the SCCM server at the TFTP level, but it's not getting the file that should clearly be there. I tried my first test with the TFTP client again, this time with wireshark running. It seends a read request on the correct file, and it looks like the SCCM server starts returning Data packets. The TFTP client continues to send read requests, and the SCCM server continues to send data packets until the TFTP client system sends an error code saying that there's been a timeout on receive. The SCCM server stops sending data packets shortly thereafter. The test file is only about 25k and should not present an issue of this sort. In my troubleshooting I've tried removing the WDS role through SCCM and then re-adding it as some guides have recommended (purging the windows temp folder in the process), I've turned off the firewalls of the computers I'm working with without any change in behavior, I've deleted the distributions for the boot files and re-distributed them/validated them. Looked for issues in the SCCM log files during the PXE process, the only issues I've found were from the setup of these - nothing during the actual process - see logs. I've checked and re-checked the settings that I've configured for these images and their distribution through SCCM. Sorry for the wall of text, wanted to provide as much info as I could as to what was happening and what I've done. I have yet to attempt this with a physical machine on the same subnet, but am working on that now. Any help is much appreciated! SMSPXE.log distmgr.log
  21. Hi, I've been reading a lot on these forums the last couple of weeks, mostly regarding SCCM etc, but at the moment I've got an issue I haven't been able to wrap my head around. We're using a standard win 2k8 r2 domain environment. This environment used to contain a server with MDT 2010 and WDS 2008 (server 2008 r2), used for deploying win7 etc, the environment used to work pretty well. Then somebody thought it was a good idea to buy some tablet computers, to be specific the HP Elitepad 900. Specs for this tablet computer indicate it is able to do PXE boot (there is an ethernet port on the docking), but due to limitations this only works using UEFI (BIOS not supported). After a lot of reading I found that wds 2008 does not support x86 uefi, so the server was upgraded (no fresh install) to windows server 2012 (with wds 2012) and mdt 2012 update 1. Legacy computers are still able to PXE boot correctly (and complete installation), but UEFI machines, or machines starting in UEFI mode can't do this at the moment. What happens is: - boot the computer over network (or tablet), we mainly want the elitepad to get working (x86 uefi), but I've also tried booting another machine using x64 UEFI with the same result - the following is shown: >>Start PXE over IPv4, Press [ESC] to exit... Station IP address is x.x.x.x Server IP address is x.x.x.x NBP filename is boot\x86\wdsmgfw.efi NBP filesize is xxxxx bytes Downloading NBP File Succeed to download NBP file. [EDIT] Not sure if it's NEP or NBP file, not very clear on the screen Then the screen changes and I see: Windows Depoyment Services (server IP: x.x.x.x) Contacting Server (x.x.x.x): - (this is like turning / - \ - / - \ ...) ESC= Exit After a while (timeout)the computer shows: Windows Deployment Services encountered an error: Error Code: 0x102 ENTER=Reboot What I've tried/changed so far: Changed the NBP filename in DHCP options, it used to be boot\x86\wdsnbp.com (when not using UEFI), before changing this I simply got network error when trying to network boot. Added NIC (and other) drivers in WDS 2012, regenerated the boot image afterwards etc. Tried reinstalling WDS on a newly installed windows server 2012 (without mdt) in standalone mode. Other stuff I can't think of at the moment :-) PXE booting of our SCCM 2012 update 1 (only used for updates & endpoint protection at the moment), but with the same result Any thoughts/ideas? I have a feeling I'm overlooking something stupid, but then again it may not be stupid. Thank you [EDIT] Sorry I should have posted this in http://www.windows-noob.com/forums/index.php?/forum/43-windows-deployment-services-wds/ [/EDIT]
  22. currently im getting the following error: PXE-T01: The specified file was not found PXE-E3b: TFTP Error- File Not found PXE-M0F: Exiting Intel PXE ROM. I think may have the wrong file specified by DHCP. currently I'm telling it to give out "pxeboot.com". Our DHCP server is running solaris. So I need to provide the tftp path to this bootfile which I dont know how to find. A UNC path will not work. Any suggestions?
  23. Have a slight problem when trying to PXE boot a UEFI system. I can get it to PXE but then get it looping saying its looking for a boot image. I've made sure the boot images are copied to the DP and are enabled to deploy from PXE DP. The server is a server 2012 R2 DP so presume that wouldn't be an issue? any ideas gratefully received.
  24. Hello, The Task Sequence that was deploying W7 with SCCM 2012 SP1 has stopped to deploying the Lenovo X240 laptop. The Laptop must load WinPE on Workgroup & PXE When I get on F8 to get an ipconfig, nothing but the message "configuration IP" is dysplayed, then WinPE reboot. I don't know if the laptop has joined the workgroup The smsts.log show 2 mains errors : Failed to download pxe variable file. Code(0x00000001) TSPxe 24/07/2015 16:09:06 1176 (0x0498) PxeGetPxeData failed with 0x80004005 TSPxe 24/07/2015 16:09:06 1176 (0x0498) RegOpenKeyExW failed for Software\Microsoft\SMS\Task Sequence TSBootShell 24/07/2015 16:09:06 784 (0x0310) GetTsRegValue() failed. 0x80070002. TSBootShell 24/07/2015 16:09:06 784 (0x0310) The driver are the following : http://support.lenovo.com/us/en/downloads/ds038819 Please, Help me.
  25. *****Resolved***** Up until a couple days ago, we had no problem imaging our Dell desktops. From OptiPlex 780's all the way up to our new 3020's. Yesterday we received 5 new 3020's that will not image at all. Most of the time it doesn't even get to the point where we can hit F12 to start. Occasionally we do get the F12 screen and it looks like it's going to start, but then freezes up and fails. I've attached a few images to show my progress. I've looked at all the different settings I can think of in SCCM and on the individual pc's and don't see anything different. Any idea what is going on here? *****Solution******* I created a new WinPE .wim, changed out task sequence to use the new .wim, applied the changes. Then changed it back to the original .wim we were using and everything started to work. Not sure why, but it works. ******Failed Solution******* So that didn't work. It worked for a few devices but then stopped working again.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.