RE: Exchange fail-over
If you have the budget...and redundancy is an issue...and you don't want your domain to know you had a server failure...then I'd recommend E2k7 CCR. The change over from Active to Passive takes about 2 minutes...users don't notice it...and it is automatic if the two CCR servers loose the heart beat. Downside: you have to have a minimum of 3 64 bit servers...two CCR servers and one server to fulfill the Hub role... For full redundancy across the board... 2 Hub servers, and 2 CCR servers. We are also using two Edge servers on a DMZ. From: Sam Cayze [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 10:10 PM To: MS-Exchange Admin Issues Subject: RE: Exchange fail-over SCR looks good, but do you really want to be doing stuff in command line when the boss is standing over you wondering when email is going to be back on line? Yes, then he will realize how important my job is and that he could't do it himself :) From: Clayton Doige [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 9:31 AM To: MS-Exchange Admin Issues Subject: Re: Exchange fail-over I have not tried 2007 SCR as yet, but have read a lot on it. SCR looks good, but do you really want to be doing stuff in command line when the boss is standing over you wondering when email is going to be back on line? The thing is, if you go to 2007 then you need to pitch your servers for 64 bit, and get the appropriate OS as well. If you are just wanting to get your existing data to an existing standby box, then Double Take is the way to go. The software will configure your target server so that all of the appropriate services are set to manual and stopped. When you failover it will update AD, and add the SPN for the source server to the target server, plus make any required changes in DNS. Users only have to restart Outlook if they were signed in at the time of the failover. And it can be controlled with one mouse click as opposed to having to type correctly when the poo hits the fan. On 18/03/2008, Michael B. Smith [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: DoubleTake (as someone else mentioned) and NeverFail are the typical recommended solutions. MessageOne is a typical 3rd party provider providing message continuity. However, I would recommend you upgrade to Exchange 2007 and use LCR or SCR; which are built into the product. If you really actually want to do active/passive Exchange clustering, search on technet.microsoft.comhttp://technet.microsoft.com/ for SCC - Single Copy Clustering. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.comhttp://theessentialexchange.com/ From: Bill Lambert [mailto:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 18, 2008 10:00 AM To: MS-Exchange Admin Issues Subject: Exchange fail-over Hello all... I want to have a stand-by Exchange box that can act as a fail-over in the event I lose my active Exchange server. I understand that this can be accomplished by clustering. Google has a zillion links about Windows/Exchange clustering so I was hoping the experts here could recommend a link where it would be a good place to start learning how to do this. Any help/advice would be greatly appreciated. Environment is W2K3 Servers and Exchange 2003, clients are a mixture of O2K3 and O2K7...all fully patched. Bill Lambert Windows System Administrator Concuity A healthcare division of Trintech, Inc. Phone 847-941-9206 Fax 847-465-9147 [cid:image001.gif@01C8899B.44396F10] NASDAQ: TTPA The information contained in this e-mail message, including any attached files, is intended only for the personal and confidential use of the recipient(s) named above. If you are not the intended recipient (or authorized to receive information for the recipient) you are hereby notified that you have received this communication in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all copies of this message. Thank you. -- Regards, Clayton [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] http://alsipius.com ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~inline: image001.gif
Exchange Management Shell killed the CDO star
Currently where I work we are using Exchange 2003. I have written some VB code that uses CDO and CDOEXM to create mailboxes for new users. Another process creates new accounts in active directory, and my code goes through all the accounts, sees what department they are in, goes to a lookup table to figure out if the department they are in gets mailboxes on our servers (some departments have their own servers so we leave them alone). Now I go to the Microsoft Upgrading skills from Exchange 2003 to 2007 class and I am introduced to the horror of the exchange management shell. I want to keep using CDO!!! But from what I was told, CDO will not work fully with Exchange 2007, especially since the RUS is gone. CDO, from my little experience with it so far, isn't a robust language to program with. It's more of a scripting system. Am I the only one who isn't happy with the management shell? ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange Management Shell killed the CDO star
Is it really the EMS you aren't happy with, or the CDO support in E2k7? What you are describing doesn't seem like it should be that hard to do via the EMS. From: Boggis, Josh [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 9:08 AM To: MS-Exchange Admin Issues Subject: Exchange Management Shell killed the CDO star Currently where I work we are using Exchange 2003. I have written some VB code that uses CDO and CDOEXM to create mailboxes for new users. Another process creates new accounts in active directory, and my code goes through all the accounts, sees what department they are in, goes to a lookup table to figure out if the department they are in gets mailboxes on our servers (some departments have their own servers so we leave them alone). Now I go to the Microsoft Upgrading skills from Exchange 2003 to 2007 class and I am introduced to the horror of the exchange management shell. I want to keep using CDO!!! But from what I was told, CDO will not work fully with Exchange 2007, especially since the RUS is gone. CDO, from my little experience with it so far, isn't a robust language to program with. It's more of a scripting system. Am I the only one who isn't happy with the management shell? ** Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange Management Shell killed the CDO star
Perhaps I just having learned enough about EMS, any guidance on where to get good information on it? From: Campbell, Rob [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 10:42 AM To: MS-Exchange Admin Issues Subject: RE: Exchange Management Shell killed the CDO star Is it really the EMS you aren't happy with, or the CDO support in E2k7? What you are describing doesn't seem like it should be that hard to do via the EMS. From: Boggis, Josh [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 9:08 AM To: MS-Exchange Admin Issues Subject: Exchange Management Shell killed the CDO star Currently where I work we are using Exchange 2003. I have written some VB code that uses CDO and CDOEXM to create mailboxes for new users. Another process creates new accounts in active directory, and my code goes through all the accounts, sees what department they are in, goes to a lookup table to figure out if the department they are in gets mailboxes on our servers (some departments have their own servers so we leave them alone). Now I go to the Microsoft Upgrading skills from Exchange 2003 to 2007 class and I am introduced to the horror of the exchange management shell. I want to keep using CDO!!! But from what I was told, CDO will not work fully with Exchange 2007, especially since the RUS is gone. CDO, from my little experience with it so far, isn't a robust language to program with. It's more of a scripting system. Am I the only one who isn't happy with the management shell? ** Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
E2k7 migration question
Hi all - We're getting ready to add our first E2k7 server I had a question - in one of our two Exchange routing groups. we have a server that's in a seperate AD Site - it's a server for 150 mailboxes in a different state. We haven't decided if we're going to leave the AD site and put a 64 bit box down there, or bring the mailboxes onto servers that are here in our main AD site. Do we need to decide before we bring the 1st E2k7 server onboard? i.e. can we test a few of the out of state mailboxes on the E2k7 server to see if performance is tolerable before we make the final decision? Another 'quick' question - how 'tolerant' of Suppress Link State Routing are Ex2k3 servers - do we need to hurry the retirement of E2k3, or can they deal with Link State being gone as long as there's an E2k7 server around to make routing decisions? Thanks all. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Re: IMAP
Well, that's good to know. However figuring out that it has to be 'something' and then forgetting it a few months later when the owner of the crappy app claims Exchange isn't working again is something we wish to help people avoid :) It's nice having this setup to prove it's not an Exchange problem from the command line of the application server. :) In front of his manager who then has to eat crow for the rather nasty words he just said. Steven Peck On Tue, Mar 18, 2008 at 4:03 PM, Michael B. Smith [EMAIL PROTECTED] wrote: Sidebar: It doesn't have to be a ?. IMAP requires that you provide an identifier so that a specific input and the specific output relative to that input can be identified. That is because IMAP allows you to pre-feed commands and not wait on their responses. For example: A001 LOGON A002 COMMANDA A003 COMMANDB wait-a-while *A003 result for COMMANDB *A001 LOGONG SUCCESSFUL .. .. .. You get the idea. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com -Original Message- From: Steven Peck [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 6:55 PM To: MS-Exchange Admin Issues Subject: Re: IMAP cmdline and technet http://support.microsoft.com/kb/189326/en-us An _important_ note... In steps 2 and later, that question mark '?', that's not for show. You _have_ to type it in. You _have_ to add a space after it. It's very irritating... ? LOGIN NTDOMAIN/NTACCOUNT/ALIAS PASSWORD Domain: corp NtAccount: john Alias: jdoe Password: something ? LOGIN corp/john/jdoe something This will tell you if IMAP is working at all. Steven Peck On Tue, Mar 18, 2008 at 3:07 PM, David Lum [EMAIL PROTECTED] wrote: My apologize for not being knowledgeable here, but I was told we need to enable IMAP so some app could use it. We are testing using Outlook Express and get the following message: I just tried an got the following error: No connection could be made because the target machine actively refused it. My first thought is that the IP address is not being allowed to talk to the Exchange server, but checking access permissions the IP's of the clients are allowed - we're trying to connect from the same LAN as the Exchange box. Where should I look next? Dave Lum - Systems Engineer [EMAIL PROTECTED] - (971)-222-1025 When you step on the brakes your life is in your foot's hands ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange Management Shell killed the CDO star
Have you taken any general Powershell courses or read books on it? From: Boggis, Josh [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 9:56 AM To: MS-Exchange Admin Issues Subject: RE: Exchange Management Shell killed the CDO star Perhaps I just having learned enough about EMS, any guidance on where to get good information on it? From: Campbell, Rob [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 10:42 AM To: MS-Exchange Admin Issues Subject: RE: Exchange Management Shell killed the CDO star Is it really the EMS you aren't happy with, or the CDO support in E2k7? What you are describing doesn't seem like it should be that hard to do via the EMS. From: Boggis, Josh [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 9:08 AM To: MS-Exchange Admin Issues Subject: Exchange Management Shell killed the CDO star Currently where I work we are using Exchange 2003. I have written some VB code that uses CDO and CDOEXM to create mailboxes for new users. Another process creates new accounts in active directory, and my code goes through all the accounts, sees what department they are in, goes to a lookup table to figure out if the department they are in gets mailboxes on our servers (some departments have their own servers so we leave them alone). Now I go to the Microsoft Upgrading skills from Exchange 2003 to 2007 class and I am introduced to the horror of the exchange management shell. I want to keep using CDO!!! But from what I was told, CDO will not work fully with Exchange 2007, especially since the RUS is gone. CDO, from my little experience with it so far, isn't a robust language to program with. It's more of a scripting system. Am I the only one who isn't happy with the management shell? ** Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** ** Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Printing List of Exchange 2003 Accounts
I need to generate a printed list of all of my users who have Exchange accounts. Is there an easy way to do this? John Hornbuckle MIS Department Taylor County School District 318 North Clark Street Perry, FL 32347 www.taylor.k12.fl.us ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Re: Printing List of Exchange 2003 Accounts
Do you want username, Display Name, email address? There are a few different approaches to doing this. One method is to point at the Exchange servers and run a script http://www.blkmtn.org/powershell-list-exchange2k3-mb-info Though there have been other methods posted on this list that point at AD with an LDAP filter instead. Steven Peck On Wed, Mar 19, 2008 at 9:27 AM, John Hornbuckle [EMAIL PROTECTED] wrote: I need to generate a printed list of all of my users who have Exchange accounts. Is there an easy way to do this? John Hornbuckle MIS Department Taylor County School District 318 North Clark Street Perry, FL 32347 www.taylor.k12.fl.us ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Exchange 2003 setup
How do I determine an Exchange setup? I am setting up a backup exchange server and I know my current Exchange server has files on C: E: and L:. I have those drives on my backup server but I am unsure of when or how to point the different parts of exchange to make it match the production exchange server. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Printing List of Exchange 2003 Accounts
You can pull the mailbox list off of the servers via WMI. That will include the mailbox display name as one of the properties. -Original Message- From: Steven Peck [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 11:38 AM To: MS-Exchange Admin Issues Subject: Re: Printing List of Exchange 2003 Accounts Do you want username, Display Name, email address? There are a few different approaches to doing this. One method is to point at the Exchange servers and run a script http://www.blkmtn.org/powershell-list-exchange2k3-mb-info Though there have been other methods posted on this list that point at AD with an LDAP filter instead. Steven Peck On Wed, Mar 19, 2008 at 9:27 AM, John Hornbuckle [EMAIL PROTECTED] wrote: I need to generate a printed list of all of my users who have Exchange accounts. Is there an easy way to do this? John Hornbuckle MIS Department Taylor County School District 318 North Clark Street Perry, FL 32347 www.taylor.k12.fl.us ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ** Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Re: Printing List of Exchange 2003 Accounts
You can also use the ADFind tool to return this info. On 3/19/08, Campbell, Rob [EMAIL PROTECTED] wrote: You can pull the mailbox list off of the servers via WMI. That will include the mailbox display name as one of the properties. -Original Message- From: Steven Peck [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 11:38 AM To: MS-Exchange Admin Issues Subject: Re: Printing List of Exchange 2003 Accounts Do you want username, Display Name, email address? There are a few different approaches to doing this. One method is to point at the Exchange servers and run a script http://www.blkmtn.org/powershell-list-exchange2k3-mb-info Though there have been other methods posted on this list that point at AD with an LDAP filter instead. Steven Peck On Wed, Mar 19, 2008 at 9:27 AM, John Hornbuckle [EMAIL PROTECTED] wrote: I need to generate a printed list of all of my users who have Exchange accounts. Is there an easy way to do this? John Hornbuckle MIS Department Taylor County School District 318 North Clark Street Perry, FL 32347 www.taylor.k12.fl.us ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ** Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
E2k03 to E2k07 upgrade question
We have a pretty basic Exchange 2003 environment that contains two servers. A small server holds OWA and Exchange wireless Activesync roles. The big server holds the mailbox server role, and also SMTP virtual server, etc. We're preparing for the Exchange 2k07 upgrade and we've taken the MS class for the upgrade so we're pretty familiar with the process, however, I have a few questions: 1. What would be the best way to start the project? My thought is to simply install Exchange 2007 on the new hardware, add it to the current email organization and start moving mailboxes. The new environment will also hold two servers-a CAS server, and then a mailbox server that will hold the other Exchange roles. We won't have an Edge Transport at first...we have an email gateway set up already on a SPAM device that will host this role at first. 2. I guess I'm just confused on what to do first. Also, at what point we need to configure the new SMTP routing roles. I'd prefer to bring the new Exchange into the environment gradually, and first move mailboxes to the server, and slowly migrate the roles out of the old environment. 3. I'm also a little confused as to when you can safely remove the old environment...I assume once all rolls have been moved to E2k07, you simply uninstall E2k03 out of the environment? I have the MS Exchange upgrade class manual, so I can easily do some refresher reading, but I just thought I'd run our upgrade scenario by a few colleagues to get some feedback. Thanks, MM ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: E2k03 to E2k07 upgrade question
I'd start by getting the Hub Transport bits sorted out first. From: Matthew McComas [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 11:51 AM To: MS-Exchange Admin Issues Subject: E2k03 to E2k07 upgrade question We have a pretty basic Exchange 2003 environment that contains two servers. A small server holds OWA and Exchange wireless Activesync roles. The big server holds the mailbox server role, and also SMTP virtual server, etc. We're preparing for the Exchange 2k07 upgrade and we've taken the MS class for the upgrade so we're pretty familiar with the process, however, I have a few questions: 1. What would be the best way to start the project? My thought is to simply install Exchange 2007 on the new hardware, add it to the current email organization and start moving mailboxes. The new environment will also hold two servers-a CAS server, and then a mailbox server that will hold the other Exchange roles. We won't have an Edge Transport at first...we have an email gateway set up already on a SPAM device that will host this role at first. 2. I guess I'm just confused on what to do first. Also, at what point we need to configure the new SMTP routing roles. I'd prefer to bring the new Exchange into the environment gradually, and first move mailboxes to the server, and slowly migrate the roles out of the old environment. 3. I'm also a little confused as to when you can safely remove the old environment...I assume once all rolls have been moved to E2k07, you simply uninstall E2k03 out of the environment? I have the MS Exchange upgrade class manual, so I can easily do some refresher reading, but I just thought I'd run our upgrade scenario by a few colleagues to get some feedback. Thanks, MM ** Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: E2k03 to E2k07 upgrade question
I agree. Slowly migrating the roles out of the old org was my plan but 2007 had a different plan. As soon as there is a Hub in the org the other servers will automagically start routing through it (at least that is what happened here). So do that first and save doing all the setup and dns issues twice. So I would go Hub then CAS then Mailbox. From: Campbell, Rob [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 1:08 PM To: MS-Exchange Admin Issues Subject: RE: E2k03 to E2k07 upgrade question I'd start by getting the Hub Transport bits sorted out first. From: Matthew McComas [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 11:51 AM To: MS-Exchange Admin Issues Subject: E2k03 to E2k07 upgrade question We have a pretty basic Exchange 2003 environment that contains two servers. A small server holds OWA and Exchange wireless Activesync roles. The big server holds the mailbox server role, and also SMTP virtual server, etc. We're preparing for the Exchange 2k07 upgrade and we've taken the MS class for the upgrade so we're pretty familiar with the process, however, I have a few questions: 1. What would be the best way to start the project? My thought is to simply install Exchange 2007 on the new hardware, add it to the current email organization and start moving mailboxes. The new environment will also hold two servers-a CAS server, and then a mailbox server that will hold the other Exchange roles. We won't have an Edge Transport at first...we have an email gateway set up already on a SPAM device that will host this role at first. 2. I guess I'm just confused on what to do first. Also, at what point we need to configure the new SMTP routing roles. I'd prefer to bring the new Exchange into the environment gradually, and first move mailboxes to the server, and slowly migrate the roles out of the old environment. 3. I'm also a little confused as to when you can safely remove the old environment...I assume once all rolls have been moved to E2k07, you simply uninstall E2k03 out of the environment? I have the MS Exchange upgrade class manual, so I can easily do some refresher reading, but I just thought I'd run our upgrade scenario by a few colleagues to get some feedback. Thanks, MM ** Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: E2k03 to E2k07 upgrade question
Of course MS says CAS first. And now that I think about that is what I did firstsort of. Our CAS and Hub are one in the same. http://technet.microsoft.com/en-us/library/aa997610(EXCHG.80).aspx From: Kennedy, Jim Sent: Wednesday, March 19, 2008 1:27 PM To: MS-Exchange Admin Issues Subject: RE: E2k03 to E2k07 upgrade question I agree. Slowly migrating the roles out of the old org was my plan but 2007 had a different plan. As soon as there is a Hub in the org the other servers will automagically start routing through it (at least that is what happened here). So do that first and save doing all the setup and dns issues twice. So I would go Hub then CAS then Mailbox. From: Campbell, Rob [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 1:08 PM To: MS-Exchange Admin Issues Subject: RE: E2k03 to E2k07 upgrade question I'd start by getting the Hub Transport bits sorted out first. From: Matthew McComas [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 11:51 AM To: MS-Exchange Admin Issues Subject: E2k03 to E2k07 upgrade question We have a pretty basic Exchange 2003 environment that contains two servers. A small server holds OWA and Exchange wireless Activesync roles. The big server holds the mailbox server role, and also SMTP virtual server, etc. We're preparing for the Exchange 2k07 upgrade and we've taken the MS class for the upgrade so we're pretty familiar with the process, however, I have a few questions: 1. What would be the best way to start the project? My thought is to simply install Exchange 2007 on the new hardware, add it to the current email organization and start moving mailboxes. The new environment will also hold two servers-a CAS server, and then a mailbox server that will hold the other Exchange roles. We won't have an Edge Transport at first...we have an email gateway set up already on a SPAM device that will host this role at first. 2. I guess I'm just confused on what to do first. Also, at what point we need to configure the new SMTP routing roles. I'd prefer to bring the new Exchange into the environment gradually, and first move mailboxes to the server, and slowly migrate the roles out of the old environment. 3. I'm also a little confused as to when you can safely remove the old environment...I assume once all rolls have been moved to E2k07, you simply uninstall E2k03 out of the environment? I have the MS Exchange upgrade class manual, so I can easily do some refresher reading, but I just thought I'd run our upgrade scenario by a few colleagues to get some feedback. Thanks, MM ** Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
PCphone Exch sp2 - now I have double contacts
Hello all - At a new client yesterday with SBS 2003 (non-R2) - and I installed Exchange Service Pack 2 (and a few other Windows Updates). Today all the PCphone clients report having double contacts listed in their mailbox. Can someone explain to me what might have happened here and if there was something I can do to avoid this next time? Joseph Danielsen, CSBS, MCSA-Messaging, MCP Network Blade Inc. 49 Marcy Street Somerset, NJ 08873 732-213-0600 ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: E2k7 migration question
Russ, You should be fine, we moved select users from our east coast exch 2000 server to the west coast 2007 server with no issues (albeit slow wan traffic). Good luck -troy From: Russ Patterson [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 7:56 AM To: MS-Exchange Admin Issues Subject: E2k7 migration question Hi all - We're getting ready to add our first E2k7 server I had a question - in one of our two Exchange routing groups. we have a server that's in a seperate AD Site - it's a server for 150 mailboxes in a different state. We haven't decided if we're going to leave the AD site and put a 64 bit box down there, or bring the mailboxes onto servers that are here in our main AD site. Do we need to decide before we bring the 1st E2k7 server onboard? i.e. can we test a few of the out of state mailboxes on the E2k7 server to see if performance is tolerable before we make the final decision? Another 'quick' question - how 'tolerant' of Suppress Link State Routing are Ex2k3 servers - do we need to hurry the retirement of E2k3, or can they deal with Link State being gone as long as there's an E2k7 server around to make routing decisions? Thanks all. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: E2k03 to E2k07 upgrade question
Matt, Microsoft has a LOT of documentation on this. Your first server should be the CAS box that will proxy owa/eas for pre2007 clients and completely replace the current OWA server. This install will prompt you for the bridgehead to connect to your current exchange which will be your mailbox server. In our case we also made the CAS box a HT (both our MB and CAS roles are HT) You can then add the 2007 mailbox servers and operate in tandem with no problems. Once all mailboxes are moved you should look up the procedure for removing your 2003 exchange server and follow the instructions. -troy From: Matthew McComas [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 9:51 AM To: MS-Exchange Admin Issues Subject: E2k03 to E2k07 upgrade question We have a pretty basic Exchange 2003 environment that contains two servers. A small server holds OWA and Exchange wireless Activesync roles. The big server holds the mailbox server role, and also SMTP virtual server, etc. We're preparing for the Exchange 2k07 upgrade and we've taken the MS class for the upgrade so we're pretty familiar with the process, however, I have a few questions: 1. What would be the best way to start the project? My thought is to simply install Exchange 2007 on the new hardware, add it to the current email organization and start moving mailboxes. The new environment will also hold two servers-a CAS server, and then a mailbox server that will hold the other Exchange roles. We won't have an Edge Transport at first...we have an email gateway set up already on a SPAM device that will host this role at first. 2. I guess I'm just confused on what to do first. Also, at what point we need to configure the new SMTP routing roles. I'd prefer to bring the new Exchange into the environment gradually, and first move mailboxes to the server, and slowly migrate the roles out of the old environment. 3. I'm also a little confused as to when you can safely remove the old environment...I assume once all rolls have been moved to E2k07, you simply uninstall E2k03 out of the environment? I have the MS Exchange upgrade class manual, so I can easily do some refresher reading, but I just thought I'd run our upgrade scenario by a few colleagues to get some feedback. Thanks, MM ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Exchange 2007 TLS Encryption
Can somebody tell me what port Exchange 2007 uses for TLS encryption to talk between two different domains??? Does it just use SMTP port 25 or something else? Thanks. Robert ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange 2007 TLS Encryption
I believe that unless you change the default, it should be port 25 regardless of whether it's using TLS or not. From: McCready, Robert [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 1:05 PM To: MS-Exchange Admin Issues Subject: Exchange 2007 TLS Encryption Can somebody tell me what port Exchange 2007 uses for TLS encryption to talk between two different domains??? Does it just use SMTP port 25 or something else? Thanks. Robert ** Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange 2007 TLS Encryption
Rob, It is solely port 25 for smtp communication between exchange 2007 servers in the same organization. When you say two domains do you mean in the same forest/exchange org? (of course all smtp email communication leaving your org for the internet will be 25) -troy From: McCready, Robert [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 11:05 AM To: MS-Exchange Admin Issues Subject: Exchange 2007 TLS Encryption Can somebody tell me what port Exchange 2007 uses for TLS encryption to talk between two different domains??? Does it just use SMTP port 25 or something else? Thanks. Robert ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange 2007 TLS Encryption
Sorry, I meant email leaving our organization destined for another company. I wasn't sure if we had TLS setup between our company and theirs, if any other port needed to be open other than 25? From: Troy Meyer [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 2:19 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 TLS Encryption Rob, It is solely port 25 for smtp communication between exchange 2007 servers in the same organization. When you say two domains do you mean in the same forest/exchange org? (of course all smtp email communication leaving your org for the internet will be 25) -troy From: McCready, Robert [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 11:05 AM To: MS-Exchange Admin Issues Subject: Exchange 2007 TLS Encryption Can somebody tell me what port Exchange 2007 uses for TLS encryption to talk between two different domains??? Does it just use SMTP port 25 or something else? Thanks. Robert ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange 2007 TLS Encryption
Check out the Data Path Security Reference at http://technet.microsoft.com/en-us/library/bb331973(EXCHG.80).aspx Chuck Robinson, MCSE: Messaging, VCP Senior Practice Consultant EMC Global Services, Microsoft Practice tel 732-321-3644 xt.45, mobile 973-865-0394, fax 732-321-6855 email: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] www.emc.com/mspracticehttp://www.emc.com/ From: McCready, Robert [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 2:05 PM To: MS-Exchange Admin Issues Subject: Exchange 2007 TLS Encryption Can somebody tell me what port Exchange 2007 uses for TLS encryption to talk between two different domains??? Does it just use SMTP port 25 or something else? Thanks. Robert ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange 2007 TLS Encryption
I've never needed to open any other ports on my firewall for TLS between smtp servers. From: McCready, Robert [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 1:26 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 TLS Encryption Sorry, I meant email leaving our organization destined for another company. I wasn't sure if we had TLS setup between our company and theirs, if any other port needed to be open other than 25? From: Troy Meyer [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 2:19 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 TLS Encryption Rob, It is solely port 25 for smtp communication between exchange 2007 servers in the same organization. When you say two domains do you mean in the same forest/exchange org? (of course all smtp email communication leaving your org for the internet will be 25) -troy From: McCready, Robert [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 11:05 AM To: MS-Exchange Admin Issues Subject: Exchange 2007 TLS Encryption Can somebody tell me what port Exchange 2007 uses for TLS encryption to talk between two different domains??? Does it just use SMTP port 25 or something else? Thanks. Robert ** Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange 2007 TLS Encryption
Thanks sirs! From: Robinson, Chuck [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 2:32 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2007 TLS Encryption Check out the Data Path Security Reference at http://technet.microsoft.com/en-us/library/bb331973(EXCHG.80).aspx Chuck Robinson, MCSE: Messaging, VCP Senior Practice Consultant EMC Global Services, Microsoft Practice tel 732-321-3644 xt.45, mobile 973-865-0394, fax 732-321-6855 email: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] www.emc.com/mspracticehttp://www.emc.com/ From: McCready, Robert [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 2:05 PM To: MS-Exchange Admin Issues Subject: Exchange 2007 TLS Encryption Can somebody tell me what port Exchange 2007 uses for TLS encryption to talk between two different domains??? Does it just use SMTP port 25 or something else? Thanks. Robert ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange 2003 setup
File locations: The executable and other miscellaneous Exchange application files are set during the initial Exchange installation. The tracking log files are set in the properties of the Exchange server The transaction logs and system path are set in the properties of the Storage Group The Database files are set in the properties of the database Thanks From: David W. McSpadden [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 12:43 PM To: MS-Exchange Admin Issues Subject: Exchange 2003 setup How do I determine an Exchange setup? I am setting up a backup exchange server and I know my current Exchange server has files on C: E: and L:. I have those drives on my backup server but I am unsure of when or how to point the different parts of exchange to make it match the production exchange server. This communication is confidential and may be legally privileged. If you are not the intended recipient, (i) please do not read or disclose to others, (ii) please notify the sender by reply mail, and (iii) please delete this communication from your system. Failure to follow this process may be unlawful. Thank you for your cooperation. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Printing List of Exchange 2003 Accounts
I'm sure I'm showing my ignorance when I say that this isn't enough info to point me in the right direction.. -Original Message- From: Campbell, Rob [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 12:43 PM To: MS-Exchange Admin Issues Subject: RE: Printing List of Exchange 2003 Accounts You can pull the mailbox list off of the servers via WMI. That will include the mailbox display name as one of the properties. -Original Message- From: Steven Peck [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 11:38 AM To: MS-Exchange Admin Issues Subject: Re: Printing List of Exchange 2003 Accounts Do you want username, Display Name, email address? There are a few different approaches to doing this. One method is to point at the Exchange servers and run a script http://www.blkmtn.org/powershell-list-exchange2k3-mb-info Though there have been other methods posted on this list that point at AD with an LDAP filter instead. Steven Peck On Wed, Mar 19, 2008 at 9:27 AM, John Hornbuckle [EMAIL PROTECTED] wrote: I need to generate a printed list of all of my users who have Exchange accounts. Is there an easy way to do this? John Hornbuckle MIS Department Taylor County School District 318 North Clark Street Perry, FL 32347 www.taylor.k12.fl.us ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ** Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: IMAP
Thanks all! My output is this: ? BAD Protocol Error: Unidentifiable command specified. It's like the port is open but that's it. IMAP4 is enabled in the Exchange account in question -Original Message- From: Steven Peck [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 3:55 PM To: MS-Exchange Admin Issues Subject: Re: IMAP cmdline and technet http://support.microsoft.com/kb/189326/en-us An _important_ note... In steps 2 and later, that question mark '?', that's not for show. You _have_ to type it in. You _have_ to add a space after it. It's very irritating... ? LOGIN NTDOMAIN/NTACCOUNT/ALIAS PASSWORD Domain: corp NtAccount: john Alias: jdoe Password: something ? LOGIN corp/john/jdoe something This will tell you if IMAP is working at all. Steven Peck On Tue, Mar 18, 2008 at 3:07 PM, David Lum [EMAIL PROTECTED] wrote: My apologize for not being knowledgeable here, but I was told we need to enable IMAP so some app could use it. We are testing using Outlook Express and get the following message: I just tried an got the following error: No connection could be made because the target machine actively refused it. My first thought is that the IP address is not being allowed to talk to the Exchange server, but checking access permissions the IP's of the clients are allowed - we're trying to connect from the same LAN as the Exchange box. Where should I look next? Dave Lum - Systems Engineer [EMAIL PROTECTED] - (971)-222-1025 When you step on the brakes your life is in your foot's hands ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Re: Printing List of Exchange 2003 Accounts
I used ADFind to extract the following info from the user properties in AD: adFind -b dc=MyDomain,dc=local -f objectcategory=person -csv -nodn sAMAccountName givenName initials sn title mail physicalDeliveryofficeName employeeNumber departmentNumber streetAddress l st postalCode telephoneNumber mobile manager description UserInfo.csv or .txt You can download ADFind from Joeware and only use the attributes you need, which in this case may be Username, First Name, Middle, Last Name, and Email Address sAMAccountName givenName initials sn mail hth On 3/19/08, John Hornbuckle [EMAIL PROTECTED] wrote: I'm sure I'm showing my ignorance when I say that this isn't enough info to point me in the right direction.. -Original Message- From: Campbell, Rob [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 12:43 PM To: MS-Exchange Admin Issues Subject: RE: Printing List of Exchange 2003 Accounts You can pull the mailbox list off of the servers via WMI. That will include the mailbox display name as one of the properties. -Original Message- From: Steven Peck [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 11:38 AM To: MS-Exchange Admin Issues Subject: Re: Printing List of Exchange 2003 Accounts Do you want username, Display Name, email address? There are a few different approaches to doing this. One method is to point at the Exchange servers and run a script http://www.blkmtn.org/powershell-list-exchange2k3-mb-info Though there have been other methods posted on this list that point at AD with an LDAP filter instead. Steven Peck On Wed, Mar 19, 2008 at 9:27 AM, John Hornbuckle [EMAIL PROTECTED] wrote: I need to generate a printed list of all of my users who have Exchange accounts. Is there an easy way to do this? John Hornbuckle MIS Department Taylor County School District 318 North Clark Street Perry, FL 32347 www.taylor.k12.fl.us ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ** Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Re: Printing List of Exchange 2003 Accounts
If you just need basic information, use the query tool within ADUC. You can point and click which query you want to run. Once the results are displayed, you can use the View/Add-Remove Columns menu to modify what information is displayed. 1) Open ADUC 2) Right-click 'Saved Queries' 3) New Query 4) Give it a name 5) Click 'Define Query' 6) In the find drop down, select Users, Contacts and Groups or Exchange Recipients *I selected Exchange Recipients* 7) Select the appropriate options on the General Tab 8) Select the appropriate options on the Storage Tab 9) Use the Advanced Tab to further define your search criteria 10) Click OK. I know it's pretty basic and not as cool as using the command line tools, but it has worked countless times for me in the past :) - Sean On 3/19/08, MarvinC [EMAIL PROTECTED] wrote: I used ADFind to extract the following info from the user properties in AD: adFind -b dc=MyDomain,dc=local -f objectcategory=person -csv -nodn sAMAccountName givenName initials sn title mail physicalDeliveryofficeName employeeNumber departmentNumber streetAddress l st postalCode telephoneNumber mobile manager description UserInfo.csv or .txt You can download ADFind from Joeware and only use the attributes you need, which in this case may be Username, First Name, Middle, Last Name, and Email Address sAMAccountName givenName initials sn mail hth On 3/19/08, John Hornbuckle [EMAIL PROTECTED] wrote: I'm sure I'm showing my ignorance when I say that this isn't enough info to point me in the right direction.. -Original Message- From: Campbell, Rob [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 12:43 PM To: MS-Exchange Admin Issues Subject: RE: Printing List of Exchange 2003 Accounts You can pull the mailbox list off of the servers via WMI. That will include the mailbox display name as one of the properties. -Original Message- From: Steven Peck [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 11:38 AM To: MS-Exchange Admin Issues Subject: Re: Printing List of Exchange 2003 Accounts Do you want username, Display Name, email address? There are a few different approaches to doing this. One method is to point at the Exchange servers and run a script http://www.blkmtn.org/powershell-list-exchange2k3-mb-info Though there have been other methods posted on this list that point at AD with an LDAP filter instead. Steven Peck On Wed, Mar 19, 2008 at 9:27 AM, John Hornbuckle [EMAIL PROTECTED] wrote: I need to generate a printed list of all of my users who have Exchange accounts. Is there an easy way to do this? John Hornbuckle MIS Department Taylor County School District 318 North Clark Street Perry, FL 32347 www.taylor.k12.fl.us ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ** Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Re: Printing List of Exchange 2003 Accounts
I meant to add: Once you've created your query, you can right-click on it and select 'Export List' to a CSV, TXT, etc. - Sean On 3/19/08, Sean Martin [EMAIL PROTECTED] wrote: If you just need basic information, use the query tool within ADUC. You can point and click which query you want to run. Once the results are displayed, you can use the View/Add-Remove Columns menu to modify what information is displayed. 1) Open ADUC 2) Right-click 'Saved Queries' 3) New Query 4) Give it a name 5) Click 'Define Query' 6) In the find drop down, select Users, Contacts and Groups or Exchange Recipients *I selected Exchange Recipients* 7) Select the appropriate options on the General Tab 8) Select the appropriate options on the Storage Tab 9) Use the Advanced Tab to further define your search criteria 10) Click OK. I know it's pretty basic and not as cool as using the command line tools, but it has worked countless times for me in the past :) - Sean On 3/19/08, MarvinC [EMAIL PROTECTED] wrote: I used ADFind to extract the following info from the user properties in AD: adFind -b dc=MyDomain,dc=local -f objectcategory=person -csv -nodn sAMAccountName givenName initials sn title mail physicalDeliveryofficeName employeeNumber departmentNumber streetAddress l st postalCode telephoneNumber mobile manager description UserInfo.csv or .txt You can download ADFind from Joeware and only use the attributes you need, which in this case may be Username, First Name, Middle, Last Name, and Email Address sAMAccountName givenName initials sn mail hth On 3/19/08, John Hornbuckle [EMAIL PROTECTED] wrote: I'm sure I'm showing my ignorance when I say that this isn't enough info to point me in the right direction.. -Original Message- From: Campbell, Rob [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 12:43 PM To: MS-Exchange Admin Issues Subject: RE: Printing List of Exchange 2003 Accounts You can pull the mailbox list off of the servers via WMI. That will include the mailbox display name as one of the properties. -Original Message- From: Steven Peck [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 11:38 AM To: MS-Exchange Admin Issues Subject: Re: Printing List of Exchange 2003 Accounts Do you want username, Display Name, email address? There are a few different approaches to doing this. One method is to point at the Exchange servers and run a script http://www.blkmtn.org/powershell-list-exchange2k3-mb-info Though there have been other methods posted on this list that point at AD with an LDAP filter instead. Steven Peck On Wed, Mar 19, 2008 at 9:27 AM, John Hornbuckle [EMAIL PROTECTED] wrote: I need to generate a printed list of all of my users who have Exchange accounts. Is there an easy way to do this? John Hornbuckle MIS Department Taylor County School District 318 North Clark Street Perry, FL 32347 www.taylor.k12.fl.us ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ** Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange fail-over
I use CA's XoSoft WansyncHA product and it works well. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
E2k7 Unified Messaging and Avaya
Does anyone on this list have E2k7 Unified Messaging with an Avaya backbone? Are you using Modular Messaging or Microsoft Unified Messaging? Our company is currently evaluating which path to take and would love to hear lessons learned about either approach. Matt ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: E2k7 Unified Messaging and Avaya
I had the Avaya connected to e2k3 via their software, IP Office. To put it mildly, it sucked. If it wasn't users bitching for speakers to hear their messages... I had it set to only go through the handset but then it wouldn't delete the messages when you told it to. About 6 patches and upgrades later, I decided it wasn't going any further. If you allowed it to fully interact with outlook, it attaches a wav file to the email it puts in the inbox. Guess what happens when they don't get deleted? Look hard at the MS Unified. I'll be embarking on a Mitel voip system with e2k7 very soon. M _ From: Matt Lathrum [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 2:01 PM To: MS-Exchange Admin Issues Subject: E2k7 Unified Messaging and Avaya Does anyone on this list have E2k7 Unified Messaging with an Avaya backbone? Are you using Modular Messaging or Microsoft Unified Messaging? Our company is currently evaluating which path to take and would love to hear lessons learned about either approach. Matt ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Exchange Management Shell killed the CDO star
See what happens when the penguin gets it's flippers into something? We go from a decent GUI back to C/Korn/Bash-shell scripting. John H. Matteson, Jr. Systems Administrator/ITT Systems FOB Orgun-E Afghanistan DSN - 318 431 8001 VoSIP - (308) 431 - Iridium - 717.633.3823 Roshain - 079 - 736 - 3832 A man who thinks of himself as belonging to a particular national group in America has not yet become an American. And the man who goes among you to trade upon your nationality is no worthy son to live under the Stars and Stripes. Woodrow Wilson -Original Message- From: Boggis, Josh [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 6:38 PM To: MS-Exchange Admin Issues Subject: Exchange Management Shell killed the CDO star Currently where I work we are using Exchange 2003. I have written some VB code that uses CDO and CDOEXM to create mailboxes for new users. Another process creates new accounts in active directory, and my code goes through all the accounts, sees what department they are in, goes to a lookup table to figure out if the department they are in gets mailboxes on our servers (some departments have their own servers so we leave them alone). Now I go to the Microsoft Upgrading skills from Exchange 2003 to 2007 class and I am introduced to the horror of the exchange management shell. I want to keep using CDO!!! But from what I was told, CDO will not work fully with Exchange 2007, especially since the RUS is gone. CDO, from my little experience with it so far, isn't a robust language to program with. It's more of a scripting system. Am I the only one who isn't happy with the management shell? ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
