DAG setup and configuration help needed
Good morning everyone For those who have had experience so far in setting up a DAG - whether it was for testing or production - I wonder if you could help me? I've been following the excellent instructions over at www.msexchange.orghttp://www.msexchange.org, beginning with part 1: http://www.msexchange.org/articles_tutorials/exchange-server-2010/high-availability-recovery/uncovering-exchange-2010-database-availability-groups-dags-part1.html My environment for this purpose is: * Physical Windows Server 2008 Enterprise for the witness. * Virtual Windows Server 2008 R2 Standard domain controller. * 2 x virtual Windows Server 2008 R2 Enterprise Exchange 2010 RU2 servers. * I am using ESXi as my virtualisation platform. * My DC is a brand new build, dcpromod to Windows Server 2008 R2 forest functional level. For the purpose of my testing, it's running DNS. * The two Exchange servers have two virtual NICs installed and configured as replication and MAPI networks. My problem is related to DAGs, and perhaps clustering. The DAG itself is created normally. It is when I come to add my two Exchange servers to the DAG that the problem(s) begin: 1. The first server is added to the DAG with no errors. 2. Upon configuration of the second server, an IP address conflict is reported. The IP conflicting is that of the first server. To me this makes no sense! Both interfaces on both servers have hardcoded IP information. 3. The DAG will then not come online, even after assigning an IP address to it. 4. This error is reported in the cluster event log on both servers: Cluster network name resource 'Cluster Name' cannot be brought online. The computer object associated with the resource could not be updated in domain 'domain'. The error code was 'Unable to find computer account on DC where it was created'. The cluster identity 'DAG1$' may lack permissions required to update the object. Please work with your domain administrator to ensure that the cluster identity can update computer objects in the domain. If you've made it this far, could you share your experience with the process and offer any tips as to why this isn't going as smoothly as I told myself it would be?! Thanks Richard
RE: List Etiquette
Or, for those that can, simply set their own Out of Office not to go to external senders. I'm in the don't give a cr$p camp - OOO replies are just emails that take a few seconds to delete, or filter. Never been a problem. From: bounce-8945627-8066...@lyris.sunbelt-software.com [mailto:bounce-8945627-8066...@lyris.sunbelt-software.com] On Behalf Of Cliff Partlow Sent: 01 June 2010 03:57 To: MS-Exchange Admin Issues Subject: RE: List Etiquette When I go out of office I just go to the Sunbelt site and set my account to not get email from the list during that time. Same here, it is just being courteous to the other list members. From The Sunny Side Of The Street! Cliff P. From: Micheal Espinola Jr [mailto:michealespin...@gmail.com] Sent: Monday, May 31, 2010 7:48 PM To: MS-Exchange Admin Issues Subject: Re: List Etiquette Same. And these are *easy* to filter. For us that belong to distribution lists, this is a must. People use OOFs. Get over it. -- ME2 On Mon, May 31, 2010 at 2:32 PM, James Kerr cluster...@gmail.commailto:cluster...@gmail.com wrote: When I go out of office I just go to the sunbelt site and set my account to not get email from the list during that time. That being said I hardly ever set those things cause they just invite spammers. On 5/31/2010 12:33 PM, John Cook wrote: Keep this in mind (in case you get one from me) we are not allowed to access external email accounts (it does wonders for keeping bad things off the network) from behind the corp firewall so some of us don't have an option. I try not to set an OOF at all for this very reason. John W. Cook Systems Administrator Partnership for Strong Families - Original Message - From: James Bensleyjwbens...@gmail.commailto:jwbens...@gmail.com To: MS-Exchange Admin Issuesexchangelist@lyris.sunbelt-software.commailto:exchangelist@lyris.sunbelt-software.com Sent: Mon May 31 08:35:28 2010 Subject: Re: List Etiquette On 31 May 2010 13:03, Andrew Levickiand...@levicki.me.ukmailto:and...@levicki.me.uk wrote: It's ironic, is it not, that it's only the Exchange list that suffers from the out of office problem? As I was typing my original post I did sense some irony there, apart from the obvious but also because of all the lists I am on, this one would be the most likely have a filter to stop out of office replies going through perhaps? -- Regards, James. http://www.jamesbensley.co.cc/ - There are only 10 kinds of people in the world, those who understand trinary, those who don't understand trinary and those who don't understand trinary. CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to.
Re: List Etiquette
If you've ever sent an email to the Patch Management list, you'd think 12 was a blessing. It may be better now, but it used to be terrible. On 31 May 2010 10:34, James Bensley jwbens...@gmail.com wrote: Can people on this list please think about amending their email accounts; I am on a few mailing lists but this is the only list on which people are inconsiderate enough to use email accounts on which they have set up an out-of-office reply, why use your primary email account, that is foolish? I have just sent an email to the list and got 12 out of office replies back from subscribers to the list. I like many of you are surely picking up mail via your mobile device, if you get 12 bounce backs for every one email you send it surely isn't going to be good for anyone's data usage. Please be more considerate, /rant over -- Regards, James. http://www.jamesbensley.co.cc/ - There are only 10 kinds of people in the world, those who understand trinary, those who don't understand trinary and those who don't understand trinary. -- On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into the machine wrong figures, will the right answers come out?' I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a question.
RE: List Etiquette
When it's one email, that's fine. When you post something to the list and you get 10 out of office emails, then it's annoying. Not alone that sometimes they don't even have a cache implemented and keep on getting out of office emails even when i reply to the same thread. That's my definition of annoying thing (that can be easily fixed). In some lists you are off the list if you refuse to change your OOO settings. Miguel --- El mar, 1/6/10, Sobey, Richard A r.so...@imperial.ac.uk escribió: De: Sobey, Richard A r.so...@imperial.ac.uk Asunto: RE: List Etiquette Para: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Fecha: martes, 1 de junio, 2010 06:47 Or, for those that can, simply set their own Out of Office not to go to external senders. I’m in the “don’t give a cr$p” camp – OOO replies are just emails that take a few seconds to delete, or filter. Never been a problem. From: bounce-8945627-8066...@lyris.sunbelt-software.com [mailto:bounce-8945627-8066...@lyris.sunbelt-software.com] On Behalf Of Cliff Partlow Sent: 01 June 2010 03:57 To: MS-Exchange Admin Issues Subject: RE: List Etiquette When I go out of office I just go to the Sunbelt site and set my account to not get email from the list during that time. Same here, it is just being courteous to the other list members. From The Sunny Side Of The Street!Cliff P. From: Micheal Espinola Jr [mailto:michealespin...@gmail.com] Sent: Monday, May 31, 2010 7:48 PM To: MS-Exchange Admin Issues Subject: Re: List Etiquette Same. And these are *easy* to filter. For us that belong to distribution lists, this is a must. People use OOFs. Get over it. -- ME2On Mon, May 31, 2010 at 2:32 PM, James Kerr cluster...@gmail.com wrote:When I go out of office I just go to the sunbelt site and set my account to not get email from the list during that time. That being said I hardly ever set those things cause they just invite spammers. On 5/31/2010 12:33 PM, John Cook wrote:Keep this in mind (in case you get one from me) we are not allowed to access external email accounts (it does wonders for keeping bad things off the network) from behind the corp firewall so some of us don't have an option. I try not to set an OOF at all for this very reason. John W. Cook Systems Administrator Partnership for Strong Families - Original Message -From: James Bensleyjwbens...@gmail.com To: MS-Exchange Admin Issuesexchangelist@lyris.sunbelt-software.com Sent: Mon May 31 08:35:28 2010 Subject: Re: List Etiquette On 31 May 2010 13:03, Andrew Levickiand...@levicki.me.uk wrote: It's ironic, is it not, that it's only the Exchange list that suffers from the out of office problem? As I was typing my original post I did sense some irony there, apart from the obvious but also because of all the lists I am on, this one would be the most likely have a filter to stop out of office replies going through perhaps? -- Regards, James. http://www.jamesbensley.co.cc/ - There are only 10 kinds of people in the world, those who understand trinary, those who don't understand trinary and those who don't understand trinary. CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to.
RE: List Etiquette
I'm with you, Richard. I just delete them. I subscribe to a non-tech list for our hospital's HCIS. Sometimes I dread posting knowing I'm going to get 40+ OOF's. From: Sobey, Richard A [mailto:r.so...@imperial.ac.uk] Sent: Tuesday, June 01, 2010 6:48 AM To: MS-Exchange Admin Issues Subject: RE: List Etiquette Or, for those that can, simply set their own Out of Office not to go to external senders. I'm in the don't give a cr$p camp - OOO replies are just emails that take a few seconds to delete, or filter. Never been a problem. From: bounce-8945627-8066...@lyris.sunbelt-software.com [mailto:bounce-8945627-8066...@lyris.sunbelt-software.com] On Behalf Of Cliff Partlow Sent: 01 June 2010 03:57 To: MS-Exchange Admin Issues Subject: RE: List Etiquette When I go out of office I just go to the Sunbelt site and set my account to not get email from the list during that time. Same here, it is just being courteous to the other list members. From The Sunny Side Of The Street! Cliff P. From: Micheal Espinola Jr [mailto:michealespin...@gmail.com] Sent: Monday, May 31, 2010 7:48 PM To: MS-Exchange Admin Issues Subject: Re: List Etiquette Same. And these are *easy* to filter. For us that belong to distribution lists, this is a must. People use OOFs. Get over it. -- ME2 On Mon, May 31, 2010 at 2:32 PM, James Kerr cluster...@gmail.commailto:cluster...@gmail.com wrote: When I go out of office I just go to the sunbelt site and set my account to not get email from the list during that time. That being said I hardly ever set those things cause they just invite spammers. On 5/31/2010 12:33 PM, John Cook wrote: Keep this in mind (in case you get one from me) we are not allowed to access external email accounts (it does wonders for keeping bad things off the network) from behind the corp firewall so some of us don't have an option. I try not to set an OOF at all for this very reason. John W. Cook Systems Administrator Partnership for Strong Families - Original Message - From: James Bensleyjwbens...@gmail.commailto:jwbens...@gmail.com To: MS-Exchange Admin Issuesexchangelist@lyris.sunbelt-software.commailto:exchangelist@lyris.sunbelt-software.com Sent: Mon May 31 08:35:28 2010 Subject: Re: List Etiquette On 31 May 2010 13:03, Andrew Levickiand...@levicki.me.ukmailto:and...@levicki.me.uk wrote: It's ironic, is it not, that it's only the Exchange list that suffers from the out of office problem? As I was typing my original post I did sense some irony there, apart from the obvious but also because of all the lists I am on, this one would be the most likely have a filter to stop out of office replies going through perhaps? -- Regards, James. http://www.jamesbensley.co.cc/ - There are only 10 kinds of people in the world, those who understand trinary, those who don't understand trinary and those who don't understand trinary. CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to.
RE: DAG setup and configuration help needed
If you are running the DAG wizard/cmdlets on one of your exchange mailbox servers that will be in the DAG - then add the REMOTE ONE FIRST (there is a bug about the permissions associated with the CNO if you don't do it that way - alternately, run the wizard elsewhere). You don't say how/when you are allocating IP addresses to the DAG, which is an important consideration in this scenario. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Sobey, Richard A [mailto:r.so...@imperial.ac.uk] Sent: Tuesday, June 01, 2010 6:29 AM To: MS-Exchange Admin Issues Subject: DAG setup and configuration help needed Good morning everyone For those who have had experience so far in setting up a DAG - whether it was for testing or production - I wonder if you could help me? I've been following the excellent instructions over at www.msexchange.orghttp://www.msexchange.org, beginning with part 1: http://www.msexchange.org/articles_tutorials/exchange-server-2010/high-availability-recovery/uncovering-exchange-2010-database-availability-groups-dags-part1.html My environment for this purpose is: * Physical Windows Server 2008 Enterprise for the witness. * Virtual Windows Server 2008 R2 Standard domain controller. * 2 x virtual Windows Server 2008 R2 Enterprise Exchange 2010 RU2 servers. * I am using ESXi as my virtualisation platform. * My DC is a brand new build, dcpromod to Windows Server 2008 R2 forest functional level. For the purpose of my testing, it's running DNS. * The two Exchange servers have two virtual NICs installed and configured as replication and MAPI networks. My problem is related to DAGs, and perhaps clustering. The DAG itself is created normally. It is when I come to add my two Exchange servers to the DAG that the problem(s) begin: 1. The first server is added to the DAG with no errors. 2. Upon configuration of the second server, an IP address conflict is reported. The IP conflicting is that of the first server. To me this makes no sense! Both interfaces on both servers have hardcoded IP information. 3. The DAG will then not come online, even after assigning an IP address to it. 4. This error is reported in the cluster event log on both servers: Cluster network name resource 'Cluster Name' cannot be brought online. The computer object associated with the resource could not be updated in domain 'domain'. The error code was 'Unable to find computer account on DC where it was created'. The cluster identity 'DAG1$' may lack permissions required to update the object. Please work with your domain administrator to ensure that the cluster identity can update computer objects in the domain. If you've made it this far, could you share your experience with the process and offer any tips as to why this isn't going as smoothly as I told myself it would be?! Thanks Richard
Beginning to Migrate from pop/smtp hosted to Exchange 2003 in house.
Yeah Me! Okay so you all have given me great direction. I am doing my testing right now. I have a 5 step process. 1. Route all smtp mail through my firewall then my Ironport then my Exchange Server. 2. Add smtp address to my user account in Exchange. 3. Migrate Outllook Express data to Outlook using the wizards. 4. Add Internet addresses for domain such as MX, A, and SPF records. 5. Cancel Email hosting service. So I have a ticket open with Ironport support to verify my changes there are cool. I am testing my email and from one of 4 hosted email accounts (All of which will be brought in house) and I don't ever see it leave or enter the smtp queue on Exchange or Ironport. So I am at a loss for why I am not seeing it. Is it because in step 2 I am giving the external pop/smtp addresses?? Please consider the environment before printing this email. image001.gif
GAL and Free Busy Info Sync
I am looking for a tool that will sync GAL and Free/Busy info from a legacy Exchange 2003 forest to an Exchange 2010 Resource Forest. I am aware of the following tools: Quest Collaboration Services (Will be Q3 at the earliest this year before they have a product that works with Exchange 2010) FIM 2010 Is there any other supported tools out there that anyone has used in this scenario that will work with Exchange 2010? Chris Pohlschneider Holloway Sportswear Network Administrator chris.pohlschnei...@hollowayusa.com 937-494-2559
Re: Beginning to Migrate from pop/smtp hosted to Exchange 2003 in house.
DNS can take time to propagate, so your new MX record may take some time to be known. I use a few DNS sites as well as query my ISP DNS servers. http://www.iptools.com/ http://www.mxtoolbox.com/SuperTool.aspx Hope this helps. Eric On Tue, Jun 1, 2010 at 8:15 AM, David McSpadden dav...@imcu.com wrote: Yeah Me! Okay so you all have given me great direction. I am doing my testing right now. I have a 5 step process. 1. Route all smtp mail through my firewall then my Ironport then my Exchange Server. 2. Add smtp address to my user account in Exchange. 3. Migrate Outllook Express data to Outlook using the wizards. 4. Add Internet addresses for domain such as MX, A, and SPF records. 5. Cancel Email hosting service. So I have a ticket open with Ironport support to verify my changes there are cool. I am testing my email and from one of 4 hosted email accounts (All of which will be brought in house) and I don’t ever see it leave or enter the smtp queue on Exchange or Ironport. So I am at a loss for why I am not seeing it. Is it because in step 2 I am giving the external pop/smtp addresses?? “Please consider the environment before printing this email.” image001.gif
RE: Beginning to Migrate from pop/smtp hosted to Exchange 2003 in house.
Haven't gotten there yet. Still migrating and testing the setup of the user account. _ From: Eric [mailto:seag...@gmail.com] Sent: Tuesday, June 01, 2010 11:23 AM To: MS-Exchange Admin Issues Subject: Re: Beginning to Migrate from pop/smtp hosted to Exchange 2003 in house. DNS can take time to propagate, so your new MX record may take some time to be known. I use a few DNS sites as well as query my ISP DNS servers. http://www.iptools.com/ http://www.mxtoolbox.com/SuperTool.aspx Hope this helps. Eric On Tue, Jun 1, 2010 at 8:15 AM, David McSpadden dav...@imcu.com wrote: Yeah Me! Okay so you all have given me great direction. I am doing my testing right now. I have a 5 step process. 1. Route all smtp mail through my firewall then my Ironport then my Exchange Server. 2. Add smtp address to my user account in Exchange. 3. Migrate Outllook Express data to Outlook using the wizards. 4. Add Internet addresses for domain such as MX, A, and SPF records. 5. Cancel Email hosting service. So I have a ticket open with Ironport support to verify my changes there are cool. I am testing my email and from one of 4 hosted email accounts (All of which will be brought in house) and I don't ever see it leave or enter the smtp queue on Exchange or Ironport. So I am at a loss for why I am not seeing it. Is it because in step 2 I am giving the external pop/smtp addresses?? Please consider the environment before printing this email. image001.gif
RE: Beginning to Migrate from pop/smtp hosted to Exchange 2003 in house.
Have you tried telnet to port 25 on the Ironport, or using a PS script to send an email using the Ironport as a smarthost? PS script (V2) Send-mailmessage -smtpserver Ironport addr/hostname -to to address -from from address -subject Test -body Test PS script (V1) $mailhost = IronPort addr/hostname $from = From address $to = To address $subj = Test $body = Test $SmtpClient = new-object system.net.mail.smtpClient $SmtpClient.Host = $mailhost $mailmessage = New-Object system.net.mail.mailmessage $mailmessage.from = ($from) $mailmessage.To.add($to) $mailmessage.Subject = $subj $mailmessage.Body = $body $smtpclient.Send($mailmessage) From: David McSpadden [mailto:dav...@imcu.com] Sent: Tuesday, June 01, 2010 10:15 AM To: MS-Exchange Admin Issues Subject: Beginning to Migrate from pop/smtp hosted to Exchange 2003 in house. Yeah Me! Okay so you all have given me great direction. I am doing my testing right now. I have a 5 step process. 1. Route all smtp mail through my firewall then my Ironport then my Exchange Server. 2. Add smtp address to my user account in Exchange. 3. Migrate Outllook Express data to Outlook using the wizards. 4. Add Internet addresses for domain such as MX, A, and SPF records. 5. Cancel Email hosting service. So I have a ticket open with Ironport support to verify my changes there are cool. I am testing my email and from one of 4 hosted email accounts (All of which will be brought in house) and I don't ever see it leave or enter the smtp queue on Exchange or Ironport. So I am at a loss for why I am not seeing it. Is it because in step 2 I am giving the external pop/smtp addresses?? Please consider the environment before printing this email. [cid:image001.gif@01CB0175.3260FED0] ** 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. ** inline: image001.gif
RE: DAG setup and configuration help needed
Thanks! Sounds promising. I'm assigning the IP address using Set-DatabaseAvailabilityGroup -DatabaseAvailabilityGroupIPv4Address blah cmdlet, AFTER the two servers have been added as members. I should probably add the IP address immediately after creating the DAG, I presume? I'll do this now, you will hear me shout from the rooftops or crying into my coffee within 20 minutes. Cheers Richard From: bounce-8946464-8066...@lyris.sunbelt-software.com [mailto:bounce-8946464-8066...@lyris.sunbelt-software.com] On Behalf Of Michael B. Smith Sent: 01 June 2010 16:14 To: MS-Exchange Admin Issues Subject: RE: DAG setup and configuration help needed If you are running the DAG wizard/cmdlets on one of your exchange mailbox servers that will be in the DAG - then add the REMOTE ONE FIRST (there is a bug about the permissions associated with the CNO if you don't do it that way - alternately, run the wizard elsewhere). You don't say how/when you are allocating IP addresses to the DAG, which is an important consideration in this scenario. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Sobey, Richard A [mailto:r.so...@imperial.ac.uk] Sent: Tuesday, June 01, 2010 6:29 AM To: MS-Exchange Admin Issues Subject: DAG setup and configuration help needed Good morning everyone For those who have had experience so far in setting up a DAG - whether it was for testing or production - I wonder if you could help me? I've been following the excellent instructions over at www.msexchange.orghttp://www.msexchange.org, beginning with part 1: http://www.msexchange.org/articles_tutorials/exchange-server-2010/high-availability-recovery/uncovering-exchange-2010-database-availability-groups-dags-part1.html My environment for this purpose is: * Physical Windows Server 2008 Enterprise for the witness. * Virtual Windows Server 2008 R2 Standard domain controller. * 2 x virtual Windows Server 2008 R2 Enterprise Exchange 2010 RU2 servers. * I am using ESXi as my virtualisation platform. * My DC is a brand new build, dcpromod to Windows Server 2008 R2 forest functional level. For the purpose of my testing, it's running DNS. * The two Exchange servers have two virtual NICs installed and configured as replication and MAPI networks. My problem is related to DAGs, and perhaps clustering. The DAG itself is created normally. It is when I come to add my two Exchange servers to the DAG that the problem(s) begin: 1. The first server is added to the DAG with no errors. 2. Upon configuration of the second server, an IP address conflict is reported. The IP conflicting is that of the first server. To me this makes no sense! Both interfaces on both servers have hardcoded IP information. 3. The DAG will then not come online, even after assigning an IP address to it. 4. This error is reported in the cluster event log on both servers: Cluster network name resource 'Cluster Name' cannot be brought online. The computer object associated with the resource could not be updated in domain 'domain'. The error code was 'Unable to find computer account on DC where it was created'. The cluster identity 'DAG1$' may lack permissions required to update the object. Please work with your domain administrator to ensure that the cluster identity can update computer objects in the domain. If you've made it this far, could you share your experience with the process and offer any tips as to why this isn't going as smoothly as I told myself it would be?! Thanks Richard
RE: DAG setup and configuration help needed
Replied offline with lab workbook. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Sobey, Richard A [mailto:r.so...@imperial.ac.uk] Sent: Tuesday, June 01, 2010 11:51 AM To: MS-Exchange Admin Issues Subject: RE: DAG setup and configuration help needed Thanks! Sounds promising. I'm assigning the IP address using Set-DatabaseAvailabilityGroup -DatabaseAvailabilityGroupIPv4Address blah cmdlet, AFTER the two servers have been added as members. I should probably add the IP address immediately after creating the DAG, I presume? I'll do this now, you will hear me shout from the rooftops or crying into my coffee within 20 minutes. Cheers Richard From: bounce-8946464-8066...@lyris.sunbelt-software.com [mailto:bounce-8946464-8066...@lyris.sunbelt-software.com] On Behalf Of Michael B. Smith Sent: 01 June 2010 16:14 To: MS-Exchange Admin Issues Subject: RE: DAG setup and configuration help needed If you are running the DAG wizard/cmdlets on one of your exchange mailbox servers that will be in the DAG - then add the REMOTE ONE FIRST (there is a bug about the permissions associated with the CNO if you don't do it that way - alternately, run the wizard elsewhere). You don't say how/when you are allocating IP addresses to the DAG, which is an important consideration in this scenario. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Sobey, Richard A [mailto:r.so...@imperial.ac.uk] Sent: Tuesday, June 01, 2010 6:29 AM To: MS-Exchange Admin Issues Subject: DAG setup and configuration help needed Good morning everyone For those who have had experience so far in setting up a DAG - whether it was for testing or production - I wonder if you could help me? I've been following the excellent instructions over at www.msexchange.orghttp://www.msexchange.org, beginning with part 1: http://www.msexchange.org/articles_tutorials/exchange-server-2010/high-availability-recovery/uncovering-exchange-2010-database-availability-groups-dags-part1.html My environment for this purpose is: * Physical Windows Server 2008 Enterprise for the witness. * Virtual Windows Server 2008 R2 Standard domain controller. * 2 x virtual Windows Server 2008 R2 Enterprise Exchange 2010 RU2 servers. * I am using ESXi as my virtualisation platform. * My DC is a brand new build, dcpromod to Windows Server 2008 R2 forest functional level. For the purpose of my testing, it's running DNS. * The two Exchange servers have two virtual NICs installed and configured as replication and MAPI networks. My problem is related to DAGs, and perhaps clustering. The DAG itself is created normally. It is when I come to add my two Exchange servers to the DAG that the problem(s) begin: 1. The first server is added to the DAG with no errors. 2. Upon configuration of the second server, an IP address conflict is reported. The IP conflicting is that of the first server. To me this makes no sense! Both interfaces on both servers have hardcoded IP information. 3. The DAG will then not come online, even after assigning an IP address to it. 4. This error is reported in the cluster event log on both servers: Cluster network name resource 'Cluster Name' cannot be brought online. The computer object associated with the resource could not be updated in domain 'domain'. The error code was 'Unable to find computer account on DC where it was created'. The cluster identity 'DAG1$' may lack permissions required to update the object. Please work with your domain administrator to ensure that the cluster identity can update computer objects in the domain. If you've made it this far, could you share your experience with the process and offer any tips as to why this isn't going as smoothly as I told myself it would be?! Thanks Richard
RE: DAG setup and configuration help needed
Whoopity-doo! Shook From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Tuesday, June 01, 2010 11:57 AM To: MS-Exchange Admin Issues Subject: RE: DAG setup and configuration help needed Replied offline with lab workbook. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Sobey, Richard A [mailto:r.so...@imperial.ac.uk] Sent: Tuesday, June 01, 2010 11:51 AM To: MS-Exchange Admin Issues Subject: RE: DAG setup and configuration help needed Thanks! Sounds promising. I'm assigning the IP address using Set-DatabaseAvailabilityGroup -DatabaseAvailabilityGroupIPv4Address blah cmdlet, AFTER the two servers have been added as members. I should probably add the IP address immediately after creating the DAG, I presume? I'll do this now, you will hear me shout from the rooftops or crying into my coffee within 20 minutes. Cheers Richard From: bounce-8946464-8066...@lyris.sunbelt-software.com [mailto:bounce-8946464-8066...@lyris.sunbelt-software.com] On Behalf Of Michael B. Smith Sent: 01 June 2010 16:14 To: MS-Exchange Admin Issues Subject: RE: DAG setup and configuration help needed If you are running the DAG wizard/cmdlets on one of your exchange mailbox servers that will be in the DAG - then add the REMOTE ONE FIRST (there is a bug about the permissions associated with the CNO if you don't do it that way - alternately, run the wizard elsewhere). You don't say how/when you are allocating IP addresses to the DAG, which is an important consideration in this scenario. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Sobey, Richard A [mailto:r.so...@imperial.ac.uk] Sent: Tuesday, June 01, 2010 6:29 AM To: MS-Exchange Admin Issues Subject: DAG setup and configuration help needed Good morning everyone For those who have had experience so far in setting up a DAG - whether it was for testing or production - I wonder if you could help me? I've been following the excellent instructions over at www.msexchange.orghttp://www.msexchange.org, beginning with part 1: http://www.msexchange.org/articles_tutorials/exchange-server-2010/high-availability-recovery/uncovering-exchange-2010-database-availability-groups-dags-part1.html My environment for this purpose is: * Physical Windows Server 2008 Enterprise for the witness. * Virtual Windows Server 2008 R2 Standard domain controller. * 2 x virtual Windows Server 2008 R2 Enterprise Exchange 2010 RU2 servers. * I am using ESXi as my virtualisation platform. * My DC is a brand new build, dcpromod to Windows Server 2008 R2 forest functional level. For the purpose of my testing, it's running DNS. * The two Exchange servers have two virtual NICs installed and configured as replication and MAPI networks. My problem is related to DAGs, and perhaps clustering. The DAG itself is created normally. It is when I come to add my two Exchange servers to the DAG that the problem(s) begin: 1. The first server is added to the DAG with no errors. 2. Upon configuration of the second server, an IP address conflict is reported. The IP conflicting is that of the first server. To me this makes no sense! Both interfaces on both servers have hardcoded IP information. 3. The DAG will then not come online, even after assigning an IP address to it. 4. This error is reported in the cluster event log on both servers: Cluster network name resource 'Cluster Name' cannot be brought online. The computer object associated with the resource could not be updated in domain 'domain'. The error code was 'Unable to find computer account on DC where it was created'. The cluster identity 'DAG1$' may lack permissions required to update the object. Please work with your domain administrator to ensure that the cluster identity can update computer objects in the domain. If you've made it this far, could you share your experience with the process and offer any tips as to why this isn't going as smoothly as I told myself it would be?! Thanks Richard
RE: GAL and Free Busy Info Sync
Note that if you HAD an Exchange 2007 server in your forest, you could use it and still use iorepl. Also note that there are several bugfixes in 2010 sp1 regarding iorepl, but I still don't know if it will be supported. NETsec's version of GALSync is another one to look at. Did you and I talk about this before? :-P Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Chris Pohlschneider [mailto:chris.pohlschnei...@hollowayusa.com] Sent: Tuesday, June 01, 2010 11:18 AM To: MS-Exchange Admin Issues Subject: GAL and Free Busy Info Sync I am looking for a tool that will sync GAL and Free/Busy info from a legacy Exchange 2003 forest to an Exchange 2010 Resource Forest. I am aware of the following tools: Quest Collaboration Services (Will be Q3 at the earliest this year before they have a product that works with Exchange 2010) FIM 2010 Is there any other supported tools out there that anyone has used in this scenario that will work with Exchange 2010? Chris Pohlschneider Holloway Sportswear Network Administrator chris.pohlschnei...@hollowayusa.commailto:chris.pohlschnei...@hollowayusa.com 937-494-2559
RE: DAG setup and configuration help needed
I appreciate it, even if you don't sniff :) From: bounce-8946529-8066...@lyris.sunbelt-software.com [mailto:bounce-8946529-8066...@lyris.sunbelt-software.com] On Behalf Of Andy Shook Sent: 01 June 2010 17:00 To: MS-Exchange Admin Issues Subject: RE: DAG setup and configuration help needed Whoopity-doo! Shook From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Tuesday, June 01, 2010 11:57 AM To: MS-Exchange Admin Issues Subject: RE: DAG setup and configuration help needed Replied offline with lab workbook. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Sobey, Richard A [mailto:r.so...@imperial.ac.uk] Sent: Tuesday, June 01, 2010 11:51 AM To: MS-Exchange Admin Issues Subject: RE: DAG setup and configuration help needed Thanks! Sounds promising. I'm assigning the IP address using Set-DatabaseAvailabilityGroup -DatabaseAvailabilityGroupIPv4Address blah cmdlet, AFTER the two servers have been added as members. I should probably add the IP address immediately after creating the DAG, I presume? I'll do this now, you will hear me shout from the rooftops or crying into my coffee within 20 minutes. Cheers Richard From: bounce-8946464-8066...@lyris.sunbelt-software.com [mailto:bounce-8946464-8066...@lyris.sunbelt-software.com] On Behalf Of Michael B. Smith Sent: 01 June 2010 16:14 To: MS-Exchange Admin Issues Subject: RE: DAG setup and configuration help needed If you are running the DAG wizard/cmdlets on one of your exchange mailbox servers that will be in the DAG - then add the REMOTE ONE FIRST (there is a bug about the permissions associated with the CNO if you don't do it that way - alternately, run the wizard elsewhere). You don't say how/when you are allocating IP addresses to the DAG, which is an important consideration in this scenario. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Sobey, Richard A [mailto:r.so...@imperial.ac.uk] Sent: Tuesday, June 01, 2010 6:29 AM To: MS-Exchange Admin Issues Subject: DAG setup and configuration help needed Good morning everyone For those who have had experience so far in setting up a DAG - whether it was for testing or production - I wonder if you could help me? I've been following the excellent instructions over at www.msexchange.orghttp://www.msexchange.org, beginning with part 1: http://www.msexchange.org/articles_tutorials/exchange-server-2010/high-availability-recovery/uncovering-exchange-2010-database-availability-groups-dags-part1.html My environment for this purpose is: * Physical Windows Server 2008 Enterprise for the witness. * Virtual Windows Server 2008 R2 Standard domain controller. * 2 x virtual Windows Server 2008 R2 Enterprise Exchange 2010 RU2 servers. * I am using ESXi as my virtualisation platform. * My DC is a brand new build, dcpromod to Windows Server 2008 R2 forest functional level. For the purpose of my testing, it's running DNS. * The two Exchange servers have two virtual NICs installed and configured as replication and MAPI networks. My problem is related to DAGs, and perhaps clustering. The DAG itself is created normally. It is when I come to add my two Exchange servers to the DAG that the problem(s) begin: 1. The first server is added to the DAG with no errors. 2. Upon configuration of the second server, an IP address conflict is reported. The IP conflicting is that of the first server. To me this makes no sense! Both interfaces on both servers have hardcoded IP information. 3. The DAG will then not come online, even after assigning an IP address to it. 4. This error is reported in the cluster event log on both servers: Cluster network name resource 'Cluster Name' cannot be brought online. The computer object associated with the resource could not be updated in domain 'domain'. The error code was 'Unable to find computer account on DC where it was created'. The cluster identity 'DAG1$' may lack permissions required to update the object. Please work with your domain administrator to ensure that the cluster identity can update computer objects in the domain. If you've made it this far, could you share your experience with the process and offer any tips as to why this isn't going as smoothly as I told myself it would be?! Thanks Richard
RE: DAG setup and configuration help needed
I appreciate the opportunity to bust on MBS when I can... Shook From: Sobey, Richard A [mailto:r.so...@imperial.ac.uk] Sent: Tuesday, June 01, 2010 1:50 PM To: MS-Exchange Admin Issues Subject: RE: DAG setup and configuration help needed I appreciate it, even if you don't sniff :) From: bounce-8946529-8066...@lyris.sunbelt-software.com [mailto:bounce-8946529-8066...@lyris.sunbelt-software.com] On Behalf Of Andy Shook Sent: 01 June 2010 17:00 To: MS-Exchange Admin Issues Subject: RE: DAG setup and configuration help needed Whoopity-doo! Shook From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Tuesday, June 01, 2010 11:57 AM To: MS-Exchange Admin Issues Subject: RE: DAG setup and configuration help needed Replied offline with lab workbook. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Sobey, Richard A [mailto:r.so...@imperial.ac.uk] Sent: Tuesday, June 01, 2010 11:51 AM To: MS-Exchange Admin Issues Subject: RE: DAG setup and configuration help needed Thanks! Sounds promising. I'm assigning the IP address using Set-DatabaseAvailabilityGroup -DatabaseAvailabilityGroupIPv4Address blah cmdlet, AFTER the two servers have been added as members. I should probably add the IP address immediately after creating the DAG, I presume? I'll do this now, you will hear me shout from the rooftops or crying into my coffee within 20 minutes. Cheers Richard From: bounce-8946464-8066...@lyris.sunbelt-software.com [mailto:bounce-8946464-8066...@lyris.sunbelt-software.com] On Behalf Of Michael B. Smith Sent: 01 June 2010 16:14 To: MS-Exchange Admin Issues Subject: RE: DAG setup and configuration help needed If you are running the DAG wizard/cmdlets on one of your exchange mailbox servers that will be in the DAG - then add the REMOTE ONE FIRST (there is a bug about the permissions associated with the CNO if you don't do it that way - alternately, run the wizard elsewhere). You don't say how/when you are allocating IP addresses to the DAG, which is an important consideration in this scenario. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Sobey, Richard A [mailto:r.so...@imperial.ac.uk] Sent: Tuesday, June 01, 2010 6:29 AM To: MS-Exchange Admin Issues Subject: DAG setup and configuration help needed Good morning everyone For those who have had experience so far in setting up a DAG - whether it was for testing or production - I wonder if you could help me? I've been following the excellent instructions over at www.msexchange.orghttp://www.msexchange.org, beginning with part 1: http://www.msexchange.org/articles_tutorials/exchange-server-2010/high-availability-recovery/uncovering-exchange-2010-database-availability-groups-dags-part1.html My environment for this purpose is: * Physical Windows Server 2008 Enterprise for the witness. * Virtual Windows Server 2008 R2 Standard domain controller. * 2 x virtual Windows Server 2008 R2 Enterprise Exchange 2010 RU2 servers. * I am using ESXi as my virtualisation platform. * My DC is a brand new build, dcpromod to Windows Server 2008 R2 forest functional level. For the purpose of my testing, it's running DNS. * The two Exchange servers have two virtual NICs installed and configured as replication and MAPI networks. My problem is related to DAGs, and perhaps clustering. The DAG itself is created normally. It is when I come to add my two Exchange servers to the DAG that the problem(s) begin: 1. The first server is added to the DAG with no errors. 2. Upon configuration of the second server, an IP address conflict is reported. The IP conflicting is that of the first server. To me this makes no sense! Both interfaces on both servers have hardcoded IP information. 3. The DAG will then not come online, even after assigning an IP address to it. 4. This error is reported in the cluster event log on both servers: Cluster network name resource 'Cluster Name' cannot be brought online. The computer object associated with the resource could not be updated in domain 'domain'. The error code was 'Unable to find computer account on DC where it was created'. The cluster identity 'DAG1$' may lack permissions required to update the object. Please work with your domain administrator to ensure that the cluster identity can update computer objects in the domain. If you've made it this far, could you share your experience with the process and offer any tips as to why this isn't going as smoothly as I told myself it would be?! Thanks Richard
OT - BES upgrade
Looking for any offers of advice or suggestions - I will be upgrading our BES server from 4.1 to 5.0 in preparation for our Exchange upgrade from 2003 to 2010. I have *no* experience with BES so I need to familiarize myself with it first and go from there. Lots to learn! Just wondering if anyone is familiar with useful lists or forums? Is the process straightforward or complex? If there's anything at all that you'd be willing to share to get me started, it would be greatly appreciated! Thanks in advance. -- Tammy George Sr. Systems Operator Technology Services Acadia University tel: (902) 585-1158 fax: (902) 585-1066
Re: OT - BES upgrade
What version of 4.1? You'll need to upgrade to 4.1.7 first (DB changes) then 5. How many users? John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 13:55:48 2010 Subject: OT - BES upgrade Looking for any offers of advice or suggestions – I will be upgrading our BES server from 4.1 to 5.0 in preparation for our Exchange upgrade from 2003 to 2010. I have *no* experience with BES so I need to familiarize myself with it first and go from there. Lots to learn! Just wondering if anyone is familiar with useful lists or forums? Is the process straightforward or complex? If there’s anything at all that you’d be willing to share to get me started, it would be greatly appreciated! Thanks in advance. -- Tammy George Sr. Systems Operator Technology Services Acadia University tel: (902) 585-1158 fax: (902) 585-1066 CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. This email and any attached files are confidential and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of the company. Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the use of this email or attachments.
RE: OT - BES upgrade
Version 4.1.6.10 and 36 users. From: John Cook [mailto:john.c...@pfsf.org] Sent: June 1, 2010 3:06 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade What version of 4.1? You'll need to upgrade to 4.1.7 first (DB changes) then 5. How many users? John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 13:55:48 2010 Subject: OT - BES upgrade Looking for any offers of advice or suggestions – I will be upgrading our BES server from 4.1 to 5.0 in preparation for our Exchange upgrade from 2003 to 2010. I have *no* experience with BES so I need to familiarize myself with it first and go from there. Lots to learn! Just wondering if anyone is familiar with useful lists or forums? Is the process straightforward or complex? If there’s anything at all that you’d be willing to share to get me started, it would be greatly appreciated! Thanks in advance. -- Tammy George Sr. Systems Operator Technology Services Acadia University tel: (902) 585-1158 fax: (902) 585-1066 CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. This email and any attached files are confidential and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of the company. Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the use of this email or attachments.
Re: OT - BES upgrade
Running on server 2003? John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 14:12:12 2010 Subject: RE: OT - BES upgrade Version 4.1.6.10 and 36 users. From: John Cook [mailto:john.c...@pfsf.org] Sent: June 1, 2010 3:06 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade What version of 4.1? You'll need to upgrade to 4.1.7 first (DB changes) then 5. How many users? John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 13:55:48 2010 Subject: OT - BES upgrade Looking for any offers of advice or suggestions – I will be upgrading our BES server from 4.1 to 5.0 in preparation for our Exchange upgrade from 2003 to 2010. I have *no* experience with BES so I need to familiarize myself with it first and go from there. Lots to learn! Just wondering if anyone is familiar with useful lists or forums? Is the process straightforward or complex? If there’s anything at all that you’d be willing to share to get me started, it would be greatly appreciated! Thanks in advance. -- Tammy George Sr. Systems Operator Technology Services Acadia University tel: (902) 585-1158 fax: (902) 585-1066 CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. This email and any attached files are confidential and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of the company. Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the use of this email or attachments. CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. This email and any attached files are confidential and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of the company. Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the use of this email or attachments.
RE: OT - BES upgrade
Yes. From: John Cook [mailto:john.c...@pfsf.org] Sent: June 1, 2010 3:14 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade Running on server 2003? John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 14:12:12 2010 Subject: RE: OT - BES upgrade Version 4.1.6.10 and 36 users. From: John Cook [mailto:john.c...@pfsf.org] Sent: June 1, 2010 3:06 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade What version of 4.1? You'll need to upgrade to 4.1.7 first (DB changes) then 5. How many users? John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 13:55:48 2010 Subject: OT - BES upgrade Looking for any offers of advice or suggestions – I will be upgrading our BES server from 4.1 to 5.0 in preparation for our Exchange upgrade from 2003 to 2010. I have *no* experience with BES so I need to familiarize myself with it first and go from there. Lots to learn! Just wondering if anyone is familiar with useful lists or forums? Is the process straightforward or complex? If there’s anything at all that you’d be willing to share to get me started, it would be greatly appreciated! Thanks in advance. -- Tammy George Sr. Systems Operator Technology Services Acadia University tel: (902) 585-1158 fax: (902) 585-1066 CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. This email and any attached files are confidential and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of the company. Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the use of this email or attachments. CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. This email and any attached files are confidential and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of the company. Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the use of this email or attachments.
Re: OT - BES upgrade
My advice, if you don't have to, don't do both upgrades at the same time. We did. didn't have any big issues with upgrade/installations, but it's a lot to take in for a busy production environment. you won't know till you in the middle of it what issues the exchange upgrade will present, especially if you have developers trying to route stuff out through exchange. BES 5.0 is slick, but very different. Since you are not already that familiar with 4.x maybe it isn't such a deal for you. On Tue, Jun 1, 2010 at 12:55 PM, Tammy George tammy.geo...@acadiau.cawrote: Looking for any offers of advice or suggestions – I will be upgrading our BES server from 4.1 to 5.0 in preparation for our Exchange upgrade from 2003 to 2010. I have **no** experience with BES so I need to familiarize myself with it first and go from there. Lots to learn! Just wondering if anyone is familiar with useful lists or forums? Is the process straightforward or complex? If there’s anything at all that you’d be willing to share to get me started, it would be greatly appreciated! Thanks in advance. -- Tammy George Sr. Systems Operator Technology Services Acadia University tel: (902) 585-1158 fax: (902) 585-1066
Re: OT - BES upgrade
Well I just suffered through this so here goes - do backups at every stage, set up a new server (2008 SP2 not R2) if at all possible and migrate users (RIM has a tool for this)between servers. Upgrades are rarely clean or pretty. Open a case with RIM prior to starting, it will help mitigate down time. HTH John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 14:19:25 2010 Subject: RE: OT - BES upgrade Yes. From: John Cook [mailto:john.c...@pfsf.org] Sent: June 1, 2010 3:14 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade Running on server 2003? John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 14:12:12 2010 Subject: RE: OT - BES upgrade Version 4.1.6.10 and 36 users. From: John Cook [mailto:john.c...@pfsf.org] Sent: June 1, 2010 3:06 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade What version of 4.1? You'll need to upgrade to 4.1.7 first (DB changes) then 5. How many users? John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 13:55:48 2010 Subject: OT - BES upgrade Looking for any offers of advice or suggestions – I will be upgrading our BES server from 4.1 to 5.0 in preparation for our Exchange upgrade from 2003 to 2010. I have *no* experience with BES so I need to familiarize myself with it first and go from there. Lots to learn! Just wondering if anyone is familiar with useful lists or forums? Is the process straightforward or complex? If there’s anything at all that you’d be willing to share to get me started, it would be greatly appreciated! Thanks in advance. -- Tammy George Sr. Systems Operator Technology Services Acadia University tel: (902) 585-1158 fax: (902) 585-1066 CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. This email and any attached files are confidential and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of the company. Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the use of this email or attachments. CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. This email and any attached files are confidential and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of the company. Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the
RE: OT - BES upgrade
Why not R2? Inquiring minds want to know…. Shook From: John Cook [mailto:john.c...@pfsf.org] Sent: Tuesday, June 01, 2010 2:27 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade Well I just suffered through this so here goes - do backups at every stage, set up a new server (2008 SP2 not R2) if at all possible and migrate users (RIM has a tool for this)between servers. Upgrades are rarely clean or pretty. Open a case with RIM prior to starting, it will help mitigate down time. HTH John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 14:19:25 2010 Subject: RE: OT - BES upgrade Yes. From: John Cook [mailto:john.c...@pfsf.org] Sent: June 1, 2010 3:14 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade Running on server 2003? John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 14:12:12 2010 Subject: RE: OT - BES upgrade Version 4.1.6.10 and 36 users. From: John Cook [mailto:john.c...@pfsf.org] Sent: June 1, 2010 3:06 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade What version of 4.1? You'll need to upgrade to 4.1.7 first (DB changes) then 5. How many users? John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 13:55:48 2010 Subject: OT - BES upgrade Looking for any offers of advice or suggestions – I will be upgrading our BES server from 4.1 to 5.0 in preparation for our Exchange upgrade from 2003 to 2010. I have *no* experience with BES so I need to familiarize myself with it first and go from there. Lots to learn! Just wondering if anyone is familiar with useful lists or forums? Is the process straightforward or complex? If there’s anything at all that you’d be willing to share to get me started, it would be greatly appreciated! Thanks in advance. -- Tammy George Sr. Systems Operator Technology Services Acadia University tel: (902) 585-1158 fax: (902) 585-1066 CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. This email and any attached files are confidential and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of the company. Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the use of this email or attachments. CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. This email and any attached files are confidential and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of the
RE: OT - BES upgrade
Not supported. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Andy Shook [mailto:andy.sh...@peak10.com] Sent: Tuesday, June 01, 2010 2:29 PM To: MS-Exchange Admin Issues Subject: RE: OT - BES upgrade Why not R2? Inquiring minds want to know…. Shook From: John Cook [mailto:john.c...@pfsf.org] Sent: Tuesday, June 01, 2010 2:27 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade Well I just suffered through this so here goes - do backups at every stage, set up a new server (2008 SP2 not R2) if at all possible and migrate users (RIM has a tool for this)between servers. Upgrades are rarely clean or pretty. Open a case with RIM prior to starting, it will help mitigate down time. HTH John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 14:19:25 2010 Subject: RE: OT - BES upgrade Yes. From: John Cook [mailto:john.c...@pfsf.org] Sent: June 1, 2010 3:14 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade Running on server 2003? John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 14:12:12 2010 Subject: RE: OT - BES upgrade Version 4.1.6.10 and 36 users. From: John Cook [mailto:john.c...@pfsf.org] Sent: June 1, 2010 3:06 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade What version of 4.1? You'll need to upgrade to 4.1.7 first (DB changes) then 5. How many users? John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 13:55:48 2010 Subject: OT - BES upgrade Looking for any offers of advice or suggestions – I will be upgrading our BES server from 4.1 to 5.0 in preparation for our Exchange upgrade from 2003 to 2010. I have *no* experience with BES so I need to familiarize myself with it first and go from there. Lots to learn! Just wondering if anyone is familiar with useful lists or forums? Is the process straightforward or complex? If there’s anything at all that you’d be willing to share to get me started, it would be greatly appreciated! Thanks in advance. -- Tammy George Sr. Systems Operator Technology Services Acadia University tel: (902) 585-1158 fax: (902) 585-1066 CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. This email and any attached files are confidential and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of the company. Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the use of this email or attachments. CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. This email and any attached files are confidential and
Re: OT - BES upgrade
RIM support told me I could run it on R2, but only with the most recent update. On Tue, Jun 1, 2010 at 1:29 PM, Michael B. Smith mich...@smithcons.comwrote: Not supported. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com *From:* Andy Shook [mailto:andy.sh...@peak10.com] *Sent:* Tuesday, June 01, 2010 2:29 PM *To:* MS-Exchange Admin Issues *Subject:* RE: OT - BES upgrade Why not R2? Inquiring minds want to know…. Shook *From:* John Cook [mailto:john.c...@pfsf.org] *Sent:* Tuesday, June 01, 2010 2:27 PM *To:* MS-Exchange Admin Issues *Subject:* Re: OT - BES upgrade Well I just suffered through this so here goes - do backups at every stage, set up a new server (2008 SP2 not R2) if at all possible and migrate users (RIM has a tool for this)between servers. Upgrades are rarely clean or pretty. Open a case with RIM prior to starting, it will help mitigate down time. HTH John W. Cook Systems Administrator Partnership for Strong Families -- *From*: Tammy George tammy.geo...@acadiau.ca *To*: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com *Sent*: Tue Jun 01 14:19:25 2010 *Subject*: RE: OT - BES upgrade Yes. *From:* John Cook [mailto:john.c...@pfsf.org] *Sent:* June 1, 2010 3:14 PM *To:* MS-Exchange Admin Issues *Subject:* Re: OT - BES upgrade Running on server 2003? John W. Cook Systems Administrator Partnership for Strong Families -- *From*: Tammy George tammy.geo...@acadiau.ca *To*: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com *Sent*: Tue Jun 01 14:12:12 2010 *Subject*: RE: OT - BES upgrade Version 4.1.6.10 and 36 users. *From:* John Cook [mailto:john.c...@pfsf.org] *Sent:* June 1, 2010 3:06 PM *To:* MS-Exchange Admin Issues *Subject:* Re: OT - BES upgrade What version of 4.1? You'll need to upgrade to 4.1.7 first (DB changes) then 5. How many users? John W. Cook Systems Administrator Partnership for Strong Families -- *From*: Tammy George tammy.geo...@acadiau.ca *To*: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com *Sent*: Tue Jun 01 13:55:48 2010 *Subject*: OT - BES upgrade Looking for any offers of advice or suggestions – I will be upgrading our BES server from 4.1 to 5.0 in preparation for our Exchange upgrade from 2003 to 2010. I have **no** experience with BES so I need to familiarize myself with it first and go from there. Lots to learn! Just wondering if anyone is familiar with useful lists or forums? Is the process straightforward or complex? If there’s anything at all that you’d be willing to share to get me started, it would be greatly appreciated! Thanks in advance. -- Tammy George Sr. Systems Operator Technology Services Acadia University tel: (902) 585-1158 fax: (902) 585-1066 -- CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. This email and any attached files are confidential and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of the company. Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the use of this email or attachments. -- CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance
RE: OT - BES upgrade
Interesting... Could the new server be 2003 as opposed to 2008? From: John Cook [mailto:john.c...@pfsf.org] Sent: June 1, 2010 3:27 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade Well I just suffered through this so here goes - do backups at every stage, set up a new server (2008 SP2 not R2) if at all possible and migrate users (RIM has a tool for this)between servers. Upgrades are rarely clean or pretty. Open a case with RIM prior to starting, it will help mitigate down time. HTH John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 14:19:25 2010 Subject: RE: OT - BES upgrade Yes. From: John Cook [mailto:john.c...@pfsf.org] Sent: June 1, 2010 3:14 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade Running on server 2003? John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 14:12:12 2010 Subject: RE: OT - BES upgrade Version 4.1.6.10 and 36 users. From: John Cook [mailto:john.c...@pfsf.org] Sent: June 1, 2010 3:06 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade What version of 4.1? You'll need to upgrade to 4.1.7 first (DB changes) then 5. How many users? John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 13:55:48 2010 Subject: OT - BES upgrade Looking for any offers of advice or suggestions – I will be upgrading our BES server from 4.1 to 5.0 in preparation for our Exchange upgrade from 2003 to 2010. I have *no* experience with BES so I need to familiarize myself with it first and go from there. Lots to learn! Just wondering if anyone is familiar with useful lists or forums? Is the process straightforward or complex? If there’s anything at all that you’d be willing to share to get me started, it would be greatly appreciated! Thanks in advance. -- Tammy George Sr. Systems Operator Technology Services Acadia University tel: (902) 585-1158 fax: (902) 585-1066 CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. This email and any attached files are confidential and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of the company. Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the use of this email or attachments. CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. This email and any attached files are confidential and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email.
RE: OT - BES upgrade
Do you have a link? I called two weeks ago, and was told that R2 support wouldn't be coming until 5.0 sp2. Thanks. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Jeff Brown [mailto:2jbr...@gmail.com] Sent: Tuesday, June 01, 2010 2:39 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade RIM support told me I could run it on R2, but only with the most recent update. On Tue, Jun 1, 2010 at 1:29 PM, Michael B. Smith mich...@smithcons.commailto:mich...@smithcons.com wrote: Not supported. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Andy Shook [mailto:andy.sh...@peak10.commailto:andy.sh...@peak10.com] Sent: Tuesday, June 01, 2010 2:29 PM To: MS-Exchange Admin Issues Subject: RE: OT - BES upgrade Why not R2? Inquiring minds want to know Shook From: John Cook [mailto:john.c...@pfsf.orgmailto:john.c...@pfsf.org] Sent: Tuesday, June 01, 2010 2:27 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade Well I just suffered through this so here goes - do backups at every stage, set up a new server (2008 SP2 not R2) if at all possible and migrate users (RIM has a tool for this)between servers. Upgrades are rarely clean or pretty. Open a case with RIM prior to starting, it will help mitigate down time. HTH John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.camailto:tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.commailto:exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 14:19:25 2010 Subject: RE: OT - BES upgrade Yes. From: John Cook [mailto:john.c...@pfsf.orgmailto:john.c...@pfsf.org] Sent: June 1, 2010 3:14 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade Running on server 2003? John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.camailto:tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.commailto:exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 14:12:12 2010 Subject: RE: OT - BES upgrade Version 4.1.6.10 and 36 users. From: John Cook [mailto:john.c...@pfsf.orgmailto:john.c...@pfsf.org] Sent: June 1, 2010 3:06 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade What version of 4.1? You'll need to upgrade to 4.1.7 first (DB changes) then 5. How many users? John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.camailto:tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.commailto:exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 13:55:48 2010 Subject: OT - BES upgrade Looking for any offers of advice or suggestions - I will be upgrading our BES server from 4.1 to 5.0 in preparation for our Exchange upgrade from 2003 to 2010. I have *no* experience with BES so I need to familiarize myself with it first and go from there. Lots to learn! Just wondering if anyone is familiar with useful lists or forums? Is the process straightforward or complex? If there's anything at all that you'd be willing to share to get me started, it would be greatly appreciated! Thanks in advance. -- Tammy George Sr. Systems Operator Technology Services Acadia University tel: (902) 585-1158 fax: (902) 585-1066 CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. This email and any attached files are confidential and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of the company. Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the use of this email or attachments. CONFIDENTIALITY STATEMENT: The
RE: OT - BES upgrade
Same thing stated at WES as well...sp2 gets you R2, I think you can run but not officially supported, much like the SQL clustering, can run but not officially supported yet. And yes, the new can be 2003, we are currently in the same boat, exchange 2003 and BES 4.1.6, have a new environment with 5.0.1 on separate environment using BES Transporter to migrate, our biggest obstacle we are dealing with now is the named property limits within exchange 2003 being reached and causing migration issues for certain users. From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Tuesday, June 01, 2010 2:46 PM To: MS-Exchange Admin Issues Subject: RE: OT - BES upgrade Do you have a link? I called two weeks ago, and was told that R2 support wouldn't be coming until 5.0 sp2. Thanks. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Jeff Brown [mailto:2jbr...@gmail.com] Sent: Tuesday, June 01, 2010 2:39 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade RIM support told me I could run it on R2, but only with the most recent update. On Tue, Jun 1, 2010 at 1:29 PM, Michael B. Smith mich...@smithcons.com wrote: Not supported. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Andy Shook [mailto:andy.sh...@peak10.com] Sent: Tuesday, June 01, 2010 2:29 PM To: MS-Exchange Admin Issues Subject: RE: OT - BES upgrade Why not R2? Inquiring minds want to know Shook From: John Cook [mailto:john.c...@pfsf.org] Sent: Tuesday, June 01, 2010 2:27 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade Well I just suffered through this so here goes - do backups at every stage, set up a new server (2008 SP2 not R2) if at all possible and migrate users (RIM has a tool for this)between servers. Upgrades are rarely clean or pretty. Open a case with RIM prior to starting, it will help mitigate down time. HTH John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 14:19:25 2010 Subject: RE: OT - BES upgrade Yes. From: John Cook [mailto:john.c...@pfsf.org] Sent: June 1, 2010 3:14 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade Running on server 2003? John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 14:12:12 2010 Subject: RE: OT - BES upgrade Version 4.1.6.10 and 36 users. From: John Cook [mailto:john.c...@pfsf.org] Sent: June 1, 2010 3:06 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade What version of 4.1? You'll need to upgrade to 4.1.7 first (DB changes) then 5. How many users? John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 13:55:48 2010 Subject: OT - BES upgrade Looking for any offers of advice or suggestions - I will be upgrading our BES server from 4.1 to 5.0 in preparation for our Exchange upgrade from 2003 to 2010. I have *no* experience with BES so I need to familiarize myself with it first and go from there. Lots to learn! Just wondering if anyone is familiar with useful lists or forums? Is the process straightforward or complex? If there's anything at all that you'd be willing to share to get me started, it would be greatly appreciated! Thanks in advance. -- Tammy George Sr. Systems Operator Technology Services Acadia University tel: (902) 585-1158 fax: (902) 585-1066 CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. This email and any attached files are confidential and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute,
Re: OT - BES upgrade
As far as I know the only server product they are shy about is '08R2. It'll run on '03 just fine. On Tue, Jun 1, 2010 at 1:43 PM, Tammy George tammy.geo...@acadiau.cawrote: Interesting... Could the new server be 2003 as opposed to 2008? *From:* John Cook [mailto:john.c...@pfsf.org] *Sent:* June 1, 2010 3:27 PM *To:* MS-Exchange Admin Issues *Subject:* Re: OT - BES upgrade Well I just suffered through this so here goes - do backups at every stage, set up a new server (2008 SP2 not R2) if at all possible and migrate users (RIM has a tool for this)between servers. Upgrades are rarely clean or pretty. Open a case with RIM prior to starting, it will help mitigate down time. HTH John W. Cook Systems Administrator Partnership for Strong Families -- *From*: Tammy George tammy.geo...@acadiau.ca *To*: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com *Sent*: Tue Jun 01 14:19:25 2010 *Subject*: RE: OT - BES upgrade Yes. *From:* John Cook [mailto:john.c...@pfsf.org] *Sent:* June 1, 2010 3:14 PM *To:* MS-Exchange Admin Issues *Subject:* Re: OT - BES upgrade Running on server 2003? John W. Cook Systems Administrator Partnership for Strong Families -- *From*: Tammy George tammy.geo...@acadiau.ca *To*: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com *Sent*: Tue Jun 01 14:12:12 2010 *Subject*: RE: OT - BES upgrade Version 4.1.6.10 and 36 users. *From:* John Cook [mailto:john.c...@pfsf.org] *Sent:* June 1, 2010 3:06 PM *To:* MS-Exchange Admin Issues *Subject:* Re: OT - BES upgrade What version of 4.1? You'll need to upgrade to 4.1.7 first (DB changes) then 5. How many users? John W. Cook Systems Administrator Partnership for Strong Families -- *From*: Tammy George tammy.geo...@acadiau.ca *To*: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com *Sent*: Tue Jun 01 13:55:48 2010 *Subject*: OT - BES upgrade Looking for any offers of advice or suggestions – I will be upgrading our BES server from 4.1 to 5.0 in preparation for our Exchange upgrade from 2003 to 2010. I have **no** experience with BES so I need to familiarize myself with it first and go from there. Lots to learn! Just wondering if anyone is familiar with useful lists or forums? Is the process straightforward or complex? If there’s anything at all that you’d be willing to share to get me started, it would be greatly appreciated! Thanks in advance. -- Tammy George Sr. Systems Operator Technology Services Acadia University tel: (902) 585-1158 fax: (902) 585-1066 -- CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. This email and any attached files are confidential and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of the company. Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the use of this email or attachments. -- CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print
RE: OT - BES upgrade
What about an in-place upgrade? I've read about this in the Upgrade documentation. Has anyone tried this? From: Jeff Brown [mailto:2jbr...@gmail.com] Sent: June 1, 2010 3:48 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade As far as I know the only server product they are shy about is '08R2. It'll run on '03 just fine. On Tue, Jun 1, 2010 at 1:43 PM, Tammy George tammy.geo...@acadiau.ca wrote: Interesting... Could the new server be 2003 as opposed to 2008? From: John Cook [mailto:john.c...@pfsf.org] Sent: June 1, 2010 3:27 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade Well I just suffered through this so here goes - do backups at every stage, set up a new server (2008 SP2 not R2) if at all possible and migrate users (RIM has a tool for this)between servers. Upgrades are rarely clean or pretty. Open a case with RIM prior to starting, it will help mitigate down time. HTH John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 14:19:25 2010 Subject: RE: OT - BES upgrade Yes. From: John Cook [mailto:john.c...@pfsf.org] Sent: June 1, 2010 3:14 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade Running on server 2003? John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 14:12:12 2010 Subject: RE: OT - BES upgrade Version 4.1.6.10 and 36 users. From: John Cook [mailto:john.c...@pfsf.org] Sent: June 1, 2010 3:06 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade What version of 4.1? You'll need to upgrade to 4.1.7 first (DB changes) then 5. How many users? John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 13:55:48 2010 Subject: OT - BES upgrade Looking for any offers of advice or suggestions - I will be upgrading our BES server from 4.1 to 5.0 in preparation for our Exchange upgrade from 2003 to 2010. I have *no* experience with BES so I need to familiarize myself with it first and go from there. Lots to learn! Just wondering if anyone is familiar with useful lists or forums? Is the process straightforward or complex? If there's anything at all that you'd be willing to share to get me started, it would be greatly appreciated! Thanks in advance. -- Tammy George Sr. Systems Operator Technology Services Acadia University tel: (902) 585-1158 fax: (902) 585-1066 CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. This email and any attached files are confidential and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of the company. Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the use of this email or attachments. CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws.
Re: OT - BES upgrade
You can run it on 2003 just fine but going forward do you want to keep setting up 2003 servers knowing EOS is not that many years off? John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 14:43:05 2010 Subject: RE: OT - BES upgrade Interesting... Could the new server be 2003 as opposed to 2008? From: John Cook [mailto:john.c...@pfsf.org] Sent: June 1, 2010 3:27 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade Well I just suffered through this so here goes - do backups at every stage, set up a new server (2008 SP2 not R2) if at all possible and migrate users (RIM has a tool for this)between servers. Upgrades are rarely clean or pretty. Open a case with RIM prior to starting, it will help mitigate down time. HTH John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 14:19:25 2010 Subject: RE: OT - BES upgrade Yes. From: John Cook [mailto:john.c...@pfsf.org] Sent: June 1, 2010 3:14 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade Running on server 2003? John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 14:12:12 2010 Subject: RE: OT - BES upgrade Version 4.1.6.10 and 36 users. From: John Cook [mailto:john.c...@pfsf.org] Sent: June 1, 2010 3:06 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade What version of 4.1? You'll need to upgrade to 4.1.7 first (DB changes) then 5. How many users? John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 13:55:48 2010 Subject: OT - BES upgrade Looking for any offers of advice or suggestions – I will be upgrading our BES server from 4.1 to 5.0 in preparation for our Exchange upgrade from 2003 to 2010. I have *no* experience with BES so I need to familiarize myself with it first and go from there. Lots to learn! Just wondering if anyone is familiar with useful lists or forums? Is the process straightforward or complex? If there’s anything at all that you’d be willing to share to get me started, it would be greatly appreciated! Thanks in advance. -- Tammy George Sr. Systems Operator Technology Services Acadia University tel: (902) 585-1158 fax: (902) 585-1066 CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. This email and any attached files are confidential and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of the company. Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the use of this email or attachments. CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil
Re: OT - BES upgrade
Michael, I may well be running in what is officially an unsupported environment, but they didn't refuse to help me, and we were able to resolve the issues I was having. I am not able to use AD to login the the BES management interface, as far as I know that is the only thing that doesn't work. I am running 5.0.1 MR2(bundle 117).That is running on a R2 HyperV VM and tied to an E2k7 server environment. Again, if I had it to do over again I'd probably install 4.x for now. On Tue, Jun 1, 2010 at 1:50 PM, May, Jeff j...@bbandt.com wrote: Same thing stated at WES as well…sp2 gets you R2, I think you can run but not officially supported, much like the SQL clustering, can run but not officially supported yet….. And yes, the new can be 2003, we are currently in the same boat, exchange 2003 and BES 4.1.6, have a new environment with 5.0.1 on separate environment using BES Transporter to migrate, our biggest obstacle we are dealing with now is the named property limits within exchange 2003 being reached and causing migration issues for certain users. *From:* Michael B. Smith [mailto:mich...@smithcons.com] *Sent:* Tuesday, June 01, 2010 2:46 PM *To:* MS-Exchange Admin Issues *Subject:* RE: OT - BES upgrade Do you have a link? I called two weeks ago, and was told that R2 support wouldn’t be coming until 5.0 sp2. Thanks. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com *From:* Jeff Brown [mailto:2jbr...@gmail.com] *Sent:* Tuesday, June 01, 2010 2:39 PM *To:* MS-Exchange Admin Issues *Subject:* Re: OT - BES upgrade RIM support told me I could run it on R2, but only with the most recent update. On Tue, Jun 1, 2010 at 1:29 PM, Michael B. Smith mich...@smithcons.com wrote: Not supported. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com *From:* Andy Shook [mailto:andy.sh...@peak10.com] *Sent:* Tuesday, June 01, 2010 2:29 PM *To:* MS-Exchange Admin Issues *Subject:* RE: OT - BES upgrade Why not R2? Inquiring minds want to know…. Shook *From:* John Cook [mailto:john.c...@pfsf.org] *Sent:* Tuesday, June 01, 2010 2:27 PM *To:* MS-Exchange Admin Issues *Subject:* Re: OT - BES upgrade Well I just suffered through this so here goes - do backups at every stage, set up a new server (2008 SP2 not R2) if at all possible and migrate users (RIM has a tool for this)between servers. Upgrades are rarely clean or pretty. Open a case with RIM prior to starting, it will help mitigate down time. HTH John W. Cook Systems Administrator Partnership for Strong Families -- *From*: Tammy George tammy.geo...@acadiau.ca *To*: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com *Sent*: Tue Jun 01 14:19:25 2010 *Subject*: RE: OT - BES upgrade Yes. *From:* John Cook [mailto:john.c...@pfsf.org] *Sent:* June 1, 2010 3:14 PM *To:* MS-Exchange Admin Issues *Subject:* Re: OT - BES upgrade Running on server 2003? John W. Cook Systems Administrator Partnership for Strong Families -- *From*: Tammy George tammy.geo...@acadiau.ca *To*: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com *Sent*: Tue Jun 01 14:12:12 2010 *Subject*: RE: OT - BES upgrade Version 4.1.6.10 and 36 users. *From:* John Cook [mailto:john.c...@pfsf.org] *Sent:* June 1, 2010 3:06 PM *To:* MS-Exchange Admin Issues *Subject:* Re: OT - BES upgrade What version of 4.1? You'll need to upgrade to 4.1.7 first (DB changes) then 5. How many users? John W. Cook Systems Administrator Partnership for Strong Families -- *From*: Tammy George tammy.geo...@acadiau.ca *To*: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com *Sent*: Tue Jun 01 13:55:48 2010 *Subject*: OT - BES upgrade Looking for any offers of advice or suggestions – I will be upgrading our BES server from 4.1 to 5.0 in preparation for our Exchange upgrade from 2003 to 2010. I have **no** experience with BES so I need to familiarize myself with it first and go from there. Lots to learn! Just wondering if anyone is familiar with useful lists or forums? Is the process straightforward or complex? If there’s anything at all that you’d be willing to share to get me started, it would be greatly appreciated! Thanks in advance. -- Tammy George Sr. Systems Operator Technology Services Acadia University tel: (902) 585-1158 fax: (902) 585-1066 -- CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in
Re: OT - BES upgrade
They don't really publicize it, but RIM has a migration plan you can purchase. I think it costs $700, which I was willing to pay for the comfort , peace of mind and convenience. It basically allows you to have a second SRP ID and your new server and old server both connected to the BB network for 90 days. With this and the free BES migration tools, I simply setup my new server and moved users from the old system to the new one at my leisure. No moving databases, knife edge cut-overs or other silliness. The migration was easy, with no downtime for users. The only effect the migration had on users was each BB was restarted remotely one time when I moved the specific user account.to the new server. Bill Tammy George wrote: Looking for any offers of advice or suggestions -- I will be upgrading our BES server from 4.1 to 5.0 in preparation for our Exchange upgrade from 2003 to 2010. I have **no** experience with BES so I need to familiarize myself with it first and go from there. Lots to learn! Just wondering if anyone is familiar with useful lists or forums? Is the process straightforward or complex? If there's anything at all that you'd be willing to share to get me started, it would be greatly appreciated! Thanks in advance. -- Tammy George Sr. Systems Operator Technology Services Acadia University tel: (902) 585-1158 fax: (902) 585-1066
RE: OT - BES upgrade
Good point - we are using this upgrade (BES 4.1.6 on 2003 to 5.0 on virtual w/2008) as an opportunity to clear out all the old stuff in the DB and old hardware/OS etc. Transporter should allow for simple move to all new environment (it says here in the fine print). From: John Cook [mailto:john.c...@pfsf.org] Sent: Tuesday, June 01, 2010 12:07 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade You can run it on 2003 just fine but going forward do you want to keep setting up 2003 servers knowing EOS is not that many years off? John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 14:43:05 2010 Subject: RE: OT - BES upgrade Interesting... Could the new server be 2003 as opposed to 2008? From: John Cook [mailto:john.c...@pfsf.org] Sent: June 1, 2010 3:27 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade Well I just suffered through this so here goes - do backups at every stage, set up a new server (2008 SP2 not R2) if at all possible and migrate users (RIM has a tool for this)between servers. Upgrades are rarely clean or pretty. Open a case with RIM prior to starting, it will help mitigate down time. HTH John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 14:19:25 2010 Subject: RE: OT - BES upgrade Yes. From: John Cook [mailto:john.c...@pfsf.org] Sent: June 1, 2010 3:14 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade Running on server 2003? John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 14:12:12 2010 Subject: RE: OT - BES upgrade Version 4.1.6.10 and 36 users. From: John Cook [mailto:john.c...@pfsf.org] Sent: June 1, 2010 3:06 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade What version of 4.1? You'll need to upgrade to 4.1.7 first (DB changes) then 5. How many users? John W. Cook Systems Administrator Partnership for Strong Families From: Tammy George tammy.geo...@acadiau.ca To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 13:55:48 2010 Subject: OT - BES upgrade Looking for any offers of advice or suggestions - I will be upgrading our BES server from 4.1 to 5.0 in preparation for our Exchange upgrade from 2003 to 2010. I have *no* experience with BES so I need to familiarize myself with it first and go from there. Lots to learn! Just wondering if anyone is familiar with useful lists or forums? Is the process straightforward or complex? If there's anything at all that you'd be willing to share to get me started, it would be greatly appreciated! Thanks in advance. -- Tammy George Sr. Systems Operator Technology Services Acadia University tel: (902) 585-1158 fax: (902) 585-1066 CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. This email and any attached files are confidential and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of the company. Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the use of this email or attachments. CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission,
Re: OT - BES upgrade
Sorry you had to pay, I got free support, do you not have T support? John W. Cook Systems Administrator Partnership for Strong Families From: Bill Humphries nt...@hedgedigger.com To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Sent: Tue Jun 01 15:21:07 2010 Subject: Re: OT - BES upgrade They don't really publicize it, but RIM has a migration plan you can purchase. I think it costs $700, which I was willing to pay for the comfort , peace of mind and convenience. It basically allows you to have a second SRP ID and your new server and old server both connected to the BB network for 90 days. With this and the free BES migration tools, I simply setup my new server and moved users from the old system to the new one at my leisure. No moving databases, knife edge cut-overs or other silliness. The migration was easy, with no downtime for users. The only effect the migration had on users was each BB was restarted remotely one time when I moved the specific user account.to the new server. Bill Tammy George wrote: Looking for any offers of advice or suggestions – I will be upgrading our BES server from 4.1 to 5.0 in preparation for our Exchange upgrade from 2003 to 2010. I have *no* experience with BES so I need to familiarize myself with it first and go from there. Lots to learn! Just wondering if anyone is familiar with useful lists or forums? Is the process straightforward or complex? If there’s anything at all that you’d be willing to share to get me started, it would be greatly appreciated! Thanks in advance. -- Tammy George Sr. Systems Operator Technology Services Acadia University tel: (902) 585-1158 fax: (902) 585-1066 CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. This email and any attached files are confidential and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of the company. Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the use of this email or attachments.
RE: OT - BES upgrade
That's how I did it, but I didn't have to pay. It was free. From: Bill Humphries [mailto:nt...@hedgedigger.com] Sent: Tuesday, June 01, 2010 12:21 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade They don't really publicize it, but RIM has a migration plan you can purchase. I think it costs $700, which I was willing to pay for the comfort , peace of mind and convenience. It basically allows you to have a second SRP ID and your new server and old server both connected to the BB network for 90 days. With this and the free BES migration tools, I simply setup my new server and moved users from the old system to the new one at my leisure. No moving databases, knife edge cut-overs or other silliness. The migration was easy, with no downtime for users. The only effect the migration had on users was each BB was restarted remotely one time when I moved the specific user account.to the new server. Bill Tammy George wrote: Looking for any offers of advice or suggestions - I will be upgrading our BES server from 4.1 to 5.0 in preparation for our Exchange upgrade from 2003 to 2010. I have *no* experience with BES so I need to familiarize myself with it first and go from there. Lots to learn! Just wondering if anyone is familiar with useful lists or forums? Is the process straightforward or complex? If there's anything at all that you'd be willing to share to get me started, it would be greatly appreciated! Thanks in advance. -- Tammy George Sr. Systems Operator Technology Services Acadia University tel: (902) 585-1158 fax: (902) 585-1066
Re: OT - BES upgrade
They let you have two SRPs at one time without paying? I know the transporter tools were free. We do have T support, but was told no multiple SRPs without buying another server license or this migration option. Martin Blackstone wrote: That's how I did it, but I didn't have to pay. It was free. *From:* Bill Humphries [mailto:nt...@hedgedigger.com] *Sent:* Tuesday, June 01, 2010 12:21 PM *To:* MS-Exchange Admin Issues *Subject:* Re: OT - BES upgrade They don't really publicize it, but RIM has a migration plan you can purchase. I think it costs $700, which I was willing to pay for the comfort , peace of mind and convenience. It basically allows you to have a second SRP ID and your new server and old server both connected to the BB network for 90 days. With this and the free BES migration tools, I simply setup my new server and moved users from the old system to the new one at my leisure. No moving databases, knife edge cut-overs or other silliness. The migration was easy, with no downtime for users. The only effect the migration had on users was each BB was restarted remotely one time when I moved the specific user account.to the new server. Bill Tammy George wrote: Looking for any offers of advice or suggestions -- I will be upgrading our BES server from 4.1 to 5.0 in preparation for our Exchange upgrade from 2003 to 2010. I have **no** experience with BES so I need to familiarize myself with it first and go from there. Lots to learn! Just wondering if anyone is familiar with useful lists or forums? Is the process straightforward or complex? If there's anything at all that you'd be willing to share to get me started, it would be greatly appreciated! Thanks in advance. -- Tammy George Sr. Systems Operator Technology Services Acadia University tel: (902) 585-1158 fax: (902) 585-1066
RE: OT - BES upgrade
I have just done a 400 user migration. All I did was download the evaluation from RIM, entered the trial key. Then used the CALs from the live environment on the new environment and the transporter suite to move the users. Completely transparent to them that anything changed. The only thing I did ensure was that the devices were online when I moved them, so it was all done in production hours and warned the users they might see it go through the activation process. The RIM documentation is very good on the process. The only issues I have seen since the migration is where a user cannot be administrated. You click on the user and find that you cannot view their properties. Apparently this is quite common. Deleting the user then going through the reactivation process was the quick and easy fix. Simon. -- Simon Butler MVP: Exchange, MCSE Sembee Ltd. e: si...@sembee.co.uk w: http://www.sembee.co.uk/ w: http://www.amset.info/ w: http://blog.sembee.co.uk/ Need cheap certificates for Exchange, compatible with Windows Mobile 5.0? http://CertificatesForExchange.com/http://certificatesforexchange.com/ for certificates from just $23.99. Need a domain for your certificate? http://DomainsForExchange.net/http://domainsforexchange.net/ Exchange Resources: http://exbpa.com/ From: Martin Blackstone [mailto:mblackst...@gmail.com] Sent: 01 June 2010 20:33 To: MS-Exchange Admin Issues Subject: RE: OT - BES upgrade That's how I did it, but I didn't have to pay. It was free. From: Bill Humphries [mailto:nt...@hedgedigger.com] Sent: Tuesday, June 01, 2010 12:21 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade They don't really publicize it, but RIM has a migration plan you can purchase. I think it costs $700, which I was willing to pay for the comfort , peace of mind and convenience. It basically allows you to have a second SRP ID and your new server and old server both connected to the BB network for 90 days. With this and the free BES migration tools, I simply setup my new server and moved users from the old system to the new one at my leisure. No moving databases, knife edge cut-overs or other silliness. The migration was easy, with no downtime for users. The only effect the migration had on users was each BB was restarted remotely one time when I moved the specific user account.to the new server. Bill Tammy George wrote: Looking for any offers of advice or suggestions - I will be upgrading our BES server from 4.1 to 5.0 in preparation for our Exchange upgrade from 2003 to 2010. I have *no* experience with BES so I need to familiarize myself with it first and go from there. Lots to learn! Just wondering if anyone is familiar with useful lists or forums? Is the process straightforward or complex? If there's anything at all that you'd be willing to share to get me started, it would be greatly appreciated! Thanks in advance. -- Tammy George Sr. Systems Operator Technology Services Acadia University tel: (902) 585-1158 fax: (902) 585-1066
Re: OT - BES upgrade
I too was given a 90 day temporary SRP. All I did was ask. It only came with 5 CALS and would not allow me to transfer my NON-temp CAL's to it. On Tue, Jun 1, 2010 at 2:40 PM, Bill Humphries nt...@hedgedigger.comwrote: They let you have two SRPs at one time without paying? I know the transporter tools were free. We do have T support, but was told no multiple SRPs without buying another server license or this migration option. Martin Blackstone wrote: That’s how I did it, but I didn’t have to pay. It was free. *From:* Bill Humphries [mailto:nt...@hedgedigger.comnt...@hedgedigger.com] *Sent:* Tuesday, June 01, 2010 12:21 PM *To:* MS-Exchange Admin Issues *Subject:* Re: OT - BES upgrade They don't really publicize it, but RIM has a migration plan you can purchase. I think it costs $700, which I was willing to pay for the comfort , peace of mind and convenience. It basically allows you to have a second SRP ID and your new server and old server both connected to the BB network for 90 days. With this and the free BES migration tools, I simply setup my new server and moved users from the old system to the new one at my leisure. No moving databases, knife edge cut-overs or other silliness. The migration was easy, with no downtime for users. The only effect the migration had on users was each BB was restarted remotely one time when I moved the specific user account.to the new server. Bill Tammy George wrote: Looking for any offers of advice or suggestions – I will be upgrading our BES server from 4.1 to 5.0 in preparation for our Exchange upgrade from 2003 to 2010. I have **no** experience with BES so I need to familiarize myself with it first and go from there. Lots to learn! Just wondering if anyone is familiar with useful lists or forums? Is the process straightforward or complex? If there’s anything at all that you’d be willing to share to get me started, it would be greatly appreciated! Thanks in advance. -- Tammy George Sr. Systems Operator Technology Services Acadia University tel: (902) 585-1158 fax: (902) 585-1066
Several NDR's
We have a user that has been receiving hundreds of the following NDR's. The date sent on the message show yesterday which was a holiday. The user did not loogn to her OWA or was not on her computer email at all yesterday. Any ideas would be appreciated. Check machine for virus, spyware, etc. Nothing found as of yet. There was nothing in the Sent Items for any of these messages. I noticed that the to in the first part of the message with a banet.net domain and the to in the diagnostic area is winn...@camelot.co.uk. Diagnostic information for administrators: Generating server: Our Exchange Server xx...@banet.net vms169129pub.verizon.net #550 5.1.1 unknown or illegal alias: xx...@banet.net ## Original message headers: Received: from Our Exchange Server ([::1]) by Our Exchange Server ([::1]) with mapi; Mon, 31 May 2010 09:35:00 -0500 From: User email with the issue To: winn...@camelot.co.uk winn...@camelot.co.uk Date: Mon, 31 May 2010 09:35:00 -0500 Subject: =?windows-1256?Q?Sponsored_by_Camelot_Groups=FE?= Thread-Topic: =?windows-1256?Q?Sponsored_by_Camelot_Groups=FE?= Thread-Index: AQHLAM5yfeXkCvk01kyPotV89Cun4Q== Message-ID: 75d9a2b054a32b4cbfb345d89fc273d61004f1d...@isdexch1.sangcty.local Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary=_000_75D9A2B054A32B4CBFB345D89FC273D61004F1D0FDISDEXCH1SangC_ MIME-Version: 1.0
RE: Several NDR's
google joe job ...Tim -Original Message- From: Brent Zalewski [mailto:bzalew...@comcast.net] Sent: Tuesday, June 01, 2010 1:26 PM To: MS-Exchange Admin Issues Subject: Several NDR's We have a user that has been receiving hundreds of the following NDR's. The date sent on the message show yesterday which was a holiday. The user did not loogn to her OWA or was not on her computer email at all yesterday. Any ideas would be appreciated. Check machine for virus, spyware, etc. Nothing found as of yet. There was nothing in the Sent Items for any of these messages. I noticed that the to in the first part of the message with a banet.net domain and the to in the diagnostic area is winn...@camelot.co.uk. Diagnostic information for administrators: Generating server: Our Exchange Server xx...@banet.net vms169129pub.verizon.net #550 5.1.1 unknown or illegal alias: xx...@banet.net ## Original message headers: Received: from Our Exchange Server ([::1]) by Our Exchange Server ([::1]) with mapi; Mon, 31 May 2010 09:35:00 -0500 From: User email with the issue To: winn...@camelot.co.uk winn...@camelot.co.uk Date: Mon, 31 May 2010 09:35:00 -0500 Subject: =?windows-1256?Q?Sponsored_by_Camelot_Groups=FE?= Thread-Topic: =?windows-1256?Q?Sponsored_by_Camelot_Groups=FE?= Thread-Index: AQHLAM5yfeXkCvk01kyPotV89Cun4Q== Message-ID: 75d9a2b054a32b4cbfb345d89fc273d61004f1d...@isdexch1.sangcty.local Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary=_000_75D9A2B054A32B4CBFB345D89FC273D61004F1D0FDISDEXCH1SangC_ MIME-Version: 1.0
email displayed names
I'm not even sure how to ask this exactly, so bear with the rambling... We've always had names in AD and in the GAL displayed as Last name, First name. So, when a email message was sent outside the company, names appeared as Last Name, First name em...@company.commailto:em...@company.com. I was asked to change that so messages displayed the name as First name Last Name em...@company.commailto:em...@company.com. So, that was easy enough, then I get the next call... Once I got it displayed as fname lname in messages, it switched to fname lname in the GAL, but they still want it to be lname, fname in the GAL. Any ideas on how to get the best of both worlds? Jeff Jeff Jackson R.B. Zack Associates, Inc. www.rbza.comhttp://www.rbza.com Celebrating 29 Years of Service! Building Business Applications that Work Since 1981. jeff.jack...@rbza.commailto:jeff.jack...@rbza.com (310) 303-3320 x180 QUIDQUID LATINE DICTUM SIT, PROFUNDUM VIDITUR (Whatever is said in Latin appears profound) The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. Access to this e-mail by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful.
RE: OT - BES upgrade
There is a trick to allow you to use production CALs with a T SRP. Overtype the first CAL with a production CAL. Then you can add the rest of the CALs to the server. I was running with 400 CALs on both servers for over a week when I did the migration I mentioned earlier in the thread. Simon. From: Jeff Brown [mailto:2jbr...@gmail.com] Sent: 01 June 2010 20:50 To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade I too was given a 90 day temporary SRP. All I did was ask. It only came with 5 CALS and would not allow me to transfer my NON-temp CAL's to it. On Tue, Jun 1, 2010 at 2:40 PM, Bill Humphries nt...@hedgedigger.commailto:nt...@hedgedigger.com wrote: They let you have two SRPs at one time without paying? I know the transporter tools were free. We do have T support, but was told no multiple SRPs without buying another server license or this migration option. Martin Blackstone wrote: That's how I did it, but I didn't have to pay. It was free. From: Bill Humphries [mailto:nt...@hedgedigger.com] Sent: Tuesday, June 01, 2010 12:21 PM To: MS-Exchange Admin Issues Subject: Re: OT - BES upgrade They don't really publicize it, but RIM has a migration plan you can purchase. I think it costs $700, which I was willing to pay for the comfort , peace of mind and convenience. It basically allows you to have a second SRP ID and your new server and old server both connected to the BB network for 90 days. With this and the free BES migration tools, I simply setup my new server and moved users from the old system to the new one at my leisure. No moving databases, knife edge cut-overs or other silliness. The migration was easy, with no downtime for users. The only effect the migration had on users was each BB was restarted remotely one time when I moved the specific user account.tohttp://account.to the new server. Bill Tammy George wrote: Looking for any offers of advice or suggestions - I will be upgrading our BES server from 4.1 to 5.0 in preparation for our Exchange upgrade from 2003 to 2010. I have *no* experience with BES so I need to familiarize myself with it first and go from there. Lots to learn! Just wondering if anyone is familiar with useful lists or forums? Is the process straightforward or complex? If there's anything at all that you'd be willing to share to get me started, it would be greatly appreciated! Thanks in advance. -- Tammy George Sr. Systems Operator Technology Services Acadia University tel: (902) 585-1158 fax: (902) 585-1066
RE: email displayed names
What's the format on the DisplaySpecifiers versus the one in the displayName? I don't recall seen what you exposed here ~D~ From: Jeff Jackson [mailto:jeff.jack...@rbza.com] Sent: Tuesday, June 01, 2010 3:32 PM To: MS-Exchange Admin Issues Subject: email displayed names I'm not even sure how to ask this exactly, so bear with the rambling... We've always had names in AD and in the GAL displayed as Last name, First name. So, when a email message was sent outside the company, names appeared as Last Name, First name em...@company.commailto:em...@company.com. I was asked to change that so messages displayed the name as First name Last Name em...@company.commailto:em...@company.com. So, that was easy enough, then I get the next call... Once I got it displayed as fname lname in messages, it switched to fname lname in the GAL, but they still want it to be lname, fname in the GAL. Any ideas on how to get the best of both worlds? Jeff Jeff Jackson R.B. Zack Associates, Inc. www.rbza.comhttp://www.rbza.com Celebrating 29 Years of Service! Building Business Applications that Work Since 1981. jeff.jack...@rbza.commailto:jeff.jack...@rbza.com (310) 303-3320 x180 QUIDQUID LATINE DICTUM SIT, PROFUNDUM VIDITUR (Whatever is said in Latin appears profound) The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. Access to this e-mail by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful.
RE: email displayed names
How do I find the format on DisplaySpecifiers, please? If it's what I think it is, it is currently Lastname, Firstname, but I've had it set both ways. The displayName is set to Firstname Lastname, this is what I changed to get the displayed name in emails to appear Firstname Lastname em...@company.commailto:em...@company.com. Jeff From: Castillo, Daniel (Directory Services) [mailto:daniel.casti...@hp.com] Sent: Tuesday, June 01, 2010 3:47 PM To: MS-Exchange Admin Issues Subject: RE: email displayed names What's the format on the DisplaySpecifiers versus the one in the displayName? I don't recall seen what you exposed here ~D~ From: Jeff Jackson [mailto:jeff.jack...@rbza.com] Sent: Tuesday, June 01, 2010 3:32 PM To: MS-Exchange Admin Issues Subject: email displayed names I'm not even sure how to ask this exactly, so bear with the rambling... We've always had names in AD and in the GAL displayed as Last name, First name. So, when a email message was sent outside the company, names appeared as Last Name, First name em...@company.commailto:em...@company.com. I was asked to change that so messages displayed the name as First name Last Name em...@company.commailto:em...@company.com. So, that was easy enough, then I get the next call... Once I got it displayed as fname lname in messages, it switched to fname lname in the GAL, but they still want it to be lname, fname in the GAL. Any ideas on how to get the best of both worlds? Jeff Jeff Jackson R.B. Zack Associates, Inc. www.rbza.comhttp://www.rbza.com Celebrating 29 Years of Service! Building Business Applications that Work Since 1981. jeff.jack...@rbza.commailto:jeff.jack...@rbza.com (310) 303-3320 x180 QUIDQUID LATINE DICTUM SIT, PROFUNDUM VIDITUR (Whatever is said in Latin appears profound) The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. Access to this e-mail by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful.
RE: email displayed names
You might want to look at http://support.microsoft.com/kb/250455 Regards, ~D~ From: Jackson, Jeff [mailto:jeff.jack...@rbza.com] Sent: Tuesday, June 01, 2010 5:04 PM To: MS-Exchange Admin Issues Subject: RE: email displayed names How do I find the format on DisplaySpecifiers, please? If it's what I think it is, it is currently Lastname, Firstname, but I've had it set both ways. The displayName is set to Firstname Lastname, this is what I changed to get the displayed name in emails to appear Firstname Lastname em...@company.commailto:em...@company.com. Jeff From: Castillo, Daniel (Directory Services) [mailto:daniel.casti...@hp.com] Sent: Tuesday, June 01, 2010 3:47 PM To: MS-Exchange Admin Issues Subject: RE: email displayed names What's the format on the DisplaySpecifiers versus the one in the displayName? I don't recall seen what you exposed here ~D~ From: Jeff Jackson [mailto:jeff.jack...@rbza.com] Sent: Tuesday, June 01, 2010 3:32 PM To: MS-Exchange Admin Issues Subject: email displayed names I'm not even sure how to ask this exactly, so bear with the rambling... We've always had names in AD and in the GAL displayed as Last name, First name. So, when a email message was sent outside the company, names appeared as Last Name, First name em...@company.commailto:em...@company.com. I was asked to change that so messages displayed the name as First name Last Name em...@company.commailto:em...@company.com. So, that was easy enough, then I get the next call... Once I got it displayed as fname lname in messages, it switched to fname lname in the GAL, but they still want it to be lname, fname in the GAL. Any ideas on how to get the best of both worlds? Jeff Jeff Jackson R.B. Zack Associates, Inc. www.rbza.comhttp://www.rbza.com Celebrating 29 Years of Service! Building Business Applications that Work Since 1981. jeff.jack...@rbza.commailto:jeff.jack...@rbza.com (310) 303-3320 x180 QUIDQUID LATINE DICTUM SIT, PROFUNDUM VIDITUR (Whatever is said in Latin appears profound) The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. Access to this e-mail by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful.
