RE: Disabling access to an Exchange 5.5 server programmatically

This is not a good idea. -Original Message- From: Stewart Jump [mailto:[EMAIL PROTECTED]] Sent: Monday, December 10, 2001 10:51 AM To: Exchange Discussions Subject: RE: Disabling access to an Exchange 5.5 server programmatically A trick we use is to put an MTA limit of a few K below

RE: Disabling access to an Exchange 5.5 server programmatically

access to an Exchange 5.5 server programmatically Thanks for the suggestion. It's an effective method for disabling user access to the Exchange server, but (a) it isn't practical if you don't have IT staff at the site (b) it isn't quick if you have to shut down large numbers of servers and (c

RE: Disabling access to an Exchange 5.5 server programmatically

A trick we use is to put an MTA limit of a few K below the size of the virus. This doesn't work to well for users on the same store but if you have a large number of servers it limits a fair bit of the damage and leaves the users with some email functionality. This can be scripted with VBscript

RE: Disabling access to an Exchange 5.5 server programmatically

why dont you just write a script to shut down all the exchange services? JJ -Original Message- From: Stewart Jump [mailto:[EMAIL PROTECTED]] Sent: Monday, December 10, 2001 3:51 PM To: Exchange Discussions Subject: RE: Disabling access to an Exchange 5.5 server programmatically

RE: Disabling access to an Exchange 5.5 server programmatically

Anyway, the Ed's method is the easiest Unpluging the box takes 2 seconds. Rgds Peter -Original Message- From: Ed Crowley [mailto:[EMAIL PROTECTED]] Sent: Monday, December 10, 2001 6:42 AM To: Exchange Discussions Subject: RE: Disabling access to an Exchange 5.5 server

RE: Disabling access to an Exchange 5.5 server programmatically

Thanks for the suggestion. It's an effective method for disabling user access to the Exchange server, but (a) it isn't practical if you don't have IT staff at the site (b) it isn't quick if you have to shut down large numbers of servers and (c) it isn't helpful when you want to work on the server

RE: Disabling access to an Exchange 5.5 server programmatically

Not sure what suggestion you are referring to... -Original Message- From: Michael Brandon [mailto:[EMAIL PROTECTED]] Sent: Monday, December 10, 2001 5:10 PM To: Exchange Discussions Subject: RE: Disabling access to an Exchange 5.5 server programmatically Thanks

Re: Disabling access to an Exchange 5.5 server programmatically

: RE: Disabling access to an Exchange 5.5 server programmatically Thanks for the suggestion. It's an effective method for disabling user access to the Exchange server, but (a) it isn't practical if you don't have IT staff at the site (b) it isn't quick if you have to shut down large numbers

RE: Disabling access to an Exchange 5.5 server programmatically

- From: Michael Brandon [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 11, 2001 7:10 AM To: Exchange Discussions Subject: RE: Disabling access to an Exchange 5.5 server programmatically Thanks for the suggestion. It's an effective method for disabling user access to the Exchange server

RE: Disabling access to an Exchange 5.5 server programmatically

Unplug the server from the network. ©2000 Ed Crowley MCSE+Internet MVP kcCC+I® Protecting the world from PSTs and Bricked Backups!™ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Michael Brandon Sent: Sunday, December 09, 2001 5:22 PM To: Exchange

Re: Disabling access to an Exchange 5.5 server programmatically

There is a KB article that gives a registry switch to restrict access to the server. This could yield a batch file that roughly looks like: stop all services run regedit to import that .reg file for disabling restart all services And, of course, access could be given back just as easily by doing