- Overview
- Realm setup
- Active Directory & SCCM setup.
- Active directory - Security group
- Active directory - Broker account
- SCCM - Deployment collection
- SCCM - Administrative category for applications
- SCCM - Administrative category for office
- SCCM - Limiting collection for collections
- AD - Parent AD group for AD group list
- AD - Staging OU
- SCCM - Configuration directory
- SCCM - WinPE boot image setup
- Configuration tool & File
- Realm secret key
- Allowed WinPE instances
- Network access account
- Notification account
- Hostname formatting
- Automatically identify hostname
- Overrides
- Active directory staging OU
- MBAM Server details
- SMTP server details
- Notification types
- User state migration (USMT)
- Logs and Profiles location
- Disk setup
- Content availability check
- Error adding collection member
- Error adding AD group member
- Wait for Bitlocker decryption
- Approved hardware
- Extension Attributes
- Using sccmtspsi (Operator view)
- Task sequence steps
- Task sequence error codes
- sccmtspsi error codes
4.2.Allowed WinPE instances
To allow a WinPE instance to run, the value corresponding to the command line parameter ‘ -instancename ‘ should be added to the below list. Read details about ‘SCCM – WinPE boot image setup’ in the previous section => Click here.
- The feature can be used to rein in old USB and Full media boot devices.
- This option helps administrators keep their USB boot devices up-to-date with the latest image.
- Administrators should assign a new instance name, when changes are made to the WinPE boot image.
- Use alphabets, numbers, – (hyphen) and . (dot); No other special characters are allowed. Cannot end or begin with a special character.
Instance names can be up to 25 characters in length.