Tag Info

New answers tagged


So for this you can harken back to your DOS days (if you had them) and utilize the 8.3 naming convention, which gets around the invalid NTFS security descriptors that aren't there. Steps to remove the invalid new destination folders: Open a command prompt with admin rights to the root folder where these new folders are listed. Use the command DIR /X to ...


You probably need to execute the following command: robocopy /copyall /e /zb However, the lack of versioning is a very serious drawback of such a method. While it is not necessarily wrong, please think twice on your current environment and use it only and only if it really make sense.


Robocopy can copy the files, folders, permissions, etc. but not the Share information. You'll need to export the Shares from the registry on the source server and import them into the registry on the destination server.


Try using WinSCP in mirror mode. WinSCP can be downloaded from here: http://winscp.net/eng/download.php Using WinSCP you won't need to map a drive, it just connects to FTP directly and does the work for you.


If it's an AD account, then by "network hiccup" I would mean that windows is having trouble looking up the account, which sometimes happens when there's a connectivity issue. It might also be that your account doesn't have the privileges to look up a domain account (being a local account, perhaps?). However, my Adobe Flash Player Updater on my ...


It's a SID, or Security Identifier. If it's showing the string rather than a "friendly name," it sounds like the new server doesn't recognize the account.


/copy:t should copy just the timestamps. Keep in mind, however, that if they are very small files that copying just the timestamps may take longer than copying the entire file. robocopy c:\src c:\dest /copy:T robocopy /help says /COPY:copyflag[s] :: what to COPY for files (default is /COPY:DAT). (copyflags : D=Data, A=Attributes, ...

Top 50 recent answers are included