Jump to content


Search the Community

Showing results for tags 'PXE'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • Official Forum Supporters
    • 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
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Windows Server 2008
    • Windows Server 2012
    • Windows Server 2016
    • Windows Server 2019
    • 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


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 115 results

  1. 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"
  2. 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">
  3. 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?
  4. 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.
  5. 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..
  6. 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.
  7. 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
  8. 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
  9. Hello, I am trying to PXE boot surface pro 4 and for some reason it does not boot. I get the attached message. It tries to PXE over IP v4, then reaches my correct DP that has PXE and WDS, it finds the correct NBP file SMSBoot\x64\wdsnbp.com (this is specified in DHCP option), it appears to be downloading and NBP file is successfully downloaded. Then without prompting to press Enter key for PXE boot, it moves to IPV6. I have tried below but no luck Upgrade firmware to latest disable secure boot Removed DHCP option - but this time it doesn't even finds my PXE server Verified and made sure MAC address of network adapter is not registered with SCCM DB Tried docking station and no luck I can PXE boot a desktop on same network with no issues. Any suggestions would be helpful Thanks.
  10. 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
  11. Hi all, I have looked all over the Internet and found people with the exact same problem, but I can't seem to fix this issue with the suggested solutions. Suddenly PXE boot stopped working. It worked for a couple of months. No changes have been made on SCCM, Firewall or DHCP but PXE suddenly stopped working. Error message (also see attached file): Your PC needs to be repaired The Boot Configuration Data for your PC is missing or contains errors. File: \boot\bcd Error code: 0x000000f You'll need to use the recovery tools on your installation media. If you... Our situation: SCCM 2012 R2 9 Distribution Points on different sites. PXE is failing on all remote locations. DHCP Options are all set and are not changed since we've set it up. Option 67 is: \smsboot\x64\wdsnbp.com In the Boot Image Properties > Dara Source the option "Deploy this boot image from the PXE-enabed distribution point" is checked. Both x86 and x64 Boot Images are deployed on the DP. We do have a custom Boot image though, only x64 as we don't deploy x86 systems. We only deploy x64 Windows 8.1. in the SMSPXE.log file I don't see any errors. There is, however, one part that keeps coming back (change MAC address): 00:12:FB:xx:xx:xx, 00000000-0000-0000-0000-0012FBB03B27: device is not in the database. 00:12:FB:xx:xx:xx, 00000000-0000-0000-0000-0012FBB03B27: Not serviced. 00:12:FB:xx:xx:xx, 00000000-0000-0000-0000-0012FBB03B27: Not serviced. 00:12:FB:xx:xx:xx, 00000000-0000-0000-0000-0012FBB03B27: Not serviced. 00:12:FB:xx:xx:xx, 00000000-0000-0000-0000-0012FBB03B27: Not serviced. So the SMSPXE.log file is full of these. My guess is that this has something to do with the problem. Any more suggestions? Thank you.
  12. 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!!
  13. 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.
  14. 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.
  15. I have some new HP Pro One 600 All In One units I am trying to pxe boot to run a task sequence on. Everything is normal until it starts to configure network settings, once that pop-up goes away it reboots. When I hit f8 and run an ipconfig it does not have an IP or anything. I am pretty sure I have the right drivers for the nic but could be wrong. When checking the smsts.log I get the following four errors, in order: Failed to download pxe variable file. Code(0x00000001) PxeGetPxeData failed with 0x80004005 RegOpenKeyExW failed for Software\Microsoft\SMS\Task Sequence GetTsRegValue() failed. 0x80070002. Hopefully it is just a checkbox somewhere but have been scratching my head with this for sometime. I am currentling imaging other machines right now with the same task sequence. Thanks for the help.
  16. Hi Guys! I'm wondering if someone could help me with a really frustrating issue I'm having with SCCM. I'll give you a quick of overview of the environment. - The Laptop we're using is brand new out of the box "HP Elitebook 755 G2" - We are trying to build a 64bit Windows 7 image on the Laptop and then Capture that image to use for the 20+ HP Books we have. - The Task Sequences have already been created and used on other machines so I'm fairly sure it will work once we get the drivers packaged into the TS (For now I just want to test that it will boot up and begin the TS) - Regardless of whether I set "Enable Unknown Computer Support" in the PXE Service Point (With a Restart of the Service) The PC will not boot from PXE, it will just say that "No Bootfile was received" - I have imported the PC into the console through the Computer Association option with SCCM. Does the laptop have to have the SCCM Client on to be able to PXE Boot to the Task Sequence? Something I've never really been able to tell or not! Presumably this isn't the case given the option to "Enable Unknown Computer Support" I'm not entirely sure which direction I am meant to go from here, I've tried looking on various forums etc. but all seem to inform me to do the same thing which hasn't been effective for me. I'd really appreciate any tidbits of information too help me discover the answer! Thanks, Josh
  17. Hi Guys! I'm wondering if someone could help me with a really frustrating issue I'm having with SCCM. I'll give you a quick of overview of the environment. - The Laptop we're using is brand new out of the box "HP Elitebook 755 G2" - We are trying to build a 64bit Windows 7 image on the Laptop and then Capture that image to use for the 20+ HP Books we have. - The Task Sequences have already been created and used on other machines so I'm fairly sure it will work once we get the drivers packaged into the TS.
  18. Hi Guys! I'm wondering if someone could help me with a really frustrating issue I'm having with SCCM. I'll give you a quick of overview of the environment. - The Laptop we're using is brand new out of the box "HP Elitebook 755 G2" - We are trying to build a 64bit Windows 7 image on the Laptop and then Capture that image to use for the 20+ HP Books we have. - The Task Sequences have already been created and used on other machines so I'm fairly sure it will work once we get the drivers packaged into the TS.
  19. Hi community, I'm quite stuck here and cannot find a solution for my problem. I've just added a new boot image (Win7x64) and all I want to do is "add" drivers to the boot image. So I went to - System Center Configuration Manager / Site Database / Computer Management / Operating System Deployment / Drivers right clicked the driver and selected add to boot image. But I cannot select a boot image because the list below is just plain empty although I've added boot images (Win7x64 enterprise (Selected the boot.wim image 2 (Microsoft Windows Setup x64)) - this image is deployed and PXE Deployment is enabled (in the boot image properties). Am I missing something? Thanks for your feedback - best regards
  20. i am having inconsistent application installation during PXE deployment and the logs are not helping me out so i was hoping someone else might have an idea. i can image one laptop and get a few missing applications one time and re-image and get a few different applications missing. for each application that fails i see the following Unspecified error (Error: 80004005; Source: Windows) SMSTS log link <![LOG[ Setting Server Certificates.]LOG]!><time="09:51:35.001+240" date="03-24-2015" component="InstallApplication" context="" type="0" thread="2488" file="utils.cpp:6171"> <![LOG[ Setting Authenticator.]LOG]!><time="09:51:35.001+240" date="03-24-2015" component="InstallApplication" context="" type="0" thread="2488" file="utils.cpp:6178"> <![LOG[set authenticator in transport]LOG]!><time="09:51:35.002+240" date="03-24-2015" component="InstallApplication" context="" type="0" thread="2488" file="libsmsmessaging.cpp:7734"> <![LOG[ Setting Media Certificate.]LOG]!><time="09:51:35.002+240" date="03-24-2015" component="InstallApplication" context="" type="0" thread="2488" file="utils.cpp:6195"> <![LOG[sending StatusMessage]LOG]!><time="09:51:35.031+240" date="03-24-2015" component="InstallApplication" context="" type="1" thread="2488" file="libsmsmessaging.cpp:4023"> <![LOG[setting message signatures.]LOG]!><time="09:51:35.032+240" date="03-24-2015" component="InstallApplication" context="" type="0" thread="2488" file="libsmsmessaging.cpp:1295"> <![LOG[setting the authenticator.]LOG]!><time="09:51:35.032+240" date="03-24-2015" component="InstallApplication" context="" type="0" thread="2488" file="libsmsmessaging.cpp:1325"> <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: SR0SCCM03.domain.com:80 CCM_POST /ccm_system/request]LOG]!><time="09:51:35.034+240" date="03-24-2015" component="InstallApplication" context="" type="1" thread="2488" file="libsmsmessaging.cpp:8604"> <![LOG[Request was successful.]LOG]!><time="09:51:35.062+240" date="03-24-2015" component="InstallApplication" context="" type="0" thread="2488" file="libsmsmessaging.cpp:8939"> <![LOG[install application action cannot continue. ContinueOnErrorFlag is set to false.]LOG]!><time="09:51:35.062+240" date="03-24-2015" component="InstallApplication" context="" type="3" thread="2488" file="installapplication.cpp:898"> <![LOG[hrInstallation, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\installapplication.cpp,899)]LOG]!><time="09:51:35.062+240" date="03-24-2015" component="InstallApplication" context="" type="0" thread="2488" file="installapplication.cpp:899"> <![LOG[pInstall->InstallApplications(saAppNames, sContinueOnError), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\main.cpp,277)]LOG]!><time="09:51:35.228+240" date="03-24-2015" component="InstallApplication" context="" type="0" thread="2488" file="main.cpp:277"> <![LOG[install Static Applications failed, hr=0x80004005]LOG]!><time="09:51:35.228+240" date="03-24-2015" component="InstallApplication" context="" type="3" thread="2488" file="main.cpp:277"> <![LOG[Process completed with exit code 2147500037]LOG]!><time="09:51:35.232+240" date="03-24-2015" component="TSManager" context="" type="1" thread="3804" file="commandline.cpp:1123"> <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="09:51:35.232+240" date="03-24-2015" component="TSManager" context="" type="1" thread="3804" file="instruction.cxx:804"> <![LOG[Failed to run the action: Install Java. Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="09:51:35.233+240" date="03-24-2015" component="TSManager" context="" type="3" thread="3804" file="instruction.cxx:895"> <![LOG[MP server http://SR0SCCM03.domain.com. Ports 80,443. CRL=false.]LOG]!><time="09:51:35.234+240" date="03-24-2015" component="TSManager" context="" type="1" thread="3804" file="utils.cpp:5881"> <![LOG[setting authenticator]LOG]!><time="09:51:35.242+240" date="03-24-2015" component="TSManager" context="" type="1" thread="3804" file="utils.cpp:5903"> <![LOG[set authenticator in transport]LOG]!><time="09:51:35.242+240" date="03-24-2015" component="TSManager" context="" type="0" thread="3804" file="libsmsmessaging.cpp:7734"> <![LOG[sending StatusMessage]LOG]!><time="09:51:35.261+240" date="03-24-2015" component="TSManager" context="" type="1" thread="3804" file="libsmsmessaging.cpp:4023"> <![LOG[setting message signatures.]LOG]!><time="09:51:35.262+240" date="03-24-2015" component="TSManager" context="" type="0" thread="3804" file="libsmsmessaging.cpp:1295"> <![LOG[setting the authenticator.]LOG]!><time="09:51:35.262+240" date="03-24-2015" component="TSManager" context="" type="0" thread="3804" file="libsmsmessaging.cpp:1325"> <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: SR0SCCM03.domain.com:80 CCM_POST /ccm_system/request]LOG]!><time="09:51:35.264+240" date="03-24-2015" component="TSManager" context="" type="1" thread="3804" file="libsmsmessaging.cpp:8604"> <![LOG[Request was successful.]LOG]!><time="09:51:35.287+240" date="03-24-2015" component="TSManager" context="" type="0" thread="3804" file="libsmsmessaging.cpp:8939"> <![LOG[set a global environment variable _SMSTSLastActionRetCode=-2147467259]LOG]!><time="09:51:35.288+240" date="03-24-2015" component="TSManager" context="" type="0" thread="3804" file="executionenv.cxx:668"> <![LOG[set a global environment variable _SMSTSLastActionSucceeded=false]LOG]!><time="09:51:35.288+240" date="03-24-2015" component="TSManager" context="" type="0" thread="3804" file="executionenv.cxx:668"> <![LOG[Clear local default environment]LOG]!><time="09:51:35.289+240" date="03-24-2015" component="TSManager" context="" type="0" thread="3804" file="executionenv.cxx:807"> <![LOG[The execution engine ignored the failure of the action (Install Java) and continues execution]LOG]!><time="09:51:35.293+240" date="03-24-2015" component="TSManager" context="" type="2" thread="3804" file="instruction.cxx:962"> <![LOG[MP server http://SR0SCCM03.domain.com. Ports 80,443. CRL=false.]LOG]!><time="09:51:35.294+240" date="03-24-2015" component="TSManager" context="" type="1" thread="3804" file="utils.cpp:5881"> <![LOG[setting authenticator]LOG]!><time="09:51:35.305+240" date="03-24-2015" component="TSManager" context="" type="1" thread="3804" file="utils.cpp:5903"> <![LOG[set authenticator in transport]LOG]!><time="09:51:35.305+240" date="03-24-2015" component="TSManager" context="" type="0" thread="3804" file="libsmsmessaging.cpp:7734"> <![LOG[sending StatusMessage]LOG]!><time="09:51:35.323+240" date="03-24-2015" component="TSManager" context="" type="1" thread="3804" file="libsmsmessaging.cpp:4023"> <![LOG[setting message signatures.]LOG]!><time="09:51:35.325+240" date="03-24-2015" component="TSManager" context="" type="0" thread="3804" file="libsmsmessaging.cpp:1295"> <![LOG[setting the authenticator.]LOG]!><time="09:51:35.325+240" date="03-24-2015" component="TSManager" context="" type="0" thread="3804" file="libsmsmessaging.cpp:1325"> <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: SR0SCCM03.domain.com:80 CCM_POST /ccm_system/request]LOG]!><time="09:51:35.326+240" date="03-24-2015" component="TSManager" context="" type="1" thread="3804" file="libsmsmessaging.cpp:8604">
  21. Hi Forum, Please help! Here's the story. When we had our SCCM installed it seems that some bright spark decided to put a trial version of SQL on the server its installed on. Last week the trial ran out and reporting stopped and then no one could connect via the consoles. Our apps team fixed this and we can now log into SCCM 2012 but we cannot build any machines via PXE. Any suggestions? I've checked the SMSPXE.log and see errors: Loaded D:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll SMSPXE 24/03/2015 10:36:17 8428 (0x20EC) Opening image file D:\RemoteInstall\SMSImages\MON0006E\winpe8.MON0006E.wim SMSPXE 24/03/2015 10:36:17 8428 (0x20EC) Found Image file: D:\RemoteInstall\SMSImages\MON0006E\winpe8.MON0006E.wim PackageID: MON0006E ProductName: Microsoft® Windows® Operating System Architecture: 0 Description: Microsoft Windows PE (x86) Version: Creator: SystemDir: WINDOWS SMSPXE 24/03/2015 10:36:17 8428 (0x20EC) Closing image file D:\RemoteInstall\SMSImages\MON0006E\winpe8.MON0006E.wim SMSPXE 24/03/2015 10:36:17 8428 (0x20EC) Failed adding image D:\RemoteInstall\SMSImages\MON0006E\winpe8.MON0006E.wim. Will Retry.. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 24/03/2015 10:36:17 8428 (0x20EC) Loaded D:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Opening image file D:\RemoteInstall\SMSImages\MON00004\boot.MON00004.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Found Image file: D:\RemoteInstall\SMSImages\MON00004\boot.MON00004.wim PackageID: MON00004 ProductName: Microsoft® Windows® Operating System Architecture: 0 Description: Microsoft Windows PE (x86) Version: Creator: SystemDir: WINDOWS SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Closing image file D:\RemoteInstall\SMSImages\MON00004\boot.MON00004.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Failed adding image D:\RemoteInstall\SMSImages\MON00004\boot.MON00004.wim. Will Retry.. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Loaded D:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Opening image file D:\RemoteInstall\SMSImages\MON00005\boot.MON00005.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Found Image file: D:\RemoteInstall\SMSImages\MON00005\boot.MON00005.wim PackageID: MON00005 ProductName: Microsoft® Windows® Operating System Architecture: 9 Description: Microsoft Windows PE (x64) Version: Creator: SystemDir: WINDOWS SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Closing image file D:\RemoteInstall\SMSImages\MON00005\boot.MON00005.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Failed adding image D:\RemoteInstall\SMSImages\MON00005\boot.MON00005.wim. Will Retry.. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Loaded D:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Opening image file D:\RemoteInstall\SMSImages\MON00006\WinPE.MON00006.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Found Image file: D:\RemoteInstall\SMSImages\MON00006\WinPE.MON00006.wim PackageID: MON00006 ProductName: Microsoft® Windows® Operating System Architecture: 0 Description: Microsoft Windows PE (x86) Version: Creator: SystemDir: WINDOWS SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Closing image file D:\RemoteInstall\SMSImages\MON00006\WinPE.MON00006.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Failed adding image D:\RemoteInstall\SMSImages\MON00006\WinPE.MON00006.wim. Will Retry.. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Loaded D:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Opening image file D:\RemoteInstall\SMSImages\MON00007\WinPE.MON00007.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Found Image file: D:\RemoteInstall\SMSImages\MON00007\WinPE.MON00007.wim PackageID: MON00007 ProductName: Microsoft® Windows® Operating System Architecture: 9 Description: Microsoft Windows PE (x64) Version: Creator: SystemDir: WINDOWS SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Closing image file D:\RemoteInstall\SMSImages\MON00007\WinPE.MON00007.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Failed adding image D:\RemoteInstall\SMSImages\MON00007\WinPE.MON00007.wim. Will Retry.. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Loaded D:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Opening image file D:\RemoteInstall\SMSImages\MON0000E\winpe.MON0000E.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Found Image file: D:\RemoteInstall\SMSImages\MON0000E\winpe.MON0000E.wim PackageID: MON0000E ProductName: Microsoft® Windows® Operating System Architecture: 0 Description: Microsoft Windows PE (x86) Version: Creator: SystemDir: WINDOWS SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Closing image file D:\RemoteInstall\SMSImages\MON0000E\winpe.MON0000E.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Failed adding image D:\RemoteInstall\SMSImages\MON0000E\winpe.MON0000E.wim. Will Retry.. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Loaded D:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Opening image file D:\RemoteInstall\SMSImages\MON0000F\winpe.MON0000F.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Found Image file: D:\RemoteInstall\SMSImages\MON0000F\winpe.MON0000F.wim PackageID: MON0000F ProductName: Microsoft® Windows® Operating System Architecture: 9 Description: Microsoft Windows PE (x64) Version: Creator: SystemDir: WINDOWS SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Closing image file D:\RemoteInstall\SMSImages\MON0000F\winpe.MON0000F.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Failed adding image D:\RemoteInstall\SMSImages\MON0000F\winpe.MON0000F.wim. Will Retry.. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Loaded D:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Opening image file D:\RemoteInstall\SMSImages\MON00010\winpe.MON00010.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Found Image file: D:\RemoteInstall\SMSImages\MON00010\winpe.MON00010.wim PackageID: MON00010 ProductName: Microsoft® Windows® Operating System Architecture: 0 Description: Microsoft Windows PE (x86) Version: Creator: SystemDir: WINDOWS SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Closing image file D:\RemoteInstall\SMSImages\MON00010\winpe.MON00010.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Failed adding image D:\RemoteInstall\SMSImages\MON00010\winpe.MON00010.wim. Will Retry.. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Loaded D:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Opening image file D:\RemoteInstall\SMSImages\MON00011\winpe.MON00011.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Found Image file: D:\RemoteInstall\SMSImages\MON00011\winpe.MON00011.wim PackageID: MON00011 ProductName: Microsoft® Windows® Operating System Architecture: 9 Description: Microsoft Windows PE (x64) Version: Creator: SystemDir: WINDOWS SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Closing image file D:\RemoteInstall\SMSImages\MON00011\winpe.MON00011.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Failed adding image D:\RemoteInstall\SMSImages\MON00011\winpe.MON00011.wim. Will Retry.. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Loaded D:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Opening image file D:\RemoteInstall\SMSImages\MON0006E\winpe8.MON0006E.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Found Image file: D:\RemoteInstall\SMSImages\MON0006E\winpe8.MON0006E.wim PackageID: MON0006E ProductName: Microsoft® Windows® Operating System Architecture: 0 Description: Microsoft Windows PE (x86) Version: Creator: SystemDir: WINDOWS SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Closing image file D:\RemoteInstall\SMSImages\MON0006E\winpe8.MON0006E.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Failed adding image D:\RemoteInstall\SMSImages\MON0006E\winpe8.MON0006E.wim. Will Retry.. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 24/03/2015 10:38:17 8428 (0x20EC)
  22. *****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.
  23. I am currently implementing SCCM 2012 and already have SCCM 2007 in place. I have unchecked PXE building in SCCM 2007 and set up PXE building in SCCM 2012 but when I attempt to PXE build on one of our machines it still seems to receive the PXE request from the SCCM 2007 system. If anybody has any ideas why this is happening or where I need to check in 2007 to ensure the function is temporarily disabled then please let me know. 2007 PXE Screen
  24. Hi, Currently our manufacturing department is using a physical machine with linux on it serving PXE bootable memtest86+ to the local subnet. They have been managing this server themselves aside from the IT department because we don't really support linux at this time.. but now the person who knew how to use it left, and it stopped working... So now its been put back into IT's hands to get this thing going... and if I need to, I will fix the linux side.... but I would MUCH rather use our existing SCCM setup for this and NOT have multiple PXE/DHCP servers So does anyone know a way to use SCCM to boot into PXE and be presented with memtest86+ to test the memory in that client machine? (this could then be added you the various tutorials on this site because many people would love a way to boot into iso live linux distributions) Here is the linux example: http://wellsie.net/p/286/ Any help is greatly appreciated!
  25. Hello, We have switched from using Symnatec Ghost for Capturing and Deploying images to using SCCM 2012. The procedure we would typically use for Ghost when we got a new machine is as follows: (General Idea) 1. Load Windows 2. Load Drivers 3. Load Updates 4. Load Software 5. Create image by Pxe'ing to our ghost server and saving this image. 6. Use PXE in Ghost to deploy the image to all other same model computers. Currently with SCCM i'm doing the same first 4 steps then: 5. Capture image using capture media saving OS 6. Deploy using PXE to SCCM Server. Is there anyway to eliminate the need for the capture media and run it from a PXE? I know there are other ways to do this i just haven't learned them yet.
×
×
  • Create New...