Save an capture image

[nuria_2]

hello
I have installed RDP 3,10 and at the moment single I have a problem. I have two discs, C:\ and E:\ On disc C are where I have installed RDP, and everything goes well, but when attempt to do an image and that keeps in E, it's not possible to finish the work. Somebody can help me.
thanks

[pasquino bocci_1]

Hi,

Your disk E must be a network share!!

Ciao

[nuria_2]

Hi,
my disk E is network share, but don´t work

[pasquino bocci_1]

Hi,

from ALTIRIS:

How to store images on a different drive or server (Local Image Store)


--------------------------------------------------------------------------------
Question


How can I use an additional or alternative storage locations for the images? What are the steps to create these map drives with PXE configuration?



--------------------------------------------------------------------------------
Answer


Please follow the following guidelines for adding additional sharepoints for files, images and data to be stored for use by Deployment server 6.1 build and higher.

Note: All drive mappings must have the same drive letter available to DOS.
Deployment Solution 6.1 only: On the Deployment Server, map a drive to the new share location where the images and files are to be stored. (Not the Datastore.) Map a network drive to point to the share for the images using the format X:\\share and choose to reconnect at logon.
Deployment Solution 6.1 only: Open the Altiris Deployment Server control panel (Start > All Programs > Altiris > Deployment Solution > Configuration) and add the drive mapping under Drive Mappings. Use the Browse button to navigate to the new share from the network neighborhood so it will have a UNC path. It should look like this:

X: \\server\share (image storage)

Note: Don't point to the mapped drive on the workstation computer or an error will occur. It can't be X: path X:.

Choose OK, and the message â the service needs to restart for this to applyâ will appear. Click OK to restart the service. If an error occurs and the computer can't be restarted, the drive mapping was incorrect or the share is not available for authentication.

Note: The service can also be started by going to the Run command and typing c:\express\axengine.exe.
Deployment Solution 6.1 only: Re-create the BootWorks boot files and add the newly mapped drive at the Network Drive Mappings window. The F: drive is the default and should not be changed. Choose the same letter for the new share location that was used in step 2. The path should be the UNC path.

Note: BootWorks requires a user name and password that can access both shares (F: and the new mapping).
Deployment Solution 6.5 and Deployment Solution 6.8: Within the PXE configuration: Step 9 of 12.
Edit the DOS Managed Boot file.
Right-click on the Boot file and pass to Manual create G: Drive Mappings Step 7 of 12. Also check LMhost file entry.
When the Boot file is finished it should reflect both Mapped drives in the Step 9 of 12.
Click Next to the end and Create PXE automation package. Step 10 of 11.

Make sure within the Create or Deploy image job the check box for Local Image Store is checked.

To manually edit the PXE boot file, go to PXE configuration, select DOS Managed, and edit the boot image box. Expand the Boot image and locate the files below.

Edit: the autoexec.bat
Add the RED Text

REM @echo off
REM BDC_TASK_TYPE= autopart or auto or pxe or network
set BDC_TASK_TYPE=$$Task$$
REM ramtype=full or partial or none
set ramtype=$$RamType$$
set ram=none

In the Mapdrv.bat file should look like this

net use F: "\\Servername\eXpress" /yes
net use G: "\\RemoteServername\image" /yes

You can add the "pause" statement between the mappings to troubleshoot the issue.

See article 21313, "How to properly configure PXE image/Rdeploy to use a dual NIC DS," for more information.

In the LMhost file:

# For example:
#
# 149.124.10.4 server1 # main office server
# 182.102.93.122 joe3 # joe's database server
172.17.51.130 SERVERNAME

Important: Save changes. In the upper right corner, there is an icon of a floppy disk. Select Next and re-compile your boot image. Step 10 of 11.

It is very important to make sure in the PXE configuration: DS tab > Default boot option is the Automation Boot ( DOS, Linux, WinPE). Also within the Disk image job, select the Default Boot option > Automation Boot.
PXE images: Within the mapdrv.bat file of the PXE boot image also needs the new share image location.
UNC paths can be used instead of Drive letters.
Within the Image job make sure Local Image Store is checked box. If the image is stored on a different share other than the eXpress share this needs to be checked for all versions of Deployment Server.
By default when you create a share the permission is set to read only. When clicking on the folder created (with it shared) and selecting "Sharing and Security" under the "Share" tab there is a button for "Permissions" this is where the "Everyone" group by default does not have Write privileges.
Make sure when making any changes to the PXE boot files to Save changes and re-compile the Boot File.
If folder is missing when testing the map drive. Fiber Line connections to alternate drives. Test the Share connection: DOS Dir to map to g drive and you notice the Image folder is missing. May need to create a sub folder in the image folder. Example: G:\\Images\SubFolder name
To troubleshoot Shares:

Try to run your imaging job again. When you see "Press F2 for Diagnostics" press F2 and choose Exit. At the DOS prompt type "net use" to report drive mappings. Are the mappings correct?

Also try typing the command 'Net View \\Server <> '. If this does not this work, you may have a name resolution problem.

Then try typing 'Net Use F: \\server\express <> '. If this fails, you may have a permissions issue.

*Make sure the user does reside on the computer where you want to store the image.

*Ceated a new user (pxeuser) and added this user to the remote share. Then recreate the pxe boot files with the new user and password.

Mapping internal alias hard drives under the eXpress share.

The image was able to be created on the remote share.Additional related Articles:

17934, "Instructions for running RapiDeploy from a command line"
19305, "How do I set up a different image location?"
20330, "Error 40 While imaging"
23987, "Imaging multiple physical hard drives with RapiDeploy"