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. 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)
  2. 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.
  3. I've been trying to create a custom UDIWizard_Config.xml to install my applications during my task sequence, but I haven't been able to get my Applications to show up when I go to Add Software to a group. I know my Configuration Manager settings are correct because my Site Settings are validated. I also have all my applications checked to "Allow this applications to be installed from the Install Application task sequence without being deployed". All my packages show up just fine. The issue is only with Applications. I'm on SCCM 2012 SP1, with MDT 2012 Update 1. Any help will be appreciated. Thanks, Leo
  4. 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
  5. 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!
  6. Just started having an issue when attempting to PXE into configmgr console for OSD. My machines will pxe to server, load boot image, load WinPE, prepare windows, load nic adapter, hang at 2012 SCCM splash scrren for about 20 seconds, then reboot. Would anybody happen to have a resolution to this issues we are seeing? I have redistibuted/updated distribution points in terms of content including boot images. This just started since i've moved and isolated this pxe service point to a new vlan. Thanks
  7. I've been beating my head against a wall trying to figure this out with no success, hoping someone can shed some light. Environment: Server 2012 Standard, x64 (Running on Hyper-V 2012) SQL 2008 R2 SCCM 2012 R2 Recent tasks (in this order) Installed, tested, and uninstalled UIUSD (Universal Imaging Utility) trial, no problems with install or uninstall. I installed CU3 update to SCCM 2012 SP1 I uninstalled ADK 8.0 I installed ADK 8.1 I installed SCCM 2012 R2 Ran windows and microsoft updates I did the upgrade to 2012 R2 to start testing some windows 8.1 deployments. In the midst of trying to get 8.1 deployments working I rebooted the server. Now the Windows Deployment Services Server service won't start. (See attached results from SMSPXE.log) When the service is trying to start, as soon as it hits that last line (Loaded D:\Windows Kits\8.1\Assessment...wimgapi.dll) I get Error: 1067 The process terminated unexpectedly. Windows Application Event Log shows Event 1000: Application Error, Faulting application name: svchost.exe_WDSServer, version: 6.2.9200.16420. Faulting module name: ntdll.dll, version 6.2.9200.16579 Things I have tried doing to fix the problem: Remove boot files from D:\RemoteInstall\SMSImages Re-distribute boot images from SCCM Remove all modules and drivers from boot images, and re-distribute Remove PXE role from DP, delete RemoteInstall folder, reboot, add pxe role, reboot. Nothing I've tried has worked. I've exhausted my google searching abilities. If anyone has suggestions of something to try I would appreciate it. Thanks
  8. Hi everyone, I am currently trying to use WDS on Windows Server 2012 r2. I also have the MDT 2012 and Windows ADK 8.1 installed. I am however, just trying to get WDS barebone working at the moment. I have had WDS working as a standalone but when I moved it to be integrated with Active Directory I have run into issues. The WDS server is on it's own VM and the DHCP/DNS/AD DS are all on another VM. I have set up a VLAN test environment with the two servers and multiple clients all on the same subnet and blocked off from our production environment. There is a screenshot of my client booting from PXE attached here. It downloads the wdsnbp.com from the correct IP. I have tried prestaging in AD with no results. If I add a computer and its GUID in AD, I can see it appear in the prestaged devices in WDS. I know all clients and servers are communicating with each other from looking through the logs. The Deployment-Services-Diagnostics log in EventViewer shows the correct client VM MAC address booting from PXE and downloading wdsnbp.com so I know it is connected to the server. My current WDS settings are: Respond to all client computers (Known and unknown) - with require administrative approval for unknown computers checked. Do not listen on DHCP ports unchecked, and configure DHCP options to indicate that this is also a PXE server unchecked. Allow Windows Deployment Services to dynamically discover valid domain servers Authorize this Windows Deployment Server in DHCP My current DHCP settings are: Option 66 configured to point to WDS server IP Option 67 configure to point to boot\x64\wdsnbp.com (I have tried x86 as well with the same results) I feel like I have tried everything and have run into a wall now. Since it worked as a standalone I believe it is likely to be something wrong with my AD setup. Any help is greatly appreciated.
  9. I'm trying to get PXE setup in our environment and am having some issues. We are running 2012 SP1 CU2 with a single site. I've setup the DP for PXE and deployed an X64 and X86 boot image that are both enabled for PXE. When I try to PXE boot it gets an IP, says it downloaded WDSNBP from the DP, identifies the architecture as x64, shows the pending request ID and then a message says "Please wait. SMS is looking for Policy" Contacting Server: 172.X.X.X. It then says TFTP Download: smsboot\x64\abortpxe.com and it aborts the process. The computer I'm trying to boot is already in the database since it has been imaged before and has the client installed. It also has an OSD task sequence deployed to it. When I look in SMSPXE.log on my primary server there are no entries since I first tried to get this working several months ago and gave up. The DP I'm trying to boot from is on the same LAN as the machine I'm trying to boot so I do not have anything configured in DHCP nor do I have IPHelpers setup. I'm not sure where to go from here since there isn't anything in the SMSPXE.log? Thanks Paul
  10. How to setup a IPV6 PXE server using windows server 2012 or windows server 2012R2? Any document about this?
  11. Hello all, I am getting the "ProxyDHCP service did not reply to request on port 4011" error. This is only on certain models, while they are on certain VLANs in our environment. I've checked and the routes are the same on these VLANs as they are at some of our other sites. I have also made sure that DHCP is setup the same for those VLANs as it is everywhere else in our environment. While looking around, I've found articles that said to make sure both boot images are on the distribution point, and they are. I have been fighting with this for about two weeks and don't know what else to do. The SMSPXE log doesn't show that anything is wrong. It shows the same for machines that I can actually PXE boot. Any help is appreciated!
  12. Hey guys- I am pretty new to SCCM, but I setup a SCCM 2012 SP1 CU4 server. I am using it for Endpoint Protection and Windows Updates. I have been reading on how to use PXE and have followed several guides to get this working. Right now my workstation will successfully boot using PXE. My problem is that the machine reboots immediately after "Preparing Network Connections." I do get an IP address when I push F8 so it's not a network driver issue. I am attaching my smsts.log file. There are 4 error lines in red, but I cannot figure out how to fix this. Coult not create WMI locator class (80040154) Failed to connect to WMI namespace \\.\ROOT\CIMV2 (Code 0x80040154) RegOpenKeyExW failed for Software\Microsoft\SMS\Task Sequence GetTsRegValue() failed. 0x80070002. Any help would be great! Thanks smsts.log
  13. I have searched all though these formus, Technet, and any place Google will send me. Any assistance would be appreciated. I'm setting up a new distribution point ("newDP") with dedicated hardware to be used for OSD. The DP is setup, but clients continue to hit the IP of the original DP, despite PXE being disabled on the Orig, but enabled on the New DP. Error Windows Boot Manager (Server IP: "origDP") File: \Boot\BCD Status: 0xc0000098 Info: The Windows Boot Configuration Data file does not contain a valid OS Entry Note that the error indicates the IP of origDP, which is NOT enabled for PXE. The boot files are indeed present (on both DPs).... the problem is wrong IP/server. We do not need or use DHCP option 66 because client and server on same network segment. The SCCM server simply replies directly to broadcast request for PXE server. Troubleshooting Verified DHCP Option 66 isn't responding with the OrigDP address Ensured Restarted WDS service on orig and newDP. Also restarted servers. Ensured boot images (and pxeboot.com) files were present on newDP Erased hard drive of a client device in case somehow using a cached IP from the hard drive (note: it is all clients, though) Ensured PXE is enabled on general tab of newDP, boot images, and Task Sequence Additional detail If I shut down origDP entirely (instead of just disabling PXE), the error changes to TFTP timeout. The SMSPXE.log file on newDP is not updated. It's not updated on origDP either (when PXE/WDS is disabled) I cannot imagine why the IP in the error is for a server not even configured to respond to PXE requests. It's been vexing me for a week and my management is becoming impatient. Any help is GREATLY appreciated. Thanks!
  14. Hello there! First i would like to thank you for the help I already got from you guys, even before i posted anything on here. This forum is great! I got a lot of useful information just from reading topics over here. But i'm still struggling... My objective is to get a WDS-server up and running so we can stop using our ghost server for reimaging our clients. I have encountered a number of problems of which I was able to resolve most by searching the web (for example that the client doesn't get an ip-address before trying to PXE-boot). But now I get following messages and I have no clue what to do. PXE-T04: Access Violation PXE-E36: Error Received from TFTP Server PXE-M-F Exiting PXE Rom Everything i find online suggests it is because my server and client are on different subnets or vlans and that it could be resolved by setting up ip helpers on the router. The problem is that my server and client are on the same subnet, I have no vlans configured as far as I know and they are directly connected to the same switch. So this means that normally when one of them broadcasts something it gets forwarded to all the others and it doesn't need interaction with the router. My setup is as follows: I have installed WDS on a seperate server (windows server 2012), so it isn't authorized in DHCP. I added options 66,67 and 60 to the DHCP-server with their required parameters (option 66 points to the ip-address of the WDS-server, option 67 points to the wdsnbp.com file). I also opened up the ports needed on the WDS-server (UDP 67-69, 4011, 50000-65000 and TCP 135, 137-139, 5040). I hope someone can help me out with this. If you need more information of a specific part, I'll try to provide it.
  15. I started to get a TFTP time out error imaging PCs here is the log from the server below. Could someone give me some pointers on what to look for? I have removed the PXE from Dist point and rebooted and reinstalled PXE on the dist point. I have checked and recreated a new boot image and check the box to distrubute the boot image. and nothing. I checked my DHCP for option settings are all correct. 066 Boot Server Host Name Standard 067 Bootfile Name Standard SMSBoot\x86\wdsnbp.com SMSPXE.log Start: Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16778090" ServerName="" ServerRemoteName=""><Machine><ClientID>GUID:869c7a8b-de66-48e9-8c92-a1fb7b6349be</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="XLA20033" OfferIDTime="11/20/2013 3:38:00 PM" PkgID="XLA00036" PackageVersion="" PackagePath="http://HX-SCCM01.XXXX.com/SMS_DP_SMSPKG$/FLA0007D" BootImageID="XLA0007D" Mandatory="0"/></ClientIDReply> SMSPXE 12/11/2013 8:52:21 AM 3060 (0x0BF4) B8:AC:6F:71:86:5B, 4C4C4544-0035-5910-8046-C2C04F524E31: found optional advertisement XLA20033 SMSPXE 12/11/2013 8:52:21 AM 3060 (0x0BF4) End of log. Then the system gets a TFTP PXE-E32 timeout
  16. Hi There, I am in the middle of a OS refresh of our estate (XP to Windows 7) and many of the sites are running 20+ machines on slow links (20mb or less) and the OS refresh must be ran outside of hours We have a very tight timescale for the OS refresh so i would like to create a protected distribution point that can be taken to these slow sides and run upgrades locally rather than pulling down the wim 20+times over a slow link. Unfortunately i only have desktop PC's i5 4GB memory at the moment to use for the DP's and plan on once the OS refresh is completed at a site, remove this DP and take it to the next site. I would like to know if i can just use Windows 7 and set this as a protected branch distribution point or if i would be best to install Server 2008 and set it up as a full DP with PXE support? The important aspect is being able to move the protected DP between sites (reassigning the protected boundary each time) SCCM 2007 SP2 R3, 1 primary site server, no secondary sites and a couple of main DP's in main sites. Thanks
  17. Alright, I've been having an insane amount of trouble with SCCM for the last few weeks. I am hoping someone can help me. I have combed these message boards and tried so many fixes, but no go. Setup: SCCM 2012 SP1 Server - 10.1.8.12 DHCP Server - On 172.x.x.x network DHCP Options: 66: 10.1.8.12 67: Tried both smsboot\x86\wdsnbp.com and boot\x86\wdsnbp.com (not sure which to use. Many conflicting posts about them. Also, case sensitive?) When I used to F12, I would get Boot File Not Found. That was before I added the DHCP Options. NOW, however, I get: DHCP.. TFTP. PXE-M0F - Exiting Intel Boot Agent Quite instant after it receives the IP. Now, I have ensured the Files are within both the SMSBoot and Boot folders. Plenty of them. 7 in the SMSBoot and 10 in the boot. I have tried uninstalling WDS. I haven't manually configured anything WDS. I let SCCM do everything. When I try PXE-booting with the laptop, NOTHING is added to the SMSPXE log. NOTHING is added to the DISTMGR log. Everything is added to the C: to avoid any storage-related problems. After restarting WDS service, there is no red in either logs. Please, somebody, save me from the demon. My brain is mush.
  18. I built a new secondary site server. It is running SCCM 2007 R3. I have checked and doubled checked that all perms are setup correctly and it has all the things it needs. IIS, BITS, remote diff compression, WebDav, R3. And the machine account has rights to the parent site DB and the machine account is a member of the needed AD groups to give it Admin rights on all required servers. In fact this secondary site is setup exactly like our other secondary sites (which all work) Each time I try to F12 a machine I get PXE-MOF Exiting Intel PXE ROM OS not found error. I've looked at the logs on the secondary site and they all say PXE is working properly. I looked in the System Status Messages and I see this over and over. The SMS PXE Service Point encountered an unknown device. Device MAC Address:00:50:56:A7:01:27 SMBIOS GUID:3EA72742-0A8C-D55A-2C66-BB20A72C145A. I've checked with our network team and they said everything is enabled on their end for DHCP to handle PXE requests. What am I missing or where else should I look?
  19. I'm trying to determine the minimum requirements for a DP in 2012 which I'd like to PXE enable. What OS? What Bitness? I THOUGHT I had read that 64 bit was required, but seem to find contradictory information. I don't want to spend my days banging my head against a brick wall if something isn't possible. More specifically I am looking to PXE enable the following two: 1) 2003R2 SP2 x86 2) 2008 Std SP1 Any specific advice as to how to make it WORK would be appreciated if they _ARE_ supported. Thanks.
  20. First and foremost thanks for the great site. Honestly couldn't have gotten started with SCCM without the site. With that said, I was able to get everything up and working fine for SCCM 2012 using the articles and forums. I decided to upgrade to SP1 to check out some of the new features and I have regretted it since. Basically I can't deploy via PXE since the upgrade. I always get the 80070002 error. I'm pretty sure it is a permissions issue but I'm baffled that an upgrade to SP1 would so drastically change permissions. I've looked far and wide for a solution and have gone as far as to set my domain admin account as the Network Access Account to see if that solved the issue. I'm able to do an install from media but it has to be a full media install. It would be great if this were something simple that I have overlooked. I have attached the latest smsts.log file. Any help or insight into what the problem is would be great. smsts.log
  21. Should I cut my losses and rebuild all my libraries? Some Background: Over the past week I have been trying to redistribute and validate all packages, applications and OSDs to our SCCM server. The reason for this is that one of the hdd for the server was relocated from one virtual datastore to another. Unfortunately we discovered after the fact that SCCM could no longer validate the hash of any of the packages - each and everyone was listed as unavailable. I set about redistributing them and validating them, but now I am faced with the situation that the process to validate\redistribute is hanging and not completing the job. Looking at the resource logs for the server I can see it is accessing the hdd at a high rate, but within tolerable limits. And aside from that, no other server resource is been unduly stressed or used. But at the same time, no packages, images, OSDs are getting validated or distributed. They all display "in progress". And have done so for several days now. And now for the complication that is the CU1 KB2817245 hotfix - this was unfortunately applied yesterday and we are unsure if it is the cause of the PXE not been able to distribute OSD TS or if that issue is tied to the "in progress" waiting. Leading me to either think I should cut my losses and to save time rebuild my entire catalogue. Or should I try and troubleshoot it some more...but then where should I start? Organisation info: We are a school with a single SCCM 2012 server in an 2008 R2 environment. All clients are managed with ConfigMngr. We make exclusive use of Windows 7 in a 40/60 split between x64 and x32 versions. Any info\help is appreciated.
  22. Hello, I have a ~8 mb bootable iso that contains the Dell diagnostics tools for laptops. Is it possible to somehow use this iso to boot into the diagnostic tool from PXE using SCCM 2007?
  23. Were are using SCCM 2012. Our school district has over 4000 computers we reimage every summer. Our collections are setup per building and computer type. One major issue we have with SCCM is reimaging laptop computers after they have had a OSD successfully completed. We feel part of the reason laptop computers give us such grief is when you look at the properties of the laptops data record, it shows the wireless MAC address not the wired which you need for PXE. We start to reimage and then all of a sudden, PXE stops working for specific models. We have spent weeks if not months trying to resolve this. We came to the conclusion that if we just make the client unknown to SCCM we could PXE again (as unknown) and things would work perfect again. Boy was I wrong. One model we have is HP Probook 6445b, which in HP's infinite wisdom, that model all has the same SMGUID. Searching the web we came across the WDS registry entry of BannedGuids. This fixed the issue in the SMSPXE.log when the machine would PXE boot and say "device is in the database" then follow with "no advertisement found" after we deleted the client from SCCM. But now we get " device is not in the database" which we want, the client PXE boots WinPE and after entering the password on the task sequence wizard, it returns the message "there are no task sequences available for this computer." We definitely have a TS assign to unknown computers. Is there some way to remove all traces of a client's record from the system center database? Is there a better solution that we just don't know about? Ultimately we would like to PXE boot any machine on our network and have a TS set up for "PXE and media only" for every OS image and driver package we use, and be able to deploy to known and unknown computers. Luckily we only have eight different models, and six different images for our district, with exceptions of course. Thanks in advance for any help and solutions. Bob Microcomputer Technical Support. West Seneca Central Schools.
  24. I am unable to PXE boot a bare metal PC using SCCM 2012 sp1. I have never tried to deploy an operating system before now. Here is my situation: Recently upgraded my SCCM 2012 site to sp1. Site system status is all green. Configured SCCM 2012 to deploy operating systems using PXE boot. When I try to PXE boot the bare metal PC, the following error message is returned: PXE-E55 ProxyDHCP service did not reply to request on port 4011. The firewall on the SCCM 2012 server is turned off. In the SMSPXE.log I have the following message: Getting boot action for unknown machine: item key: 2046820352 SMSPXE 4/11/2013 9:46:31 AM 3008 (0x0BC0) Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName="" ServerRemoteName=""><Machine><ClientID>b3a3b006-6b2f-45bf-aa94-3b4fd1d4ddac</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="RHC2002C" OfferIDTime="4/10/2013 3:53:00 PM" PkgID="RHC0001D" PackageVersion="" PackagePath="http://myserver/SMS_DP_SMSPKG$/RHC00020" BootImageID="RHC00020" Mandatory="0"/></ClientIDReply> SMSPXE 4/11/2013 9:46:31 AM 3008 (0x0BC0) 78:45:C4:24:00:43, 4C4C4544-004A-3610-8043-B6C04F545731: found optional advertisement RHC2002C SMSPXE 4/11/2013 9:46:31 AM 3008 (0x0BC0) I have tried reinstalling WDS and disabling/re-enabling PXE booting in SCCM 2012 3 times to no avail. I am up against a brick wall on this one. Almost ready to call Microsoft but wanted to let you guys have a look at this first. Any help would be appreciated.
  25. I am currently using SCCM 2012 SP1 RTM on server 2012. My trouble is PXE boot is not working. It go through the pxe process and see the pxe server and connects it tries to boot from both. I have included images of what i am getting. I know i might have left some things out any help would greatly appropriated PXE BOOT.rtf PXE ERROR.rtf
×
×
  • Create New...