Deployment Solution

I recently upgraded our DS from 6.1 to 6.9.

Our images are stored on a separate PC and worked fine prior to the upgrade.

Since the upgrade, when trying to image an PC's it fails with 'Error 3: The specified path was not found An error occurred accessing the security-settings file'.

When I try to map any drives with the net use command, I get the same error.

I have also tried copying the files back to the eXpress share, rdeploy starts, gets to about 4%, then quits with the error 'Error: Imaging download failed.. The production partition may be corrupted!'.

Permissions on both shares being used are OK, we have even set them to everyone having full control.

Any help would be appreciated as we have a pile of new PC's to image.

You might try to convert your image to 6.9

After 2 days we have finally found a work around.

When using the net use command from the F drive, we received the message 'Error 3: The specified path was not found An error occurred accessing the security-settings file', but if we change to the A drive, net use maps the required share on the PC where our images are stored.

We had to change our script from :

net use n: \\hwcrey-006000\images /p:yes
set path=f:
set path=i:
rdeploy.exe -md -fn:\dc7800.img

to :

a:
cd net
net use n: \\hwcrey-006000\images /p:yes
set path=f:
set path=i:
f:
rdeploy.exe -md -fn:\dc7800.img

I think the images that we have on our eXpress share are failing because we are now running Altiris on a virtual server with a gigabit NIC, below is the error log:

Error description:
The image is invalid.
(Note: Current volume is NTFS from source slot 1.)

Possible causes:
Data has been corrupted (e.g. in an image or on the network).
A gigabit ethernet card is being used.

Possible resolutions:
Repeat the operation to see if the problem occurs in the same manner again.
Simplify the network by removing routers, etc. that might corrupt data.
If a file is being read, recreate the file.
Disable 'TCP Checksum Offloading' on the servers with the gigabit NICs where the image is stored.


==================== Technical details ====================

Logfile = created Mon Aug 4 10:22:44 2008
Build = rdeploy.exe 6.1 (5798)
Cmdline = f:\rdeploy.exe -noprompt -md -f.\Images\NEW530.IMG

Status = 120 (0x78)
Source file = rdeploy/img/image6.cpp
Line number = 2185 (0x889)
Stack trace = 0x671867 0x6b850a 0x660f73 0x662f25 0x61426c 0x64fb22 0x6f9beb 0x64e46b 0x612b56 0x63a4a9 &Known=0x65f050
Note = Current volume is NTFS from source slot 1.
Imaging library revision = 5798 (dos-x86-release build, Thu 06/17/2004 02:36 PM)

We have also found that once all the scripts have completed and the deployment job shows as completed, the computers have hung when trying to add to domain.

quote:

---

the computers have hung when trying to add to domain

---

We had the same problem with one of our customers. This was due the fact the aclient needs an upgrade because a old version is used in the image. The resolution was to first upgrade the (d)aclient and then add the computer to the domain with the configuration task.