thadkew

With Win10, there are a lot of ways you can deploy it. One way is to lay it down, install apps and then capture (similar to win7) another is to use provisioning packages (take an OEM image and just run the provisioning packages to customize it) If you're going to start deploying Win10, you need to make sure you have the latest Windows ICD. Also, check around for the guides here on this site as well as Johan's site

OK Use the drivers from here: http://ftp.hp.com/pub/caps-softpaq/cmit/HP_WinPE_DriverPack.html Add them to your deployment share and ensure they are added to the boot image. It should work once you do that. Good luck!

OK So the boot image is based on the version of MDT you're using, not the version of OS you're deploying. That means that if you're using MDT 2010, you can use the Windows 7 NIC drivers in the boot image. If you're using MDT 2012, you would use the WIndows 8 drivers, etc... If you're deploying Windows 7, you have probably added the Windows 7 NIC drivers to the driver packages, and possibly to the WinPE boot image, but if you're using MDT 2013, it will not recognize that. You will need to download the Windows 8.1 NIC drivers and import those into the boot image and update the deployment share. Please provide what version of MDT you're using and we can point you to the proper NIC drivers that you should be using.

One of the things to be mindful of is that you don't want to put the Windows 7 drivers on your boot image. You'll need the drivers required by the version of WinPE you're using. For example: If it's a WinPE 5, you'll be using Win8.1 drivers for your nic.

This indicates that the drivers haven't been added to the boot image. Looks like it's missing the Intel® Ethernet Connection I219-V drivers on the boot.wim

We have a build and capture task sequence as well as a deploy task sequence. Because I'm super paranoid, I have put the same task in both: Create a package with your LayoutModification.xml file Create a group toward the end of your imaging process called Image Customizations create a Run Command Line step called Set-ExecutionPolicy Bypass and use this command: powershell.exe -command "Set-ExecutionPolicy Bypass" create a Run Command Line step called "Set Layout" and use this command: powershell.exe import-startlayout -layoutpath LayoutModification.xml -mountpath $env:SystemDrive \ and make sure that it uses your customization package Again, I'm super paranoid and I don't trust anything to work properly. (Measure twice - cut once, am I right??) I hope this helps a little.

You should create a new start menu now. I had the same issue and after creating a new start menu that I applied during the OSD process, all those place holders are gone. check here: http://www.osd-couture.com/2014/11/windows-10-deploying-customized-start.html https://winpeguy.wordpress.com/2015/12/09/win10-start-menu-cleanup-using-defaultlayouts-xml/

You're going to want to create the media into an ISO that you would write to a USB. You'll need the MDT server and an ISO writer (something like Ultra ISO) and a large USB drive (64gb maybe? Depends on the drivers and the apps) If you notice in MDT, you have the option to create MDT Media. Use this site as a tutorial to do exactly what you want: http://www.vkernel.ro/blog/creating-an-offline-mdt-deployment-media

can you hit f8 to open command line and then do a diskpart? I'd be interested in seeing if it can list your volumes. I'm thinking that it doesn't have the disk drivers to be able to access the drive. http://happysccm.com/2014/12/16/format-failed-0x80070057-during-task-sequence/ also, you might need the KB and add it to your boot wim: Win10ADK-Hotfix-KB3143760.exe

Few things: Are you using the UEFI formatting or MBR formatting on these? All indications are that the drive is either still encrypted/locked or hasn't been formatted properly.

