Thank you for the explanation! That is one reason I hadn't seen before, that's for sure.
Did you get a chance to look at the link that Marcus sent and decide if that would do what you want or not? Or do you need something different? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Burkes, Jeremy [Contractor] Sent: Friday, March 04, 2005 6:52 AM To: [email protected] Subject: RE: [ActiveDir] OT: VBScript Question The issues that I am referring to are security violations which are instances where someone as violated the proper handling of data. The Navy, Department of Defense requires that we defrag the exchange information store. Moving user mailboxes is not an option. The reason I am creating this script is I have been all the departments in separate information stores. I am hoping that when one of these violations occur I can just dismount that departments store, defrag, then mount again. This will allow me to keep every other department up and running. Currently we stop all Exchange services, defrag the one store, then start the Exchange services effectively bringing everyone on that server down. Jeremy ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mulnick, Al Sent: Thursday, March 03, 2005 10:11 PM To: [email protected] Subject: RE: [ActiveDir] OT: VBScript Question Figured the Navy was still part of the government :) I asked the question because the only time I would *ever* want to defrag a db in Exchange 200x is because I was forced to. Otherwise, I would prefer to move the user mailstores to an alternate db on the same server instead. It would be a) safer and b) faster and c) just generally a better idea than defragging a db in place and taking those kinds of chances. It's not like 5.5 when you had only one store instance. You can move the user mail stores around almost at will (as long as they're not logged on of course) and clients don't even have to update at this point. They'll get the new (be default defragged) db, and you'll have made the problem that drove you there go away. I'm interested in "issues" that would cause you to want to defrag as I just plain don't understand at this point and hate to offer advice without full understanding of the possible ramifications and issues that may be present. I think Marcus posted some useful coding techniques that should help you recapture the command line information. From there you should be able to push it to a log file, which I think is what you were after in the first place (vs. piping it from the command line to the text file). Al ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Burkes, Jeremy [Contractor] Sent: Thursday, March 03, 2005 6:53 PM To: [email protected] Subject: RE: [ActiveDir] OT: VBScript Question I work for the government and we have to run offline defrags after hours for issues that arise. In the past we just had a batch file that stopped all exchange services on a machine and then ran the offline defrag then restarted the services. We want to streamline the process. Jeremy ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mulnick, Al Sent: Thursday, March 03, 2005 5:51 PM To: [email protected] Subject: RE: [ActiveDir] OT: VBScript Question Before getting to a better idea to automate, I have to ask is this something to automate? What drives you to want to automate the off-line defragmentation in Exchange 2000 and what makes you want to do that in the first place? Al ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Burkes, Jeremy [Contractor] Sent: Thursday, March 03, 2005 5:43 PM To: [email protected] Subject: [ActiveDir] OT: VBScript Question Everyone, I am creating a VB script that is dismounting, defraging, then mounting exchange information stores on an exchange server. My script is complete but I want to improve it. The problem I am having is that I build a command line to run eseutil and call it using WshShell Object Run Method which is appended to a file using the >> sign(s) with the bWaitOnReturn set to True (see link for more info). Unfortunately, this causes my script to wait as it should but I have no idea what is going on since the log file is not written to until eseutil completes its pass. So the commandline just sits there while my script and eseutil run in the background. Is there anyway to output to both the command line and the output file the progress of eseutil? Better ideas for providing more information on the script running to the user? TIA. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/script56/ht ml/wsmthrun.asp <http://msdn.microsoft.com/library/default.asp?url=/library/en-us/script56/h tml/wsmthrun.asp> Jeremy ----------------------------------------------------- Jeremy Burkes Strategic Systems Program MIS Department [EMAIL PROTECTED] PH: 202-764-1270 "All that is necessary for the forces of evil to win in the world is for enough good men to do nothing." - Edmund Burke "It is not how many times you get knocked down, it is how many times you get back up." - Vince Lombardi List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
