Video Screencast Help

PC Transplant update - does it repliciate

Created: 09 May 2013 • Updated: 14 May 2013 | 3 comments
This issue has been solved. See solution.

I am going to update PCTransplant using this link :

Can you tell me if this will replciate to all site servers if done on the NS ?


Operating Systems:

Comments 3 CommentsJump to latest comment

BugTastic's picture

Looks like it doesn't. Now I just need to visit each site server and do the upgrade process again. Marvellous. It just gets better the longer you work with this software. <sarcasm>

Thomas Baird's picture

I'll try to find out more about why this is, or is not.  Good comment.

Thomas Baird
Enthusiast for making things better!

Thomas Baird's picture

Bugtastic is correct - it will NOT replicate out to the site servers by default, and in fact, this may not be a good idea to have it do so by default.  Replication, remember, is a synchronization of folders, so if any changes were made to a site server, the NS would overwrite those.

However, if you have a large number of site servers, a package can be created to do this for you.  We used to do this for the drivers packages prior to them adding it to the product.  You could even clone one of the Drivers packages already on the system, modify it to point to the PCT folders on both the initial page AND the page for the package servers, and voila - you'd have replication.  This can be helpful in other ways too, but bears the risk


[Recommended] You could also just use a Copy File task to replicate out the changed file.

PS>  We're asking Product Management to make something to help resolve this in the future - good feature request!

IF you decide you would rather keep these folders in synch on all your servers (be cautious, this will include ALL changes you make to the PCT folder!), here's how you can make a package for the PCT folder and set it to replicate:  (Pretty sure this should work, but my environment is VERY small to test against!)

NOTE: do not replicate the PCT Packages folders!  This would wipe out the default location of any PCT client packages you've created on site servers!!

NOTE: If you've made customizations to the site servers, this will overwrite any changes made to this folder on any site server!!.  Replication synchronizes the destination with the source, removing anu changes made to the destination on every synchronization, so it may not be a good idea.

1> Navigate to Manage | Software

2> Right-click on the left pane on "Deliverable Software" and select Import Software.

3> Select "Software Release", and "Access Package from a Directory on the NS..."

4> In the Location, browse to the folder where you put the updated files and select it.  By default it will look something like: C:\Program Files\Altiris\Altiris Agent\Deployment\Task Hanlder/PCT

5> Select "Display Location" so it enumerates all the files.

6> Select OK.  You will be prompted that you have not selected an installation file - this is fine, just click OK to continue.

7> Leave the selction to "create a new software resource" and give it a name.  I chose PCT Folder.

8> Put in a company and Version.

9> De-select "Open Software Resource" and Select OK

10> Navigate in the console to Manage | All Resources \ Default \ All Resources \ Package

11> Type PCT in the search criteria (top right of right pane) to narrow down to your new package.

12> Right-click your package and choose Actions | Edit Package

13> Select the Package Server tab, and modify the destination location to almost match that which is in the Drivers Package, which should be this:
\\%COMPUTERNAME%\Deployment\Task Handler\PCT

14> Modify the package server selection to be "All Package Servers" and click OK to save your changes.

15> Right-click the package again and select "Update Distribution Points" to update your site servers.

Thomas Baird
Enthusiast for making things better!