As with most things involving SCCM and OSD, there are multiple ways of doing it. I learned (through a lot of beating my head against the wall) that USMT can be it's own task sequence. You can configure it separately and run it outside of an OS deployment. It can even be done locally by running the USMT command to save it either on a flash drive or on a network share. If you do that, you can even double click the USMT file and put in the security code and add all the profiles on the newly imaged machine. USMT is pretty cool. Then you can If you're wanting to run USMT on an existing Win7 and then you wanna wipe and load a new OS, start up a new task sequence, add a command line step at the very beginning and run the USMT command similar to this: scanstate \\server\share\migration\mystore /i:migapp.xml /i:migdocs.xml /o /config:config.xml /v:13 /encrypt /key:"mykey" Then you can continue into the wipe and load. To restore, you'd use something like this: loadstate \\server\share\migration\mystore /i:migapp.xml /i:migdocs.xml /v:13 /decrypt /key:"mykey" Just remember, task sequences are compeltely flexible and can become whatever you want them to do. Here's more info on the USMT commands. https://technet.microsoft.com/en-us/library/hh825175.aspx

Need your SMSTS.LOG file. Could be a bunch of things. Couple of questions: -UEFI or Legacy boot? -Are you using any queries when installing drivers?

That works perfectly. Don't know what I would do without you, Niall. Thanks so much.

OK Figured it out. I'm going to document it here so that I can find it if I need it later. Step 1: Create ROLES in MDT 2013 and add your ConfigMgr Packages to the newly created Role Step 2: Update the customSettings.ini file to point to the MDT Database Step 3: In the SCCM 2012 Task Sequence, add a task to install Packages and put a dot in the Install software packages according to dynamic variable list and set the Base variable name to PACKAGES. Also put a check in the box for If installation of a software package fails, continue installing other packages in the list Step 4: In the Options of the newly created Install Package step, add a task sequence variable named PACKAGES to the name of your newly created ROLE in MDT 2013 OPTIONS: Add a new group with the Role Name and add the Install Package step underneath. Set the task sequence variable of the newly created group (name it PACKAGES) to the name of the MDT 2013 ROLE. Add a GATHER step before the newly created Install Package step. This seemed to work for me.

