We would like to know the appropriate way to get PS010 (the new package server) ready with every image package and have them downloaded so PS008 and PS009 can be gone completely and be still able to image using the new package server.
ITMS 8.5 RU4, 8.6
Scenario 1: When the Package Server owning the image package is still available
If the image is owned by a Package Server then this Package Server is the source of that image and all other Package Servers are downloading this image from this owner.
If the customer wants to dismiss the Package Server which owns some images, then he/she should transfer image ownership to some other Package Server:
Would be then necessary to "Take ownership" of the image packages on PS009 (wait for the process to finish) and then "Take ownership" of those packages on PS010 since also PS009 will be decommissioned?
Yes. There should be an owner for other PS-es to be able to download it.
on PS009 (still one of the remaining old PSes), we choose an image package and did "Take Ownership". After a bit, this package changed to "Locally Managed".
One thing that we are not sure if it was set that way but on PS010 (new PS with no Cache files for image packages) that same package was marked for Deletion after PS009 took ownership. We checked on 'SMP Console>Settings>Deployment>Image Management>Select the testing image>open the image settings' and we saw that under the "package servers" tab, just the PS009 showed as the assigned package server instead of "All Package Servers"
"Take ownership" AFAIK does not change any assignment on NS, it just changes the owner of the package. The fact that this setting exists, means this was done before by someone, and this explains why files were deleted from PS010. It could have received this policy earlier and deleted the package files.
Now you need to put the assignment back, so PS010 will be able to download the package "take ownership" of it.
Scenario 2: When the original package server is not longer present
Can we use ResourceImportTool if we don't want to follow this process described above or when the original package server is not longer available?
Images can also be imported via ResourceImportTool.exe, however it creates new image resources, and cannot replace existing ones. Default location of ResourceImportTool on PS is "C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\Tools\ResourceImportTool.exe" if Deployment Solution Package Server is installed. If the original package server is not longer available but there is another package server that still have a downloaded copy of the image package(s) file(s), you can use the ResourceImportTool.exe to grab the files from that existing location.
If I run the ResourceImportTool on the new package server, by doing that also makes the package to be flagged as "Locally managed"?
Adds the files and uses the same GUID as previously referenced for that same set of files for the package that is missing the files under the Cache folder?
Or creates a new whole image package reference on the SMP that will be listed as a new image reference under Image Management in the SMP Console?
It will add it as a new image to the existing list of images, and will not reference existing GUIDs as there is no option in ResourceImportTool for GUID selection.