pembertj

Here is an example of something we have used on our campus. Going from this posting here: https://technet.microsoft.com/en-us/library/gg682159.aspx go to step 4 and expand and then go to "To use a custom script to determine the presence of a deployment type" and expand Success = write something to host and exit 0 failure = clear host and exit 0 ---------------------- $ini2 = Get-Content "C:\Program Files (x86)\ImageNow6\imagenow.ini" If ($ini2 -match "image02.xxx.xxx") { Write-Host "installed" Exit 0 } Else { Clear-Host Exit 0 }

I've seen this if you have any network hiccups when it is trying to download the OS Wim - network drops and you get this error. Also you may want to check your network access account and make sure it has the proper access. http://www.windows-noob.com/forums/topic/6274-how-to-set-proper-user-rights-permissions-for-sccm-2012s-service-accounts/

See here for some answers: http://www.windows-noob.com/forums/topic/12780-scep-on-windows-10-rtm/

I can't find the Technet article, but this is by design - once you upgrade to ADK 10 you can no longer customize the old boot images. ~Tom

I imported the boot images for Win10 once and it worked fine, I wanted to go back and re-import another copy to do some additional testing and have also ran into this error with no solution yet... ~Tom

I did see that page before I installed Win10 ADK but I'm guess I'm confused why I need to mess with DISM and manually adding the CABS when I can just point SCCM to the WIM and use optional components that is built into the console...? I will go through the steps anyway and report back... ~Tom

Upgraded to CM12R2 SP1 with Win 8.1 ADK, then updated ADK to 10 at a later date.

MP is VMware (server 2008 r2) - SCCM 2012 R2 SP1 CU1 and ADK 10 DPx2 are physical servers SQL on a physical server - server 2012, sql 2008 r2 Test machines are on many different subnets using ip-helpers My PXE test machine is on the same subnet so I'm not using any helpers or DHCP options. The only optional components in my boot images are WinPE-NetFx WinPE-PowerShell WinPE-DismCmdlets WinPE-StorageWMI but I'll probably take out DismCmdlets and StorageWMI

Let me know if you don't put a ticket in, I will...

I've had to do a few tickets recently for SCCM problems - turns out if they find it is a bug (which one was in my case) and not a mis-configuration of the software they will refund the cost of the ticket. ~Tom

I take it this is you as well? Any luck from Microsoft? I'm tempted to open a ticket... https://www.mail-archive.com/listsadmin@lists.myitforum.com/msg03980.html

Dewayne- Can you tell me what optional components you have installed? I'm trying to narrow down what might trigger this. I have Windows-Powershell (WinPE-Powershell) Windows-Powershell (WinPE-DismCmdlets) Windows-Powershell (WinPE-StorageWMI) Microsoft.NET (WinPE-NetFX)

I thought I had fixed it by re-building the WIM all over again but the problem has sprouted up again on a few random machines. Not sure what else to try at this point. I am going to revert to the old boot image for most of my Task Sequences until someone else has another idea...

Strange it seems rebuilding the WIM worked, I kept all the same optional components and drivers. ~Tom

I launched powershell a few different times from the f8 command prompt and it did crash at the command line once or twice...

Working on my Windows 10 Enterprise Task Sequence - This week I switched over the ADK on our site server to ADK 10. After switching the ADK I am getting an error whenever a powershell script runs in the WinPE phase. It doesn't seem to make a difference what is in the powershell script - it even fails on a one-line "Run Command Line" step that calls powershell.exe. Has anyone ran into this issue or a fix? Execution of task sequence failed. Recursion too deep; the stack overflowed. (Error: 800703E9; Source: Windows) technet post with the same issue (german), only post I could find with same issue https://social.technet.microsoft.com/Forums/de-DE/33c17c89-3000-4d8d-9b86-7c5a7b55a1fa/sccm-2012-r2-sp1-mit-adk-10-recursion-too-deep-the-stack-overflowed-error-800703e9-source?forum=systemcenterde

