Jump to content


Search the Community

Showing results for tags 'ADK 8.1'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

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


Website URL


Location


Interests

Found 2 results

  1. Hi, all: Looking for some help troubleshooting a PXE issue. Thus far, I have set up WDS, MDT 2013, and ADK 8.1 and can successfully capture/deploy a Windows 8.1 image by running the Lite Touch.vbs script from my deployment share. While deploying in this method isn't terrible, the goal is to ensure that it can be done via PXE. I had previously been able to successfully boot Windows 7 machines with WDS, MDT 2012 Update 1, and ADK 8.0, but recently had to upgrade to roll out 8.1 images. Now I can't get the new 8.1 machines to boot via PXE. System in the example is prestaged in ADDS. Options 60 and 67 are unchecked on WDS server as DHCP and DNS are on another server. I've enabled logging on WDS in an effort to figure out where the PXE is failing, but it doesn't tell me much. Events only indicate that wdsnbp.com was downloaded via TFTP successfully. The machines attempting to boot say the same thing. I receive the following when booting: >>Start PXE over IPv4. Station IP address is 10.1.50.129 Server IP address is 10.1.1.216 NBP filename is boot\x64\wdsnbp.com NBP filesize is 30832 Bytes. Downloading NBP file... Succeed to download NBP file. System automatically reboots and goes straight into Windows. It's almost as if there's no boot image being referenced in the NBP file, but I've checked my Boot Images in WDS to ensure that an 8.1 image exists. I replaced the 8.1 boot image just in case and the issue is the same. Any thoughts? Your help is appreciated!
  2. I have searched around, and apparently no one else is experiencing this issue. I am hoping someone here can provide some troubleshooting tips or answers. Issue: New standalone installation of SCCM 2012 R2 Site Server fails in the prerequisite phase due to missing Windows Automated Deployment Toolkit 8.1 components. Environment: Site Server - Windows Server 2008 R2 SP1 (VMWare VM) SQL Server - Windows Server 2008 R2 SP1 (VMWare VM), SQL Server 2008 R2 SP2 CU 6, hosting SCCM and WSUS DB's. All prerequisite applications installed and functioning without error on both servers. Troubleshooting: - Confirmed version of ADK 8.1 is NOT preview. - Uninstalled and reinstalled ADK 8.1 with required components. - Verified ADK 8.1 is installed (image attached) Any help on this would be appreciated. This is not an upgrade, just a new, standalone installation. Thanks, Brian
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.