Configuring Post-deployment Activities
Post deployment activities help prepare devices for use immediately after an OS image is deployed. The OS Deployment add-on in Endpoint Central allows these settings to be configured as part of a deployment template. This page explains each available option and how it can be used during template creation.
Shutdown or Restart the Target Computer
This setting determines what action the target computer performs after the deployment completes. Select either Shutdown or Restart based on how the device will be used. Restart is recommended when the device must be ready for immediate use, while shutdown is suitable when the device will be used later. This action runs automatically without manual intervention.
User Profile Migration Settings
When upgrading to a newer operating system, existing user data and configurations may not automatically transfer. To simplify this transition, backups of user profiles can be created and migrated to the target device. Select the required user profile backup under User Profile Migration Settings to include it in the template.
User profile backups can also be mapped to individual devices by selecting Computer Specific Settings under the Customize tab and assigning the backup to the corresponding MAC address.
For detailed steps on creating profile backups, refer to Backing Up User Profiles. To learn more about migrating profiles during deployment, refer to User Profile Migration.
Configuring Target Computer Details
Cloned images may cause the same Security Identifier (SID) to appear across multiple devices, which can affect domain or workgroup functionality. To avoid duplication, enable Generate New SIDs under Post Deployment Activities. This automatically assigns a unique SID to each target computer. The existing SID may also be retained if required.
Target Computer Name or Naming Pattern
Deployment templates allow defining computer names or patterns for devices receiving the image. Common methods include fixed names, sequential numbering, or prefix-based naming using hardware attributes such as serial numbers.
Examples:
- Fixed name: Specifying WIN-COMPUTER names all devices as “WIN-COMPUTER”.
- Sequential pattern: WINPC-{1} results in “WINPC-1”, “WINPC-2”, “WINPC-3”, and so on.
- Serial number: WINPC-<SERIALNO> produces names such as “WINPC-F3QQ123”. (Ensure prefixes do not exceed seven characters.)
- Number padding: WINPC-{001} produces names such as “WINPC-001”, “WINPC-002”.
- Device code: WINPC-<DEVICECODE> applies laptop, desktop, or Surface device codes defined under Customize > Customize Deployment > Deployment Template > Computer Name Pattern Settings.
- Remote office code: WINPC-<ROCODE> uses location-specific codes, typically derived from the office name.
These patterns may also be combined (e.g., prefix + serial number + sequence).
For device-specific naming, Computer Specific Settings can be used to assign individual computer names, domains, or other parameters. These values are applied once deployment is complete.
If choosing the option Specify computer name during deployment, the deployment process allows entering a name manually. If no name is provided, the system waits 10 minutes for input. After this period, the name from Computer Specific Settings is applied; if none exists, the name embedded in the image is retained.
Adding Target Computers to a Domain
The deployment template can automatically add target computers to a domain. This is useful when the source (imaging) machine and target machines belong to different domains. Provide details such as the domain name, network type, and credentials of an administrator with permissions to join devices to that domain.
Adding Target Computers to a Domain and OU
Devices can also be placed directly into a specific Organizational Unit (OU). Provide the OU details while configuring the domain. After deployment, the device joins both the domain and the designated OU automatically.
Adding User Accounts to the Target Computer
User accounts can be created on the target device during post deployment. This is useful when preparing devices for new employees or assigning accounts before handover.
Adding Applications
Applications, drivers, executables, and scripts can be installed automatically after deployment. For information on configuring applications, refer to the Adding Applications guide.
Once post-deployment settings are configured and the template is finalized, proceed with the image deployment. For detailed steps, refer to Deploying OS Images.
Yes No