Over the years I have done a few customsettings.ini file configurations. Some for LTI, some for ZTI. I have done a bunch of demos during class, sessions and for customers, but I realize I have never published them, and since my blog post Back to Basic – Custom Settings Explained is the most read post I have done (it has been on the top 10 list since it was published) I decided to publish the rest of them
Scenario: |
You are about to deploy virtual machines using LiteTouch |
Requirements: |
|
Solution: |
[Settings] Priority=ByVMType, Default Properties=MyCustomProperty [Default] [ByVMType] [IsVM-True] |
BDD.log: |
Using from [Settings]: Rule Priority = BYVMTYPE, DEFAULT —— Processing the [BYVMTYPE] section —— —— Processing the [IsVM-True] section —— Property OSINSTALL is now = Y Using from [IsVM-True]: OSINSTALL = Y Property OSDCOMPUTERNAME is now = VDI-8069-2911-20 Using from [IsVM-True]: OSDCOMPUTERNAME = VDI-8069-2911-2 Property DONOTCREATEEXTRAPARTITION is now = YES Using from [IsVM-True]: DONOTCREATEEXTRAPARTITION = YES —— Processing the [DEFAULT] section —— |
Remark: |
In this case we are using a section called ByVmType which will find a subsection called IsVM-True if we are running a VM which will set the OSinstall property to Y and then it will build the OSDComputername based on VDI plus the 12 most left characters in the serial number. |
Download: |
http://sdrv.ms/XTctly |
/Mike
Share this:
Categories: Deployment, MDT
The Deployment Bunny 
OSDComputername=VDI-#Left(“%SerialNumber%”,12)# cannot work in vmware due to spaces, so how do yo handle it?