SCCM'de MDT DB kullanarak domaine dahil etme islemini otomatik ve lokasyon spesifik gerceklestirmek

Eger sizde benim gibi Task Sequence'nizde bilgisayarlarin domaine dahil olma isleminde "Apply Network Settings" lokasyona ozel degerleri otomatik algilayip uygulamak istiyorsaniz. Yani bir den fazla domain'e sahipseniz ancak bir den fazla islem yaratip her bir domain icin ayri sorgular yazmak istemiyorsaniz. SCCM'nize entegre olmus MDT'nin veritabanini kullanarak bu islemi kolaylastirabilirsiniz.

Tek yapmaniz gereken MDT DB de yaratiiginiz lokasyonlarin ozelliklerine gerekli degerleri girmek ve SCCM OSD'de ki Task Sequence'de bu degerleri cagirmak olacak.

MDT DB'de lokasyon altinda degistirilecek degerler Domain and Workgroup bolumu altinda yer almakta, buradaki degerleri kendi domain ayarlariniza gore konfigure etmeniz gerekmekte. Bu zaten sadece MDT kullanilarak yapilan isletim sistemi kurulumlarindan bildiginiz bir adim olabilir.

DomainAdmin : Bilgisayari domaine eklerken kullanilacak kullanici adi. Ornek : OSDAdmin

DomainAdminDomain : DomainAdmin kullanicisinin domaini Ornek: Domain1

DomainAdminPassword : Domain Admin kullanicisinin sifresi

JoinDomain : Bilgisayarin dahil edilecegi domain adi, Ornek: Domain1.yerel

MachineObjectOU : Bilgisayar objesinin yaratilacagi OU, Ornek: OU=YeniBilgisayarlar,DC=Domain1,DC=yerel

Daha sonra SCCM'de ki mevcut task sequence'nizde Apply Network Settings adimini konfigure etmeniz gerekmekte, degisken isimleri aynen MDT DB deki gibi olacagindan isiniz cok basit.

Domain : %JoinDomain%
DomainOU : %MachineObjectOU%
Account : %DomainAdmin%
Password : %DomainAdminPassword%

Seklinde degisikliklerinizi yapmaniz yeterli olacak, sifre yi girerken yuzdeleri basa ve sona yazmayi unutmayin,

Using MDT DB to get location specific Domain Joining parameters in SCCM OSD

If you have multiple domains as me and want to automate domain joining task by sensing locations automatically in SCCM OSD, you can use MDT DB to do it easily. You can also do this by adding more actions with different queries to your TS or customizing your coustomsettings.ini. But I prefer using MDT DB as changes there doesn't need to be refresh as packages, GUI makes it easier to manage and more foolproof, etc.

All you need to do is modifying location details on your MDT DB and call these variables in your SCCM TS.

So first edit your location details in MDT Workbench, you'll need to edit four values here as shown below.

DomainAdmin : The name of the account used to join the domain. Example : OSDAdmin

DomainAdminDomain : The domain of the account used to join the domain. Example: Domain1

DomainAdminPassword : The password of the account used to join the domain.

JoinDomain : The name of the domain in which the computer should be placed. Example: Domain1.local

MachineObjectOU : The OU in which the computer account should be created (if it does not already exist)., Exaple: OU=NewComps,DC=Domain1,DC=Local

Then you'll need to modify your "Apply Network Settings" action in your TS to use values in MDT DB. It is very as MDT Workbench displays these as it is. So all you need to do adding % to the start and the end of the variable as below.

Domain : %JoinDomain%
DomainOU : %MachineObjectOU%
Account : %DomainAdmin%
Password : %DomainAdminPassword%

 

All done, now you can test it.

Please note that you'll need a working SCCM and MDT integration to use this method first.

How to prompt for computer name in MDT/SCCM Task Sequence (OSD)

I was using Collection Variables in Collection Settings to ask Computer Name [OSDComputerName] at the beginning of my OSD Task Sequences. It was useful but it doesn't have confirmation or correction features.

So I wanted to change it to something asks if the entered computer names is correct and allow user to change name before final confirmation.

And it worked nicely : )

My new prompt for the computer name script is

Feel free to use, change or optimize.

You can create a SCCM Package and run this script via "Run Command Line" action in your task sequence (cscript "PromptForComputerName.wsf").

Or you can place it into your MDT Scripts (Toolkit package) and  run "Use Toolkit Package" action before it from, then run (cscript "%deployroot%PersonalPromptForComputerName.wsf") in a "Run Command Line" action just after "Use Toolkit Package".

MDT/SCCM OSD Task Sequence - Install Software Failed (hr=80008013) for Programs with dependencies

When you install an application with dependencies (nested); by running other SCCM package/programs first in MDT/SCCM OSD it fails with the error code  0x80008013 which means (E_FAIL_DEPENDENCY_NOT_RUN : This program cannot run because it depends on another program that has not run successfully before. This error code is returned to task sequence manager when a task sequence Install Software Action step cannot be run because the step has a child program which has not been run before.).

The reason is OSD in SCCM can't install the dependencies first, so you need to separate programs for your OSD Install software tasks.

The task sequence execution engine failed executing the action (Cisco Any Connect) in the group (Laptop Software) with the error code 2147516435 Action output: _ProgramID="Silent  Install",PKG_PackageID="SMS0012C"' Verified policy is compiled in 'root\ccm\policy\machine' namespace content location count = 1 Invoking Execution Manager to install software
FALSE, HRESULT=80008013 (e:\nts_sms_fre\sms\client\osdeployment\installsoftware\installsoftware.cpp,282)
0, HRESULT=80008013 (e:\nts_sms_fre\sms\client\osdeployment\installsoftware\installsoftware.cpp,746)
Entering ReleaseSource() for \\DPSERVER\SMSPKGE$\SMS0012C reference count 1 for the source \\DPSERVER\SMSPKGE$\SMS0012C\ before releasing
Released the resolved source \\DPSERVER\SMSPKGE$\SMS0012CpInstall->Install(sPackageID, sProgramName), HRESULT=80008013 (e:\nts_sms_fre\sms\client\osdeployment\installsoftware\main.cpp,374)
Failed to invoke Execution Manager to Install Software for PackageID='SMS0012C' ProgramID='Silent Install' AdvertID='SMS20333' hr=0x80008013 Install Software failed, hr=0x80008013 Install Software failed, hr=0x80008013.

See http://technet.microsoft.com/en-us/library/bb632794.aspx  for
Custom Error Codes for Configuration Manager 2007.

MDT / SCCM OSD - Run actions based on chassis type

It is very easy to run chassis type specific actions in task sequences by querying , all you need to do is adding  Task Sequence Variable in Options. Fill Variable field with IsLaptop , select your condition and write the value you wanted (True or False)

 

WinPE AdoDB SQL Connection Error (429)

I was using MDT wDB for OS deployments, now I am creating the same (better) system with SCCM for wider and easier deployment. I prefer MDT integration to SCCM as it provides lots of flexibility and customizability.

Today, I wanted to use MDT DB with my SCCM OSD, so I created a new MDT Settings package and copied my old CustomSettings.ini from MDT and customized. Duplicated my current build TS and changed the MDT Settings package in respective Gather actions.

Deployed a test machine and found out no localization settings have applied. So I found the error "Unable to create ADODB.Connection object, impossible to query SQL Server: ActiveX component can't create object ( 429 )" in logs. After a few web search I found MDT Boot image usage is recommended as it has necessary libraries to create ADODB connection.

As usual I wanted to fix that instead of using my old MDT boot image, checked WinPE_FPs folder in WAIK and seen there is a winpe-mdac.cab (MS Data Access Components) and added this package to boot image.

• dism /mount-wim /WimFile:g:\wimwork\boot.csrx64.wim /index:1 /MountDir:G:\WimWork\x64


• dism /image:G:\WIMWork\csrx64 /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\winpe-mdac.cab"


• dism /unmount-image /MountDir:G:\WIMWork\csrx64 /Commit

Now I have necessary libraries in my new boot image and it can connect to SQL server.

Note : Don't forget to change Netlib value to DBMSSOCN in your CustomSettings.ini if you will use SQL Authentication instead of Windows Authentication.

Configuring location based settings automatically by using Win32 IP4RouteTable in OSD - Task Sequence

The idea was creating location specific variable sets to automatically configure regional settings during deployment.

 

 

