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

7.Requesting a Ad free license (Optional)

The token request tool is used to request a sccmtspsi token for an operator. 

Click to open the downloads page to get the Token request tool.

Note: dot Net framework 4.5 or above is required to run the Token request tool.

Launch the tool from the start menu as per the below image.

Paid license for Users/Organisation are complied based on the following attributes. For organisational license tokens user based attributes are ignored.

Active Directory attributes : company, mailgivenName, sn, streetAddress, l, couserGUID, domainGUID.

! ! Important notice !! : The request token generated by the ‘Token Request Tool’ is encrypted using encryption standards detailed in Advanced Encryption Standard (AES) and ISO/IEC 18033-3:: Block ciphers. For privacy and security reasons, We DO NOT save any of the above attribute data into our systems after issuing the license token. So if the license token is lost or tampered with, the licensee will have to re-submit a newly generated request token to receive a new paid license token which will be charged separately. It is best practice to backup your license token to a safe location within your network.

Note:

  • Purchase a Paid sccmtspsi license token, only if you have used the Free license token first. Check if sccmtspsi works within your environment.
  • Paid license tokens can only be issued to a person (Employee, Contractor etc) or for an Organisation.
  • The Paid license token owner should have all of these attributes set. [company, mailgivenName, sn, streetAddress, l, couserGUID, domainGUID].
  • A Paid license token cannot be shared between two people. But Organisation license tokens can be used by all user with a Domain whose domainGUID  was used for licensing.
  • Any change to the above listed active directory attributes will require a new Paid license token [Reissue of a token will incur cost and completion of a declaration form).
  • Prerequisites : This tool requires dot Net framework 4.5 or higher.

Open the token request tool and input the username (samaccountname or userID) of the operator to whom the token will be issued. In addition to the username also provide the Realm name of the Realm to which the token will be assigned.

Save the request token (*.rtoken file) to a location on your computer.

Send the request token to us tokenrequest@sccmtspsi.com .

You will be emailed a License token after your payment is received and the request token is processed.

Place the License token(s) inside the “token” sub-folder in the realm configuration drive.

Suggest Edit