Been pulling the remainder of my hair out. Trying to install software packages according to a dynamic variable list. I have followed the steps of Jason Sandys in this post, and Jarvis Davis in this post In MDT 2013, I have created the ROLES properly, adding the ConfigMgr Packages with their proper XXX00000:Program parameter. I have set the Task Sequence Variable for ROLE to be WTS and set a Gather step before the install package. In the SCCM 2012 task sequence, I have added an Install Package step, selected Install software packages according to dynamic variable list and given the base variable name of ROLE I have updated the custom settings.ini file to show: [settings] Priority=CSettings, CPackages, CApps, CAdmins, CRoles, Locations, LSettings, LPackages, LApps, LAdmins, LRoles, MMSettings, MMPackages, MMApps, MMAdmins, MMRoles, RSettings, RPackages, RApps, RAdmins, Default Properties=MyCustomProperty [Default] _SMSTSOrgName=MyCompany Inc. OSInstall=Y SkipCapture=YES SkipAdminPassword=NO SkipProductKey=YES SkipComputerBackup=YES SkipBitLocker=YES EventService=http://WPS01:9800 ;[DynamicPackages] ;SQLServer=WPS01 ;Database=MDTDB ;StoredProcedure=RetrieveApplications ;StoredProcedure=RetrievePackages ;Netlib=DBNMPNTW ;Parameters=MacAddress ;SQLShare=DeploymentShare$ [CSettings] SQLServer=WPS01 Instance=MDTDB Database=MDTDB Netlib=DBNMPNTW SQLShare=DeploymentShare$ Table=ComputerSettings Parameters=UUID, AssetTag, SerialNumber, MacAddress ParameterCondition=OR [CPackages] SQLServer=WPS01 Instance=MDTDB Database=MDTDB Netlib=DBNMPNTW SQLShare=DeploymentShare$ Table=ComputerPackages Parameters=UUID, AssetTag, SerialNumber, MacAddress ParameterCondition=OR Order=Sequence [CApps] SQLServer=WPS01 Instance=MDTDB Database=MDTDB Netlib=DBNMPNTW SQLShare=DeploymentShare$ Table=ComputerApplications Parameters=UUID, AssetTag, SerialNumber, MacAddress ParameterCondition=OR Order=Sequence [CAdmins] SQLServer=WPS01 Instance=MDTDB Database=MDTDB Netlib=DBNMPNTW SQLShare=DeploymentShare$ Table=ComputerAdministrators Parameters=UUID, AssetTag, SerialNumber, MacAddress ParameterCondition=OR [CRoles] SQLServerWPS01 Instance=MDTDB Database=MDTDB Netlib=DBNMPNTW SQLShare=DeploymentShare$ Table=ComputerRoles Parameters=UUID, AssetTag, SerialNumber, MacAddress ParameterCondition=OR [Locations] SQLServer=WPS01 Instance=MDTDB Database=MDTDB Netlib=DBNMPNTW SQLShare=DeploymentShare$ Table=Locations Parameters=DefaultGateway [LSettings] SQLServer=WPS01 Instance=MDTDB Database=MDTDB Netlib=DBNMPNTW SQLShare=DeploymentShare$ Table=LocationSettings Parameters=DefaultGateway [LPackages] SQLServer=WPS01 Instance=MDTDB Database=MDTDB Netlib=DBNMPNTW SQLShare=DeploymentShare$ Table=LocationPackages Parameters=DefaultGateway Order=Sequence [LApps] SQLServer=WPS01 Instance=MDTDB Database=MDTDB Netlib=DBNMPNTW SQLShare=DeploymentShare$ Table=LocationApplications Parameters=DefaultGateway Order=Sequence [LAdmins] SQLServer=WPS01 Instance=MDTDB Database=MDTDB Netlib=DBNMPNTW SQLShare=DeploymentShare$ Table=LocationAdministrators Parameters=DefaultGateway [LRoles] SQLServer=WPS01 Instance=MDTDB Database=MDTDB Netlib=DBNMPNTW SQLShare=DeploymentShare$ Table=LocationRoles Parameters=DefaultGateway [MMSettings] SQLServer=WPS01 Instance=MDTDB Database=MDTDB Netlib=DBNMPNTW SQLShare=DeploymentShare$ Table=MakeModelSettings Parameters=Make, Model [MMPackages] SQLServer=WPS01 Instance=MDTDB Database=MDTDB Netlib=DBNMPNTW SQLShare=DeploymentShare$ Table=MakeModelPackages Parameters=Make, Model Order=Sequence [MMApps] SQLServer=WPS01 Instance=MDTDB Database=MDTDB Netlib=DBNMPNTW SQLShare=DeploymentShare$ Table=MakeModelApplications Parameters=Make, Model Order=Sequence [MMAdmins] SQLServer=WPS01 Instance=MDTDB Database=MDTDB Netlib=DBNMPNTW SQLShare=DeploymentShare$ Table=MakeModelAdministrators Parameters=Make, Model [MMRoles] SQLServer=WPS01 Instance=MDTDB Database=MDTDB Netlib=DBNMPNTW SQLShare=DeploymentShare$ Table=MakeModelRoles Parameters=Make, Model [RSettings] SQLServer=WPS01 Instance=MDTDB Database=MDTDB Netlib=DBNMPNTW SQLShare=DeploymentShare$ Table=RoleSettings Parameters=Role [RPackages] SQLServer=WPS01 Instance=MDTDB Database=MDTDB Netlib=DBNMPNTW SQLShare=DeploymentShare$ Table=RolePackages Parameters=Role Order=Sequence [RApps] SQLServer=WPS01 Instance=MDTDB Database=MDTDB Netlib=DBNMPNTW SQLShare=DeploymentShare$ Table=RoleApplications Parameters=Role Order=Sequence [RAdmins] SQLServer=WPS01 Instance=MDTDB Database=MDTDB Netlib=DBNMPNTW SQLShare=DeploymentShare$ Table=RoleAdministrators Parameters=Role I cannot get this to actually install the packages. I receive errors in the logs like this: Failed to run the action: Install Role Packages. Unspecified error (Error:800004005; Source Windows) What am I missing?

I created a new x64 boot image and it appears to have resolved my issue. Even the one machine that has been causing me all kind of problems has now been tamed... Fingers crossed that the boot image is the fix.

Recently updated to R2 and sporadically we have machines going through OSD that will restart after applying the operating system step (normal) and run through the windows setup, appluying drivers and such (also normal). What's not normal is that occassionaly, machines will restart and just go to a black screen with a white arrow. The dreaded "Black Screen of Death." I've ensured that all drivers are up to date and we're using a query for which device drivers to install. This happens on multiple models, so it's not just one particular model. Task sequence is for Windows 7 x64 The error log shows the lines "Failed to load envrionment from c:|_SMSTaskSequence\TSEnv.dat (80040154) " and "Failed to load the task sequencing Environment object from C:\_SMSTaskSequence\TSEnv.dat Code(0x80040154)" Any ideas how to combat this? Teh Googles are not kind to my searches.

Thanks Kimmyel. I added that script to my build and capture sequence and it didn't remove the apps. The script ran fine, no errors. What i fear is happening, and it seems to make sense, is that the Apps are being installed when Windows 8.1 initializes. Keep in mind, however, that I'm just testing the capture. When I start the captured image, the apps show up. I haven't tried the standard computer task sequence to see if the apps might be removed.

Am i right in assuming that the apps for Windows 8.1 (like Food&Drink, Health&Fitness, Skype, etc) are installed as the OS "prepares" itself. The reason for my assumtion is because while trying to capture a base image, i have a powershell function that removes those (and other) apps, but for some reason the apps are there after the machine starts. My powershell is this: powershell.exe -executionpolicy bypass -command "&{Get-AppxPackage -AllUsers | Remove-AppxPackage}" However, when the image is started, the apps are still there. Should this command be a step in the Standard Computer deployment and not in the build and capture section?

Don't know if this should be in deployment or in this area. So here goes: Am i right in assuming that the apps for Windows 8.1 (like Food&Drink, Health&Fitness, Skype, etc) are installed as the OS "prepares" itself. The reason for my assumtion is because while trying to capture a base image, i have a powershell function that removes those (and other) apps, but for some reason the apps are there after the machine starts. I'm going to ask this in deployment, but i was wanting some background on how it may work. Thanks!

Is there a way to not delete the MIG file after the USMT has run (successfully or unsuccessfully). I deployed the OS to a computer and the USMT hardlink captured fine, but after the OS was installed and the USMT went to apply the profile, there was a problem with the a local account and didn't apply the USMT mig file. In the task sequence, I have for the restore sequence to "Continue on error." Is there anyway to keep the task sequence from delelting the USMT folder? I can't afford to lose any more MIG files because of a local account problem.

Is it possible to have administrators dynamically added based on OU? Like maybe an If/Then, for example? We have several OUs and within each one, the administrator needs to be set based on a group within that OU. The reason it's necessary is that the GPO isn't running properly and the group that controls the GPO doesn't know what they're doing. We've waited on them for about 5 months and since it's clearly over their heads (and above my pay grade), this seems like the only way around it. I have some administrators that i've added to the customsettings.ini. i didn't know if i there were more ways to do it...

