How can I use an existing DS6.9 .IMG file with DS7?
I have an existing image created with DS6.9 RDeploy (.img). I want to test distributing it with the new DS7 "Deploy Disk Image" task in NS7.
The rdeploy.exe file on the server (in \Altiris\Altiris Agent\Agents\Deployment\Task Handler\rdeploy folder) is version 6.9 - so it should be able to deploy the image file just fine.
However, I can't find anywhere to create a "Disk Image Package" in the NS & tell it to use the existing .img file. When you set up the "Deploy Disk Image" task, it asks you to select an "Image name" - if you click Browse, it gives you a list of disk images to select from - but it's empty.
I presume this list is populated when you use the "Capture Disk Image" task to pull an image off of a PC.
Under Settings > All Settings > Deployment and Migration, there is a "Disk Image Packages" folder that looks like it would be this same list of disk images. But there is no right-click > New > Disk Image Package selection (just Folder, Item Link, or Web Link) or a ☼New button or anything like that there.
Is there any way to manually create a "disk image" package in NS7 without using the "Capture Disk Image" task to create the .img file from a client PC (i.e. use an existing .img file)?
my guess.
Without looking into it.
1. create a capture disk image task. Name it exactly what your old file is
2. have windows search for that file
3. copy and replace the newly created image with your old one.
In theory this will work. The problem is you will not have the NS 7 agent on the machine and if you did sysprep you will have to copy a sysprep file into the image for it to do post config.
Linux Man
Viddect
good guess...
Thanks viddect,
Yeah, under DS, we have the image come down & then use FIRM tasks to copy drivers, scripts, & such into the new production partition before booting to prod (kind of a home-made HII). One of the things it copies in is the install of AClient with the .inp file configured for that DS. That way we can use the same image on multiple DS's & then config it after depending on what DS you imaged from.
I'm figuring I can still do the Automation tasks to copy the scripts & such into the production partition after the image is installed (after RDeploy completes), and that one of those would be the NS 7 Agent installation - of course, I guess we'll have to install the DS task handler plugins too if we want to use those for any post-image config or install tasks.
It's a work in progress to convert, and getting the existing image deployable is just the first step.
So you don't see a manual way to create a "Disk Image Package" without using the Create Image task either, huh? Hmmm... that seems like a very stringent requirement since RDeploy can create images without NS. Needs more flexability!
Would you like to reply?
Login or Register to post your comment.