Select * FROM Win32_IP4RouteTable WHERE Destination='0.0.0.0' AND ( NextHop='10.99.0.254' OR NextHop='10.101.0.254' OR NextHop='10.103.0.254' OR NextHop='10.104.0.254' )

The query above is very useful as it queries the routing table to find gateway and it looks ok when you run test it in SCCM Console.

But, it doesn’t work and generates errors below during deployment

(You can use VB, PS scripts, Control.exe with .xml file or other methods by using same WMI query after Setup Windows & CM action (Windows Mode) to set regional settings, they should be easier. But I wondered if I can fix that one, as I always have used default boot images provided in WAIK and I wanted to gain some familiarity with WinPE imaging/tools. I am sure the method below may not be the good/best practise but that is what I did in last few hours, it was good experimental work for me and I believe some parts can be useful for others as well.)

Windows could not parse or process the unattended answer file for pass [specialize]. The settings specified in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft-Windows-Shell-Setup].

 
If you click ok to Restart/OK, it goes in to reboot loop with message below.The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click "OK" to restart the computer, and then restart the
installation.



And also the error message below can be found in advertisement status messages.



If you check sms*.log files in deployment client drive you can also find error messages related to operands. (Attaching .vhd is very useful to do that.)
Reason ? The reason is Win32_IP4RouteTable class is invalid as it is not included in winpe-wmi.cab.


Win32_IP4RouteTable class has two files named Wmipiprt.mof and Wmipiprt.dll

(For more details : http://msdn.microsoft.com/en-gb/library/windows/desktop/aa394162(v=vs.85).aspx)
So I wanted to include this class to my Win-PE image.

 

1. Preperation

Enable command support option in your current boot image, start deployment but don’t select TS and proceed to installation.



Press F8 to open command prompt

1. Connect to your workstation
   
   
   
   • (net use K: \yourmachinec$ )
   
   
   
   


2. Copy the wmipiprt.* files to WindowsSystem32wbem folder (X: Drive)
   
   
   
   • (Copy K:windowssystem32wbemwmipiprt.* X:WindowsSystem32wbem)
   
   
   
   


3. Change your working folder to X:WindowsSystem32wbem
   
   
   
   • Cd X:WindowsSystem32wbem
   
   
   
   


4. Run MOF compiler for the class
   
   
   
   • Mofcomp wmipiprt.mof
   
   
   
   


5. Take a copy of Win-PE Wbem
   
   
   
   • Xcopy X:WindowsSystem32wbem K:WinpeWork /s /e
   
   
   
   


6. Register the the dll
   
   
   
   • Regsvr32 wmipiprt.dll
   
   
   
   


7. Backup Win-PE HKLMSoftware (If you are ok the .reg file I provided you can skip all reg steps until Modifying the Image)
   
   
   
   • Reg save HKLMSOFTWARE HKLMSoft.reg
   
   
   
   


8. Take a copy of exported reg file
   
   
   
   • Copy HKLMSoft.reg K:WinpeWork
   
   
   
   

On your workstation

Load the C:WinpeworkHKLMSoft.reg file with load hive option to your workstations HKLM, you can use any name for Hive name (e.g. WINPE)



Then search wmipiprt in loaded hive,


You’ll find two entries under CLSID, export these to .reg files and merge in one reg file. And unload the hive “WINPE”.  (You can also use the .reg below)

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\WIMSOFT\Classes\CLSID\{23B77E99-5C2D-482D-A795-62CA3AE5B673}]
@="WBEM IP Route Provider"

[HKEY_LOCAL_MACHINE\WIMSOFT\Classes\CLSID\{23B77E99-5C2D-482D-A795-62CA3AE5B673}\InprocServer32]
@="X:\\Windows\\System32\\wbem\\WMIPIPRT.dll"
"ThreadingModel"="Both"

[HKEY_LOCAL_MACHINE\WIMSOFT\Classes\CLSID\{6D7A4B0E-66D5-4AC3-A7ED-0189E8CF5E77}]
@="WBEM IP Route Event Provider"

[HKEY_LOCAL_MACHINE\WIMSOFT\Classes\CLSID\{6D7A4B0E-66D5-4AC3-A7ED-0189E8CF5E77}\InprocServer32]
@="X:\\Windows\\System32\\wbem\\WMIPIPRT.dll"
"ThreadingModel"="Both"

2. Modifying the image (Be sure you have a backup of your original boot image in separate place.)

Mount your boot image in writable mode.

Imagex /mountrw G:WIMWorkx64boot.wim G:WIMWorkx64mount

(G:WIMWorkx64mount is an empty folder)

Open G:WIMWorkx64mount folder, you’ll see your winpe image contents

Delete G:WIMWorkx64mountWindowsSystem32wbem contents

Copy the K:WinpeWorkwbem content you have copied from running Win-PE to your work folder in first steps of Preparation above.

Run Regedit, select HKLM then select load hive from menu,

Select G:WIMWorkx64mountWindowsSystem32ConfigSoftware to load and give WIMSOFT as a name if you are going to use my .reg file above.

Run the .reg you’ve created by correcting paths or directly the one above.

(Check two new entries under WIMSOFTClassesCLSID)

Unload WIMSOFT Hive.

Now we need to dismount the image with commit option.

Imagex /unmount /commit G:WIMWorkx64mount

Finished.

Take a backup of your current boot image on SCCM, copy this one to your source and update your distribution points to test. (Or create a new image, to test first.)



Now you can use Win32_IP4RoutingTable in Win-PE mode.

Place your variable set tasks just before the Configure action in PostInstall phase.

Change TEMP folder used by MDT

If you have a server with MDT installed and you notice that during boot image creation the server runs really slow or you are just flat out of space on the drive you installed MDT you can change the MDT temp directory to another location.

During the boot image creation process all of items included in the wim are stored in the temp directory which could result in poor performance or a total crash of you system if you have low disk space.

Open regedit and go to the below key and add a new String value with the name of Temp_Dir with a value of the location you want the temp directory.

HKLM\SOFTWARE\Microsoft\Deployment 4\

Temp_Dir\"E:\MDTTEMP"

WDS Auto-Add ve AD'de Prestaging verilerini temizlemek

