Jump to content


Search the Community

Showing results for tags 'boot'.

  • 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 16 results

  1. Hi everyone, I'm going to tell you my problem if you can help me !!! My environment: Sccm 2012 I have to distribute windows 10 and I am testing with a virtual machine. I configured the DP by enabling the PXE and not WDS. DHCP configured (66-67) When the boot starts on the client I get the error you see in the attached file. Also on the SMSPXE.log file comes the message: not able to open SMSBoot \ x86 \ wdsnbp.com I don't know what to do anymore .... help me thank you very much!
  2. I was attempting to create a new boot image (testing concept) and the following error message occurred after the WIM loaded. The following file is missing or corrupt.... 0xc0000359 megasas2.sys I am using a 64 bit boot image, with the Dell WinPE driver cab (v10) loaded. What is causing this issue?
  3. Hi All, I installed SCCM 1706, SQL 2016, ADK for Windows 10 (version 1703), and MDT 8443 on a Server 2016 VM, and I followed this guide https://www.windows-noob.com/forums/topic/12873-how-can-i-deploy-windows-10-enterprise-x64-with-mdt-2013-update-1-integrated-with-system-center-2012-r2-sp1-configuration-manager/ because I wanted to deploy Windows 10 with SCCM. I was able to deploy Windows 10 to a Hyper-V VM using PXE, but I couldn't make it work on an actual laptop or desktop (both HP). I got the following blue screen after pressing F12. I've disabled and re-enabled my distribution po
  4. Running into an issue that I cannot wrap my head around. We recently switched from HTTPS to HTTP and now clients will not talk to remote MPs or DPs on Secondary Sites. Talking back to MP on Stand Alone Primary works fine. I have revoked certs from CA and removed certs from servers but all of my Secondary sites are having issues with MPs and DPs (no PXE Boot Filename Received). Also removed Secondary Site, WDS, WSUS, all prereqs and reinstalled. Tried PXE booting to WDS + MDT 2013 and that works, but once SCCM PXE boot is turned on, I get the error. Boot images are distributed to DPs and Task S
  5. Hi all, I have my own lab in running on my Macbook Pro (mid 2015). I'm using vmware Fusion 8 pro and almost everything works fine. When I try to run a task sequence to build and capture it fails when the step is "capture" because the network driver is not loaded. Actually I added two network drivers to my boot image: from vmware and intel 82574L (which is the one that is not loading). Nevertheless, the computer restart and start loading the boot image to capture the windows, but fails immediately and I'm out of options. Does any one had this issue before? The driver is not digita
  6. Hey Guys - Recently started at a new position where I am primarially working with an SCCM 2012 1511 environment which was set up over the past month. Yesterday, I requested that MDT 2013 be installed and once I got approval, installed MDT 2013 Update 2 on the primary then ran the integration tool successfully. This morning, I went to create the MDT packages which I usually do by creating a test MDT client task sequence. When doing so, I get to the MDT Boot Image page, but cannot select the option to create a new boot image!?! As I didn't install SCCM, I don't have specifics, but wa
  7. Hey all, I'm at my wits end here. I'm trying to add support for a new generation of laptops to my SCCM 2012 R2 TS. I have already gone through the trouble of gathering all the required drivers for the new models and created new Driver Packages only to find that the new models all use a newer\different NIC driver than the previous generation. No big deal I think, I'll just create a new boot WIM for testing, get the appropriate drivers for WinPE and I'm good! Well, not so fast. For some reason when I add the new boot WIM to my testing Task Sequence and try to PXE, the machine is unable to p
  8. What is Significance of MSR, SYS, EFI partitions for Win 8.1 Native Boot VHD? How? I ask because I've built and native booted several variations of Win 8.1 VHDs on target SPro 3. I'd like to know pros & cons. CONTEXT: So, with a lot of help and input from multiple amazing people from multiple forums and coming closer to the goal of my project. I have found and tested the ways and means to complete the steps in my project. Some interesting questions and thoughts have come up. (http://forums.mydigitallifeSPAM!/threads/62362-Virtualize-Win8-1-BIOS-MBR-Physical-Partition-gt-to-gt-
  9. 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 anyon
  10. Hi Guys, I'm trying to make an MDT Boot Image in SCCM but everytime I try to it just errors out part way through. I've tried reinstalling MDT/WADK and removing/installing the MDT ConfigMgr integration but it hasn't made any difference. Any ideas? Started processing. Creating boot image. Copying WIM file. Mounting WIM file. WIM file mounted. Setting Windows PE system root. Set Windows PE system root. Set Windows PE scratch space. Adding standard components. Adding component: winpe-dismcmdlets Error while importing Microsoft Deployment Toolkit Task Sequence. System.ServiceModel.Commun
  11. SCCM 2007 SP2 It all started when we got the new machine model in our organization. Ran the task sequence, In the SMSTS log I found Failed to download pxe variable file, which pointed that PE was missing Network driver. Went into Boot images, right clicked and added the network driver for the model. Update Image to DP, Failed. Tried to remove the driver, update to DP failed again. Tried to add a new Boot image, failed with finalized image required error. Could you please help? Do I need to uninstall WAIK? If yes, is there any prerequisite or precaution I should take before doing it on Produc
  12. At first I attempted to add drivers to a specific boot WIM and then updated the DP but got an error. Researched the error couldn't find anything, so I decided to update one of the other boot WIMs which we have and same thing (this time I didn't even try to add drivers, for one of them I even deleted the drivers and then update the DP) Here is the error I get. Error: Boot image to update: MDT Custom PE Error: Actions to perform: Add ConfigMgr binaries Disable Windows PE command line support Add drivers Error: Failed to import the following drivers: Error: The wizard det
  13. Hi everyone, I know it's possible but I don't know how to do that and I don't find the answer or my keyword search is not good... So I create a bootable ISO with a TSequence media wizard using bootable media... the way to deploy wim across the network. But now I want to put the Wim file on my ISO boot file (on a usb key after...) and modify the TS to get the wim directly on the ISO and not on the network.... how can I do that ?? I'm on SCCM SP2 R3 and try to deploy Windows 7 x64. It works fine on a network but with the wim file on the key I can optimize time to create workstati
  14. 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:
  15. Greetings all, This is a great website! I am testing an implementation of SCCM2012 RC2 and all task sequences are failing regardless of what task I attempt. I've attached the log file from the pxe booted machine. From what I can tell, WinPE is unable to communicate with the MP (MNCMP.OTC.EDU). The test environment is running native mode. The machine is getting an IP address. Any thoughts? smsts.log
  16. Hi everybody! We have a SCCM 2007 R2 environment with nearly 20 secondary sites under 1 central site. Now it comes to security permissions delegations to the local admin at the local sites that they can do their Windows 7 Rollout. I created a security structure in SCCM with a flat hierarchie of groups in the AD. For the moment it works fine. A few days ago we had the situation that seems to clear all PXE flags to the "All Systems" collections. Many machiens that will get an OS over a Task Sequence were still in the OS Deployment collection (mandentory advertised), that means that these m
×
×
  • Create New...