ersatyle

right, but I don't think the TS variables are already set up so early in WinPe (I may be wrong), that's why I was thinking an ignore button would just do the trick (there is probably more clever solutions but my coding abilities are somewhat limited)

well in a standalone image you don't need network connectivity to run the task sequence right? you can just run it from an usb key. But it's still using the boot image to boot in winPE at the beginning, so if we have a script asking for network in the boot image without any way to ignore it the task sequence can't start. hope it helps, let me know if it still unclear?thanks

so I've implemented the script in an MDT 2013 update 2 boot image (integrated with sccm) , works great, detects when no network or when no disk, really really usefull, should be included by default Niall, thanks a lot for putting this together and sharing it! Now... i'm sometimes using a standalone image, using the same boot image, is there a way in the script to detect it (or prestaged media) and bypass the network detection in this case? yeah I could choose another boot image without the script but I have other customizations as well and like to keep thing as simple as possible thanks a lot

nice guide thanks! do you know which method take precedence if the smsts.ini is specified in the wim and in the extrafiles? And can you check or change the extrafiles folder after the boot image has been created? (is it the same as the source directory for the prestart command?Or could you add those values from the prestart command, like registry in WinPE?) (IE: i'm not sure if I did add this extra file folder during the creation of the boot image, and I'd like to avoid creating a new one...) Thanks a lot

Hi, probably not a direct answer but when confronted with the same scenario instead of using the application model I use the old package system, and specify for the deployment to run the program from the Distribution Point, so that won't use the cache at all. (the application model will download in the cache, there is no options to avoid that) I've also considered increasing the cache size with the right click tools from now micro on the targeted collection ( you can also clear the cache) hope that helps, good luck

thanks so much for this script, works top notch (using winpe 10 x64 from mdt 2013 integrated in sccm 1606 & adk 1607 here.) only suggestion would be to add a detection or an ignore button in the case of a standalone media, so that the same boot image could be used for online or offline imaging. But yeah that will help tremendously for the new models!

hi, sounds super interesting and usefull I'll try to implement this with an mdt boot img quick question before how would it reacts if it's a standalone image? thanks!

i know this is old but as it came up from a google search my way to do this (notably for activInspire) is to wrap those installer with the PowerShell App Deployment Toolkit as I really don't want to create 5 or 6 applications at each new version and manage the supersedence and dependencies the task sequence idea is good also but you loose the ability to deploy to a user collection and you still have to create 5 or 6 package (or 1 pacakge and 6 program) hope that helps.

hi, would you be kind enough to share how did you manage to find this issue? I see this error only on dell latitude 2120 laptop, and I'm really not sure what could cause it. thanks

hi, I'm getting the exact same problem here also. Anyone found anything related to this? thanks

hello, did you uncheck "use media hook" when creating your boot image if you used mdt integration? For me I fill the OSDcomputername variable only for the new computers, if the computer already exist in the sccm database it will keep the existing name. now I use the Apply Windows Settings step also, but don't have a key as we use a key management server how do you manage your key after that?maybe could you post some screenshot to give a more clearer idea of what your doing and what's wrong. good luck

Hello all, hopefully you can help solving this issue that's bugging me for quite a time. When we're deploying new computers, or computers that are not in the sccm database, we use the OsdComputername variable to name the computer, it's working well but when I'm looking for the logs in the console under system status> advertisment status the default computer name (minint-xxx) appears in the system column instead of the given name, until the task "Setup windows and ConfigMgr" has completed (and still the new name is displayed only for the "Software Distribution" component. here is a screenshot of what I see, it's not really important for 1 or 2 computer but when we're deploying 100 at the same time it's impossible to troubleshoot. https://skydrive.liv...3E677D04EA!5652 so how could we have the name we had specified in the osdcomputername variable at the start of the task sequence displayed in the "system" name in the status messages report? I know there is the the _SMSTSMachineName buit in variable but i'm sure how I can use that in my task sequence. thanks

salut, do you try adminstrateur or administrator account? did you modify the unattended.xml file (or do you specify it in the next step "configure windows and configmgr?) and if you enable this step is it working?

hi, I don't have a "capture" TS I use the iso created via right click on task sequence > create task sequence media>capture media" (3rd choice) And then I run the cd directly from the live OS (it starts the sms\bin\i386\tsmbautorun.exe) (so I'm not using the guide here on windows noob to capture the installation, right?) see here if it can help http://www.kozeniauskas.com/itblog/2008/01/21/sccm-how-to-capture-image/ http://technet.microsoft.com/en-us/library/bb694129.aspx As I said, I don't have sccm client on the machine at this point, I'll install it later via a task sequence once the computer is in our network. Hope this can help.

hello, I'm currently working on the same scenario, this is what I do: install windows7, boot in audit mode customize the installation with applications, specifig config etc the machine is not in the domain, nor the sccm client installed on it once I'm done with the customization, I capture it using the "capture media" included in sccm (right click on task sequence > create task sequence media>capture media" you'll have a iso file, you can burn it and launch it (you can't boot on it), it will capture your installation and create a wim for you After that I import the wim file, and include it in my task sequence. good luck!