VMware Converter fails on physical client - not enough space

Hello

I try to use VMware Converter on a physical client that runs Windows 7 and get this error message:

Failed: The VSS snapshots cannot be stored because there is not enough space on the source volumes or because the source computer has not all NTFS volumes. Error code:
2147754783 (0x8004231F).

When you run DISKPART - VOLUME LIST I can see that the two partitions is formatted with NTFS.

Anyone have any idea why the process fails?

Thanks in advance.

-Edgar

In addition, found this with a search... you all unallocated on your hard drives partitions?

http://community.Spiceworks.com/topic/254411-VSS-error-when-trying-to-P2V-server-using-VMware-Converter

Tags: VMware

Similar Questions

  • VMware Converter failed % 2: ERROR: could not open the file %s

    I'm trying to convet system winnt in esx, always fail in the setp2. I tired to convet locally and remotely and get the same error message. Help, please

    10:32 step 1: connecting to Agent VMware Converter on 172.19.129.10

    10:32 step 2: creation of target virtual machine and the conversion of the data

    10:32:05 configuring settings for the virtual machine target...

    10:32:07 creating virtual machine target...

    10:33:04 ERROR: could not open the file %s

    The newspaper has been attached

    This is the result of that port TCP 443 is blocked?

    Nope

    More likely, the system of the source (172.19.129.10) cannot reach the host ESX by DNS or TCP Port 902 is stuck between them.

    HA - nfc: / /------Corcus [storage2] / [email protected]:902

    Kind regards

    EvilOne

    VMware vExpert 2009

    NOTE: If your question or problem has been resolved, please mark this thread as answered and awarded points accordingly.

  • Time Machine backup fails because "there is not enough space on the «DiskStation «»

    My backups regular TimeMachine to DiskStation stopped working a few months ago.  I thought it was because I ran out of space but now I installed an extra 1 TB RAID and I always get this error message.

    Here is the chronology of events that led to the error message.

    16/01/10 23:09 - Backup started manually (1.47 TB TB 2.45 available):

    16/01/10 23:11 - preparation of backup... (1.47 TB TB 2.45 available)

    16/01/10 23:15 - "backup: zero KB of 63.8 MB, calculating time remaining..." »

    16/01/10 23:22-2.1 MB saved 63.8 and the first estimate of the remaining time: 'about 4 hrs.

    16/01/10 23:50 - now 2.3 63.8 MB MB, 16 hours left (I'm ready for bed).

    16/01/10 23:55-5 minutes later and it backed up 419 MB!

    16/01/11 00:55 - an hour later and it is up to 6.72 GB but the gas target increased to 7.39 GB (I went to bed)

    16/01/11 06:50 - next day morning and it's up to 23,76 GB and the goal is now to 26.13 GB

    16/01/11 18:49 - I go home at night and it failed.

    Here is the view viewfinder of the TimeMachine file that I am trying to backup (note, a lot of disk space):

    This is the view of the Inspector of it:

    System details:

    -MacBook Pro 2013 with OS X 10.11.2

    -LAN WiFi Pace 2Wire998 router with DiskStation connected by Ethernet, MacBook Pro by WiFi

    -Synology DiskStation DS411slim with 4 x 2.5 "hard drives installed.

    A device third-party network attached storage (NAS) or a router is unsuitable for use with Time Machine, especially if it's your only backup. I know that's not what you want to hear. I know that Time Machine accepts the device as a backup destination. I know that the manufacturer says the device will work with Time Machine, and I also know that it usually seems to work. Except when you are trying to restore and find that you can't.

    Apple has published a specification for network devices that works with Time Machine. No third party provider, AFAIK, does meet this specification. They all use the application of Netatalk incomplete, obsolete Apple Filing Protocol.

    Apple does not endorse any device third-party network for use with Time Machine. See this support article.

    Network backup, use as destination an Apple Time Capsule or an external storage device connected to another Mac or a 802.11ac AirPort base station. Only 802.11ac base stations support time Machine, not older model.

    Otherwise, use Time Machine at all. There are other ways to save, although none of them are nowhere near as effective or as well integrated with OS X. I don't have a specific recommendation.

    If you are determined to continue to use the device with Time Machine, your only remedy for any resulting problem is the manufacturer (who will blame Apple, neither you nor anyone else but herself.)

  • 702 Installer fails with not enough space in / tmp

    Trying to install coldfusion702 on solaris. Fails to complain about not enough space in / tmp (I got 10 GB). Tried to download the file again (assuming that possible corruption). Tried to place somewhere else in the tmp setting IATEMPDIR var. Nothing seems to help.

    Hope that someone has encountered something like this and can offer a solution. Maybe I'm missing something or a package. In the result below, ' expr: non-numeric argument ' caught my attention - I have the feeling that the script fails to the analysis of output of the df command.

    Thank you
    Henry
    -command line output-
    ./ColdFusion-702-sol.bin
    Preparing to install...
    WARNING: / tmp has insufficient disk space!
    Attempt to use/export/home/username for install base and tmp dir.
    expr: non-numeric argument

    CAVEAT! The amount of disk/tmp space required to perform the
    This facility is superior to what is available. Please
    release at least 0 kilobyte in / tmp and try this
    Setup again. You can also set the environment IATEMPDIR
    variable to a directory on a partition to free enough disk
    disk space. To set the variable enter one of the following
    commands at the prompt of UNIX before running this command line
    Once again the installer:

    Just in case where someone else encounters this problem, here is the solution, my colleague helped me to understand.

    install the script analysis through the output of the command df to calculate the space in / tmp or any other temporary location for the installation files. If you have a large amount of space allocated to the/tmp (on solaris, it would be 5 GB or more) the output will look like this:
    / tmp (swap): 19773408 blocks 400226 files
    Note that there is no space between: and the size, the installation script is looking for the 4th field, which is in this case the word 'blocks' which is obviously false.

    To work around it, we have created a temporary script with filename "df" which replaces the df command:
    #! / bin/sh
    / usr/sbin/DF | tr ":" " "
    and the PATH has changed to have this temporary location of script at the beginning. This allowed the installer to run as it simply replaces: with space.

  • Cannot convert Server 2008 R2 Machine get error: Instant The VSS cannot be stored, because there is not enough space on the source volumes or because the source computer does not all NTFS volumes. Error code: 2147754783 (0x8004231F).

    I have a couple of server 08 R2 machines where the P to V conversion fails.  I did some research and the problem seems to be related to the system reserved Partition that has 0% available 100 MB free space.  Conversion fails with the error below.

    VSS snapshots cannot be stored because there is not enough space on the source volumes or because the source computer has not all NTFS volumes. Error code:
    2147754783 (0x8004231F).


    Someone had this problem and came to the top with a solution or to get around?


    Thanks in advance

    Guessed it.  My snapshots Appassure did not also exist with a similar error, so that's what I did to solve it.  My servers now converted without any problem.

    1. Open disk management.
    2. Look at the partition of the PRS and see if it is 100% full.
      • If Yes, proceed to step 3.
      • If this is not the case, check if there are readers who have no more of 300 MB free (minimum requirement to use VSS).
    3. Click a drive, select properties and then select the instant snapshots tab.
    4. Ensure that all shadow copies are disabled and no limit on all players.
    5. Go to the partition of the SRP and assign the B:drive letter.
    6. Open the B: drive via disk management, and then locate the folder System Volume Information. Note: if necessary, change the folder options so that you can view hidden files, folders and drives.
    7. Right-click the System Volume Information folder, and then select Properties.
    8. On the Security tab, click Edit, and then add the group with full control everyone in the folder.
    9. Open the System Volume Information folder (you should see log files are full), open a running as an administrator command prompt and then type the following commands to unload the filter driver.
      • B:
      • B:\>FLTMC UNLOAD AAFSFLT
    10. Navigate to the System Volume Information folder, and then type the following commands:
      • B:\>CD System Volume Information
      • B:\System Volume Information > AALOG_ DEL * (this will remove all of the log files, and then re-create a new)
      • B:\System Volume Information > CD\
      • B:\>FLTMC LOAD AAFSFLT
    11. Close the command prompt window.
    12. In Windows, right click on the reserve system folder and remove the Group everyone.
    13. In Disk Manager, remove the B: drive (and click Yes when prompted with a warning window).
  • B2496824 Player 7.1 + Win 10 (split volume) error: not enough space on the disk

    Hello!

    I have the following configuration:

    Host: Windows 7 x 64 professional

    Host: Samsung 840 EVO 240 GB SSD with 48 GB of free

    Comments: Overview of Windows 10

    Comments: 60 GB VMDK, spread across 30 x 2 GB vmdk, which are NOT previously affected

    Description of the problem:

    I do upgrade from Windows in the Win10 system, and then at one point I had a warning of VMware Player, which is not accessible VMDK #009

    It's the NEWSPAPER, which States that vmdk #009 running out of space... which is very strange, considdering that I have 40 GB free in the guest OS and 48 GB free in the HOME... and the VMDK is an expansion of volume

    2015 04-15 T 10: 47:20.827 + 02:00 | VMX | I120: MsgQuestion: msg.vmxaiomgr.retrycontabort.rudeunplug response = 2

    2015 04-15 T 10: 47:20.827 + 02:00 | VMX | I120: DISKLIB-LIB: RWv failed ioId: #46815 (13) (13).

    2015 04-15 T 10: 47:20.827 + 02:00 | VMX | I120: DISK: drive e/s on scsi0:0 failed: there is not enough space on the file system for the selected operation (13)

    2015 04-15 T 10: 47:20.827 + 02:00 | VMX | I120: # dumping contents of iov #.

    2015 04-15 T 10: 47:20.827 + 02:00 | VMX | I120: WRITE

    2015 04-15 T 10: 47:20.827 + 02:00 | VMX | I120: startSector = 37601304

    2015 04-15 T 10: 47:20.827 + 02:00 | VMX | I120: numSectors = 8

    2015 04-15 T 10: 47:20.827 + 02:00 | VMX | I120: numBytes = 4096

    2015 04-15 T 10: 47:20.827 + 02:00 | VMX | I120: numEntries = 1

    2015 04-15 T 10: 47:20.827 + 02:00 | VMX | I120: entries [0] = F53A8000 / 4096

    2015 04-15 T 10: 47:20.841 + 02:00 | VMX | I120: VMXAIOMGR: retry on write ' C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10 - s009.vmdk ': there is not enough space on the disk.

    2015 04-15 T 10: 47:20.841 + 02:00 | VMX | I120: VMXAIOMGR: System: err = 700002 errCode = 112 freeSpace = 51699863552

    2015 04-15 T 10: 47:20.841 + 02:00 | VMX | I120: VMXAIOMGR: ' C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10 - s009.vmdk ': writing s = 825058708480 n = 4096 = 1 IAF = 0

    2015 04-15 T 10: 47:20.841 + 02:00 | VMX | I120: VMXAIOMGR: v [0] = F53A9000:4096

    2015 04-15 T 10: 47:20.844 + 02:00 | VMX | I120: VMXAIOMGR: retry on write ' C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10 - s009.vmdk ': there is not enough space on the disk.

    2015 04-15 T 10: 47:20.844 + 02:00 | VMX | I120: VMXAIOMGR: System: err = 700002 errCode = 112 freeSpace = 51699863552

    2015 04-15 T 10: 47:20.844 + 02:00 | VMX | I120: VMXAIOMGR: ' C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10 - s009.vmdk ': writing s = 825058708480 n = 4096 = 1 IAF = 0

    2015 04-15 T 10: 47:20.845 + 02:00 | VMX | I120: VMXAIOMGR: v [0] = F53A9000:4096

    2015 04-15 T 10: 47:20.846 + 02:00 | VMX | I120: VMXAIOMGR: retry on write ' C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10 - s009.vmdk ': there is not enough space on the disk.

    2015 04-15 T 10: 47:20.846 + 02:00 | VMX | I120: VMXAIOMGR: System: err = 700002 errCode = 112 freeSpace = 51699863552

    2015 04-15 T 10: 47:20.846 + 02:00 | VMX | I120: VMXAIOMGR: ' C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10 - s009.vmdk ': writing s = 825058708480 n = 4096 = 1 IAF = 0

    2015 04-15 T 10: 47:20.846 + 02:00 | VMX | I120: VMXAIOMGR: v [0] = F53A9000:4096

    2015 04-15 T 10: 47:20.848 + 02:00 | VMX | I120: VMXAIOMGR: retry on write ' C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10 - s009.vmdk ': there is not enough space on the disk.

    2015 04-15 T 10: 47:20.848 + 02:00 | VMX | I120: VMXAIOMGR: System: err = 700002 errCode = 112 freeSpace = 51699863552

    2015 04-15 T 10: 47:20.848 + 02:00 | VMX | I120: VMXAIOMGR: ' C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10 - s009.vmdk ': writing s = 825058708480 n = 4096 = 1 IAF = 0

    2015 04-15 T 10: 47:20.848 + 02:00 | VMX | I120: VMXAIOMGR: v [0] = F53A9000:4096

    2015 04-15 T 10: 47:20.850 + 02:00 | VMX | I120: VMXAIOMGR: retry on write ' C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10 - s009.vmdk ': there is not enough space on the disk.

    2015 04-15 T 10: 47:20.850 + 02:00 | VMX | I120: VMXAIOMGR: System: err = 700002 errCode = 112 freeSpace = 51699863552

    2015 04-15 T 10: 47:20.850 + 02:00 | VMX | I120: VMXAIOMGR: ' C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10 - s009.vmdk ': writing s = 825058708480 n = 4096 = 1 IAF = 0

    2015 04-15 T 10: 47:20.850 + 02:00 | VMX | I120: VMXAIOMGR: v [0] = F53A9000:4096

    2015 04-15 T 10: 47:20.851 + 02:00 | VMX | I120: VMXAIOMGR: retry on write ' C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10 - s009.vmdk ': there is not enough space on the disk.

    2015 04-15 T 10: 47:20.851 + 02:00 | VMX | I120: VMXAIOMGR: System: err = 700002 errCode = 112 freeSpace = 51699863552

    2015 04-15 T 10: 47:20.851 + 02:00 | VMX | I120: VMXAIOMGR: ' C:\Users\mkirk\Documents\Virtual Machines\Windows 10\Windows 10 - s009.vmdk ': writing s = 825058708480 n = 4096 = 1 IAF = 0

    2015 04-15 T 10: 47:20.851 + 02:00 | VMX | I120: VMXAIOMGR: v [0] = F53A9000:4096

    After copying VMDK #009 in a new file

    and after running the tool of restoration Performance of Samsung,

    Windows 10 VM is now back in business!

  • Not enough space on the data store

    I created a VM w2k8 server. I have attached a second virtual drive to it in the vsphere client determined I gave him too much space. I went back in the vshere client and click on delete. Now, when I go to add a second drive with the right amount of space I want t use I get error not enough space on the data store. I noticed that the old file vdmk still exist but do not know how to proceed. It is a 5 ESX environment and the data store is on the SAN. Space on the windows server is listed as unallocated.

    Hello and welcome to the community of VMware. Well I would like to browse the data store and make sure that there are no vmdk files sitting here that, if the other wise not to be there. Have a go at this and feedback your conclusions.

    Best wishes.

  • Not enough space on the data store.  Newb help please.

    I have a running ESXi 4.1.0 2 Windows VMs server.  Everything worked very well, but I had to turn off all of the server and physically move.  When I powered it back, only on virtual machines with the power on at the same time.  The other dies with the error above.  I have very little experience with VMware and I'd appreciate any help.  Thank you.

    Welcome to the community - the reason why you can't turn on your VM is because a vmkernel swap file is created when you turn on the virtual machine, and if there is not enough space, then, you will receive this error - you'll need clean the directories where are installed the virtual machines - you'll need to remove all of the log files If there are snapshots commit those and then you should be able to powere on virtual machines

  • HP Jet x 360: not enough space for the full Windows 10 upgrade

    Just got a HP x 360 for my granddaughter stream.  Indicates its eligible for the upgrade of Windows 10.  When I try to install it through the process, but before it ends and the error comes up saying not enough space. I have to add memory and if so, how.

    Monkey,

    The computer may be running out of physical space required for migration instead of memory needed to actually to crunch the numbers and run the migration program.

    The migration process uses more than 10 GB of space on your computer.

    Please take a look on the following document, including the important notes section.

    Specifications for Windows 10

    Excerpt:

    • Latest OS:

      Make sure you run the latest version of Windows 7 SP1 or Windows Update 8.1.

      Don't know what version you use? Click here to find out. Need to download the latest version? Click here for Windows 7 SP1 or Windows Update 8.1.

    • Processor:

      1 gigahertz (GHz) processor or more fast or SoC

    • RAM:

      1 gigabyte (GB) for 32-bit or 2 GB for 64-bit

    • Hard disk space:

      16 GB for 32-bit OS 20 GB for 64-bit operating system

    • Graphics card:

      DirectX 9 or later version with WDDM 1.0 driver

    • Display:

      800 x 600

  • IOException: error = 12, not enough space when the duplication of external process

    Hi all

    I've encountered the question as:

    java.io.IOException: cannot run program "/ usr/local/bin/sudo ': error = 12, not enough space
    at java.lang.ProcessBuilder.start(ProcessBuilder.java:460)
    at java.lang.Runtime.exec(Runtime.java:593)
    at java.lang.Runtime.exec(Runtime.java:466)
    ...
    Caused by: java.io.IOException: error = 12, not enough space
    at java.lang.UNIXProcess.forkAndExec (Native Method)
    to java.lang.UNIXProcess. < init > (UNIXProcess.java:53)
    at java.lang.ProcessImpl.start(ProcessImpl.java:65)
    at java.lang.ProcessBuilder.start(ProcessBuilder.java:453)

    When I tried to call an external script by Runtime.exec. I checked the physical memory and swap, two of them were more than 2 GB at the point where the exception was thrown. The same exception was thrown by the other processes external duplication of wire...

    Everyone please throw me some lights on this issue? I have seen no exception OutOfMemoryError either from my application.

    Thank you and best regards.

    You're out of swap space. Nothing to do with local memory, heap, OutOfMemoryErrors, etc.

  • Not enough space within the CC Installer error.

    Hello

    (1) purchased annual presentation of creative cloud

    (2) downloaded, installed the creative cloud

    (3) failed to install Acrobat Pro XI, it shows that there is not enough space

    (4) installation directory modified in the settings

    (5) I tried "repeat."

    (6) shows the same error

    (7) exit the program Creative Cloud

    8) launched again with admin rights, tempted to "repeat" installation

    (9) problem remains.

    Live Adobe support is not an answer.

    Phone support is 39 USD / incident (nice!).

    Thanks in advance for your help.

    Alex.

    Receipt of answer, but what they could help to was:

    (1) it is recommended to install all the Adobe products on the C drive (where the operating system is installed)

    According to your questions:

    (1) on my RAM disk only 270 MB of free space (I have 6 drives well and lots of space on others)

    (2) change the installation with the settings menu directory did not help a

    Solution:

    As I used the symbolic links to install Adobe Reader on RAM disk (if not impossible) to push (900% +) my daily productivity, I have to

    (A) uninstall all adobe products

    (B) remove all symbolic links to these

    (C) Manage fresh install again.

    Thanks for trying to help.

    Alex.

  • vSphere Host Update Utility - ERROR: not enough space on the boot partition

    I get the following error when I run the host update utility

    ERROR: Not enough space on the boot partition

    The boot partition doesn't have enough space to store initrd.img.

    Expected free space (MB): 50, found: 44

    I can free until you reach the required amount?

    Send the output of this command:

    DF h

    And the version of ESX 3.x

    See also this KB (there are a few tips on where space can be lost):

    http://KB.VMware.com/kb/1016511

    André

  • ORA-273xx OS OS system error message: not enough space in CAR 11.0.1.7

    Hello world

    We have Oracle RAC on HP - UX 11.32 with two knots after a while that one of the nodes had shot and you cannot issue an order until the server is restarted.


    Here is a log of messages in the queue alerts.

    ERRORS
    =======
    Process m00D died, see the trace file
    Boot process failed, error of the battery:
    Errors in the /u01/app/oracle/diag/rdbms/ecmprd/ECMPRD2/trace/ECMPRD2_psp0_9389.trc file:
    ORA-27300: OS dependent operating system: fork failed with status: 12
    ORA-27301: OS Error Message: not enough space
    ORA-27302: an error occurred at: skgpspawn3
    M007 died the process, see the trace file



    Trace file
    ============
    2011-01-18 15:03:19.980
    Boot process failed, error of the battery:
    ORA-27300: OS dependent operating system: fork failed with status: 12
    ORA-27301: OS Error Message: not enough space
    ORA-27302: an error occurred at: skgpspawn3

    2011-01-18 15:13:20.135
    Boot process failed, error of the battery:
    ORA-27300: OS dependent operating system: fork failed with status: 11
    ORA-27301: OS Error Message: Resource temporarily unavailable
    ORA-27302: an error occurred at: skgpspawn5



    I think it's the limitation or problem of operating system kernel. no luck that we stuck with bad engineer as we took a week, but no action until now I try now he climbs, we open bu SR.

    Anyway any idea that will really help

    DB v 11.1.0.7


    Thank you

    Hello

    See the TechNote MOS:

    * Troubleshooting error ORA-27300 ORA-27301 ORA-27302 [579365.1 ID] *.

    Thank you
    A H E E R X

  • Time Machine-not enough space error

    Hi all

    I had to unplug my computer and move it to another room and now after all hang up, I get this message "not enough space for full backup". There are about 150 GB to 2 TB disk space as it is filled with iTunes and Time machine backups.

    I guess it's because ever since I hooked everything back up Time Machine think it is made the first backup of everything rather than pick up where he left off when he made the last backup?

    Please tell me that I shouldn't let it save it for the first time again. It took an eternity to accomplish this last time as the computer kept going to sleep.

    Thanks for any help,

    Al

    Start with 18 in the 1st article linked.

    Troubleshooting of Time Machine

    Solving the problems of Time Machine

  • Bad burn on Blu - Ray; not enough space?

    Hi all

    I bought a blu ray burner =:

    http://www.bhphotovideo.com/c/product/1051647-reg/samsung_se_506cb_rswd_sam_slim _exterior_blue_ray.html

    Create the disk opens its doors to about 66% asks me to insert a disc. The project is only about 3 minutes. long.

    Then, at some point, I get the error message; "Not enough space on the startup disk.

    Once the error was; not enough space on the disk, but it's a Virgin blu - ray disc. (BD - R)

    There is plenty of space on the hard drive of my iMac.

    The burner did not come with software to Mac but I chose the burner in the FCX share window.

    Other: When I right click on a movie on the desktop file I see an option for burning, but where can I say it blu - ray?

    Thank you

    Al

    Is the library of the PCF on your startup disk and where the media is stored?

    If you burn a movie from a file in the Finder, it is a data disk and will not readable on a Blu Ray player.

    Russ

