Deployment and Imaging Group

Environment: Server 2008 R2 and we are running 7.5.

I have a handful of Windows Server 2008 R2 at various remote sites that I am having problems with and determined that the systems need to be reimaged.  Running a basic deploy image task lays an image down on Disk 0 and overwrites any existing data.  The way these devices are configured is the file shares exist on a 2nd partition of Disk 0 and I want to keep this data after reimage. Also, if I am reimaging a Site Server, will the NS know enough to use a seperate Site Server to handle the Tasks and Packages or should I remove it from the list of site servers?

Disk configuration as seen below:

I only want the image task to deploy to the C: partition.

Is there a way to configure the advanced options of a deploy task to only target the first partition?

Here are the default advanced options:

If you will reimage a SS, I personally would remove its site services first so that it will not be effected by site maintenance logic.

Have you tried the "As Follows" option, as that looks like it will allow you to do what you need?

I'm attempting that now.  Should know in about an hour.

Edit:

It did and it didnt work.

The image is from a 40GB disk and so on the target system we know have a 40GB NTFS file system with Windows Server 2008 R2 and then the rest unformatted.  (this is a box I'm testing on and not my end desired target of course)

Back when we were using just ghost you had the options of choosing the partition you want to deploy the image to.

Here are the guidelines for the "As Follows" option. This will let you deploy the one partition and not overwrite the the others.

As Follows
This option lets you:

• Set a custom size for the partitions being deployed.
  Click on the partition number to display the resizing options for the desired partition. Make the changes as needed.

• Determine whether to deploy all of the partitions or just one partition.
  Clear all but one of the partitions. Mark the single partition you want to deploy.
  For example, if your image has four partitions (1-4), you can deploy partitions 1 or 2 or 3 or 4, but you cannot deploy 1 & 2, or 1 & 3, or 2 & 4, etc.
  
  Destination disk settings
  When you are only deploying one partition using the “As Follows” option, you must also configure the Destination disk option found on the Command-line page (tab) to include the desired disk and partition number. The format for the Destination disk option is A:B where A is the disk and B is the partition to which the partition will be restored. When deploying only one partition, all other partitions are left intact. This can be very useful, for example, if you want to restore the system partition (which may have been corrupted), but leave the partition containing the users information untouched.
  
  Failure to configure the Destination disk option will result in a “Provide valid destination partition for single partition deployment” error message.

As far as the the Site Server question goes, you could try manually assigning the Site Server you are going to deploy an image to, to a different Task Server such as your NS computer. If you check, you might find that it is already assigned to the NS computer anyway.

I did the as follows with a single.  I am on my personel computer so i cant take a screenshot but as the screenshot for the advanced Command-line option is displayed above, for the destination disk entry should i be typing "1:1" without quotes?  I'd love to kick this off tonight and go in tomorrow and see if it worked or not.  Thanks for everyones help so far!

I have not used the command line options in SMP and it would be nice if the ?HELP gave examples...

How will the 300MB BDE drive play in to all of this?  I really dont see a need for it in a server environemnt but requirements are requirements...

I'm attempting the DST option as 1:1.  Well see what that gets us...