Microsoft RichCopy is a freely available utility written by Microsoft Programmer Ken Tamaru. It is designed to copy large numbers of files over the network. It is optimized for loftier operation and supports many useful features such as Graphical User Interface and control-line interface, extended file and directory include and exclude filtering, FTP access, retain timestamp, remove files from destination that practise not exist at source, verify, retry and resume failed copies, and much more.
A common scenario that begs the use of RichCopy is to replicate images, personality packages, software packages, etc. for use with Deployment Solution 6.x. Deployment Solution 6.ten does non have whatever congenital-in mechanism for file replication, so RichCopy fits very nicely hither. For this article, I volition show how to replicate these files in conjunction with Deployment Solution 6.x, but you can utilise the process to replicate any files to any servers. It is best to have the same share name on all servers, including the Deployment Server. Y'all may name this share anything you like, but we will refer to it having the proper noun "Deployment".
On all servers, including Deployment Server, decide a location with gratuitous space to hold all your images, personality packages, software packages, etc. with plenty of room to grow. Create a directory named "Deployment" and share this directory every bit "Deployment". One time you have done this, yous will need to motility these files into the Deployment share of your Deployment Server.
Now, you lot need to replicate these files to your other servers. Since Deployment Server does non automatically replicate files between servers, you lot will need to manage this replication yourself using Microsoft RichCopy.
On all of the servers you lot want to replicate the Deployment share to, download and install Microsoft RichCopy. You can find it at http://technet.microsoft.com/en-us/magazine/2009.04.utilityspotlight.aspx.
Subsequently you have installed it, you volition need to determine the command-line parameters you lot will be using.
- Open up the RichCopy Graphical User Interface.
- Enable advanced options by clicking the View Menu, then selecting Advanced.
- Side by side click the Pick button.
- In the "Overview" page, enable all of the options you want for the copy. I recommend the following:
Supervene upon DSSERVER with the proper noun of your Deployment Server.
b. Default Destination Path: D:\Deployment
Enter the local path to your Deployment Share here.
c. Purge
Enabling this pick will delete any file from the destination directory that does not exist in the source directory. This makes cleanup of unused files much easier, you will only demand to delete the file from the source server and the deletion will be replicated down when the scheduled replication occurs.
d. Verify (Optional)
If you don't mind the replication taking longer, enable the Verify selection to ensure that the information files preserve their integrity.
e. Ignore READ-Just flag
Enabling this option will allow read-only files to be overwritten.
f. Copy if Availability in Destination: Not exist
Enabling this option will copy files that exist in the source that practise not exist in the destination.
grand. Copy if File size is: Unlike
Enabling this choice volition copy files where the size of the source file is unlike than the size of the destination file.
h. Copy if Fourth dimension stamp is: Updated
Enabling this option will re-create files where the time postage stamp of the source file is newer than the time stamp of the destination file.
i. Engagement/Time type: Last write
Enabling this option will base the fourth dimension postage comparing on the last write time. - In the "File attributes, Error Handling" page, specify the attributes and security information you want to copy. I recommend the following:
Enabling this choice volition fix the file attributes of the destination file to match the file attributes of the source file.
b. Fourth dimension stamp
Enabling this selection will set the time stamps of the destination file to match the time stamps of the source file.
c. Descretionary Access Control List
Enabling this option will set the Descretionary Access Control Listing of the destination file to match the Descretionary Access Control Listing of the source file.
d. Grouping
Enabling this option volition set up the security group information of the destination file to match the security grouping information of the source file.
e. Owner
Enabling this selection volition prepare the owner user account of the destination file to match the possessor user account of the source file.
f. System Access Control List
Enabling this pick will ready the System Access Control Listing of the destination file to lucifer the System Access Control Listing of the source file. - Go to the "Others" page, select the Control line parameters, and copy them to the clipboard. We will employ these afterwards. You lot might want to salvage them in a text file.
- If you want to save these settings to a file for reference later, Click OK, become to the File carte du jour, choose Save Every bit, give the file a proper name, and click Save.
- Close RichCopy.
Now that you lot accept the command-line arguments that you lot need, you can prepare a scheduled task to perform the replication. On all of the servers yous want to replicate the Deployment share to, open up the Control Panel, open up Scheduled Tasks, and create a new Scheduled Job with the following settings:
- Give information technology whatsoever proper noun you want, such equally "Replicate Deployment Share"
- Use an account that has read/write NTFS and Share permissions to the Deployment share on the Deployment Server and local server.
- Run whether user is logged on or non.
Make certain the password is stored with the job and so information technology can admission network resources. - For the program to run, choose "C:\Plan Files\Microsoft Rich Tools\RichCopy 4.0\RichCopy.exe" on a 32-chip server or "C:\Plan Files (x86)\Microsoft Rich Tools\RichCopy 4.0\RichCopy64.exe" on a 64-chip server.
- Add the control-line parameters that you copied to the clipboard earlier.
- Schedule the job to run once a solar day or multiple times per day. Since RichCopy only replicates files that take changed, at that place is less risk of scheduling multiple times per day because most of the time the schedule kicks off, no files will be copied and occasionally one or two will.
Now, all yous demand to exercise is manually run the replication command the showtime time or wait for the schedule to kicking off. Then, your servers volition all maintain a copy of the Deployment share from your Deployment Server.
DOWNLOAD HERE
Posted by: ramosthicat.blogspot.com
Post a Comment