Maybe you are looking for

  • Win7 64 bit & Tecra A6 - only 2.99 GB RAM is shown as usable

    Right, I have installed Windows 7 64 bit on my Tecra A6 and most seem OK. I have a request and here I have 4 GB memory installed and Windows indicates 4 GB in system properties. However, it's showing only 2.99 GB as usable.I thought that the 64-bit v

  • FPGA: DC - RMS measurement vi

    Hello experts! Can someone tell me how the "DC - RMS Measurements.vi"? Specifaclly, I would like to know if it returns an average commute or work on blocks of data, as an average lets say more than 1000 samples and only returning a single value/1000s

  • How constantly sample meter signal for quadrature linear encoder

    Hi all Trying to permanently change value of Schneeberger linear encoder quadrature at certain frequency as 10 Hz of the sample and the output to the text file. Everything I choose in the external clock that I can't run the DAQ assistant. No one know

  • Microsoft know that there is a virus Removal Tool MS

    original title; is soft micro aware there is a ms removal tool virus "while on my pc, it was taken on what was obvisuly a false" virus tool withdrawal soft micro. My question is miro soft to aware of this and so until they make about it? This virus g

  • Robocopy XP has no commands to copy files.

    I discovered and use Robocopy to maintain (horodateurs) dates on my files.  I have many gigabytes of data on multiple hard drives.  When I use Win7 I use the "/ DCOPY:T" option to Robocopy to enable this.  Everything works fine under Win7.  There are