Windows deployment wizard
-
Tuesday, January 22, 2013 3:44 AM
Hi,
I am trying to deploy Windows 7 with few applications in on new machine. The below steps are displayed after F12 PXE Boot.
Select the Task Sequence
Specify the product key needed to install this operating system
Configure the Computer Name
Join the machine in domain
Specify whether to restore data and settings
Set the time Zone
Select one or more applications to install
Select to Enable bitlocker
Ready to beginI need to disable the below task sequences. How do i disable it in MDT
Specify the product key needed to install this operating system
Specify whether to restore data and settings
Set the time Zone
Select one or more applications to install
Select to Enable bitlockerRegards,
Boopathi S
- Edited by boopathi subramaniam Tuesday, January 22, 2013 5:44 AM
All Replies
-
Tuesday, January 22, 2013 6:16 AM
SkipProductKey=YES
You can find the documentation in the link below, its great :)
http://www.microsoft.com/en-us/download/details.aspx?id=25175
-
Tuesday, January 22, 2013 10:51 AM
hi Samus,
It is already there in the CustomSettings.ini. But still i am asking to select product key and applications, Please help me to fond the issue
[Default]
OSInstall=Y
SkipBDDWelcome=YES
SkipAdminPassword=YES
SkipLocaleSelection=YES
KeyboardLocale=0409:00004009
KeyboardLocalePE=0409:00004009
SkipApplications=YES
SkipAppsOnUpgrade=YES
SkipCapture=YES
SkipProductKey=YES
SkipTimeZone=YES
TimeZoneName=India Standard Time
SkipBitLocker=YES
SkipUserData=YES -
Tuesday, January 22, 2013 12:20 PM
Hmm that is strange. If you have a volume license key then you can add it with:
ProductKey=AAAAA-BBBBB-CCCCC-DDDDD-EEEEE-FFFFF
But i think it is weird that you get the wizzard even though you have the Skip-parameter. Could you take a look at the ZTIgather.log and see what value SkipProductKey and SkipApplications have? maybe you could upload the log file anywhere so i can take a look?
-
Tuesday, January 22, 2013 1:15 PMMake sure you update your deployment share so these settings will be updated. This could help
-
Tuesday, January 22, 2013 5:28 PMAfter you make the changes to your CustomSettings.ini, you need to right click on the deployment share and update. Then take the newly update boot.wim and reimport into WDS boot images.
Thanks! Nate
-
Thursday, January 24, 2013 12:18 PM
I restored the Script folder from backup and I am able to get the settings I required
Thanks
-
Thursday, January 24, 2013 1:42 PM
actually you don't need to update you deployment share if you update your customsettings.ini since it isn't included in your boot image.
you only need to update your deployment share when you add boot critical drivers like NIC/MSD drivers or when you updated your bootstrap.ini
-
Thursday, January 24, 2013 9:34 PM
Are you sure?
I think updating the deployment share will also trigger other actions, but I am not sure.
Don't confuse this with boot image generation!Usually MDT recognizes very well if the boot image needs to be regenerated, there should be no harm in doing it. (It never regenerated the boot images for me when it was not necessary, but it sometimes missed to regenerate it when it was actually required)
-
Friday, January 25, 2013 8:04 AM
it also checks if you changed what kind of packages you want in your boot image yes but you won't need to update it if all you did is change your customsettings.ini.
When i was testing i made changes to it all the time without needing to update my deployment share.
-
Sunday, January 27, 2013 6:45 PMmake sure you update the deployment share. I also believe that while creating the task sequence u unchecked the ask for produckt key.
Regards, Shishir Kushawaha "If this thread answered your question, please click on "Mark as Answer"

