deployed image has larger system reserved partition

Hello, Aaron

Did you deploy the image to the same machine? Is it UEFI? Did you deploy entire drive or partitions separately?

It would be useful to see a log file C:\ProgramData\Acronis\DeployServer\AgentsLogs\XXX.XXX.XXX.XXX_YY_Y_YYY-ZZ-ZZ.log  just after deployment. Is it possible to attach it here?

Best regards.

Not UEFI.  Entire drive.

<?xml version="1.0" encoding="UTF-8" ?>
<log uuid="A2978CFF-8454-F08D-155B-4F501162157A" product="Acronis Snap Deploy 5 Agent" version="5.0" build="1656" >
    <event id="1" level="2" module="51" code="0" time="1456249583" message="Resolve the machine by name '192.168.35.1:0'." />
    <event id="2" level="5" module="51" code="0" time="1456249583" message="Failed to resolve the machine." />
    <event id="3" level="2" module="51" code="0" time="1456249585" message="Resolve the machine by name '192.168.35.1:0'." />
    <event id="4" level="5" module="51" code="0" time="1456249585" message="Failed to resolve the machine." />
    <event id="5" level="2" module="51" code="0" time="1456249587" message="Resolve the machine by name '192.168.35.1:0'." />
    <event id="6" level="5" module="51" code="0" time="1456249587" message="Failed to resolve the machine." />
    <event id="7" level="2" module="51" code="0" time="1456249589" message="Resolve the machine by name '192.168.35.1:0'." />
    <event id="8" level="5" module="51" code="0" time="1456249589" message="Failed to resolve the machine." />
    <event id="9" level="2" module="51" code="0" time="1456249591" message="Resolve the machine by name '192.168.35.1:0'." />
    <event id="10" level="5" module="51" code="0" time="1456249591" message="Failed to resolve the machine." />
    <event id="11" level="2" module="51" code="0" time="1456249593" message="Resolve the machine by name '192.168.35.1:0'." />
    <event id="12" level="5" module="51" code="0" time="1456249593" message="Failed to resolve the machine." />
    <event id="13" level="2" module="51" code="0" time="1456249595" message="Resolve the machine by name '192.168.35.1:0'." />
    <event id="14" level="5" module="51" code="0" time="1456249595" message="Failed to resolve the machine." />
    <event id="15" level="2" module="51" code="0" time="1456249597" message="Resolve the machine by name '192.168.35.1:0'." />
    <event id="16" level="2" module="100" code="2" time="1456249598" message="Acronis Snap Deploy for PC - Deployment License successfully acquired from '192.168.35.1'." line_tag="0x876D9AA543F78CF4">
        <field name="$module" type="TIdentifier">
            osd_demon_glx_1656
        </field>
    </event>
    <event id="17" level="2" module="51" code="3342371" time="1456249598" message="Preparing to clean up disk Disk number: 1 is started." />
    <event id="18" level="2" module="51" code="0" time="1456249599" message="Cleanup operation for disk Disk number: 1 has been initialized." />
    <event id="19" level="2" module="1" code="506" time="1456249599" message="Locking partition E:..." />
    <event id="20" level="2" module="1" code="506" time="1456249599" message="Locking partition C:..." />
    <event id="21" level="2" module="51" code="0" time="1456249599" message="Cleanup operation for disk Disk number: 1 has been saved." />
    <event id="22" level="2" module="51" code="3342372" time="1456249599" message="Preparing to clean up disk {0} completed." />
    <event id="23" level="2" module="1" code="504" time="1456249599" message="Pending operation 49 started: 'Clearing disk (Hard disk 1)'." />
    <event id="24" level="2" module="51" code="0" time="1456249599" message="Disk Disk number: 1 is opened as a target." />
    <event id="25" level="2" module="51" code="0" time="1456249599" message="Server 192.168.35.1:49,261 is opened as a source." />
    <event id="26" level="2" module="51" code="0" time="1456249599" message="Disk tcp://7478733512 is opened as a source." />
    <event id="27" level="2" module="51" code="0" time="1456249599" message="Have initialized partition:&lt;endl/>&lt;indent value=4>Start - 2048, Size - 292864, Resize enabled - true" />
    <event id="28" level="2" module="51" code="0" time="1456249599" message="Have initialized partition:&lt;endl/>&lt;indent value=4>Start - 294912, Size - 351356928, Resize enabled - true" />
    <event id="29" level="2" module="51" code="42" time="1456249764" message="MBR has been deployed on disk 1 (signature 'FE3875A')." line_tag="0xE3394061D0E3A566">
        <field name="$module" type="TIdentifier">
            osd_demon_glx_1656
        </field>
    </event>
    <event id="30" level="2" module="29" code="0" time="1456249764" message="Bootability fix operation has started." />
    <event id="31" level="2" module="29" code="0" time="1456249764" message="Bootability fix operation has finished." />
</log>

According to the log, resize for the 100MB partition was enabled:

<event id="27" level="2" module="51" code="0" time="1456249599" message="Have initialized partition:&lt;endl/>&lt;indent value=4>Start - 2048, Size - 292864, Resize enabled - true" />

The target partition was extended to about 143MB.

You can disable resize in the template settings:

1. Start editing the deployment template;

2. Open the deployment template settings;

3. Select the Disk space utilization item;

4. Select the "As in the Master image" option;

5. Save the deployment template.

Note: If the target disk is bigger than the source one, there will be unallocated space on the target disk after deployment. And you will need to extand the volume C: manually.

Hi, thanks for your reply.

The language is pretty specific in the "disk space utitilization" dialog box, stating only the last volume is expanded during the resizing.  The behavior is different, the system reserved volume is resized, not just the last volume.  We've used SnapDeploy with Windows 7 for four years without this being a problem, the last volume was always expanded correctly and the others were untouched.  Since upgrading SnapDeploy it's become a problem.

Having to resize volumes after the fact is a waste of time and we'll switch to another product if that's the real answer.

Thanks 

Unfortunately I could not reproduce the issue on the latest build. 100 MB partition was not expanded after deployment.

1. Could you clarify what version of Snap Deploy was used to create the master image?

2. How many partitions does the master image have?

3. How many partitions was selected to deploy?

Best regards.