1. Overview
  2. Realm setup
  3. Active Directory & SCCM setup.
    1. Active directory - Security group
    2. Active directory - Broker account
    3. SCCM - Deployment collection
    4. SCCM - Administrative category for applications
    5. SCCM - Administrative category for office
    6. SCCM - Limiting collection for collections
    7. AD - Parent AD group for AD group list
    8. AD - Staging OU
    9. SCCM - Configuration directory
    10. SCCM - WinPE boot image setup
  4. Configuration tool & File
    1. Realm secret key
    2. Allowed WinPE instances
    3. Network access account
    4. Notification account
    5. Hostname formatting
    6. Automatically identify hostname
    7. Overrides
    8. Active directory staging OU
    9. MBAM Server details
    10. SMTP server details
    11. Notification types
    12. User state migration (USMT)
      1. Data store encryption
      2. Migration types
      3. Free space
      4. Config XML
      5. Migration rules XML
      6. Ignore return error codes
      7. Migrating EFS files
      8. Move domain
      9. Move user
      10. Currupt user profiles
    13. Logs and Profiles location
    14. Disk setup
    15. Content availability check
    16. Error adding collection member
    17. Error adding AD group member
    18. Wait for Bitlocker decryption
    19. Approved hardware
    20. Extension Attributes
  5. Using sccmtspsi (Operator view)
    1. sccmtspsi login window content
    2. sccmtspsi controls
      1. Asset hostname
      2. Unlock bitlocker
      3. Get task sequence deployments
      4. Get operating system images and packages
      5. Get office application
      6. Get SCCM applications
      7. Get SCCM collections
      8. Get AD Groups
      9. sccmtspsi actions
      10. Data migration options
      11. Primary users
      12. AD / SCCM entry
      13. Extension Attributes
  6. Task sequence steps
    1. sccmtspsi-tasksequence.exe
    2. Task sequence variables
    3. Apply operating system image step
  7. Requesting a Ad free license (Optional)
  8. Task sequence error codes
  9. sccmtspsi error codes

4.7.Check hostname structure, SCCM conflicts & DNS conflicts ?

SCCMTSPSI can automatically identify conflicts. Automatic conflict identification happens in the following ways.

  • Does a DNS lookup to identify if another device with the same NetBIOS name is active (responding to ICMP requests) in the network.
  • Submits a request to SCCM containing the physical address and/or the system management BIOS identifier of the device. By default, when processing actions sccmtspsi will fail if record conflicts are identified.

Cautiously select the option Truebutallow! to allow the operator to override conflicts. To enforce conflict checks select True and to turn off conflict checks completely select False.

When Truebutallow! is used the operator adds a ! before the hostname. e.g. !PC456W10 . Where PC456W10 is the hostname, “PC” is the prefix and “W10” is the suffix.

Truebutallow! also provides the operator with an option to overrides the case, prefix and suffix mandate.

For e.g. If the operator enters a hostname !456 , sccmtspsi will not add the prefix “PC” and the suffix “W10″ . Thus the host name remains as 456 . But conversely, If the operator enters a hostname 456 , sccmtspsi will add the prefix “PC” and the suffix “W10″ and the hostname will now change to PC456W10 .

Suggest Edit