Jump to content


Search the Community

Showing results for tags 'MDT 2013'.



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 3 results

  1. Hi Everyone, sorry in advance for been a bit long winded. I am having an issue with MDT 2013, ADK for 8.1 working WDS. To start deploying server 2012, 8.1 and eventually Windows 10 (I know I will have to update MDT and ADK), a new server with 2012 R2 was built. MDT 2013 and ADK for Windows 8.1 was installed. I added the nic drivers to MDT out of box drivers. I then created the boot wims through MDT Update Deployment Share and installed WDS, I added the boot wim to WDS. However when I pxe boot I get the following error message after hitting F12 for network service boot. http://www.google.com/imgres?imgurl=https://neosmart.net/wiki/wp-content/uploads/sites/5/2015/01/your-pc-needs-to-be-repaired-1.jpg&imgrefurl=https://neosmart.net/wiki/your-pc-needs-to-be-repaired/&h=600&w=980&tbnid=lgk55v24IoFx1M:&docid=raSohln5yHyVpM&ei=-eSwVbqNOMGX7Qa8vaiQAw&tbm=isch&ved=0CB0QMygAMABqFQoTCPrtmY-n8cYCFcFL2wodvB4KMg However if I create a bootable cd from the iso that was created through Update Deployment Share, it works correctly. I had a look through the following thread https://social.technet.microsoft.com/Forums/windowsserver/en-US/a164b948-1778-42bd-8d77-9cef1ca70866/image-capture-boot-image-fails-with-0xc000000f?forum=winserversetup and mounted and unmounted the wim using DISM, still got the same error. Next I restored the machine to an earlier snapshot (Aren’t they Great saved me many a time), and installed MDT 2012 and ADK for Windows 8, same error. Final test to make sure that it wasn’t the server. I updated the old server which has server 2008 R2 on it with MDT 2010 and ADK 2.0 (which does work honest ) to MDT 2012 and ADK for Windows 8, regenerated the boot image added to WDS and get the same boot BCD error. At this point I am stuck, has anyone come across this before or have any ideas? Any Help appreciated Kola
  2. Hello! Im trying to create a "standard" image for Windows Embedded 8 Industry Enterprise in MDT 2013 but for some reason when i click through the wizard i can't choose the language pack.. Please see the following image: Anyone know how to solve this? What i wan't is to install a english language pack (en-us) but as you can see there is now available packs. If i look in Windows System Image Manger on the image i can see that the language pack is installed.. Any tips or help is very much appreciated! // Stylaren
  3. I have been beating my brains out for over a week. I have a few models of Dell PC's that can no longer PXE boot to the LiteTouchPE_x64.wim image. However, the can boot to the 32 bit one. What it does is it loads (slowly) the Boot image and as it gets ready to load it gives an error from Windows Boot Manager: Windows failed to start. A recent hardware or software change might be the cause. Blah Blah Info: The Application or operating system couldn't be loaded because the required file is missing or contains errors. Different models show different missing files Dell Optiplex 745's bxvbda.sys Dell Optiplex 780's winload.exe Both of these models were working previously and no changes were made to the server before the error occurred.
×
×
  • Create New...