I've now tested the same task sequence on 3 separate models of Dell machines with no problems. It seems to be tied to (in my case) only Hyper-V VMs...

The ones I've been testing it on are Hyper-V VMs that have worked fine for win7/8.1 captures that we do. I'll test more on vmware vms and some physical machines and see if it is something with the hyper-v VMs... ~Tom //edit: strange it worked on a vmware vm with no problems. I am going to attempt on another model Dell machine here (or two). I'm curious if it is just related to Hyper-V VMs for some reason...

We just went to R2 SP1 CU1 as well. Whats strange as well is I've had it fail 20x on VMs but the first time I tried it on a physical machine it works fine...

I have been using Win8.1 ADk as well, but from what I've read on here and a couple of other blog posts it seems like you might actually need Win10 ADK - I am going to attempt the process again today with Win10 ADK installed on my site. ~tom

Captured image, I haven't tried with just the install.wim right from the DVD - not really a feasible option in the long term...

I'm having a strange issue, starting to mess around with building a Windows 10 Enterprise image for our campus and I seem to be having a problem with the task sequence properly reading in the computername that I give it. Windows PE phase: 1. Prompt for OSDComputername using VB Script (same thing we have done with Win7/8.1 with no issues) 2. Use powershell to check variables: OSDComputername shows correct name and _SMSTSMachinename shows correct name. Checking $env:computername in PE shows MINIWINPC or something (which is normal) 3. After Apply Network Settings C:\windows\panther\unattend\unattend.xml shows the correct name Windows phase: 1. Machine gets name WIN-XXXXXXX 2. Use powershell to check variables: OSDComputername shows correct name and _SMSTSMachinename shows correct name. Checking $env:computername in PE shows WIN-XXXXXX or later in the task sequence DESKTOP-XXXXXX 3. Machine joins domain and at end of task sequence has name of DESKTOP-XXXXXXX but seems to sometimes join domain under name WIN-XXXXXXX and end with DESKTOP-XXXXXX and cannot log into the machine (security database relationship error with domain controller) Has anyone ran into anything like this in Win10 or Win7/8.1 and found a solution? Out of probably 20 imaging attempts and fiddling with various settings I have only got it to get the correct name once... Thanks ~Tom

reading here (comments): https://ndswanson.wordpress.com/2015/01/09/installing-system-center-endpoint-protection-on-windows-10/ and the link he points out in his comment https://technet.microsoft.com/en-us/library/Hh508770.aspx If you manage endpoint protection for Windows 10 Technical Preview computers, then you must configure System Center 2012 Configuration Manager to update and distribute malware definitions for Windows Defender. Because Windows Defender is included in Windows 10, an endpoint protection agent does not need to be deployed to client computers. It seems that maybe Defender is replacing SCEP (mine is getting SCEP policies as well...) ~Tom

On our campus we just add a password to the boot environment (same screen in the console where you enable unknown computer support on the distribution point). Rotate it frequently if you are worried about too many people knowing the password. We don't do this on our campus but other people take an approach similar to what you mentioned - disable unknown computer support, and when you get a "new" computer manually import the computer into SCCM (so it is no longer unknown) and drop it into a collection that can see the task sequences.

I recently updated our site to SCCM 2012 R2 SP1. I was able to do a Windows 10 (10074) base capture with no problems. When deploying the captured base to a laptop I could not get it to correctly finish the task sequence - It seemed to be not joining the domain correctly then when it went to store the Bitlocker keys in AD at the end of the Task Sequence it would fail. After doing some more digging I found a few Technet posts like this one : Can't Join Domain - Windows 10 Enterprise: https://social.technet.microsoft.com/Forums/en-US/9544b999-56d4-44e4-8966-f0d455a0c337/cant-join-domain-windows-10-enterprise?forum=WinPreview2014Setup Disabling the bitlocker steps will allow the Task Sequence to finish with no problems, but this would not be a long term solution to the problem. Has anyone else ran into this problem and/or been able to fix it? Thanks ~Tom