[Settings]
Priority=ByIsOnBattery, Virtual, Laptop, Desktop, HardwareInfo, Default
Properties=MakeAlias, ModelAlias
[ByIsOnBattery]
SubSection=ByIsOnBattery-%IsOnBattery%
[ByIsOnBattery-True]
OSInstall=NO
[Laptop]
Subsection=Laptop-%IsLaptop%
[Laptop-True]
SkipDomainMembership=YES
SkipComputerName=YES
BDEInstallSuppress=NO
BDEDriveLetter=S:
BDEDriveSize=300
BDEInstall=TPM
BDERecoveryKey=AD
BDEKeyLocation=**share location**
OSDComputerName=CPWL#RIGHT("%SERIALNUMBER%",10)#
[Desktop]
Subsection=Desktop-%IsDesktop%
[Desktop-True]
SkipDomainMembership=YES
SkipComputerName=YES
BDEInstallSupress=YES
OSDComputerName=CPWD#RIGHT("%SERIALNUMBER%",10)#
[Virtual]
Subsection=Virtual-%IsVM%
[Virtual-True]
SkipDomainMembership=YES
SkipComputerName=NO
BDEInstallSupress=YES
OSDComputerName=CPWV#RIGHT("%SERIALNUMBER%",10)#
On Thu, Feb 27, 2014 at 4:10 PM, Charles Moore <[email protected]>wrote:
> Fellow MDTers,
>
>
>
> I am currently trying to automate the deployment of a Hyper-V client using
> MDT 2013. MY cs.ini has the following for VMWare....
>
>
>
> [VMware, Inc.]
>
> OSDComputerName=FTSVM#Right(replace("%SERIALNUMBER%"," ",""),8)#
>
>
>
> Does anyone use now or no of the cs.ini entry for hyper-V, I've searched
> the internet with no answer to this.
>
>
>
> I am trying to use the schema of FTSVM%serialnumber% so FTSVM0123456 as an
> example, FTSVM are static, and 123456 is the serial number populated from
> the serial number of the Hyper-V.
>
>
>
>
>
> ------------------------------
>
> CONFIDENTIALITY NOTICE: This email message and any attachments hereto are
> intended only for use by the addressee(s) named herein and may contain
> information which is legally privileged, confidential and/or exempt from
> disclosure under applicable law. If you are not the intended recipient, or
> an authorized representative of the intended recipient, of this email
> message, you are hereby notified that any review, dissemination,
> distribution, copying, or use (including any reliance thereon) of this
> email message, and/or any attachment hereto, is strictly prohibited.
>
> Although this transmission and any attachments are believed to be free of
> any virus or other defect that might affect any computer system into which
> it is received and opened, it is the responsibility of the recipient to
> ensure that it is free from virus or other defect and no responsibility is
> accepted by the sending company, its subsidiaries and affiliates, as
> applicable, for any loss or damage arising in any way from its use.
>
> If you have received this email message in error, please immediately
> notify the sender by return email and permanently delete from your system,
> the original and any copies of this email and any attachments hereto and
> any printout hereof. Unauthorized interception of this email is a violation
> of federal criminal law.
>