Yes it is possible. And it works well. I created a new application with a text file and the Lite Touch wim in a folder and a bat file to do the leg work: The text file preforms the diskpart functions and the bat file does the rest: Here's the text file: select disk 0 select partition 2 assign letter v And here's the bat file: REM copy diskpart command file xcopy "%~dp0recover_zone.txt" c:\ REM run diskpart diskpart /s c:\recover_zone.txt ping -i 127.0.0.1 >NUL REM copy WIM and SDI xcopy "%~dp0LiteTouchPE_x86-(2).wim" v:\ xcopy "%~dp0boot.sdi" v:\ ping -i 127.0.0.1 >NUL REM Delete file del c:\recover_zone.txt REM bcdedit /create /d "Windows 7" /application osloader echo Exporting the system BCD store to BcdTemp bcdedit /export BcdTemp REM if errorlevel 1 echo Error - we need to have admin privileges. REM if errorlevel 1 goto Endit rem Set the name of the Winpe .wim file set WimNm=LiteTouchPE_x86-(2).wim rem Set the name of the WinPE .sdi file set SdiNm=boot.sdi rem Set the drive where the two WinPE boot files are located ( x: with no \ ) set WPDrv=V: rem Set the folder path to the WinPE boot files ( no drive letter, no trailing \ ) set WPPth= rem Description that shows up in the boot menu set WPDes="Recovery" rem Create the osloader and device options entries in the bcd store. rem Get the randomly created GUID numbers that uniquely identify our two entries. For /F "tokens=3 delims= " %%1 in ('bcdedit.exe /store BcdTemp /create /application OSLOADER /d %WPDes%') do set guid1=%%1 echo Osloader entry id is %guid1% For /F "tokens=3 delims= " %%1 in ('bcdedit.exe /store BcdTemp /create /device /d %WPDes%') do set guid2=%%1 echo Device options entry id is %guid2% echo Setting items in the osloader entry bcdedit /store BcdTemp /set %guid1% device ramdisk=[%WPDrv%]%WPPth%\%WimNm%,%guid2% bcdedit /store BcdTemp /set %guid1% osdevice ramdisk=[%WPDrv%]%WPPth%\%WimNm%,%guid2% bcdedit /store BcdTemp /set %guid1% path \windows\system32\boot\winload.exe bcdedit /store BcdTemp /set %guid1% locale en-US bcdedit /store BcdTemp /set %guid1% inherit {bootloadersettings} bcdedit /store BcdTemp /set %guid1% systemroot \windows bcdedit /store BcdTemp /set %guid1% detecthal Yes bcdedit /store BcdTemp /set %guid1% winpe Yes bcdedit /store BcdTemp /set %guid1% ems No echo Setting items in the device options entry bcdedit /store BcdTemp /set %guid2% ramdisksdidevice partition=%WPDrv% bcdedit /store BcdTemp /set %guid2% ramdisksdipath %WPPth%\%SdiNm% echo Setting bootmgr to include the WinPE entry in the boot display list bcdedit /store BcdTemp /set {bootmgr} displayorder %guid1% /addlast rem Create an undo cmd file to delete the entries directly from the system bcd store. echo Creating the DelWinpe.cmd undo command file echo bcdedit /delete %guid1% >>DelWinpe.cmd echo bcdedit /delete %guid2% >>DelWinpe.cmd echo Display bootmgr and the two new entries bcdedit /store BcdTemp /enum {bootmgr} bcdedit /store BcdTemp /enum %guid1% bcdedit /store BcdTemp /enum %guid2% echo. If errorlevel 1 echo Error - something went awry. Not importing the temporary store. If errorlevel 1 goto Endit REM echo Ready to import the temporary store into bcd system store... REM pause echo Importing BcdTemp into the system BCD store. bcdedit /import BcdTemp :Endit set guid1= set guid2= set WpDrv= set WPPth= set WimNm= set SdiNm= set WPDes= bcdedit /timeout 3 I found the meat of the script here http://social.technet.microsoft.com/Forums/en-US/itprovistasetup/thread/333f16c6-efca-4899-8cf2-95f05af61986/ Then i put the task at the end of my task sequence. Tested and it works!!!

I was checking this thread: http://www.edugeek.net/forums/o-s-deployment/93538-microsoft-deployment-toolkit-2012-rtm.html

Can the deployment share built in 2010 be opened in 2012? I read somewhere that if you install 2012 on top of your existing 2010 installation, things will break. Anyone have any history with it?