Deployment Solution

I have 150 computers to image. I am using the automation environment to image the systems.  Not to familiar yet with Altiris as its a complex set of software but here goes.

I wish to create an image of a system that I can then deploy to 150 systems via a deploy task. Here is my process so far.

Run network discovery to bring in all the systems into Altiris.

Create client job

reboot to automation

deploy image

reboot to production

Problem is I tested this on 1 machine and it ends up with the same name as the machine it was imaged from.

If using sysprep, will that allow me to sysprep 1 system, and deploy it to 150 machines and those machines keep their existing names?

Not sure how this works, any help would be greatly appreciated.

Here is what I would like to do.

Deploy image to 150 machines

The 150 machines can keep their existing names and IPs.

Hi,

   Yes !  by deploying the sysprepped image you can avoid duplicate names and IPs.

Use the following tasks in the capture job

1. Prepare for image capture.

2. Capture image.

3. Reboot to production.

To deploy the image .(basic steps)

1. Reboot to atuomation.

2. deploy image.

3. Reboot to production.

I would also recommend to go through the article.

http://www.symantec.com/docs/HOWTO30267

Thanks

I may have been not so clear.

Let me try and clarify.

I have the following computers:

SIM1

SIM2

SIM3

SIM4

and so on.

I would like to take an updated (patched) image and deploy it to SIM1 - SIM4.

When I deploy the image, is there a way to keep the existing names and IP addresses of SIM1, SIM2, SIM3, and SIM4?

If I sysprep then i have to go setup 150 machines after imaging.

You can add a new task of apply system configuration after deploy image task.

There you will have options to select the leave existing name and ip address.

Thanks.

Sysprep should do that actually and if you deploy the system and choose generate sysprep it should change the computername during sysprep. the captured image is sure syspreped? 

To get a fixed IP adress you should add the following to the unattend.xml(NScap\bin\Win32\X86\Deployment\) and save it as custom_attend.xml.(the @tcpIP is what DS uses to put in the inventory data)

Choose custom sysprep configuration file in the task and use the custom file.

<component name="Microsoft-Windows-TCPIP" processorArchitecture="x86"
publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS"
xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <Interfaces>
- <Interface wcm:action="add">
- <Ipv4Settings>
<DhcpEnabled>false</DhcpEnabled>
</Ipv4Settings>
- <UnicastIpAddresses>
<IpAddress wcm:action="add" wcm:keyValue="1">@tcpIP/24</IpAddress>
</UnicastIpAddresses>
<Identifier>Local Area Connection</Identifier>

- <Routes>
- <Route wcm:action="add">
<Identifier>0</Identifier>
<Prefix>0.0.0.0/0</Prefix>
<NextHopAddress>0.0.0.0</NextHopAddress>
<Metric>20</Metric>
</Route>
</Routes>
</Interface>
</Interfaces>
</component>
 

some more info on Token and Deployment Tasks here.

https://www-secure.symantec.com/connect/articles/tokens-deployment-solution-7x

https://www-secure.symantec.com/connect/downloads/deployment-solution-samples-v71-sp1-smpcms-71-x64