WDS Auto-Add veritabanini temizlemek
WDS Auto-Add veritabanindaki onaylanmis bilgisayarlari her 30 gunde bir temizler. Isterseniz bu sureyi WDSUTIL /Set-Server /AutoAddPolicy /RetentionPeriod /Approved:Days komutu ile degistirebilirsiniz.  (http://technet.microsoft.com/en-us/library/cc754289(WS.10).aspx)

Ornegin 7 gune ayarlamak icin :
WDSUTIL /Set-Server /AutoAddPolicy /RetentionPeriod /Approved:7

Eger isterseniz  wdsutil /delete-AutoAddDevices /DeviceType:ApprovedDevices komutu ule tum onaylanmis bilgisayarlari Auto-Add veritabanindan temizleyebilirsiniz.  (http://technet.microsoft.com/en-us/library/cc770832(WS.10).aspx).

Ancak WDS Auto-Add veritabaninda yapilan temizlik Active Directory'deki bilgisayar hesabinda bulunan RemoteInstall/NetBootGUID degerini temizlemez, degeri elle silebilirsiniz.

AD'deki prestaging verilerini temizlemek
Eger prestaged bilgisayarlara ait RemoteInstall/GUID degerlerini Active Directory'den temizlemek isterseniz asagidaki powershell komutlarindan yararlanabilirsiniz. Kendim bu ihtiyacimi giderirken uzerinden gectigim adimlari oldugu gibi paylasiyorum, kavranmasini kolaylastiracagini umuyorum.

Bir bilgisayarin NetbootGUID degerini gormek icin

Get-ADComputer -Identity ComputerName -Properties NetbootGuid

Bir bilgisayarin NetbootGUID degerini temizlemek icin

Set-ADComputer -Identity ComputerName -clear NetbootGUID

Tum bilgisayarlarin NetboodGUID degerlerini gormek icin

Get-ADComputer -Filter {NetbootGUID -like "*"} -Properties NetbootGUID

Tum bilgisayarlarin NetboodGUID degerlerini ek degerlerle listelemek icin

Get-ADComputer -Filter {NetbootGUID -like "*"} -Properties NetbootGUID,created | Format-List -Property name,distinguishedName,created,NetbootGUID

Yaratilma degeri bir haftadan eski ve NetbootGUID degerine sahip tum bilgisayarlari listelemek icin

Get-ADComputer -Filter {NetbootGUID -like "*"} -Properties NetbootGUID,Created | ? {$_.Created -le ((get-date).addDays(-7))} | Format-List -Property name,distinguishedName,created,NetbootGUID

Yaratilma degeri bir haftadan eski ve NetbootGUID degerine sahip tum bilgisayarlara ait NetbootGUID degerini temizlemek

Get-ADComputer -Filter {NetbootGUID -like "*"} -Properties name,NetbootGUID,Created | ? {$_.Created -le ((get-date).addDays(-7))} | Set-ADComputer -clear NetbootGUID

Yaratilma degeri bir haftadan eski ve NetbootGUID degerine sahip tum bilgisayarlara ait NetbootGUID degerini temizlemek (Daha kisa  : Created degerini almamiz yeterli tarih denklemi icin.)

Get-ADComputer -Filter {NetbootGUID -like "*"} -Properties Created | ? {$_.Created -le ((get-date).addDays(-7))} | Set-ADComputer -clear NetbootGUID

Komutlar hakkinda daha fazla bilgi icin
Set-ADComputer : http://technet.microsoft.com/en-us/library/ee617263.aspx
Get-ADComputer : http://technet.microsoft.com/en-us/library/ee617192.aspx

Purging WDS database and clearing prestaging values from AD computers

Purging Auto-Add Database in WDS WDS purges approved computers from Auto-Add database every 30 days by default.
You can also change the retention period for approved computers record by running WDSUTIL /Set-Server /AutoAddPolicy /RetentionPeriod /Approved:Days command. (http://technet.microsoft.com/en-us/library/cc754289(WS.10).aspx)

To change the length of time approved computers are held in the Auto-Add database to 7 days.
WDSUTIL /Set-Server /AutoAddPolicy /RetentionPeriod /Approved:7

If you wan't to manually purge approved computers in Auto-Add database you can run wdsutil /delete-AutoAddDevices /DeviceType:ApprovedDevices command, or to delete all (approved, pending, rejected) you can visit this URL (http://technet.microsoft.com/en-us/library/cc770832(WS.10).aspx).

But this process doesn't clear computer's RemoteInstall/NetBootGUID property from Active Directory, so you might need to clear this value in AD.
Clear prestaging data in AD
If you also need to clear RemoteInstall GUID property from all prestaged machines in AD as WDSUtil only clears it's own Auto-Add database, you can use powershell commands below to do that.

• To see a computer's NetbootGUID
  

  Get-ADComputer -Identity ComputerName -Properties NetbootGuid

  
  


• To clear a computer's NetbootGUID
  

  Set-ADComputer -Identity ComputerName -clear NetbootGUID

  
  


• To list all computers have NetboodGUID value
  

  Get-ADComputer -Filter {NetbootGUID -like "*"} -Properties NetbootGUID

  
  


• To list all computers have NetboodGUID value by formatted output
  

  Get-ADComputer -Filter {NetbootGUID -like "*"} -Properties NetbootGUID,created | Format-List -Property name,distinguishedName,created,NetbootGUID

  
  


• To list all computers older than a week and have NetboodGUID value by formatted output
  

  Get-ADComputer -Filter {NetbootGUID -like "*"} -Properties NetbootGUID,Created | ? {$_.Created -le ((get-date).addDays(-7))} | Format-List -Property name,distinguishedName,created,NetbootGUID

  
  


• To clear NetbootGUID from all computers older than a week and have NetbootGUID value
  

  Get-ADComputer -Filter {NetbootGUID -like "*"} -Properties name,NetbootGUID,Created | ? {$_.Created -le ((get-date).addDays(-7))} | Set-ADComputer -clear NetbootGUID

  
  


• To clear NetbootGUID from all computers older than a week and have NetbootGUID value (Shorter : we only need Created property for date equation)
  

  Get-ADComputer -Filter {NetbootGUID -like "*"} -Properties Created | ? {$_.Created -le ((get-date).addDays(-7))} | Set-ADComputer -clear NetbootGUID

  
  

To get more detail about
Set-ADComputer : http://technet.microsoft.com/en-us/library/ee617263.aspx
Get-ADComputer : http://technet.microsoft.com/en-us/library/ee617192.aspx

MDT Unable to find SETUP Hatası

Merhaba

Eger MDT ile bir isletim sistemi imajini capture edip, sonrasinda kurarken asagidaki gibi bir hata aliyorsaniz kurulum SETUP dosyalarina sahip degil demektir bu durumda capture ettiginiz imaji MDT ye import ederken asagidaki sekilde isletim sistemi kurulum kaynagini gostererek SETUP icin gerekli dosyalarinda import edilmesini saglamaniz gerekmektedir.

Ornek Hata:
ERROR-Unable to find SETUP, needed to install the image
\servershareOperating Systemsfolderimage.wim
ZTI ERROR - Non-zero return code by LTIApply. rc=1
Non-zero return code rc=-2147467259 0x80004005

SETUP dosyalarinin gosterilmesi

MDT Windows 64 bit IaStor.sys 0xc0000359 Error

I have just experienced a problem while I was trying to install Windows 7 64bit by MDT2010. The error was 0xc0000359 and it was related to Intel's storage driver IaStor.sys. If you will experience this problem as me, all you need to do is download and import latest Intel Matrix Storage Manager drivers to Out-of-Box Driver repository.

You can find and download latest version from Intel Matrix Storage Manager

To extract the package use -a parameter, it will extract contents to C:\Program Files\Intel directory, you will find two folders in it, one for 32bit other for 64bit. Just import whole folder to MDT drivers and don't forget to update your deployment share, it will create you an updated boot image.

MDT Windows 64 bit IaStor.sys 0xc0000359 hatasi

MDT 2010 ile Windows 7 x64 yukleme testi yaparken Windows un IaStor.Sys dosyasini yukleyemedigi ile ilgili bir hata olan 0xc0000359 hatasini aldim. Bu tip bir sorunla sizde karsilasirsaniz cozmek icin Intel'in sitesinden en guncel SATA surucu paketini cekip MDT suruculeri arasinda aktarmaniz gerekiyor.

Link : Intel Matrix Storage Manager

Paketi indirdikten sonra -a parametresi ile icerigini acabilirsiniz C:\ altinda koyacagi log dosyasindan da gorebileceginiz gibi suruculeri C:\Program Files\Intel altina acacaktir, bu klasoru MDT den direkt olarak Out-of-box drivers altina import edebilirsiniz. Islem sonrasi Share'inizi update etmeli ve yeni imajinizi kullanmalisiniz.

MDT Paylaşım Lokasyonunu Otomatik Belirleme

MDT ile imaj olusturmaya baslayali uzun zaman oldu, simdi farkli lokasyonlardan da tek imaj , tek veritabani, tek paylasim kullanabilmek icin uzerinde calismaktayim, her lokasyonun kendi lokalinden kaynaklara ulasabilmesi icin SQL Replikasyonu, DFS-R gibi teknolojilerden faydalanmaktayim. Ancak dun DFS performansindan veya olasi DFS problemlerine karsin bu is baska nasil yapilir diye dokumanlari okurken BootStrap.ini de Gateway tanimlamalari ile lokasyon tanimlanabildigini buldum, bu ozellik cok hos , istemci gatewayinden nerede oldugunu ayirt edebilip ayarlari buna gore ozellestirebiliyorsunuz. Ankara'da isen Ankara paylasimina eris, su kullanici ile diyebiliyorsunuz.

Veya DeployRoot u tamamen bos birakabiliyorsunuz bu durumda sistem sizin yarattiginiz LocationServer.xml dosyasini okuyor ve kullaniciniza sizin tanimlamis oldugunu lokasyonlari listeliyor, bu yontemle ayni lokasyonda bir den fazla paylasiminiz var ise bunlara agirlik vererek yuku de dagitabiliyorsunuz.

Ben hem bootstrap.ini de gateway ve lokasyon degiskenlerini kullandim hem de eger lokasyonlardan birine eslesmedigi durumda LocationServer.xml i kullanmasi icin konfigure ettim.

BootStrap.ini de yapmaniz gereken

[Settings] altinda Priority i degistirmeniz olacak, boylelikle islem once Gateway eslesmelerine oncelik verecek ornegin :

[Settings]
Priority=DefaultGateway,Default

Daha sonra gatewayleri ve lokasyonlari tanimlayacaksiniz, ornegin

[Default Gateway]
192.168.1.1=Istanbul
192.168.3.1=Ankara

Daha sonra lokasyona ait ozellikleri asagidaki sekilde tanimlayabilirsiniz.

[Istanbul]
DeployRoot=\IstanbulSunucunuzDeploymentShare$ (MDT2010 oncesinde Distribution$)

[Ankara]
DeployRoot=\AnkaraSunucunuzDeploymentShare$ (MDT2010 oncesinde Distribution$)

Ikinci oncelik ise varsayilan yani Default, bu eslesme olmamasinda kullanicak ana yontem

[Default]

Buraya eslesme olmazsa kullansin diye bir sunucu tanimlabilirsiniz veya bos birakip sistemin LocationServer.xml okumasini isteyebilirsiniz.

Yukaridaki bolge degiskenlerine elbette normalde kullanabildiginiz UserID, UserDomain, SkipBDDWelcome vs gibi degerleri kullanabilirsiniz.

LocationServer.xml i yaratmak icin MDT dokumanini incelemeniz gerekiyor cunku kurulum klasorlerinde bulamayacaksiniz. Ben burada bir ornegi sizinle paylasacagim


Ornegin yukaridaki gibi bir XML i yaratip Disk:DeploymentShareExtra FilesDeployControl altina kopyalayip imaji tekrar olusturursaniz boot sirasinda eger herhangi bir deployroot tanimi bulunamaz ise sistem size xml de tanimlamis oldugunuz sunuculari listeleyecektir. Extra Files klasorunu MDT de Share ozelliklerine Extra Files kismindan tanimlamalisiniz ki dosyayi imaj icina alsin, bunu atlamayiniz.

Ayni XML de bolgeye has ozellikleri de tanimlayabilirsiniz , ornegin alan kodu icin



Fakat da bootstrap.ini de oldugu gibi paylasima erisecek kullanici tanimlanamamakta, bunun olmamasi benim planlarimi aksatmisti cunku yarattigim imajlar kurulumcuya sadece makine adi sormaya ayarli, geri kalan tum bilgileri klavye, alan kodu, domain, ou, uygulamalar vb seyleri zaten otomatize etmistim. Bunun uzerine MDT scriptleri nasil calisir diye arastirmaya basladim ve benim isimi gorecek bir cozum buldum, ayni seye ihtiyaci olacaklar icin umarim faydali olur.

ScriptsDeployWiz_Validation.vbs dosyasinda asagidaki kismi bulun
ValidateDeployRoot = FALSE

Do
On Error Resume Next
Err.Clear
If oFSO.FileExists(DeployRoot.value & "ControlOperatingSystems.xml" ) then

ve su sekilde eklemeyi yapin, normalde asagidaki ek daha alt satirlarda zaten degiskenleri okumak icin var ancak bu kod kullanici haklari size sorulduktan sonra calistigi icin, kullanici bilgileri icin kullanilamamakta, biz kullanici haklari kismindan once okuyacagiz parametrelerimizi,

ValidateDeployRoot = FALSE
For each oItem in oXMLSiteData.selectNodes("//servers/server")
If SiteList.value = oUtility.SelectSingleNodeString(oItem,"serverid") then
For each oVariable in oItem.selectNodes("otherparameters/parameter")
Set oName = oVariable.Attributes.getQualifiedItem("name","")
If not oName is Nothing then
oProperties(oName.Value) = oVariable.Text
End if
Next

End if
Next
Do
On Error Resume Next
Err.Clear
If oFSO.FileExists(DeployRoot.value & "ControlOperatingSystems.xml" ) then

Daha sonra asagidaki bolumu

oEnvironment.Item("UserID") = ""
oEnvironment.Item("UserDomain") = ""
oEnvironment.Item("UserPassword") = ""

su sekilde degistirin ki , XML den okudugumuz bilgileri eslestirelim,

oEnvironment.Item("UserID") = oProperties("UserID")
oEnvironment.Item("UserDomain") = oProperties("UserDomain")
oEnvironment.Item("UserPassword") = oProperties("UserPassword")

Asagidakileri de yukarida verilen ornekteki gibi parametrelere ekleyiniz.



Imajinizi olusturup , boot ettiginiz de eger GW eslesmesi olmazsa veya bootstrap.ini de DeployRoot tanimli degilse sistem size bolge-sunucu listesini gosterecektir, ve siz secim yapip Next'e bastiginizda kullanici bilgileri ekrani doldurulmus gelecektir.

Iyi gunler.

Not:XML leri imaj seklinde koydum cunku blogger xml leri algilayip sadece atanmis degerleri gosteriyordu.

(MDT Paylaşım Lokasyonunu Otomatik Belirleme)

WDS de tüm aygıtları listelemek.

WDS (Windows Deployment Server)de Approved, Pending ve Rejected device lari yonetim icin bir script hazirlamaya basladim, ilk asamada bu devicelari listelemek icin yazmis oldugum script i konuyla ilgilenen arkadaslara esin kaynagi olmasi icin paylasmak istedim. Script basitce wdsutil komutunu kullanarak devicelari text dosyasina aldiktan sonra, dosyalari parse edip daha kullanilabilir bir hale getirmek icin noktali virgul ile ayrilmis sekilde duzenliyor.


Ornegin,
wdsutil /get-AutoAddDevices /DeviceType:RejectedDevices sonucunu export ettigimizde asagidaki sekilde kullanimi daha zor olan bir formattaki ciktiyi



Bu sekle donusturerek kolaylik sagliyor.

 'ListWDSAllDevices.vbs Written by : Osman Shener
 'Feel free to use! (Kill the hero, but don't eat his right :) (Don't try to undertand it is a funny translation of a Turkish proverb))

Const ForReading = 1
 Const ForWriting = 2
 Const TristateUseDefault=-2

Dim objFSO, arrStr, wshell, objRegEx

Set objFSO = CreateObject("Scripting.FileSystemObject")
 Set wshell = CreateObject("WScript.Shell")
 Set objRegEx = CreateObject("VBScript.RegExp")
 objRegEx.Pattern = ":"

wshell.run "%COMSPEC% /C wdsutil /get-AutoAddDevices /DeviceType:PendingDevices > C:PendingDevices.txt", 0, TRUE
 wshell.run "%COMSPEC% /C wdsutil /get-AutoAddDevices /DeviceType:RejectedDevices > C:RejectedDevices.txt", 0, TRUE
 wshell.run "%COMSPEC% /C wdsutil /get-AutoAddDevices /DeviceType:ApprovedDevices > C:ApprovedDevices.txt", 0, TRUE
 set wshell = nothing

'Create Pending Devices Semicolon seperated list!
 Set objFile = objFSO.OpenTextFile("C:PendingDevices.txt", ForReading, True, TristateUseDefault)

Do Until objFile.AtEndOfStream
 strLine = objFile.ReadLine
 Set colMatches = objRegEx.Execute(strLine)
 If colMatches.Count > 0 Then
 For Each strMatch in colMatches
 strPenText = strPenText + strLine + ";"
 If Left(strLine, 11) = "Join domain" Then
 strPenText = strPenText & vbCrLf
 End If

' Wscript.Echo strPenText
 Next
 End If
 Loop
 objFile.Close

Set objFile = objFSO.OpenTextFile ("C:PendingDevicesList.txt", ForWriting, True, TristateUseDefault)
 objFile.Write(strPenText)
 objFile.Close

'Create Approved Devices Semicolon seperated list!
 Set objFile = objFSO.OpenTextFile("C:ApprovedDevices.txt", ForReading, True, TristateUseDefault)

Do Until objFile.AtEndOfStream
 strLine = objFile.ReadLine
 Set colMatches = objRegEx.Execute(strLine)
 If colMatches.Count > 0 Then
 For Each strMatch in colMatches
 strAppText = strAppText + strLine + ";"
 If Left(strLine, 13) = "Approval time" Then
 strAppText = strAppText & vbCrLf
 End If

' Wscript.Echo strAppText
 Next
 End If
 Loop
 objFile.Close

Set objFile = objFSO.OpenTextFile ("C:ApprovedDevicesList.txt", ForWriting, True, TristateUseDefault)
 objFile.Write(strAppText)
 objFile.Close

'Create Rejected Devices Semicolon seperated list!
 Set objFile = objFSO.OpenTextFile("C:RejectedDevices.txt", ForReading, True, TristateUseDefault)

Do Until objFile.AtEndOfStream
 strLine = objFile.ReadLine
 Set colMatches = objRegEx.Execute(strLine)
 If colMatches.Count > 0 Then
 For Each strMatch in colMatches
 strRejText = strRejText + strLine + ";"
 If Left(strLine, 14) = "Rejection time" Then
 strRejText = strRejText & vbCrLf
 End If
 Next
 End If
 Loop
 objFile.Close

Set objFile = objFSO.OpenTextFile ("C:RejectedDevicesList.txt", ForWriting, True, TristateUseDefault)
 objFile.Write(strRejText)
 objFile.Close

Unattended.txt (GuiUnttended) TimeZone Endeksi

Asagida Unattended.txt dosyasini duzenlerken TimeZone degeri vermek icin ihtiyac duyabileceginiz TimeZone index ini bulabilirsiniz arkadaslar, GUIUnattended bolumu altinda bulunan TimeZone icin degeri TimeZone=130 (Istanbul icin) seklinde verebilirsiniz.

Index	Time Zone	Description
000	Dateline Standard Time	(GMT-12:00) International Date Line West
001	Samoa Standard Time	(GMT-11:00) Midway Island, Samoa
002	Hawaiian Standard Time	(GMT-10:00) Hawaii
003	Alaskan Standard Time	(GMT-09:00) Alaska
004	Pacific Standard Time	(GMT-08:00) Pacific Time (US and Canada); Tijuana
010	Mountain Standard Time	(GMT-07:00) Mountain Time (US and Canada)
013	Mexico Standard Time 2	(GMT-07:00) Chihuahua, La Paz, Mazatlan
015	U.S. Mountain Standard Time	(GMT-07:00) Arizona
020	Central Standard Time	(GMT-06:00) Central Time (US and Canada)
025	Canada Central Standard Time	(GMT-06:00) Saskatchewan
030	Mexico Standard Time	(GMT-06:00) Guadalajara, Mexico City, Monterrey
033	Central America Standard Time	(GMT-06:00) Central America
035	Eastern Standard Time	(GMT-05:00) Eastern Time (US and Canada)
040	U.S. Eastern Standard Time	(GMT-05:00) Indiana (East)
045	S.A. Pacific Standard Time	(GMT-05:00) Bogota, Lima, Quito
050	Atlantic Standard Time	(GMT-04:00) Atlantic Time (Canada)
055	S.A. Western Standard Time	(GMT-04:00) Caracas, La Paz
056	Pacific S.A. Standard Time	(GMT-04:00) Santiago
060	Newfoundland and Labrador Standard Time	(GMT-03:30) Newfoundland and Labrador
065	E. South America Standard Time	(GMT-03:00) Brasilia
070	S.A. Eastern Standard Time	(GMT-03:00) Buenos Aires, Georgetown
073	Greenland Standard Time	(GMT-03:00) Greenland
075	Mid-Atlantic Standard Time	(GMT-02:00) Mid-Atlantic
080	Azores Standard Time	(GMT-01:00) Azores
083	Cape Verde Standard Time	(GMT-01:00) Cape Verde Islands
085	GMT Standard Time	(GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London
090	Greenwich Standard Time	(GMT) Casablanca, Monrovia
095	Central Europe Standard Time	(GMT+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague
100	Central European Standard Time	(GMT+01:00) Sarajevo, Skopje, Warsaw, Zagreb
105	Romance Standard Time	(GMT+01:00) Brussels, Copenhagen, Madrid, Paris
110	W. Europe Standard Time	(GMT+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna
113	W. Central Africa Standard Time	(GMT+01:00) West Central Africa
115	E. Europe Standard Time	(GMT+02:00) Bucharest
120	Egypt Standard Time	(GMT+02:00) Cairo
125	FLE Standard Time	(GMT+02:00) Helsinki, Kyiv, Riga, Sofia, Tallinn, Vilnius
130	GTB Standard Time	(GMT+02:00) Athens, Istanbul, Minsk
135	Israel Standard Time	(GMT+02:00) Jerusalem
140	South Africa Standard Time	(GMT+02:00) Harare, Pretoria
145	Russian Standard Time	(GMT+03:00) Moscow, St. Petersburg, Volgograd
150	Arab Standard Time	(GMT+03:00) Kuwait, Riyadh
155	E. Africa Standard Time	(GMT+03:00) Nairobi
158	Arabic Standard Time	(GMT+03:00) Baghdad
160	Iran Standard Time	(GMT+03:30) Tehran
165	Arabian Standard Time	(GMT+04:00) Abu Dhabi, Muscat
170	Caucasus Standard Time	(GMT+04:00) Baku, Tbilisi, Yerevan
175	Transitional Islamic State of Afghanistan Std.	(GMT+04:30) Kabul
180	Ekaterinburg Standard Time	(GMT+05:00) Ekaterinburg
185	West Asia Standard Time	(GMT+05:00) Islamabad, Karachi, Tashkent
190	India Standard Time	(GMT+05:30) Chennai, Kolkata, Mumbai, New Delhi
193	Nepal Standard Time	(GMT+05:45) Kathmandu
195	Central Asia Standard Time	(GMT+06:00) Astana, Dhaka
200	Sri Lanka Standard Time	(GMT+06:00) Sri Jayawardenepura
201	N. Central Asia Standard Time	(GMT+06:00) Almaty, Novosibirsk
203	Myanmar Standard Time	(GMT+06:30) Yangon (Rangoon)
205	S.E. Asia Standard Time	(GMT+07:00) Bangkok, Hanoi, Jakarta
207	North Asia Standard Time	(GMT+07:00) Krasnoyarsk
210	China Standard Time	(GMT+08:00) Beijing, Chongqing, Hong Kong SAR, Urumqi
215	Singapore Standard Time	(GMT+08:00) Kuala Lumpur, Singapore
220	Taipei Standard Time	(GMT+08:00) Taipei
225	W. Australia Standard Time	(GMT+08:00) Perth
227	North Asia East Standard Time	(GMT+08:00) Irkutsk, Ulaan Bataar
230	Korea Standard Time	(GMT+09:00) Seoul
235	Tokyo Standard Time	(GMT+09:00) Osaka, Sapporo, Tokyo
240	Yakutsk Standard Time	(GMT+09:00) Yakutsk
245	A.U.S. Central Standard Time	(GMT+09:30) Darwin
250	Cen. Australia Standard Time	(GMT+09:30) Adelaide
255	A.U.S. Eastern Standard Time	(GMT+10:00) Canberra, Melbourne, Sydney
260	E. Australia Standard Time	(GMT+10:00) Brisbane
265	Tasmania Standard Time	(GMT+10:00) Hobart
270	Vladivostok Standard Time	(GMT+10:00) Vladivostok
275	West Pacific Standard Time	(GMT+10:00) Guam, Port Moresby
280	Central Pacific Standard Time	(GMT+11:00) Magadan, Solomon Islands, New Caledonia
285	Fiji Islands Standard Time	(GMT+12:00) Fiji Islands, Kamchatka, Marshall Islands
290	New Zealand Standard Time	(GMT+12:00) Auckland, Wellington
300	Tonga Standard Time	(GMT+13:00) Nuku'alofa

HP Quick Launch Button Uygulama ve Surucusunu MDT ile sessizce kurmak

1. Suruce ve uygulama paketini HP'den indirin, benim kullandigim versiyon SP44777.exe
2. Paketi bir klasore acin WinRar ile : C:HPQLBD
3. CMD acip C:HPQLBD klasorune girin
3. setup.exe -r -f1"c:setup.iss" komutunu calistirip uygulamayi kurun
4. Eger uygulama calistiginiz bilgisayar uzerinde lazim degil ise kaldirin.
5. Yarattiginiz C:setup.iss dosyasini to C:HPQLBD klasorune kopyalayin, uzerine yazma islemini onaylayin.
6. Dosyayi WinRAR ile RAR layin.
7. RAR dosyanizi acip ToolsConvert Archive to SFX i secin.
8. Advanced SFX Options i secin.
9. Run after extraction kismina setup.exe -s yazin.

10.Modes TAB : Unpack to temporary folder box'unu ve Hide all button'i secin.
11. OK'e basin ve Winrar'i kapatin.

12.Hazir, simdi uygulamayi MDT de Application olarak yaratabilirsiniz, Silent Installation Command kismina yarattiginiz sfx rar uygulama adini yazmaniz yeterli olacaktir.

MDT Properties

Properties that can be overwritten (last value wins) and are automatically set by the BDD scripts
Property ID	Type	Overwrite ?	Description
DeployRoot	string	TRUE	The UNC path to the deployment share
ResourceRoot	string	TRUE	The UNC path to resources (drivers, packages) kept separate from the deployment share
DeployDrive	string	TRUE	The drive letter mapped to the deployment share (Lite Touch only)
ResourceDrive	string	TRUE	The drive letter mapped to resources (drivers, packages) kept separate from the deployment share (Lite Touch only)
DeploymentMethod	string	TRUE	The method being used for the deployment (NETWORK, MEDIA, OSD, etc.)
DeploymentType	string	TRUE	The type of deployment (NEWCOMPUTER, REFRESH, REPLACE, UPGRADE) being performed
Phase	string	TRUE	The current phase of the deployment (NEWCOMPUTER, STATECAPTURE, PREINSTALL, INSTALL, POSTINSTALL, STATERESTORE)
DeploySystemDrive	string	TRUE	The drive (e.g. C:) that Windows should be deployed to
DestinationDisk	string	TRUE	Disk Number that the image will be deployed to
DestinationPartition	string	TRUE	Disk Partition that the image will be deployed to
DestinationLogicalDrive	string	TRUE	Logical Drive that the image will be deployed to
DestinationVariable	string	TRUE	Variable that contains the logical drive that the image will be deployed to
Properties that cannot be overwritten (first value wins)
Property ID	Type	Overwrite ?	Description
UserID	string	FALSE	User ID used for connecting to network paths
UserDomain	string	FALSE	Domain for the user ID used to connect to network paths
UserPassword	string	FALSE	Password for the user ID used to connect to network paths
UDShare	string	FALSE	User data share used for capturing user state to a network path
UDDir	string	FALSE	Directory on the user data share where user state should be placed
UDProfiles	string	FALSE	List of profiles that should be captured by USMT as part of the user state
SLShare	string	FALSE	Script log share where all BDD scripts should be copied at the end of the deployment process
EventShare	string	FALSE	Event share UNC where all BDD scripts should write events for MOM management pack
OSInstall	string	FALSE	Flag to indicate whether this machine is authorized for an OS deployment (if set, it must be YES or Y to proceed)
ComputerName	string	FALSE	The new computer name to assign to the computer
OSDComputerName	string	FALSE	The new computer name to assign to the computer (used with ConfigMgr)
Home_Page	string	FALSE	The Internet Explorer home page that should be used on the computer
JoinDomain	string	FALSE	The name of the domain that should be joined (do not set if using JoinWorkgroup)
JoinWorkgroup	string	FALSE	The name of the Workgroup that should be joined (do not set if using JoinDomain)
DomainAdmin	string	FALSE	Account used to join to Domain (may be in 'Domain\UserName' or 'UserName@Domain.com' format)
DomainAdminDomain	string	FALSE	Domain of Account used to join to Domain (Vista Only, must be blank if 'DomainAdmin' conains domain)
DomainAdminPassword	string	FALSE	Password of Account used to join to Domain
MachineObjectOU	string	FALSE	The OU that should be used when the computer is joined to the domain (only if the computer account does not already exist)
OSDINSTALLSILENT	string	FALSE	OSD flag to indicate that no OSD new computer wizard should be displayed
OSDINSTALLPACKAGE	string	FALSE	OSD variable to indicate which SMS OSD package should be installed (only used for new computer)
OSDINSTALLPROGRAM	string	FALSE	OSD variable to indicate which program should be used for the specified OSD package (only used for new computer)
OSDNEWMACHINENAME	string	FALSE	OSD variable that specifies the computer name that should be assigned (only used for new computer)
ScanStateArgs	string	FALSE	Command line arguments that should be added to the USMT Scanstate command line
LoadStateArgs	string	FALSE	Command line arguments that should be added to the USMT Loadstate command line
ComputerBackupLocation	string	FALSE	Specifies where the computer backup should be stored (AUTO, NETWORK, NONE, specific path, default is AUTO)
BackupShare	string	FALSE	Network share (UNC) where the computer backup should be stored
BackupDir	string	FALSE	Directory on the network share where the computer backup should be stored
BackupDrive	string	FALSE	Drive to include in the backup (defaults to the drive with disk 0 partition 1, can be set to ALL)
UserDataLocation	string	FALSE	Full path to the USMT user state store that should be restored onto a particular machine
DoCapture	string	FALSE	Flag to indicate that the machine should be Sysprepped and captured as a new WIM image
ProductKey	string	FALSE	Product key string that should be inserted into unattend.xml, sysprep.inf, or unattend.txt
OverrideProductKey	string	FALSE	Multiple activation key (MAK) that should be applied after Windows Vista is deployed
WDSServer	string	FALSE	Name of the WDS server that should be used when installing WDS images (default is the server that contains the original image)
CaptureGroups	string	FALSE	Specifies whether to capture the local group membership from the machine (default is YES; ALL can also be specified)
AdminPassword	string	FALSE	Specifies the local administrator password to assign (default is to use existing value)
OrgName	string	FALSE	Specifies the organization name (default is none)
FullName	string	FALSE	Specifies the full name (default is none)
TimeZone	string	FALSE	TimeZone Identifier for Windows XP Builds (example: PST = 004 )
TimeZoneName	string	FALSE	TimeZone Identifier for Windows Vista Builds (example: PST = 'Pacific Standard Time')
TaskSequenceID	string	FALSE	TaskSequence ID used to automate LTI/ZTI build selection (default is blank)
BuildID	string	FALSE	Build ID used to automate LTI/ZTI build selection (default is blank)
InputLocale	string	FALSE	Locale used for Keyboard, (XP only, example: 0409:00000409, default is OS Default)
KeyboardLocale	string	FALSE	Locale used for Keyboard, can be either 0409:00000409 or en-US format (default is OS Default)
UserLocale	string	FALSE	Locale used for user when logged in, en-US format (default is OS Default)
UILanguage	string	FALSE	Default Locale used for OS before user is logged in, en-US format (default is OS Default)
Xresolution	string	FALSE	The Horizontal Resolution of the screen (example: 1024, default is OS Default)
Yresolution	string	FALSE	The Vertical Resolution of the screen (example: 768, default is OS Default)
BitsPerPel	string	FALSE	The Color Depth of the screen in Bits Per Pixel (example: 32, default is OS Default)
Vrefresh	string	FALSE	The vertical Refresh rate of the monitor in Hz (example: 60, default is OS Default)
AreaCode	string	FALSE	Area code for the computer's location.
CountryCode	string	FALSE	Country/region code to use for telephony.
LongDistanceAccess	string	FALSE	Number to dial to gain access to an outside line, such as 9.
Dialing	string	FALSE	Type of dialing to use for the telephony device in the computer, such as 'Tone' or 'Pulse' (XP only).
OSDBitLockerMode	string	FALSE	Specifies the type of BDE install. (KEY|TPMKey|TPMPin|TPM)
BdeInstallSuppress	string	FALSE	Boolean to indicate whether a BDE Install should be attempted.
BdeInstall	string	FALSE	(Deprecated) Specifies the type of BDE install. (KEY|TPMKey|TPMPin|TPM)
OSDBitLockerTargetDrive	string	FALSE	Specifies the drive to be encrypted (default OS Drive)
OSDBitLockerStartupKeyDrive	string	FALSE	Specifies the location of Key files (Drive)
BdeKeyLocation	string	FALSE	(Deprecated) Specifies the location of Key files (Drive)
OSDBitLockerCreateRecoveryPassword	string	FALSE	Indicates whether a recovery password should be generated for AD.
BdeRecoveryKey	string	FALSE	(Deprecated) Indicates whether a recovery password should be generated for AD.
OSDBitLockerWaitForEncryption	string	FALSE	Boolean (any value) indicated whether process should be held to wait for drive encryption to complete.
BdeWaitForEncryption	string	FALSE	(Deprecated) Boolean (any value) indicated whether process should be held to wait for drive encryption to complete.
BdeDriveLetter	string	FALSE	Drive Letter for BDE partition (default S:)
BdeDriveSize	string	FALSE	Drive size for BDE partition (default 2048MB)
BdePin	string	FALSE	BdePin for TPMPin (numeric only)
WinREInstall	string	FALSE	Install Windows Recovery Environment.
WinREDriveLetter	string	FALSE	Drive Letter for BDE partition (default R:)
WinREDriveSize	string	FALSE	Drive size for BDE partition (default 10000MB)
TpmOwnerPassword	string	FALSE	Specifies the TPM Password for setting Ownership
OSDBitLockerRecoveryPassword	string	FALSE	Specifies the password to use for BDE Password scenarios
OSDBitLockerStartupKey	string	FALSE	Specifies the value to use for startup key.
OSDMP	string	FALSE	OSD variable to indicate which SMS management point should be used (only needed for new computer)
OSDSITECODE	string	FALSE	OSD variable to indicate which SMS site code should be used (only needed for new computer)
ServerA	string	FALSE	Server name to be used during the deployment process
ServerB	string	FALSE	Server name to be used during the deployment process
ServerC	string	FALSE	Server name to be used during the deployment process
USMTConfigFile	string	FALSE	USMT configuration XML file that should be used when running Scanstate and Loadstate
WipeDisk	string	FALSE	Specifies whether the disk should be wiped.
_SMSTSORGNAME	string	FALSE	Customizes the Task Sequencer engine's display banner.
WsusServer	string	FALSE	The URL of the WSUS server that should be used (optional, will use Windows Update or policyt settings by default)
Wizard control variables (first value wins)
Property ID	Type	Overwrite ?	Description
SkipWizard	string	FALSE	Flag to skip the deployment wizard altogether (if set to YES, default is blank)
SkipCapture	string	FALSE	Flag to skip the capture of an image (if set to YES, default is YES)
SkipAdminPassword	string	FALSE	Flag to skip the Administrator User Account Password wizard page(if set to YES, default is blank)
SkipApplications	string	FALSE	Flag to skip the wizard pane that asks for applications to be installed (if set to YES, default is blank)
SkipAppsOnUpgrade	string	FALSE	Flag to skip the wizard pane that asks for apps to be installed only for upgrades (if set to YES, default is blank)
SkipComputerBackup	string	FALSE	Flag to skip the computer backup wizard pane (if set to YES, default is blank)
SkipDomainMembership	string	FALSE	Flag to skip the domain membership wizard pane (if set to YES, default is blank)
SkipComputerName	string	FALSE	Flag to skip the Computer Name wizard pane (if set to YES, default is blank)
SkipDeploymentType	string	FALSE	Flag to skip the initial deployment type wizard pane (if set to YES, default is blank)
SkipUserData	string	FALSE	Flag to skip the user data wizard pane (if set to YES, default is blank)
SkipPackageDisplay	string	FALSE	Flag to skip the packages (language packs) wizard pane (if set to YES, default is blank)
SkipLocaleSelection	string	FALSE	Flag to skip the locale selection wizard pane (if set to YES, default is blank)
SkipProductKey	string	FALSE	Flag to skip the product key wizard pane (if set to YES, default is blank)
SkipSummary	string	FALSE	Flag to skip the final wizard summary screen (if set to YES, default is blank)
SkipFinalSummary	string	FALSE	Flag to skip the Summary_Definition_XXX.xml screen (if set to YES, default is blank)
SkipBDDWelcome	string	FALSE	Flag to skip the BDD Welcome screen (if set to YES, default is blank)
SkipTimeZone	string	FALSE	Flag to skip the TimeZone screen (if set to YES, default is blank)
SkipTaskSequence	string	FALSE	Flag to skip the Task Sequence (OS Selection) screen (if set to YES, default is blank)
SkipBuild	string	FALSE	Flag to skip the Build (OS Selection) screen (if set to YES, default is blank)
SkipBitLocker	string	FALSE	Flag to skip the BitLocker (if set to YES, default is blank)
SkipBitLockerDetails	string	FALSE	Flag to skip BitLocker details screen (if set to YES, default is blank)
Action Properties (commonly defined within Management Console)
Property ID	Type	Overwrite ?	Description
OSDAdapterCount	string	FALSE	Number of Adapters defined here( either blank, 0 or 1)
OSDAdapter0Name	string	FALSE	If present, match all settings to the adapter with this name.
OSDAdapter0MacAddress	string	FALSE	If present, match all settings to the adapter with this MAC address.
OSDAdapter0EnableDHCP	string	FALSE	If false, will disable DHCP, otherwise True (true if blank).
OSDAdapter0IPAddressList	string	FALSE	Comma delimited list of IPAddress Lists
OSDAdapter0SubnetMask	string	FALSE	Comma delimited list of Subnet masks
OSDAdapter0Gateways	string	FALSE	Comma delimited list of Gateway cost metrics
OSDAdapter0GatewayCostMetric	string	FALSE	Comma delimited list of Gateway Cost MEtrics as either integers, or the string 'Automatic' (if empty, uses automatic)
OSDAdapter0DNSServerList	string	FALSE	Comma delimited list of DNS Servers
OSDAdapter0DNSSuffix	string	FALSE	DNS Suffix, example Frabrikam.com
OSDAdapter0EnableDNSRegistration	string	FALSE	True/False to enable FULL DNS registration.
OSDAdapter0EnableFullDNSRegistration	string	FALSE	True/False to enalbe DNS Registration
OSDAdapter0EnableLMHOSTS	string	FALSE	True/False to enable LMHosts
OSDAdapter0EnableWINS	string	FALSE	True/False to enable WINS
OSDAdapter0TcpipNetbiosOptions	string	FALSE	NetBIOS OPtions 1 or 0
OSDAdapter0WINSServerList	string	FALSE	Comma delimited list of WINS Servers
OSDAdapter0EnableTCPIPFiltering	string	FALSE	True/False to enable TCP/IP Filtering.
OSDAdapter0TCPFilterPortList	string	FALSE	Comma delimited list of TCP Filters
OSDAdapter0UDPFilterPortList	string	FALSE	Comma delimited list of IDP Filters
OSDAdapter0IPProtocolFilterList	string	FALSE	Comma delimited list of IP Protocol FIlters
OSDDiskIndex	string	FALSE	Disk index used for Partitioning (Default is 0)
OSDPartitions	string	FALSE	Number of Partitions listed here (Default is None, max of 2, use Default configuration)
OSDPartitions0TYPE	string	FALSE	Type of partition (Default: Primary, can be Logical or extended)
OSDPartitions0FILESYSTEM	string	FALSE	Type of File System (Default: NTFS, can be FAT32)
OSDPartitions0BOOTABLE	string	FALSE	True/False - Is the partition bootalbe (default: True if 1st partition)
OSDPartitions0QUICKFORMAT	string	FALSE	True/False - Shall the format be quick (default: True)
OSDPartitions0VOLUMENAME	string	FALSE	Volume name
OSDPartitions0SIZE	string	FALSE	Size of partition
OSDPartitions0SIZEUNITS	string	FALSE	Size units of partition (default: MB, can be GB or %)
OSDPartitions0VOLUMELETTERVARIABLE	string	FALSE	Variable Name to receive DriveLetter
OSDPartitions1TYPE	string	FALSE	Type of partition (Default: Primary, can be Logical or extended)
OSDPartitions1FILESYSTEM	string	FALSE	Type of File System (Default: NTFS, can be FAT32)
OSDPartitions1BOOTABLE	string	FALSE	True/False - Is the partition bootalbe (default: True if 1st partition)
OSDPartitions1QUICKFORMAT	string	FALSE	True/False - Shall the format be quick (default: True)
OSDPartitions1VOLUMENAME	string	FALSE	Volume name
OSDPartitions1SIZE	string	FALSE	Size of partition
OSDPartitions1SIZEUNITS	string	FALSE	Size units of partition (default: MB, can be GB or %)
OSDPartitions1VOLUMELETTERVARIABLE	string	FALSE	Variable Name to receive DriveLetter
Roles
Property ID	Type	Overwrite ?	Description
OSRoles	string	FALSE	Comma-delimited list of role IDs to be installed
OSRoleService	string	FALSE	Comma-delimited list of role service IDs to be installed
OSFeatures	string	FALSE	Comma-delimited list of features to be installed
Configure ADDS
Property ID	Type	Overwrite ?	Description
ReplicaOrNewDomain	string	FALSE	Chooses whether the domain controller will be a replica or part of a new domain
NewDomain	string	FALSE	Choice between a new forest or new domain in an existing tree or a new domain in a new tree
NewDomainDNSName	string	FALSE	DNS domain name of new domain
ParentDomainDNSName	string	FALSE	Parent DNS domain
ReplicaDomainDNSName	string	FALSE	Replica DNS domain
ChildName	string	FALSE	Name of child domain
DomainNetBiosName	string	FALSE	NetBios Name
ForestLevel	string	FALSE	Forest Level
DomainLevel	string	FALSE	Domain functional level
AutoConfigDNS	string	FALSE	Chooses to auto configure DNS
ConfirmGC	string	FALSE	Chooses whether to Confirm communication to GC
CriticalReplicationOnly	string	FALSE	Chooses to only replicate critical information
ADDSUserName	string	FALSE	Username chosen to run dcpromo
ADDSUserDomain	string	FALSE	Domain for user chosen to run dcpromo
ADDSPassword	string	FALSE	Password for user chosen to run dcpromo
ReplicationSourceDC	string	FALSE	DC used to replicate content
DatabasePath	string	FALSE	Path to store the AD database
LogPath	string	FALSE	Path to store the AD database logs
SysVolPath	string	FALSE	Path to store the SYSVOL
SafeModeAdminPassword	string	FALSE	Password used for safemode recovery
SiteName	string	FALSE	AD SiteName
Configure DHCP
Property ID	Type	Overwrite ?	Description
DHCPServerOptionRouter	string	FALSE	Routers for the DHCP Server Option
DHCPServerOptionDNSServer	string	FALSE	DNS Server for the DHCP Server Option
DHCPServerOptionWINSServer	string	FALSE	WINS Server for the DHCP Server Option
DHCPServerOptionDNSDomain	string	FALSE	DNS domain for the DHCP Server Option
DHCPServerOptionNBTNodeType	string	FALSE	NBT NodeType for the DHCP Server Option
DHCPServerOptionPXEClient	string	FALSE	PXE Client option for the DHCP Server Option
DHCPScopes	string	FALSE	Number of DHCP Scopes to Configure
DHCPScopes0SubnetMask	string	FALSE	Subnet mask for the first DHCP Scope
DHCPScopes0IP	string	FALSE	IP Subnet for the first DHCP Scope
DHCPScopes0Name	string	FALSE	Name for the first DHCP Scope
DHCPScopes0Description	string	FALSE	Description for the first DHCP Scope
DHCPScopes0StartIP	string	FALSE	Starting IP address the first DHCP Scope
DHCPScopes0EndIP	string	FALSE	Ending IP for the first DHCP Scope
DHCPScopes0ExcludeStartIP	string	FALSE	Start of the excluding IP range for the first DHCP Scope
DHCPScopes0ExcludeEndIP	string	FALSE	End of the excluding IP range for the first DHCP Scope
DHCPScopes0OptionRouter	string	FALSE	Router of the excluding IP range for the first DHCP Scope
DHCPScopes0OptionDNSServer	string	FALSE	DNS Server for the first DHCP Scope
DHCPScopes0OptionWINSServer	string	FALSE	WINS Server for the first DHCP Scope
DHCPScopes0OptionDNSDomainName	string	FALSE	DNS Domain Name for the first DHCP Scope
DHCPScopes0OptionNBTNodeType	string	FALSE	NBT Node Type for the first DHCP Scope
DHCPScopes0OptionLease	string	FALSE	Lease Duration for the first DHCP Scope
DHCPScopes0OptionPXEClient	string	FALSE	PXE Client for the first DHCP Scope
Authorize DHCP
Property ID	Type	Overwrite ?	Description
UserName	string	FALSE	Username used to authorize DHCP
Password	string	FALSE	Password used to authorize DHCP
Configure DNS
Property ID	Type	Overwrite ?	Description
DNSZones	string	FALSE	Number of DNS Zones to Configure
DNSZones0Name	string	FALSE	Name of the first DNS Zone
DNSZones0Type	string	FALSE	Type of Zone
DNSZones0MasterIP	string	FALSE	Primary IP for the zone
DNSZones0DirectoryPartition	string	FALSE	AD Partition to store the zone
DNSZones0FileName	string	FALSE	File Name of the first DNS Zone
DNSZones0Scavenge	string	FALSE	Enables scavenging
DNSZones0Update	string	FALSE	Enables dynamic updates
DNSServerOptionDisableRecursion	string	FALSE	Disables recursion on the DNS server
DNSServerOptionBINDSecondaries	string	FALSE	Allows BIND secondaries
DNSServerOptionFailOnLoad	string	FALSE	Toggles fail on load
DNSServerOptionEnableRoundRobin	string	FALSE	Enables Round Robin
DNSServerOptionEnableNetmaskOrdering	string	FALSE	Enables netmask ordering
DNSServerOptionEnableSecureCache	string	FALSE	Enables cache security
DNSServerOptionNameCheckFlag	string	FALSE	Name Check Flag
Configure WINS
Property ID	Type	Overwrite ?	Description
WINSPartners	string	FALSE	Number of WINS Partners to Configure
WINSPartners0Name	string	FALSE	Name of the first WINS partner
WINSPartners0Type	string	FALSE	Type of the WINS partner
WINSPartners0IP	string	FALSE	IP address of the first WINS partner
Values used for SCCM Scenarios
Property ID	Type	Overwrite ?	Description
OSDImageIndex	string	FALSE	Index of installation image within WIM (Used for OEM Scenario).
OSDInstallEditionIndex	string	FALSE	Index of installation image within WIM (Used for OEM Scenario).
ConfigFileName	string	FALSE	Filename of config file (example: unattend.xml (Used for OEM Scenario).
OSDAnswerFilePath	string	FALSE	path for answer file (example: c:\unattend.xml) (Used for OEM Scenario).
OSDImageCreator	string	FALSE	User ID of installation account (Used for OEM Scenario).
OSDInstallType	string	FALSE	Installation Type (example: SysPrep ) (Used for OEM Scenario).
OSDTargetSystemDrive	string	FALSE	Disk Drive used to install OS (Used for OEM Scenario).
OSDTargetSystemRoot	string	FALSE	Install path for OS (Used for OEM Scenario).
OSDisk	string	FALSE	Disk drive used to install OS, typically written by ZTIDiskPart.wsf (Used for OEM Scenario).
OSVersionNumber	string	FALSE	OS Major and Minor version number (example: 6.0) (Used for OEM Scenario).
OSArchitecture	string	FALSE	OS CPU Architecture Type (example: x86 or x64) (Used for OEM Scenario).
ImagePackageID	string	FALSE	Package ID for the OS image to install (Used for OEM Scenario).
InstallPackageID	string	FALSE	Package ID for the OS image to install (Used for OEM Scenario).
OSDImagePackageID	string	FALSE	Package ID for the OS image to install (Used for OEM Scenario).
ConfigFilePackage	string	FALSE	Package ID for the Configuration Package to use for installation (Used for OEM Scenario).
Lists
Property ID	Type	Overwrite ?	Description
Packages	list		List of SMS packages that should be installed
Applications	list		List of applications (GUIDs) that should be installed
MandatoryApplications	list		List of applications (GUIDs) that will be installed
Administrators	list		List of groups and users to add to the Administrators group
PowerUsers	list		List of groups and users to add to the Power Users group
DriverPaths	list		Driver path UNCs that should be used (no default)
DriverGroup	list		Driver groups that should be used (default is All Drivers)
StorageDriverGroup	list		Storage Driver groups that should be used for XP/2003 (default is All Drivers)
StorageDriverSysPrepGroup	list		Storage Driver groups that should be used XP/2003 during SysPrep (default is All Drivers)
DomainOUs	list		Optional list of Domain OU's to be displayed to users.
USMTMigFiles	list	FALSE	USMT XML files that should be used when running Scanstate and Loadstate
Groups	list	FALSE	List of local security groups to capture and restore (default is 'Administrators' and 'Power Users')
LanguagePacks	list		List of language packs (GUIDs) to be installed
PackageGroup	list		Package groups that should be used (default is All Drivers)
Role	list	FALSE	Specifies roles that should be assigned to the computer
Location	list	FALSE	Locations for the computer (typicaly resolved via a database lookup based on the default gateway)
WUMU_ExcludeKB	list		List of Windows Update/Microsoft Update patches to ignore (by associated KB Articles)
WUMU_ExcludeID	list		List of Windows Update/Microsoft Update patches to ignore (by associated Update ID)