Deployment Solution

Hi,

I'm using Deployment Solution 6.9 sp4.
I'm able to install dagent on x64 Win7. The agent is communicating to the server successfully.

But, when I'm unable to capture the image.

When the system is booting from PXE automation
1. Getting DHCP ip address
2. Copying files
3. drivers are loading
4. Altiris agent console is opened but showing "Unable to connect to the server. Session Terminated"

Please help me.

Regards
Amar
 

You need to integrate the Vista (PE 2.1) NIC drivers into your automation.

Don't forget to integrate it into both automations (32 and 64 Bit) if you use both.

Beware of "Automatic Selection" (32/64) if the drivers are not integrated.

Hi Mistral,

Thank you for your reply.

In the PXE configuration,
I've created a "WinPE x64" boot menu and changed the drive letter to Z: Please find the enclosed screenshot.
But, in PXE configuration summary page, it is showing DRIVE MAPPINGS to F: & Z:  Please find the enclosed screenshot.

Booted the system by selecting "WinPE x64" Please find the enclosed screenshot.

NIC Drivers are loaded.
Launching dagent.....Please find the enclosed screenshot.

Client Record Updated. Please find the enclosed screenshot.
Immediately, Connection closed. Session Terminated. Please find the enclosed screenshot.

I'm getting the same issue on both VMware system and on Physical system.

I cannot see your initial "Unable to connect to server". It looks like the agent terminates gracefully because there is nothing to do.

Also it looks like you force the client to boot to Automation manually (F8) - why?

If you assign an image job/task and select the correct Automation in the task, the client should boot to Automation automatically.

How you trying to image?

I forced the client to boot to Automation manually (F8) to capture screenshots only.

Eventhough image capture job is assigning, client is not completeing the job due to connection is getting closed. Please find the attached screenshot.

In server, where can we collect the logs.

As Mistral already mentioned, this seems an issue with the job configuration to run in Production vs in Automation and then also which automation environment. Could you confirm your job is configured to run in the configured Automation environment or attach some details about how the job is configured?

The most common causes for this behaviour are;

1) You have a job queued up before the current one. Make sure that there are no other jobs queued up other than the one you are testing (or order by "Scheduled At" and ensure they don't come first). If your computer is trying to install something in production, it will not simply exist autoamtion and reboot into production, even if you force it to automation. Agent update jobs can cause this... so check.

2) AS BBC said above... The next most likely is that the first task in the job you are running is not set to automation, or is set to a different automation than what you manually selected. Check the job and make sure these are configured and match i.e. a Job configured for an automation environment called "WinPE x86" autoamtion will not work if you boot "WinPE x64" automation or a DOS autoamtion, etc.

3) Another possibility... the computer has a duplicate DS account or has just generated one because of a primary key difference. Check at the top of DS for a "New Computer" that is based of the computer's Serial Number. If your primary keys are set to something like "Serial + MAC", ensure that there are no other computers in DS that share that information. Unless the primary key is unique, you could be picking up another DS account that has no tasks assigned.

4) there is probably a fourth... but I can't think of one at present.

Prepare Pxe image with x64 configuration through  boot menu and changed the drive letter (keep  drive letter except A to F).

After successfull completion of WinPE x64 save changes in Pxe configuration utility so that new WinPE image appears in drop down list of automation preboot environment.

Select newly created WinPE x64 preboot env in create image job and schedule the task on client .

Make sure that In this case you need not require to boot the client into automation forcefully using F8.