DerDa

Hi, I am currently trying to create a Task Sequence to Upgrade Windows 8 to Windows 8.1. I want to use a Task Sequence because the customer is using 802.1x network authentication and when just running an Application or Package with the setup.exe /auto:upgrade command the dot3svc service is not coming up again when the PC boots into Windows 8.1 the very first time. And without this service Windows is not able to authenticate with the network. The workaround for this issue is just another reboot. Therefore I created a Task Sequence with the following steps: 1. Reboot into OS 2. Upgrade to Windows 8.1 (setup.exe /auto:upgrade) 3. Reboot into OS 4. Install Windows Updates 5. Install a fix for Single Sign On for Lotus Notes 6. Reboot into OS It's doing step 1+2 and then nothing. Could it be that the problem is, that the Upgrade is moving all data from C:\ to C:\Windows.old including the _SMSTaskSequence folder? But why am I not able to find the folder within C:\Windows.old? I've attached some log files (execmgr / smsts / tsagent). If required I will provide further log files. Just to avoid a few questions: 1. I tried to argue to DO NOT an Upgrade for several reasons (e.g. no sysprep support) but the customer still want to have an upgrade instead of a new installation 2. I've tried using an application and a package 3. Just using setup.exe /auto:upgrade without 802.1x authentication is working fine, if not using a task sequence 4. I've set the the option "Configuration Manager client will force a mandatory device restart" in application user experience settings 5. A rollout without 802.1x is not an option 6. I am using SCCM 2012 R2 SP1 with one primary site. It would be nice if someone could help me out. Thank you Regards Ingo WIBMZVM00033.zip

Hi, I have testes with 7 new VMs which are in the same subnet as the SCCM server with advanced logging enabled. You can find attached three smsts.log files. For your information: I haven't changed anything except of the Logging settings for the Task Sequence. So these are the same as in my first try. This time nearly all PCs failed at "SAP 730" Installation package which ran fine in the past tries. I've added two logs with SAP issue und one with Lotus Notes issue again. Regards Ingo SCCMLogs.zip

Thank you. I have now set up a new Boot Image and TS and will try with the logging settings again. I will post further information.

Thanks for your answer. As said I don't think that the problem are the packages where the TS failed, because the TS succeeded with other PCs. All PCs were started with the same Task Sequence. Furthermore you can see in the smsts.log that the files for Office were downloaded (e.g. 55281-smsts-20131009-125912.log)

Hi, did you ever solve this issue? Thanks

I've attached some smsts Log files of three different PCs which have failed. Hopefully someone is able to help me. Thank you! Logs.zip

Hi, I am having some issues while setting up several PCs using a PXE OSD task sequence to known Computers (I've added them manually using a file) with Windows 8 including several packages. My problem is that I can set up one or two PCs at the same time without any issues. Last night we tried to set up 15 PCs at the same time, but unfortunately only two of them succeded (the first two which were started - different DPs - so one per DP). The other PCs failed on different steps during the task sequence. As said when running only one PC there is no problem. Some Infos about my Environment: One Primary Site on a SCCM 2012 SP1 with one additional DP in another WAN location. The Servers are running Windows Server 2012. The PCs are all on other subnets and separated from the Server subnet. Packages and Updates are working well. Hope you can help me on this. Thank you Regards Ingo