**DONOTDELETE** (Lurker) 2002-04-29 08:57 PM	replication script
	Does anyone have a replication script? I currently have 4 win2k ad servers and 15 nt 4 BDC's in my domain and would like to be able to automatically replicate the login scripts to the BDC's from the win2k domain controllers?? Thanks
Rocco Capra (Hey THIS is FUN) 2002-04-29 09:42 PM	Re: replication script
	Since our company doesn't use "Replication", I have a Bat file I use to copy my login script out to our BDC's and the PDC, everytime I make a change to the login script. You can use a Kix file to do the same. You only have to copy the files then when you make changes. If you want it to be automatted just use Task Scheduler to run the copy bat file whenever you want it to. Rocco [ 29 April 2002, 21:43: Message edited by: Rocco Capra ]
Kdyer (KiX Supporter) 2002-04-30 04:21 AM	Re: replication script
	hedge01, ROBOCOPY from the Resource Kit is your Friend.. Good stuff when used with an SMTP Mailer so that you can see the results. HTH, - Kent
Les (KiX Master) 2002-04-30 04:40 AM	Re: replication script
	I've always been happy with the REPL service. No need for an emailer 'cause it just keeps on working.
ash wilson (kyosei) (Getting the hang of it) 2002-04-30 11:36 AM	Re: replication script
	AGREE strongly with Les. Replication exports CHANGES only. This means it ADDS new files, OVER-WRITES changed files and REMOVES deleted files. Script/batch copying over-writes everything and means more network traffic. Replication is the way to go, set it and forget it! No problems, no worries.
Rocco Capra (Hey THIS is FUN) 2002-04-30 02:47 PM	Re: replication script
	kyosei, Yeah, I know the batch method stinks, but since the "server" team has thier heads up, you know where, and can't get repl to work, it is the best I can do for now. Rocco
MCA (KiX Supporter) 2002-05-20 05:20 PM	Re: replication script
	Dear, We are using also a BATch procedure for distribution our scripts to different servers. We use following rules: - create on all servers same username with same password and with enough rights to make file changes. same username/password to prevent entering username with password in BATch procedures. - only main script/procedure (which doesn't need be changed daily) will be put in both REPL directories (import/export) and the other scripts/ procedures will be changed on a fixed drive mapping for all users. - don't move complete REPL directories to prevent problems with f.e. SAM file. Also we make those files read-only and hidden, which isn't a problem for kix32. Just by calling kix32 with complete paths it will work as expected. The advantage of using BATch procedure. You doesn't need to wait for replication. Also to prevent unwanted files in REPL directories we only put the managing task by one person. greetings.