Jump to content


Search the Community

Showing results for tags 'vnext'.

  • 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 1 result

  1. Hi All, We are in the process of testing Windows 10 in-Place Upgrades which is going pretty well. The problem we are running into is that if the VNext UPgrade task sequence fails, it disappears from the software center and the only way to get it back is to remove and re-install the client. In our configuration, the re-install takes at least 10 hours to fully complete which is a giant waste of valuable troubleshooting time. Has anyone seen this before? I have tried using this rerun task sequence which allows you to remove the wmi information but that didn't do anything. I've tried removing the deployment and redeploy, I've deleted the entire task sequence and recreated it, I've removed the computer from the collection and added it back in. Nada nada nada. Very frustrating. I actually have a ticket open with MS premier support and am waiting for them to get back to me on this. I just thought I'd post to see if anyone has run into something similar. Any feed back is appreciated. Thanks! -James
×
×
  • 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.