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, Ive been following some guides here to help me set up our existing SCCM2012 (not installed SP1 yet) for deployment (previously it only handled SCEP). After configuring and testing deployment within the same subnet i decided to go ahead with trials in the net where most of the deployments will happen. I configured the DHCP server with option 66 and 67 without problems but when i went to try the deployment i encountered the error. The pc will PXE boot successfully but it fails after checking policy assignments. SMSTS.log: CLibSMSMessageWinHttpTransport::Send: URL: AXXE13VM.AXXE.com:80 CCM_POST /ccm_system/request TSPxe 05.03.2013 11:10:56 1256 (0x04E8) Request was succesful. TSPxe 05.03.2013 11:10:56 1256 (0x04E8) Decompressing reply body. TSPxe 05.03.2013 11:10:56 1256 (0x04E8) ::DecompressBuffer(65536) TSPxe 05.03.2013 11:10:56 1256 (0x04E8) Decompression (zlib) succeeded: original size 280, uncompressed size 672. TSPxe 05.03.2013 11:10:56 1256 (0x04E8) Request client ID: GUID:DAA20757-CED8-470F-BF25-BAB672C4B9A4 TSPxe 05.03.2013 11:10:56 1256 (0x04E8) Response client ID: GUID:DAA20757-CED8-470F-BF25-BAB672C4B9A4 TSPxe 05.03.2013 11:10:56 1256 (0x04E8) Retrieving Policy Assignments: TSPxe 05.03.2013 11:10:56 1256 (0x04E8) Successfully read 0 policy assignments. TSPxe 05.03.2013 11:10:56 1256 (0x04E8) Retrieving collection variable policy. TSPxe 05.03.2013 11:10:56 1256 (0x04E8) Found 0 collection variables. TSPxe 05.03.2013 11:10:56 1256 (0x04E8) Retrieving machine variable policy. TSPxe 05.03.2013 11:10:56 1256 (0x04E8) Found 0 machine variables. TSPxe 05.03.2013 11:10:56 1256 (0x04E8) Setting machine/collection variables in the task sequencing environment. TSPxe 05.03.2013 11:10:56 1256 (0x04E8) Exiting TSMediaWizardControl::GetPolicy. TSPxe 05.03.2013 11:10:56 1256 (0x04E8) WelcomePage::OnWizardNext() TSPxe 05.03.2013 11:10:56 1208 (0x04B8) Loading Media Variables from "X:\sms\data\variables.dat" TSPxe 05.03.2013 11:10:56 1208 (0x04B8) CryptDecrypt (hKey, 0, 1, 0, pData, &dwDecryptedLen), HRESULT=80090005 (e:\nts_sccm_release\sms\framework\smscrypt\windes.cpp,150) TSPxe 05.03.2013 11:10:56 1208 (0x04B8) SMS::Crypto::DES::DecryptBuffer( (BYTE*)pszPassword, (DWORD)(wcslen(pszPassword)*sizeof(WCHAR)), encryptedBuffer.getBuffer(), (DWORD)encryptedBuffer.size(), pbDecryptedBuffer, dwDecryptedBufferSize ), HRESULT=80090005 (e:\nts_sccm_release\sms\framework\tscore\tsremovablemedia.cpp,387) TSPxe 05.03.2013 11:10:56 1208 (0x04B8) No assigned task sequence. TSPxe 05.03.2013 11:10:56 1208 (0x04B8) From what i gather here everything works as it should, but something is preventing SCCM from seeing this machine as valid for deployment hence no policy available? I have removed and re-added the machine to the collection for which i want to run deployment thinking this might fix it. I have double checked to see wether i got more than one computer with the same GUID. I dont think there is anything wrong with my collections considering deployment works on subnet A (same as sccm server) but fails on subnet B ? Any advice out there will be greatly appreciated. I can supply more information if needed, just let me know what you need! Thanks in advance!
  2. Does SCCM 2012 SP1 support client boot from PXE over IPV6, If yes how to setup IPV6 PXE. SCCM 2012 SP1 support IPV4 PXE, witch I deploy an OS successfully. I don't know whether a client can boot via IPV6 PXE?
  3. Hi All, I have a strange problem: 1. I have staged one computer as "Unknown". 2. After staging was completed i deleted the entry in SCCM from devise node 3. Try to restage this computer as "unknown" I always received Pending request id bla bla bla I have no "Unknown" entry in SCCM so i can't re-delete this one and no clear last pxe request possible. I have tried to make a clear last pxe on the unknow computers collections, but no luck. How can i stage this computer ? as i can't see this one anywhere anymore. What actions should i do ? PS: Try the registry key HKLM\software\microsoft\sms\DP regdword: "CacheExpire"=120 Restart WDS -> no luck Restart Server -> no luck Thanks in advance, i have a big headake now
  4. I am currenty replacing SCCM 2007 with SCCM 2012. Because of that, I have two fully working environments. Performing a new OSD with a machine directly from the factory is easy in SCCM2012: I simply import the compuer, with it's desired hostname, and the MAC adress of the machine, and point towards a specific device collection, allowing the task sequence to run. (I do not use unknown computer support in the 2012 enviroment, but we did in the previous 2007 environment). Performing OSD that way, works like a charm! I can even deploy the SCCM 2012 agent to a SCCM 2007 machine, making it communicating fully, then making the system a member of the very same osd-collection, in that way triggering the OSD via PXE or from Windows in the Software Center. I'm using Option 66 and 67 in my DHCP, on specific scopes. Recently, I've been trying to educate my collegues, in how to use the SCCM 2012 console. A collegue of mine simply asked: "what's the easiest way to reinstall a computer, that is currently in the SCCM 2007 system?" Well, as I have the "Active Directory System Discovery" discovery method enabled, I can actually see the objects from our AD under devices in SCCM 2012. Deploying the SCCM 2012 agent to one of those object would work, and then making it a member of the collection. But that's a bit unnecessary, right? So, I just tried to rightclick on the object, which currently says Client=No (as the machine is a member of the sccm 2007, or none at all), choose "add selected items" -> "add selected items to existing device collection", choosing my osd-collection. Seems legit? Trying to PXE a machine gives me the following: "CLIENT MAC ADDR: BLABLABLA GUID: BLABLABLA CLIENT IP: 172.X.X.X MASK: 255.255.255.0 DHCP IP: 172.X.X.X GATEWAY IP: 172.X.X.X Downloaded WDSNBP... Architecture: x64 WDSNBP started using DHCP Referral. Contacting Server: MY SCCM WITH WDS (gateway: 172.x.x.x)... No responsde from Windows Deployment Services server. Launching pxeboot.com... Press F12 for network service boot." When pressing F12 I get this: "Windows failed to start. A recent hardware or software change might be the cause. To fix the problem: 1. Insert your Windows installation disc and restart your computer. 2. Choose your language settings, and then click "Next". 3. Click "Repair your computer". If you do not have this disc, contact your system administrator or computer manufacturer for assistance. File: \Boot\BCD Status: 0xc000000f Info: An error occurred while attempting to read the boot configuration data." Any thoughts on this? Seem like doing a re-OSD the easy way, is an impossible way. Thanks Johan
  5. Hello, I am having a problem with PXE booting the Dell Latitude E6410 and E4310 laptops from SCCM, and I wanted to see if anyone has seen a similar problem before. Our SCCM is setup with 1 primary server and 2 secondary servers. The laptops will image fine from the primary and 1 of the secondaries. The site that has the problems gives this error message when trying to PXE boot those 2 models: PXE-E51: No DHCP or proxyDHCP offers were received. PXE-M0F: Exiting Intel Boot Agent. I know that the PXE-E51 error usually means that the computer is not getting an IP address, but it works when imaging other Dell models. I have already tried creating a new task sequence and advertisement. I removed WDS and the PXE service point, and set them up again. I deleted the boot images from distribution point, and pushed them back down to the regular distribution point, and the SMSPXEIMAGES$ distribution point. At this point, I am all out of ideas of what else I can try. Thank you for your help.
  6. Hi All, I have been reading through this forum quite a bit, including using the guides available to setup a couple of SCCM installs (firstly with 2007, and now with 2012). My current issue is with getting PXE to work. In my SMSPXE.log file when trying to PXE boot a machine, i get the following messages: sending with winhttp failed; 80072efe SMSPXE 30/10/2012 3:38:24 PM 1588 (0x0634) Failed to get information for MP: https://FQDN. 80072efe. SMSPXE 30/10/2012 3:38:24 PM 1588 (0x0634) PXE::DB_InitializeTransport failed; 0x80004005 SMSPXE 30/10/2012 3:38:24 PM 1588 (0x0634) PXE::DB_LookupDevice failed; 0x80004005 SMSPXE 30/10/2012 3:38:24 PM 1588 (0x0634) Set media certificate in transport SMSPXE 30/10/2012 3:38:24 PM 1588 (0x0634) Set authenticator in transport SMSPXE 30/10/2012 3:38:24 PM 1588 (0x0634) In SSL, but with no client cert SMSPXE 30/10/2012 3:38:24 PM 1588 (0x0634) sending with winhttp failed; 80072efe SMSPXE 30/10/2012 3:38:24 PM 1588 (0x0634) Failed to get information for MP: https://FQDN. 80072efe. SMSPXE 30/10/2012 3:38:24 PM 1588 (0x0634) PXE::DB_InitializeTransport failed; 0x80004005 SMSPXE 30/10/2012 3:38:24 PM 1588 (0x0634) PXE::DB_ReportStatus failed; 0x80004005 SMSPXE 30/10/2012 3:38:24 PM 1588 (0x0634) PXE Provider failed to process message. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 30/10/2012 3:38:24 PM 1588 (0x0634) Set media certificate in transport SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634) Set authenticator in transport SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634) In SSL, but with no client cert SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634) sending with winhttp failed; 80072efe SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634) Failed to get information for MP: https://FQDN. 80072efe. SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634) PXE::DB_InitializeTransport failed; 0x80004005 SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634) PXE::DB_LookupDevice failed; 0x80004005 SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634) Set media certificate in transport SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634) Set authenticator in transport SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634) In SSL, but with no client cert SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634) sending with winhttp failed; 80072efe SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634) Failed to get information for MP: https://FQDN. 80072efe. SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634) PXE::DB_InitializeTransport failed; 0x80004005 SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634) PXE::DB_ReportStatus failed; 0x80004005 SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634) PXE Provider failed to process message. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 30/10/2012 3:38:32 PM 1588 (0x0634) Set media certificate in transport SMSPXE 30/10/2012 3:39:27 PM 1588 (0x0634) Set authenticator in transport SMSPXE 30/10/2012 3:39:27 PM 1588 (0x0634) In SSL, but with no client cert SMSPXE 30/10/2012 3:39:27 PM 1588 (0x0634) sending with winhttp failed; 80072efe SMSPXE 30/10/2012 3:39:27 PM 1588 (0x0634) Failed to get information for MP: https://FQDN. 80072efe. SMSPXE 30/10/2012 3:39:27 PM 1588 (0x0634) PXE::DB_InitializeTransport failed; 0x80004005 SMSPXE 30/10/2012 3:39:27 PM 1588 (0x0634) PXE::DB_LookupDevice failed; 0x80004005 SMSPXE 30/10/2012 3:39:27 PM 1588 (0x0634) Set media certificate in transport SMSPXE 30/10/2012 3:39:28 PM 1588 (0x0634) Set authenticator in transport SMSPXE 30/10/2012 3:39:28 PM 1588 (0x0634) In SSL, but with no client cert SMSPXE 30/10/2012 3:39:28 PM 1588 (0x0634) sending with winhttp failed; 80072efe SMSPXE 30/10/2012 3:39:28 PM 1588 (0x0634) Failed to get information for MP: https://FQDN. 80072efe. SMSPXE 30/10/2012 3:39:28 PM 1588 (0x0634) PXE::DB_InitializeTransport failed; 0x80004005 SMSPXE 30/10/2012 3:39:28 PM 1588 (0x0634) PXE::DB_ReportStatus failed; 0x80004005 SMSPXE 30/10/2012 3:39:28 PM 1588 (0x0634) PXE Provider failed to process message. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 30/10/2012 3:39:28 PM 1588 (0x0634) Set media certificate in transport SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634) Set authenticator in transport SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634) In SSL, but with no client cert SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634) sending with winhttp failed; 80072efe SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634) Failed to get information for MP: https://FQDN. 80072efe. SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634) PXE::DB_InitializeTransport failed; 0x80004005 SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634) PXE::DB_LookupDevice failed; 0x80004005 SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634) Set media certificate in transport SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634) Set authenticator in transport SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634) In SSL, but with no client cert SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634) sending with winhttp failed; 80072efe SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634) Failed to get information for MP: https://FQDN. 80072efe. SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634) PXE::DB_InitializeTransport failed; 0x80004005 SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634) PXE::DB_ReportStatus failed; 0x80004005 SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634) PXE Provider failed to process message. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 30/10/2012 3:39:35 PM 1588 (0x0634) I've replaced the server name with FQDN, but you can see the errors I am having. Some things I have tried are: removing and re-adding the Distribution Point changing the date on some of the certificates (to hopefully generate new ones). removed and re-installed the WDS role. rebooted. restarted WDS service. PXE booting has worked once for me, but when it did the task sequence i was trying to run (build and capture) failed, but before I had a chance to look into that, PXE stopped working. I have tried this on a couple of different machines, and at the client end, I get the following message: Status: 0xc000000f Info: An error occured while attempting to read the boot configuration data. I am at my wits end trying to get this to work, I have searched online, and the only solution it looks to be is to rebuld the server, which I really do not want to do. (if i do though, i will wait for SP1). If I haven't provided enough info, please let me know, and I will be sure to post it. Thanks in advance!
  7. Hi all I have had WDS and PXE running quite happily for a few months, but all of a sudden it has stopped working. WDS is installed on a member server DNS & DHCP on a seperate server Everything is on a single VLAN Set to accept known & unknown What I seem to be getting on 2 site is "pxe-e55: ProxyDHCP service did not reply to request on port 4011" I've been looking around (including this forum) and can't quite find the same scenario. This is a very basic setup - what am I missing? It was all working without any issues until recently. Have there been any patches to Win2k8R2 that would affect it? Any advice would be very gratefully received! Thanks in advance Rich
  8. So here's the deal...when PXE booting a workstation it displays the MAC and the SMS BIOS GUID-- which I've used before to import a workstation, though usually we just boot workstations as Unknown and deploy an OS through the Unknown Computers collection--but when trying to image this one particular workstation, we noted that it simply kept restarting itself after running the pre-execution hook. Taking a look at the logs revealed that when it begins the identity request, that it is logging a different SMS BIOS GUID than what is displayed when we first PXE boot. This then resolves to a different NetBIOS name (even though the MAC address is logged correctly), which is how I first noticed that the SMS BIOS GUID was wrong. For example, what is seen in SMSTS.log: Preparing Client Identity Request. TSPxe 9/10/2012 2:50:33 PM 1220 (0x04C4) Setting transport. TSPxe 9/10/2012 2:50:33 PM 1220 (0x04C4) Setting SourceID = d25404f6-c37b-4ee8-91c0-c0b6aeaa4cf4. TSPxe 9/10/2012 2:50:33 PM 1220 (0x04C4) Setting site code = ###. TSPxe 9/10/2012 2:50:33 PM 1220 (0x04C4) Setting SMBIOS GUID = 4C4C4544-0000-2010-8020-80C04F202020. TSPxe 9/10/2012 2:50:33 PM 1220 (0x04C4) Adding MAC Address 00:19:B9:24:65:5A. TSPxe 9/10/2012 2:50:33 PM 1220 (0x04C4) So here are how the SMS BIOS GUID's are being reported for the same workstation: 4C4C4544-0000-2010-8020-80C04F202020 <-- SMSTS log file 44454C4C-0000-1020-8020-80C04F202020 <-- pxe boot initialization You can note that they are nearly identical, with the first and third sections pretty much being the reverse of each other. All of my site system and component statuses are fine...no errors there (with the exception of an AD discovery error). On top of this, we had a workstation accidentally get imaged a couple weeks ago due to a duplicate reported MAC address. Interestingly enough, if you checked the MAC address on the workstation then it would give you the correct information, but the DDR client properties in SCCM listed the incorrect MAC. I ran the duplicate MAC address report and found a couple entries listed, and just ended up deleting them at the time (figuring that they would get added back with their correct MAC's, which they have thus far). The issue in this case though is that the client wasn't reporting the correct value back to SCCM (which was obviously not duplicated based on ipconfig /all command from the "supposedly" conflicting workstations)...which is similar to what's happening here with the PXE booting and the SMS BIOS GUID. So all that being said, has anyone else run into this problem or have any ideas on a solution? Please let me know if I can provide further information! Thanks!
  9. I have been trying to get OSD to work on diffrent subnet. Got it working on 1 laptop but having imported computer info into SCCM ready for more OSD get the following message on both new laptops. Architecture: x64 WDSNBP started using DHCP referral Contacting server (myIP) (Gateway: 0.0.0.0) no response from windows deployment services server Launching pxeboot.com.. Press f12 for network service boot I then press f12 and get the following: connects to sccm and then goes into the Windows Boot Manager screen with the following error: File: \Boot\BCD Status 0x000000f info: An Error occurred while attempting to read the boot configuration data Any suggestions please??
  10. Hello! This is my first post, and I am new to SCCM 2012 (but used SCCM 2007 a fair bit). I have been following Anyweb's guides in my test environment, and have been having issues successfully booting the Build and Capture images (Step 10 http://www.windows-noob.com/forums/index.php?/topic/4468-using-sccm-2012-rc-in-a-lab-part-7-build-and-capture-windows-7-x64/ ) . I am able to boot both x86 and x64 images, select the task sequence, but then immediately I am hit with: “Failed to Run Task Sequence - This Task Sequence cannot be run because the program files for <package_ID> cannot be located on a distribution point.” I have verified the package in question is in fact on the question (the package in question is actually either my x86 or x64 boot image). I do have the "Copy the content in this package to a package share on distribution points" checkbox checked on the package as well! I have tried on both x86 and x64 computers, with Broadcom and Intel network chips (trying to rule out driver issues as I experienced many in WDS deployments). Any ideas where I should look next? I'm really at a stand still on this!!
  11. Hi, is it possible to use SCCM to give network admins a choice of images when using PXE boot? With WDS we were able to log in then choose the correct image for the PC. If this is possible with SCCM any hints would be very appreciated!
  12. Discovered this morning that my PXE DP is out of space. I searched high and low for any large files, which resulted in none. Selected all files and folders and that resulted in 16gb out of 60gb. Found a KB article from MS stating this issue for Self-Signed Certs. http://support.microsoft.com/kb/2713467 So now I have 40-45gb of files that I cannot access. We have tried to view the files in powershell, cmd shell, booted the server into a PE...everything bombs out. Looking at my local system, I navigate to that path and there a few files there with a size avg of 1-2kb. Does anyone know what would happen if we were to delete the files? Im hoping we could try and delete the folder and see how far it can get.
  13. When i try to pxe boot a client, i only get PXE-E53 "No boot filename received" I have tried to reinstall wds/pxe several times.. searched trough a lot of post with similar problems..tried lot of solutions.. but still stuck.. I really dont know where to begin to troubleshoot this.. SMSPXE: reply has no message header marker SMSPXE 27.04.2012 12:36:19 3936 (0x0F60) PXE::DB_LookupDevice failed; 0x80004005 SMSPXE 27.04.2012 12:36:19 3936 (0x0F60) Set enterpirse certificate in transport SMSPXE 27.04.2012 12:36:19 3936 (0x0F60) Set media certificate in transport SMSPXE 27.04.2012 12:36:19 3936 (0x0F60) Set authenticator in transport SMSPXE 27.04.2012 12:36:19 3936 (0x0F60) In SSL, but with no client cert SMSPXE 27.04.2012 12:36:19 3936 (0x0F60) Set authenticator in transport SMSPXE 27.04.2012 12:36:19 3936 (0x0F60) In SSL, but with no client cert SMSPXE 27.04.2012 12:36:19 3936 (0x0F60) reply has no message header marker SMSPXE 27.04.2012 12:36:19 3936 (0x0F60) Failed to send status message (80004005) SMSPXE 27.04.2012 12:36:19 3936 (0x0F60) Failed to send the status message SMSPXE 27.04.2012 12:36:19 3936 (0x0F60) PXE::DB_ReportStatus failed; 0x80004005 SMSPXE 27.04.2012 12:36:19 3936 (0x0F60) PXE Provider failed to process message. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 27.04.2012 12:36:19 3936 (0x0F60) Edit: also tried to add option 66/67 in dhcp.. i get past the pxe boot.. but recieve a \boot\bcd error And the same lines of errors in SMSPXE
  14. Hi, I've got some trouble getting PXE to work on my SCCM 2012 Installation. I got a DHCP server on my primary domain controller (same VLAN as the SCCM server) I've enabled PXE support for clients and Allow this distribution point to respond to incoming PXE requests, Enable unknown computer support. Also i've created a MDT 2012 Boot image using the guides on this forum. The Boot image is deployed to the distribution point and the property Deploy this boot image from the PXE service point is enabled , and the Operation System image is deployed as well. On my Cisco network switches my VLAN is configured to accept ip-helper addresses from my DHCP server, and my SCCM server. But the PXE client wont boot. Any suggestions?
  15. All of a sudden when booting PXE, it is now downloading the x64 boot image instead of the x86 as it was before. I'm trying to figure out why as some of our machines don't support x64 and fail to boot PXE. Has anyone heard of this or have any idea? Our imaging process is practically stopped because of this and since school is starting in two weeks.....definitely not a good thing, LOL Thanks, Todd
  16. Good evening, I've recently starting taking over SCCM activities at my place of work and as I've started to work on our PXE boot to load OSs on bare computers, I've come across some problems and I'm hoping someone with more knowledge and experience can at least point me in the right direction. Here's what's happening, I'll explain it all as best I can: Turn on the computer and press F12 to go into the Network Boot. Wait for it to contact the server and then press F12 again to Network Boot. It loads the boot image... The standard SCCM screen comes up and says Windows is Starting and then applies it's drivers. Next, JUST before it would normally get to the Login screen where we put in our password before we can select which task sequence we want to run, the background is all that is seen and then the computer restarts. So, my question is this, is there a log somewhere that will tell me exactly whats happening at the point when it's restarting? I could probably figure it out if I knew which log to look at but I'm still learning my way around all the logs and what they say and I haven't come across the right one yet. So if anyone has any idea what the problem may be or what log I should be looking at, I would greatly appreciate any assistance!
  17. If anyone is interested, I have just produced (today) a solution to use WDS as a PXE boot point, to Boot PE and then automatically run a batch to image a PC using imagex to a nominated (in batch) file share, we've had a lot of leavers lately and I needed a quick way of backing up a lot of machines. If anyone is interested in this, i'll document it up. Aaron
  18. Hi, I am having a very strange error crop up while testing the deploy and capture of a boot OS via a task sequence. The error occurs on x86 or x64, on VM's or physical clients. SCCM 2012 is installed per the fantastic tutorial here and this error is appearing on part 7. When deploying the boot image to the target pc, the PE environment loads and immediately resets the client pc with this error: Failed to run task sequence - An error occurred while retrieving policy for this computer (0x80004005) After some searching around I found and tried these: Link 1: Permissions & Link 2: Certificates Unfortunately, neither helped. I have granted sufficient permissions to client systems to access the boot.wim image and the only certificate available is loaded into SCCM and is unblocked. Its difficult to be 100% sure re the certificates issue, as that link is to a 2007 SCCM structure and I think that Admin.\Security\Certificates would be the corresponding location in 2012. At this point I have reinstalled the distribution point, setup new boot images for both x86 & x64, created new tasks and sent them out to the clients and still ... nothing. Clients are still restarting immediately after the PE loads. I have tried to look at the smsts.log on the clients, but they are listed as empty, so cannot. The smspxe.log file reports business as usual with no unusual\error based behaviour. Any ideas anyone or anyWeb? At this point I am at my wits end, but need to continue regardless... Cheers & Thanks
  19. Hi everyone. I'm trying install windows 7, but witout succsess. SMSPXE.log: reply has no message header marker SMSPXE 20.06.2012 17:14:50 3880 (0x0F28) PXE::DB_LookupDevice failed; 0x80004005 SMSPXE 20.06.2012 17:14:50 3880 (0x0F28) reply has no message header marker SMSPXE 20.06.2012 17:14:50 3880 (0x0F28) Failed to send status message (80004005) SMSPXE 20.06.2012 17:14:50 3880 (0x0F28) Failed to send the status message SMSPXE 20.06.2012 17:14:50 3880 (0x0F28) PXE::DB_ReportStatus failed; 0x80004005 SMSPXE 20.06.2012 17:14:50 3880 (0x0F28) PXE Provider failed to process message. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 20.06.2012 17:14:50 3880 (0x0F28) I was trying do like here but it didn't help me.
  20. Good Morning Folks, I'm hoping someone can shed some light for me. I'm wondering how many folders should live inside of the Remoteinstall folder? I currently only have 3 which are SMSBoot, SMSIMAGES, and SMStemp. I noticed that in my other Remoteinstall folder that have been renamed Remoteinstall.old that there are about 5 or 6 more folders. I ask this because I recently had to re-install my PXE Service Point on my Primary server as it was being somewhat flaky and had some errors in the SCCM System Status Node. I followed the guide from here , uninstalled/reinstalled and thought I was good to go. Later on I tried re-imaging a computer, I was able to boot from PXE ( recieved the x64 boot image ) but I recieved the following error after about 30 minutes or so at the step "Setup is Applying System Settings" "Windows could not parse or process the unattend answer file for pass {specialize}. The settings specified in the answer file cannot be applied. The error was detected while processing settings for component [Windows-Shell-Setup]" I've used this image and task sequence multiple times in the past and everything went smooth so I'm not sure why I'm now facing this issue. Can anyone guide me in the right direction? Thanks for your time.
  21. Now that I've got my PXE working I'm running into the error of: Failed to run task sequence because the program files cannot be located on a distribution point. In the documentation for RC2 it states to enable the "Copy content to a share on distribution points" but then after that it's vague on where it means when it says "Note: once you have enabled the setting above your Deployment distribution settings gets a new drop down menu choice, access content directly from a distribution point when needed by the running task sequence" Where can I find this and what exactly needs to be done here Disregard, I figured it out.
  22. I have installed a hierarchy SCCM 2012 - CAS-PRI. PXE is enabled. Now, when I PXE boot a Hyper-V VM at first boots fine then goes upto Build and Capture TS selection. Once selected, next I see retrieving policy for this computer, resolving task sequence dependencies and then errors out (in smsts.log: 0x80040102). Attached are few screenshots and SMSts.log file. smsts.log Strange part of the PXE is once I remove computer from the Devices list so that I can retry but VM won't PXE boot until few mins (pic 4). Why? does SCCM takes time to clear out that unknown computer from the system?
  23. I did the following: 1. import the images and files from my SCCM 2012 RC2 server. All were manually imported (Copied the files, and added them manually) 2. set the boot images up but did not deploy them 3. added the pxe role to the server 4. deployed the pxe boot images 5. setup the OS installer for windows 7 6. set up the task list for windows 7 7. set up the image for windows 7 (captured using RC2) 8. set up a collection target 9 deployed the task sequence to the collection 10. added a VM with static mac to the collection 11. tried to pxe boot The VM is not getting DHCP on two subnets it should be getting -- in theory i should be getting another error than it timing out like its not on a network at all. VM is on a Hyper-V 2008 R2 Host. distmgr.log
  24. Hi, I need to setup PXE boot on my vlan for SCCM 2012. We have setup the IP Helper to point to the IP address of the SCCM Site/DP. Where is the file located which I will need for DHCP to give out to the clients to boot from? I'm new to PXE booting in general so I'm a little confused about all this. Here is the location of the file that I'm currently having it boot to \\SCCM\SMS_STK\osd\boot\x64\boot.wim Acutally the other admin did say that when he sets it up he wont be needing the unc path, just the filename of the boot file. I've gone through and enabled PXE boot in SCCM. Currently when my machine tries to boot it gets the following error. PXE-T04: Access Violation PXE-E36: Error received from TFTP server PXE-M0F: Exiting PXE ROM
  25. I'm having an issue imaging one of my desktops. This is a standard Windows 7 64 bit image and I genearally use it a couple times a week with no issue. I have one computer, however, where it just hangs indefinately on the installation of Office. This is the last advertisement shown for my Windows 7 image on this computer (2 days ago). Information Milestone VAN 5/2/2012 4:53:18 PM VAND04601 Software Distribution 10005 Program started for advertisement "VAN20181" ("VAN000EC" - "Office Professional 2010 (x32 Only)"). Command line: "\\abc.def.LOCAL\SMSPKGD$\VAN000EC\setup.exe" /adminfile custom.msp Working directory: \\abc.def.LOCAL\SMSPKGD$\VAN000EC\ User context: NT AUTHORITY\SYSTEM 1464 1296 And when I check the SMS Trace (C:\Program files (x86)\SMS_CCM|smspxe.log) I get multiple lines with this (but no error). Advertisement results: OfferId:VAN20181 OfferTime:02/08/2011 10:38:00 PackageID:VAN00138 BootImageID:VAN00001 PackageVer: PackagePath:\\VCVANSCCM1\SMSPXEIMAGES$\SMSPKG\VAN00001\ Mandatory:0 smspxe 4/24/2012 1:56:12 PM 3532 (0x0DCC)
×
×
  • Create New...