Testing, please ignore
Test Post ~JasonG
Re: Testing, please ignore
Fail. On Thu, May 6, 2010 at 9:33 AM, Jason Gurtz jasongu...@npumail.com wrote: Test Post ~JasonG
RE: Testing, please ignore
Seriously - there's enough traffic to this list without using it to test. From: Jonathan Link [mailto:jonathan.l...@gmail.com] Sent: Thursday, May 06, 2010 9:36 AM To: MS-Exchange Admin Issues Subject: Re: Testing, please ignore Fail. On Thu, May 6, 2010 at 9:33 AM, Jason Gurtz jasongu...@npumail.com wrote: Test Post ~JasonG CONFIDENTIALITY NOTICE: This email, including attachments, is for the sole use of the intended recipient(s) and may contain confidential and/or protected health information. Under the Federal Law (HIPAA), the intended recipient is obligated to keep this information secure and confidential. Any disclosure to third parties without authorization from the member of as permitted by law is prohibited and punishable under Federal Law. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. NOTA DE CONFIDENCIALIDAD: Este facsímile, incluyendo lo adjunto, es para el uso exclusivo del destinatario(s) y puede contener información confidencial y/o información protegida de salud. En virtud de la Ley Federal (HIPAA), el destinatario tiene la obligación de mantener esta información segura y confidencial. Cualquier divulgación a terceros sin la autorización de los miembros de lo permitido por la ley está prohibido y penado en virtud de la Ley Federal. Si usted no es el destinatario, por favor, póngase en contacto con el remitente por teléfono y destruir todas las copias del mensaje original
RE: Testing, please ignore
Actually, partial success! After two weeks with an open ticket at Cisco/Ironport they are no longer categorizing messages from this list as marketing. Now they just have to fix their submission system and I can close the ticket. With luck it will be before the end of the year. ~JasonG -Original Message- From: Jonathan Link [mailto:jonathan.l...@gmail.com] Sent: Thursday, May 06, 2010 09:36 To: MS-Exchange Admin Issues Subject: Re: Testing, please ignore Fail. On Thu, May 6, 2010 at 9:33 AM, Jason Gurtz jasongu...@npumail.com wrote: Test Post ~JasonG
Re: Testing, please ignore
Received. On 2010/05/06, at 22:40, Jason Gurtz jasongu...@npumail.com wrote: Actually, partial success! After two weeks with an open ticket at Cisco/Ironport they are no longer categorizing messages from this list as marketing. Now they just have to fix their submission system and I can close the ticket. With luck it will be before the end of the year. ~JasonG -Original Message- From: Jonathan Link [mailto:jonathan.l...@gmail.com] Sent: Thursday, May 06, 2010 09:36 To: MS-Exchange Admin Issues Subject: Re: Testing, please ignore Fail. On Thu, May 6, 2010 at 9:33 AM, Jason Gurtz jasongu...@npumail.com wrote: Test Post ~JasonG
RE: Testing, please ignore
And ingored... Now lets see how many OoO replies I get! John. -Original Message- From: Andrew Levicki [mailto:and...@levicki.me.uk] Sent: 06 May 2010 14:43 To: MS-Exchange Admin Issues Cc: MS-Exchange Admin Issues Subject: Re: Testing, please ignore Received. On 2010/05/06, at 22:40, Jason Gurtz jasongu...@npumail.com wrote: Actually, partial success! After two weeks with an open ticket at Cisco/Ironport they are no longer categorizing messages from this list as marketing. Now they just have to fix their submission system and I can close the ticket. With luck it will be before the end of the year. ~JasonG -Original Message- From: Jonathan Link [mailto:jonathan.l...@gmail.com] Sent: Thursday, May 06, 2010 09:36 To: MS-Exchange Admin Issues Subject: Re: Testing, please ignore Fail. On Thu, May 6, 2010 at 9:33 AM, Jason Gurtz jasongu...@npumail.com wrote: Test Post ~JasonG ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.clearswift.com **
Exchange 2010 OWA bottom viewing pane
*Why* did Microsoft remove the bottom viewing pane in Exchange 2010 OWA? I never liked the right side pane in Outlook and fortunately Outlook 2010 still supports the bottom pane. It makes no sense that they would support it in Outlook 2010 but not in Exchange 2010 OWA. I'm going to have some upset users when we switch...
RE: Exchange 2010 OWA bottom viewing pane
No you don't, just wait for SP1 :) See http://msexchangeteam.com/archive/2010/04/07/454533.aspx Met vriendelijke groeten, KHLim Katholieke Hogeschool Limburg Associatie KULeuven http://www.khlim.behttp://www.khlim.be/ Tim Vandael ICT Systeembeheerder Campus Diepenbeek, Agoralaan gebouw B, bus 1, 3590 Diepenbeek T +32 11 23 08 94 - F +32 11 23 07 89 - G +32 478 40 52 36 tim.vand...@khlim.bemailto:tim.vand...@khlim.be From: Paul Steele [mailto:paul.ste...@acadiau.ca] Sent: donderdag 6 mei 2010 16:14 To: MS-Exchange Admin Issues Subject: Exchange 2010 OWA bottom viewing pane *Why* did Microsoft remove the bottom viewing pane in Exchange 2010 OWA? I never liked the right side pane in Outlook and fortunately Outlook 2010 still supports the bottom pane. It makes no sense that they would support it in Outlook 2010 but not in Exchange 2010 OWA. I'm going to have some upset users when we switch... inline: image001.gif
RE: Exchange 2010 OWA bottom viewing pane
The article doesn't mention a release date. I had heard it's going to be later in the fall. What's the current rumour? From: Vandael Tim [mailto:tim.vand...@khlim.be] Sent: May-06-10 11:21 AM To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 OWA bottom viewing pane No you don't, just wait for SP1 J See http://msexchangeteam.com/archive/2010/04/07/454533.aspx Met vriendelijke groeten, KHLim Katholieke Hogeschool Limburg Associatie KULeuven http://www.khlim.be http://www.khlim.be/ Tim Vandael ICT Systeembeheerder Campus Diepenbeek, Agoralaan gebouw B, bus 1, 3590 Diepenbeek T +32 11 23 08 94 - F +32 11 23 07 89 - G +32 478 40 52 36 tim.vand...@khlim.be mailto:tim.vand...@khlim.be From: Paul Steele [mailto:paul.ste...@acadiau.ca] Sent: donderdag 6 mei 2010 16:14 To: MS-Exchange Admin Issues Subject: Exchange 2010 OWA bottom viewing pane *Why* did Microsoft remove the bottom viewing pane in Exchange 2010 OWA? I never liked the right side pane in Outlook and fortunately Outlook 2010 still supports the bottom pane. It makes no sense that they would support it in Outlook 2010 but not in Exchange 2010 OWA. I'm going to have some upset users when we switch... image001.gif
RE: FYI - MSFT doesn't tell all it knows
I don't think that that has ever been hidden info. Exchange, since at least 5.5, has had the option of using different DNS servers for outgoing resolution; somewhat necessitating it having a different resolver. (This doesn't mean that I defend them fixing things they didn't tell about.) Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -Original Message- From: Ben Scott [mailto:mailvor...@gmail.com] Sent: Thursday, May 06, 2010 11:09 AM To: MS-Exchange Admin Issues Subject: Re: FYI - MSFT doesn't tell all it knows On Thu, May 6, 2010 at 10:12 AM, Carol Fee c...@massbar.org wrote: If the SMTP doesn't use the operating system resolver, where does it find the DNS servers that it uses ? Only Microsoft knows for sure, but my guess is that Exchange gets the IP address(es) of your full-service resolvers from the OS, but then uses its own internal stub resolver implementation. -- Ben
Anyone using FortiGate as a spam filter?
Looking for some operational experiences. ~JasonG
Re: FYI - MSFT doesn't tell all it knows
On Thu, May 6, 2010 at 11:17 AM, Michael B. Smith mich...@smithcons.com wrote: Exchange, since at least 5.5, has had the option of using different DNS servers for outgoing resolution; somewhat necessitating it having a different resolver. I don't know anything about what the DNS resolver code on Windows looks like, but on *nix, at least, you can simply call the resolver library routines with a different configuration structure. It's all the same code; no fork needed. -- Ben
Re: Anyone using FortiGate as a spam filter?
We paid for the service but turned it off, it gave almost no control over what it does with spam, was difficult to know if missing mail was being rejected by the filter or something else... very little management options. On Thu, May 6, 2010 at 10:24 AM, Jason Gurtz jasongu...@npumail.com wrote: Looking for some operational experiences. ~JasonG
RE: Anyone using FortiGate as a spam filter?
Yes we do, However we have it simply add to the subject line ==SPAM== we then have a rule on our GATEWAY (Policy Patrol) which move these to a Folder. Policy patrol allows users to check their spam folders via a 2hourly email notification and release if required. But do we have Fortigate drop or reject? No. From: Jeff Brown [mailto:2jbr...@gmail.com] Sent: donderdag 6 mei 2010 17:30 To: MS-Exchange Admin Issues Subject: Re: Anyone using FortiGate as a spam filter? We paid for the service but turned it off, it gave almost no control over what it does with spam, was difficult to know if missing mail was being rejected by the filter or something else... very little management options. On Thu, May 6, 2010 at 10:24 AM, Jason Gurtz jasongu...@npumail.commailto:jasongu...@npumail.com wrote: Looking for some operational experiences. ~JasonG DISCLAIMER 5/6/2010 5:50:15 PM This communication is intended only for use by MS-Exchange Admin Issues. It may contain confidential or privileged information. If you receive this communication unintentionally, please inform us immediately. Thank you. 180 has registered companies in the United States and in the Netherlands. 180 Los Angeles LLC . (180) 1424 Second Street, Suite 200 and 300, Santa Monica, California 90401, is registered with the trade register in the US in Delaware under file number 4260284 and the corporation's FEIN is 20-5982098. 180 Amsterdam BV (180) Herengracht 506, 1017 CB, Amsterdam is registered with the trade register in the Netherlands under number 34253037 and VAT number NL8161.54.673.B.01. The content of this communications is not legally binding unless confirmed by letter or telefax. Please note that 180 is neither liable for the proper transmission nor for the complete transmission of the information contained in this communication or for any delay in its receipt. Also please note that the confidentiality of email communication is not warranted. All services and other work provided by 180 are subject to our general conditions (supplier terms and conditions). The conditions are available for inspection at Herengracht 506, Amsterdam and at the Chamber of Commerce in Amsterdam. If you wish to receive a hard copy of these conditions, please send an e-mail with your address to i...@180amsterdam.commailto:i...@180amsterdam.com In the event you send to 180 any unsolicited ideas and/or materials (whether consisting of texts, images, sounds, software, information or otherwise) (Materials) by e-mail or otherwise, 180 shall be entitled to use, copy and/or commercially exploit such Materials to the fullest extent, free of charge and 180 will not be bound by any confidentiality obligation in respect thereof.
Sharing Calendars
Hello all... We have a need to share both Outlook 2003 and 2007 calendars with people outside of our Exchange org. Is there a 3rd party app that you could recommend for this? We have Exchange 2003 fully patched. Thanks! Bill Lambert Windows System Administrator Concuity Phone 847-941-9206 Fax 847-465-9147 The information contained in this e-mail message, including any attached files, is intended only for the personal and confidential use of the recipient(s) named above. If you are not the intended recipient (or authorized to receive information for the recipient) you are hereby notified that you have received this communication in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all copies of this message. Thank you. image001.jpg
Re: Sharing Calendars
Bill, I had a similar challenge last year and handled it by creating an exchange account for the outsiders. I removed logon permissions from the rest of the machines in my domain and had the outsiders use OWA to see the calendars they needed. Now they can see the calendars they need, and schedule meetings with internal contacts without needing to call up an admin and have them check calendars for them. -Bill On Thu, May 6, 2010 at 9:06 AM, Bill Lambert blamb...@concuity.com wrote: Hello all… We have a need to share both Outlook 2003 and 2007 calendars with people outside of our Exchange org. Is there a 3rd party app that you could recommend for this? We have Exchange 2003 fully patched. Thanks! *Bill Lambert* *Windows System Administrator* *Concuity* *Phone 847-941-9206* *Fax 847-465-9147* [image: concuityABC] *The information contained in this e-mail message, including any attached files, is intended only for the personal and confidential use of the recipient(s) named above. If you are not the intended recipient (or authorized to receive information for the recipient) you are hereby notified that you have received this communication in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all copies of this message. Thank you. *** image001.jpg
RE: Sharing Calendars
Thanks for the reply, Bill, and it's a great idea. I'll definitely consider that if a 3rd party app isn't too expensive. Bill Lambert Concuity Phone 847-941-9206 The information contained in this e-mail message, including any attached files, is intended only for the personal and confidential use of the recipient(s) named above. If you are not the intended recipient (or authorized to receive information for the recipient) you are hereby notified that you have received this communication in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all copies of this message. Thank you. From: Bill Songstad [mailto:bsongs...@gmail.com] Sent: Thursday, May 06, 2010 11:18 AM To: MS-Exchange Admin Issues Subject: Re: Sharing Calendars Bill, I had a similar challenge last year and handled it by creating an exchange account for the outsiders. I removed logon permissions from the rest of the machines in my domain and had the outsiders use OWA to see the calendars they needed. Now they can see the calendars they need, and schedule meetings with internal contacts without needing to call up an admin and have them check calendars for them. -Bill On Thu, May 6, 2010 at 9:06 AM, Bill Lambert blamb...@concuity.com wrote: Hello all... We have a need to share both Outlook 2003 and 2007 calendars with people outside of our Exchange org. Is there a 3rd party app that you could recommend for this? We have Exchange 2003 fully patched. Thanks! Bill Lambert Windows System Administrator Concuity Phone 847-941-9206 Fax 847-465-9147 The information contained in this e-mail message, including any attached files, is intended only for the personal and confidential use of the recipient(s) named above. If you are not the intended recipient (or authorized to receive information for the recipient) you are hereby notified that you have received this communication in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all copies of this message. Thank you. image001.jpg
RE: Testing, please ignore
Yeah right, like anyone on this list can ignore anything. Come on, we are geeks and this is our social life. J Thank You ~Doug Rooney Sonoma Tilemakers IT Manager 7750 Bell Rd. Windsor Ca, 95492 i...@sonomatilemakers.com mailto:i...@sonomatilemakers.com -Original Message- From: Jason Gurtz [mailto:jasongu...@npumail.com] Sent: Thursday, May 06, 2010 6:34 AM To: MS-Exchange Admin Issues Subject: Testing, please ignore Test Post ~JasonG
RE: Testing, please ignore
Yeah, but do you have to remind us? Roger Scudder Consultant From: Doug Rooney [mailto:d...@sonomatilemakers.com] Sent: Thursday, May 06, 2010 12:28 PM To: MS-Exchange Admin Issues Subject: RE: Testing, please ignore Yeah right, like anyone on this list can ignore anything. Come on, we are geeks and this is our social life. J Thank You ~Doug Rooney Sonoma Tilemakers IT Manager 7750 Bell Rd. Windsor Ca, 95492 i...@sonomatilemakers.com -Original Message- From: Jason Gurtz [mailto:jasongu...@npumail.com] Sent: Thursday, May 06, 2010 6:34 AM To: MS-Exchange Admin Issues Subject: Testing, please ignore Test Post ~JasonG
Re: Testing, please ignore
On Thu, May 6, 2010 at 12:28 PM, Doug Rooney d...@sonomatilemakers.com wrote: Yeah right, like anyone on this list can ignore anything. Come on, we are geeks and this is our social life. J Hey, I resemble that remark! -- Ben
Exporting to PST
I am trying to export a mailbox in Exchange 2007, sp2 using Powershell. The command-let is Export-Mailbox -Identity username -PSTFolderPath c:\username.pst. StatusCode : -1056749164 StatusMessage: Error occurred in the step: Moving messages. Failed to copy messages to the destinat ion mailbox store with error: MAPI or an unspecified service provider. ID no: -- I have added/removed, added again, full rights to the mailbox for myself, and another user. I still get the same error. I have done this numerous times in the past without issue. Any ideas? Thanks!
RE: Exporting to PST
Mailbox over 2gigs? Try a different folder path? Anthony Shields Systems Administrator The Epstein School (404) 250-5659 From: Chris Blair [mailto:chris_bl...@identisys.com] Sent: Thursday, May 06, 2010 4:04 PM To: MS-Exchange Admin Issues Subject: Exporting to PST I am trying to export a mailbox in Exchange 2007, sp2 using Powershell. The command-let is Export-Mailbox -Identity username -PSTFolderPath c:\username.pst. StatusCode : -1056749164 StatusMessage: Error occurred in the step: Moving messages. Failed to copy messages to the destinat ion mailbox store with error: MAPI or an unspecified service provider. ID no: -- I have added/removed, added again, full rights to the mailbox for myself, and another user. I still get the same error. I have done this numerous times in the past without issue. Any ideas? Thanks! The Epstein School is a proud beneficiary of the Jewish Federation of Greater Atlanta.
RE: Exporting to PST
Mailbox is over 2gigs, almost 4 gigs. The machine I am running this on has Office 2007 installed, and I have exported 8 GB mailboxes before. Using different paths gives the same error. From: Shields, Anthony [mailto:ashie...@epsteinatlanta.org] Sent: Thursday, May 06, 2010 3:08 PM To: MS-Exchange Admin Issues Subject: RE: Exporting to PST Mailbox over 2gigs? Try a different folder path? Anthony Shields Systems Administrator The Epstein School (404) 250-5659 From: Chris Blair [mailto:chris_bl...@identisys.com] Sent: Thursday, May 06, 2010 4:04 PM To: MS-Exchange Admin Issues Subject: Exporting to PST I am trying to export a mailbox in Exchange 2007, sp2 using Powershell. The command-let is Export-Mailbox -Identity username -PSTFolderPath c:\username.pst. StatusCode : -1056749164 StatusMessage: Error occurred in the step: Moving messages. Failed to copy messages to the destinat ion mailbox store with error: MAPI or an unspecified service provider. ID no: -- I have added/removed, added again, full rights to the mailbox for myself, and another user. I still get the same error. I have done this numerous times in the past without issue. Any ideas? Thanks! The Epstein School is a proud beneficiary of the Jewish Federation of Greater Atlanta.
RE: Exporting to PST
Mailbox is over 2gigs, almost 4 gigs. The machine I am running this on has Office 2007 installed, and I have exported 8 GB mailboxes before. Yeah not an issue no more... Got all the perms you need? http://technet.microsoft.com/en-us/library/bb266964%28EXCHG.80%29.aspx helpful error id #:)
More Digital Cert woes (somewhat off topic)
I got the cert for our 2010 CAS server installed successfully this morning (Thanks Michael B.) Everything was flowing smoothly for a few hours, so we decided to export the cert install it on our 2007 CAS server. We'll be using both for several days/weeks as we migrate fully to 2010. (Split DNS, trying to economize on names in the SAN as much as possible.) The cert does not have the 2007 CAS server name as one of the SAN entries. We changed all the internal URLs that looked pertinent to a name that was a SAN entry, but now we are getting this error from Communicator: --- Microsoft Office Communicator 2007 --- Communicator is in the process of trying to locate your Exchange Web Services. Your Outlook calendar information and Out of Office message may not be available and your calls may not be forwarded based on your working hours. --- OK --- This error occurs as Communicator is starting up; if you click YES on the digital cert nag (2 green check marks, then a red X on The name on the security certificate is invalid or does not match the name of the site) that pops up with it Communicator starts with no other issues. You then get the same nag (2 green checkmarks the red X) when you start Outlook. Any suggestions as to what else I need to change to get rid of the nag?
RE: Exporting to PST
I have all the perms, even removed them and added them again to make sure they are really there. I found a forum post somewhere saying to reboot. I will try that tonight and let everyone know. Thanks for the help. -Original Message- From: Joseph L. Casale [mailto:jcas...@activenetwerx.com] Sent: Thursday, May 06, 2010 3:14 PM To: MS-Exchange Admin Issues Subject: RE: Exporting to PST Mailbox is over 2gigs, almost 4 gigs. The machine I am running this on has Office 2007 installed, and I have exported 8 GB mailboxes before. Yeah not an issue no more... Got all the perms you need? http://technet.microsoft.com/en-us/library/bb266964%28EXCHG.80%29.aspx helpful error id #:)
RE: Exporting to PST
I found a forum post somewhere saying to reboot. I will try that tonight and let everyone know. Heh, it just needs 15 minutes or whatever the time period is before the perms get refreshed. You could simply restart the store as well. If they were set, sounds like something else is messed up. I can't recall having issues in a few years w/ that but you're wkst isn't 64 bit is it?
Re: Exporting to PST
If you have BES, try using the BESAdmin account. BES should definitely have all the perms Does your PST path have a . at the end of the file name? Existing PST with same name? On Thu, May 6, 2010 at 1:04 PM, Chris Blair chris_bl...@identisys.comwrote: I am trying to export a mailbox in Exchange 2007, sp2 using Powershell. The command-let is “Export-Mailbox -Identity username -PSTFolderPath c:\username.pst.” StatusCode : -1056749164 StatusMessage: Error occurred in the step: Moving messages. Failed to copy messages to the destinat ion mailbox store with error: MAPI or an unspecified service provider. ID no: -- I have added/removed, added again, full rights to the mailbox for myself, and another user. I still get the same error. I have done this numerous times in the past without issue. Any ideas? Thanks!
RE: Exporting to PST
I let the permission stew overnight, and still getting the same error. No it's 32 bit workstation. -Original Message- From: Joseph L. Casale [mailto:jcas...@activenetwerx.com] Sent: Thursday, May 06, 2010 3:54 PM To: MS-Exchange Admin Issues Subject: RE: Exporting to PST I found a forum post somewhere saying to reboot. I will try that tonight and let everyone know. Heh, it just needs 15 minutes or whatever the time period is before the perms get refreshed. You could simply restart the store as well. If they were set, sounds like something else is messed up. I can't recall having issues in a few years w/ that but you're wkst isn't 64 bit is it?
Another Export-Mailbox question
I am creating a powershell script that can export several mailboxes to PST of users that are going to be disabled and deleted. I know there is a XML and on screen logging when you run export-mailbox but is there any way to add error checking into a script that will verify the mailbox exported successfully? I want the script to be automated so if it fails on the PST export it will not do anything else to the account.
Can Powershell do this?
As we proceed with our Exchange 2010 migration, I discovered that some mailboxes appear corrupted to powershell users, resulting in this error: [PS] C:\get-mailbox -identity rmurphy WARNING: The object ad.acadiau.ca/academic/rmurphy has been corrupted, and it's in an inconsistent state. The following validation errors happened: WARNING: Property expression rmurphy isn't valid. Valid values are: Strings that includes '@', where '@' cannot be the last character After some digging I discovered that the AD account attribute UserPrincipleName does not have a domain associated with it (e.g. 'rmurphy' instead of 'rmur...@domain'). This can be fixed easily in ADUC under the Account tab, but with over 100 users in this state I'd like to find a programmatic way of doing it. I could whip together a C# or VB script to fix the problem, but I was wondering if this sort of thing could be done in PowerShell. I'm still learning PS but from what I've seen I think the answer is yes. Anyone PowerShell experts out there?
RE: Can Powershell do this?
Yes. Just set the userPrincipalName attribute. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -Original Message- From: Paul Steele [mailto:paul.ste...@acadiau.ca] Sent: Thursday, May 06, 2010 7:07 PM To: MS-Exchange Admin Issues Subject: Can Powershell do this? As we proceed with our Exchange 2010 migration, I discovered that some mailboxes appear corrupted to powershell users, resulting in this error: [PS] C:\get-mailbox -identity rmurphy WARNING: The object ad.acadiau.ca/academic/rmurphy has been corrupted, and it's in an inconsistent state. The following validation errors happened: WARNING: Property expression rmurphy isn't valid. Valid values are: Strings that includes '@', where '@' cannot be the last character After some digging I discovered that the AD account attribute UserPrincipleName does not have a domain associated with it (e.g. 'rmurphy' instead of 'rmur...@domain'). This can be fixed easily in ADUC under the Account tab, but with over 100 users in this state I'd like to find a programmatic way of doing it. I could whip together a C# or VB script to fix the problem, but I was wondering if this sort of thing could be done in PowerShell. I'm still learning PS but from what I've seen I think the answer is yes. Anyone PowerShell experts out there?
Re: Can Powershell do this?
Here are some great examples on how to manipulate AD attributes using Powershell and Quest PowerShell Commands for Active Directory: http://www.quest.com/activeroles-server/powershelldemo/chap00.htm http://dmitrysotnikov.wordpress.com/2007/07/16/programmatically-manipulate-ad-user-attributes-with-powershell/
RE: Exporting to PST
2 hours for permissions. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -Original Message- From: Joseph L. Casale [mailto:jcas...@activenetwerx.com] Sent: Thursday, May 06, 2010 4:54 PM To: MS-Exchange Admin Issues Subject: RE: Exporting to PST I found a forum post somewhere saying to reboot. I will try that tonight and let everyone know. Heh, it just needs 15 minutes or whatever the time period is before the perms get refreshed. You could simply restart the store as well. If they were set, sounds like something else is messed up. I can't recall having issues in a few years w/ that but you're wkst isn't 64 bit is it?
RE: More Digital Cert woes (somewhat off topic)
The internal EWS URL (Set-WebServicesVirtualDirectory) and the EXCH CertPrincipalName (Set-OutlookProvider) Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Russ Patterson [mailto:rus...@gmail.com] Sent: Thursday, May 06, 2010 4:41 PM To: MS-Exchange Admin Issues Subject: More Digital Cert woes (somewhat off topic) I got the cert for our 2010 CAS server installed successfully this morning (Thanks Michael B.) Everything was flowing smoothly for a few hours, so we decided to export the cert install it on our 2007 CAS server. We'll be using both for several days/weeks as we migrate fully to 2010. (Split DNS, trying to economize on names in the SAN as much as possible.) The cert does not have the 2007 CAS server name as one of the SAN entries. We changed all the internal URLs that looked pertinent to a name that was a SAN entry, but now we are getting this error from Communicator: --- Microsoft Office Communicator 2007 --- Communicator is in the process of trying to locate your Exchange Web Services. Your Outlook calendar information and Out of Office message may not be available and your calls may not be forwarded based on your working hours. --- OK --- This error occurs as Communicator is starting up; if you click YES on the digital cert nag (2 green check marks, then a red X on The name on the security certificate is invalid or does not match the name of the site) that pops up with it Communicator starts with no other issues. You then get the same nag (2 green checkmarks the red X) when you start Outlook. Any suggestions as to what else I need to change to get rid of the nag?
Re: Can Powershell do this?
I found some things wrong in my last post this is a little better.
$users - get-qaduser
Foreach ($user in $users){
$sam = $user.samaccountname
set-qaduser $sam -UserPrincipalName $...@domain.local
}
On Thu, May 6, 2010 at 7:26 PM, KenM kenmli...@gmail.com wrote:
You can do sometihng like this with the quest cmdlts
I dont know your environment so this may not work for you and may need a
little tweaking if you have over 1000 users in your domain. Can make it more
efficient with a LDAP filter looking for users without a UPN.
$user = get-qaduser
Foreach($user in $users) {set-qaduser $user.samaccountname
-Userprincipalname '$user.samaccountn...@domain.local'}
On Thu, May 6, 2010 at 7:06 PM, Paul Steele paul.ste...@acadiau.cawrote:
As we proceed with our Exchange 2010 migration, I discovered that some
mailboxes appear corrupted to powershell users, resulting in this error:
[PS] C:\get-mailbox -identity rmurphy
WARNING: The object ad.acadiau.ca/academic/rmurphy has been corrupted,
and it's in an
inconsistent state. The following validation errors happened:
WARNING: Property expression rmurphy isn't valid. Valid values are:
Strings that includes '@',
where '@' cannot be the last character
After some digging I discovered that the AD account attribute
UserPrincipleName does not have a domain associated with it (e.g.
'rmurphy' instead of 'rmur...@domain'). This can be fixed easily in ADUC
under the Account tab, but with over 100 users in this state I'd like to
find a programmatic way of doing it. I could whip together a C# or VB
script to fix the problem, but I was wondering if this sort of thing
could be done in PowerShell. I'm still learning PS but from what I've
seen I think the answer is yes. Anyone PowerShell experts out there?
RE: Exporting to PST
What's your version? (SP and UR?) This error can result from permissions or from having a too old UR/SP combination. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Chris Blair [mailto:chris_bl...@identisys.com] Sent: Thursday, May 06, 2010 4:11 PM To: MS-Exchange Admin Issues Subject: RE: Exporting to PST Mailbox is over 2gigs, almost 4 gigs. The machine I am running this on has Office 2007 installed, and I have exported 8 GB mailboxes before. Using different paths gives the same error. From: Shields, Anthony [mailto:ashie...@epsteinatlanta.org] Sent: Thursday, May 06, 2010 3:08 PM To: MS-Exchange Admin Issues Subject: RE: Exporting to PST Mailbox over 2gigs? Try a different folder path? Anthony Shields Systems Administrator The Epstein School (404) 250-5659 From: Chris Blair [mailto:chris_bl...@identisys.com] Sent: Thursday, May 06, 2010 4:04 PM To: MS-Exchange Admin Issues Subject: Exporting to PST I am trying to export a mailbox in Exchange 2007, sp2 using Powershell. The command-let is Export-Mailbox -Identity username -PSTFolderPath c:\username.pst. StatusCode : -1056749164 StatusMessage: Error occurred in the step: Moving messages. Failed to copy messages to the destinat ion mailbox store with error: MAPI or an unspecified service provider. ID no: -- I have added/removed, added again, full rights to the mailbox for myself, and another user. I still get the same error. I have done this numerous times in the past without issue. Any ideas? Thanks! The Epstein School is a proud beneficiary of the Jewish Federation of Greater Atlanta.
RE: Another Export-Mailbox question
Just test the command:
If (blah...) { Do the rest..} etc
From: KenM [mailto:kenmli...@gmail.com]
Sent: Thursday, May 06, 2010 5:03 PM
To: MS-Exchange Admin Issues
Subject: Another Export-Mailbox question
I am creating a powershell script that can export several mailboxes to PST of
users that are going to be disabled and deleted. I know there is a XML and on
screen logging when you run export-mailbox but is there any way to add error
checking into a script that will verify the mailbox exported successfully? I
want the script to be automated so if it fails on the PST export it will not do
anything else to the account.
RE: Can Powershell do this?
Looks similar to C# or VBscript. I'll have to track down the Quest
cmdlet stuff and give it a try...
From: KenM [mailto:kenmli...@gmail.com]
Sent: May-06-10 9:37 PM
To: MS-Exchange Admin Issues
Subject: Re: Can Powershell do this?
I found some things wrong in my last post this is a little better.
$users - get-qaduser
Foreach ($user in $users){
$sam = $user.samaccountname
set-qaduser $sam -UserPrincipalName $...@domain.local
}
On Thu, May 6, 2010 at 7:26 PM, KenM kenmli...@gmail.com wrote:
You can do sometihng like this with the quest cmdlts
I dont know your environment so this may not work for you and may need a
little tweaking if you have over 1000 users in your domain. Can make it
more efficient with a LDAP filter looking for users without a UPN.
$user = get-qaduser
Foreach($user in $users) {set-qaduser $user.samaccountname
-Userprincipalname '$user.samaccountn...@domain.local'}
On Thu, May 6, 2010 at 7:06 PM, Paul Steele paul.ste...@acadiau.ca
wrote:
As we proceed with our Exchange 2010 migration, I discovered
that some
mailboxes appear corrupted to powershell users, resulting in
this error:
[PS] C:\get-mailbox -identity rmurphy
WARNING: The object ad.acadiau.ca/academic/rmurphy has been
corrupted,
and it's in an
inconsistent state. The following validation errors happened:
WARNING: Property expression rmurphy isn't valid. Valid values
are:
Strings that includes '@',
where '@' cannot be the last character
After some digging I discovered that the AD account attribute
UserPrincipleName does not have a domain associated with it
(e.g.
'rmurphy' instead of 'rmur...@domain'). This can be fixed easily
in ADUC
under the Account tab, but with over 100 users in this state I'd
like to
find a programmatic way of doing it. I could whip together a C#
or VB
script to fix the problem, but I was wondering if this sort of
thing
could be done in PowerShell. I'm still learning PS but from what
I've
seen I think the answer is yes. Anyone PowerShell experts out
there?
RE: Can Powershell do this?
C# is on the glide path from PowerShell.
You don't need the Quest cmdlets, you just need get-mailbox and set-mailbox;
which are built-in cmdlets for Exchange.
Regards,
Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com
From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: Thursday, May 06, 2010 9:53 PM
To: MS-Exchange Admin Issues
Subject: RE: Can Powershell do this?
Looks similar to C# or VBscript. I'll have to track down the Quest cmdlet stuff
and give it a try...
From: KenM [mailto:kenmli...@gmail.com]
Sent: May-06-10 9:37 PM
To: MS-Exchange Admin Issues
Subject: Re: Can Powershell do this?
I found some things wrong in my last post this is a little better.
$users - get-qaduser
Foreach ($user in $users){
$sam = $user.samaccountname
set-qaduser $sam -UserPrincipalName $...@domain.localmailto:$...@domain.local
}
On Thu, May 6, 2010 at 7:26 PM, KenM
kenmli...@gmail.commailto:kenmli...@gmail.com wrote:
You can do sometihng like this with the quest cmdlts
I dont know your environment so this may not work for you and may need a little
tweaking if you have over 1000 users in your domain. Can make it more efficient
with a LDAP filter looking for users without a UPN.
$user = get-qaduser
Foreach($user in $users) {set-qaduser $user.samaccountname -Userprincipalname
'$user.samaccountn...@domain.local'mailto:'$user.samaccountn...@domain.local'}
On Thu, May 6, 2010 at 7:06 PM, Paul Steele
paul.ste...@acadiau.camailto:paul.ste...@acadiau.ca wrote:
As we proceed with our Exchange 2010 migration, I discovered that some
mailboxes appear corrupted to powershell users, resulting in this error:
[PS] C:\get-mailbox -identity rmurphy
WARNING: The object
ad.acadiau.ca/academic/rmurphyhttp://ad.acadiau.ca/academic/rmurphy has been
corrupted,
and it's in an
inconsistent state. The following validation errors happened:
WARNING: Property expression rmurphy isn't valid. Valid values are:
Strings that includes '@',
where '@' cannot be the last character
After some digging I discovered that the AD account attribute
UserPrincipleName does not have a domain associated with it (e.g.
'rmurphy' instead of 'rmur...@domain'). This can be fixed easily in ADUC
under the Account tab, but with over 100 users in this state I'd like to
find a programmatic way of doing it. I could whip together a C# or VB
script to fix the problem, but I was wondering if this sort of thing
could be done in PowerShell. I'm still learning PS but from what I've
seen I think the answer is yes. Anyone PowerShell experts out there?
