Break it down babe;
secedit /configure - Allows you to configure the current system settings using security settings stored in a database - /db (our DB path) /cfg (for the Security template that would imported into the Database) /overwrite /quiet
xcopy - Pretty self explanatory - In this case, copying probably ADMX Group Policy files to Group Policy folder (if you had a Domain Controller, your Group Policy files would be in your SYSVOL\Domain\Policies folder)
Now the REG ADD command is missing an actual value to change or add. Maybe the screenshot is omitting the details. However, the key mentioned, all I could find is:
> Please know that WinTrust is a name (and DLL) of Microsoft Trust verification services, which provide a common API for determining whether a specific subject can be trusted.
> Trust verification services are implemented by trust providers. There is a built-in trust provider: Software Publishing. The Software Publishing trust provider allows a calling application to determine whether a software component contains digital signatures that identify it as being authentic software released by a publisher that is trusted on the local user’s system.
> Software Publishing trust provider uses registry key (on per user basis) to specify trust policy flags. The policy flags are defined as enumeration of WintrustGetRegPolicyFlags (you can see details here: http://msdn.microsoft.com/en-us/library/aa388197).
There is another REG ADD entry that seems to be specific to the software related to Dominion Voting Systems but that's nothing suspicious really.
And then of course restarting the SQL Server related Services.
Not real smoking guns.
Check out robocopy, do an initial copy, then set it up to auto run every X min. It works both locally and across the local network.
Make sure to read all of the options, it's very powerful, but will take some twerking to work just right.
I would suggest not using drag and drop for very large file transfers on Windows. It will take longer than using something like robocopy or xcopy (both CLI, command prompt, commands).
Since you are copying the plots, you can still farm them until the copy is finished (you may run into "looking up" times >5 seconds). Once the copy is finished, remove the old plot folders from the Chia client and add the new ones. Once you verify everything is working (run a plot check), then you delete the original plots you copied from.
Read the docs for xcopy, and use the appropriate flags for noninteractive copying?
> You can suppress this message by using the /i command-line option, which causes xcopy to assume that the destination is a directory if the source is more than one file or a directory.
> /y Suppresses prompting to confirm that you want to overwrite an existing destination file.
Here is a full example that might help: On the D drive I have a folder at the root called "Italy". Under that root folder are a 3 jpg files and a sub-directory called sub. In the sub directory there are 3 files
D:\italy\
1.jpg
2.jpg
3.jpg
D:\italy\sub\
4.jpg
5.jpg
6.jpg
​
If I create a C:\testitaly directory using the command:
mkdir C:\testitaly
Then if I run:
xcopy D:\italy C:\testitaly /C /E
I get:
D:\italy\1.jpg
D:\italy\2.jpg
D:\italy\3.jpg
D:\italy\sub\4.jpg
D:\italy\sub\5.jpg
D:\italy\sub\6.jpg
6 File(s) copied
You can read what the C and E options means here:
https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/xcopy
Found a solution that works for me. I used the following command:
xcopy "C:\Documents and Settings" "J:\Documents and Settings" /c /v /s /f /r /h /n
This is not applicable for this issue, but in the case it helps someone else, if you're wanting to copy a file from one place in your network to another, you could use the xcopy command tool using the /z parameter
https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/xcopy
You can write your own scripts using robocopy or rsync. You can also look at commercial backup software that does incremental backups - Macrium Reflect, Veeam, etc.
Heck, even XCOPY supports only copying files that are newer than destination.
Robocopy doesn’t need a /d switch. It doesn’t blindly copy files, it looks at the destination while it’s doing it. If a file already exists in the destination and it’s identical to the source file it skips it.
Robocopy is a lot like rsync. It’s used for synchronizing folders.
https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/robocopy
https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/xcopy
Try changing your xcopy command to this.
cmd /c xcopy C:\*.csv %DeployRoot%\StaffDevices /qcivy
https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/xcopy for information on the switches chosen.
For troubleshooting, you may want to remove the c from the list of switches, as that may mask issues you are encountering. You could also put a delay in the task sequence and then the command manually to verify what you need exactly.
If robocopy is not part of the OS you are using, Xcopy has similar options.
https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/xcopy
Try
xcopy a: b: /s /l /r > logfile.txt
Robocopy has been included with every OS since Vista. https://en.wikipedia.org/wiki/Robocopy?wprov=sfla1
Thanks for your reply. This sounds like it definitely could be the right answer. Unfortunately I can't check, as I needed a quick fix yesterday, so I copied the entire folder structure (rooted at SFZ) using xcopy in powershell (with /s
and /e
options iirc), then deleted the original and renamed the new. I then checked file renaming in explorer & powershell and it was working.
According to the xcopy docs, "By default, xcopy does not copy hidden or system files" and By default, xcopy removes the read-only attribute.". So this would explain why my xcopy quick fix worked if it did not copy desktop.ini to the new location.
If it happens again, I will definitely look for desktop.ini and ready-only attributes. The folders were created by extracting from zip files to various locations, so I might try and replicate the problem too.
https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/xcopy
Definitely this. No need to install any software or the entire Linux subsystem.
Create a simple backup_minecraft.txt file add the xcopy command as per docs below
Microsoft help: https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/xcopy
Rename the file so that the extension is .cmd instead of .txt.
Then open Task Scheduler and create a task with a recurring trigger that runs the .cmd file.
PM if you need any help.
If you are on windows you can just do this.
Assume drive C is your normal drive and G is the one backup one (just picking random letters)
In the prompt type
xcopy C:\ G:\ /s/r/e/v/z/c/i/d
Press enter
This will copy all the new and updated files to the backup drive, and ignore the ones that haven't changed
Here is the xcopy reference for understanding what all those switches do.
I use teracopy all the time for everyday file manipulation but for huge amounts of data I prefer xcopy.
nothing wrong with teracopy just sharing an alternative option
https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/xcopy
I sometimes use xcopy with hickeryd parameters instead of restarting.
2 times, the second shows anything not copied or use a "/l"
https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/xcopy
Write a batch file that copies all new files in a direcory to a backup location then run the batch file as a scheduled windows task every 30 mins or so.
You probably will want to look up the command line switches for xcopy. https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/xcopy
Look into xcopy
.
You can first use xcopy /t /e ...
to copy the directory structure (without copying files) if your converter software doesn't automatically make new folders.
Then cd ...
into the original folder, you can use xcopy /s /l ...
to generate a list of files to convert relative to the original folder.
Finally, cd
back to the upper level and run the file converter on the list of input file names preceded by the original folder name; while using the input file names preceded by the new folder name as output. Since the previous step gives you relative path, preceding with different top level folders maintains the entire hierarchy in that folder.
References: