anyweb

have you distributed both architecture boot images ?

I'm still working on it, these guides take time...and i want it to be good...

and if you remove line 1... what happens ?

i believe it's a bug and in both 1511 and 1607 versions of the Windows 10 ADK, Microsoft is aware of it here's something on connect, vote for it https://connect.microsoft.com/ConfigurationManagervnext/feedback/EditFeedback.aspx?FeedbackID=3110654

thanks ! can you attach the ccmsetup.log as well please ?

thanks ! can you attach the ccmsetup.log as well please ?

i don't understand your question, did you use my PowerShell script to create the collections ?

don't use copyprofile it's a bad idea, especially with windows 10, what exactly do you need configured in the default profile ? also what version of ConfigMgr are you using ?

that guide is for the technical preview release and really is only for very short term labs (limited to 10 clients) i'm working on getting a newer guide for SCCM Current Branch out this week, so please be patient

surely you could save a lot of time by modifying this to suit your needs, it works https://www.niallbrady.com/2016/05/17/introducing-the-windows-10-uefi-bitlocker-frontend-for-system-center-configuration-manager-current-branch/

have you applied this hotfix ? http://support.microsoft.com/kb/2905002/en-us

what error do you get exactly ?

check the speed and duplex settings of the nic in question, perhaps they are hard coded to 100mb full duplex ?

what do the WUAHandler.log, PatchDownloader.log and UpdatesHandler.log files reveal ?

you can press left shift and f10 does that help, if not grab the logs after the failure the unattend.xml file location varies depending on what part of the deployment process you are in, but in general look in C:\Windows\Panther\

please attach your smsts.log file and unattend.xml

try at least 10gb for your SCCM lab and things will be much better, the more ram you give it (or rather SQL) the better.

hi, the smsts.log file will be on the client that you are pxe booting, you say it doesn't work (pxe boot), so what does happen, you need to be more descriptive

the All Workstations collection should automatically populate with client computers based on the membership query, if you want to manage your AD Server then install the configmgr client on it as you see fit, that's entirely up to you, but I wouldn't place it in the All Workstations collection, perhaps you might create a All AD Servers or similar collection

IntroductionMicrosoft has released yet another update for System Center Configuration Manager (Current Branch), this time it’s version 1610, that means that since System Center Configuration Manager’s (Current Branch) first release there have been the following releases: 1511 (Initial release, soon to be unsupported) 1602 1606 followed by Update rollup 1 1610 So what’s new ? Windows 10 Upgrade Analytics integration allows you to assess and analyze device readiness and compatibility with Windows 10 to allow smoother upgrades. Office 365 Servicing Dashboard and app deployment to clients features help you to deploy Office 365 apps to clients as well as track Office 365 usage and update deployments. Software Updates Compliance Dashboard allows you to view the current compliance status of devices in your organization and quickly analyze the data to see which devices are at risk. Cloud Management Gateway provides a simpler way to manage Configuration Manager clients on the Internet. You can use the ConfigMgr console to deploy the service in Microsoft Azure and configure the supported roles to allow cloud management gateway traffic. Client Peer Cache is a new built-in solution in Configuration Manager that allows clients to share content with other clients directly from their local cache with monitoring and troubleshooting capabilities. Enhancements in Software Center including customizable branding in more dialogs, notifications of new software, improvements to the notification experience for high-impact task sequence deployments, and ability for users to request applications and view request history directly in Software Center. New remote control features including performance optimization for remote control sessions and keyboard translation. This release also includes new features for customers using Configuration Manager connected with Microsoft Intune. Some of the new feature include: New configuration item settings and improvements now only show settings that apply to the selected platform. We also added lots of new settings for Android (23), iOS (4), Mac (4), Windows 10 desktop and mobile (37), Windows 10 Team (7), Windows 8.1 (11), and Windows Phone 8.1 (3). Lookout integration allows to check device’s compliance status based on its compliance with Lookout rules. Request a sync from the admin console improvement allows you to request a policy sync on an enrolled mobile device from the Configuration Manager console. Support for paid apps in Windows Store for Business allows you to add and deploy online-licensed paid apps in addition to the free apps in Windows Store for Business. Upgrading to 1610You can upgrade directly to System Center Configuration Manager (Current Branch) 1610 from 1511, 1602 or 1606. If you are however upgrading from System Center Configuration Manager 2012 (SP1 or R2SP1) then you must upgrade to 1606 first. Below you can see the process of upgrading from 1606 to 1610. Click on Check for Updates if nothing appears today (2016/11/18) run the PowerShell script to get into the fast ring for this release. Once it’s found by the sub-system, the console will list the update in a state of downloading. and the dmpdownloader.log will reveal the Generating state message 6 and it’s corresponding guid. Once it’s downloaded the console will list it as state available. Installing the UpdateRight click on the update and choose Install Update Pack when the Wizard appears, make your choice for pre-reqs and click next. review list of Features included in this update pack, only one was selected when I ran this, so I selected the other two. Before clicking next at the Client update settings please see this post and review the EULA, Accept and continue close that wizard when done Note: The CMUpdate.log will take some time to start logging the installation of the update, so be patient if nothing appears to happen, it will. Once the update is installed you’ll see a HMAN notification. at which point you can upgrade the console to the latest version once done, the console version also sports a new Support ID

hi Peter, please post the smsts.log file so we can determine why it failed, first thoughts would be to verify the cdkey and/or unattend.xml references

have you tried integrating MDT into ConfigMgr and using what it provides ?

you can use maik kosters web services to achieve that, have you looked at them at all ?

what does distmgr.log tell you ?

from log1 that means it cannot communicate with the mp due to network issues (no ip, or dns problems), so you need to pause the task sequence mid action, and verify if it indeed is able to communicate with the dp/mp otherwise of course it will fail most likely cause, lack of network drivers in the boot image for the hardware involved cheers niall