Pages

Search

Suggestions wanted for drive configuration for new Exchange 2003 server - Microsoft Exchange

Suggestions wanted for drive configuration for new Exchange 2003 server - Microsoft Exchange

Suggestions wanted for drive configuration for new Exchange 2003 server

Posted: 20 Sep 2007 05:46 PM PDT

Exactly. The reason you will want to use two databases is in the event one
fails your time to restore is half that of a 100 GB database. You could
break it down into four databases if you want.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"Mike O" <can> wrote in message
news:ON4jk7%23%phx.gbl... 

move to exchange 2003

Posted: 20 Sep 2007 12:52 AM PDT

OOI - Why 2003?

"Janaka Sampath" wrote:
 

Problem moving Public folders with "Move all replicas"

Posted: 19 Sep 2007 09:01 PM PDT

Hello Customer,

Thank you for update.

Thanks Ed for the input. Ed is correct, you need the Exchange
administrative rights of your logon user account.

I also think this is a permission issue. Please try the following steps:

1. Start ADSI Edit. In the CN=Configuration container, locate the
following container (where ORGANIZATION is the name of your Exchange 2000
or Exchange 2003 organization and administrative_group is the name of your
administrative group):
CN=Services,CN=Microsoft Exchange,CN= ORGANIZATION ,CN=Administrative
Groups,CN= administrative_group ,CN=Folder Hierarchies,CN=Public Folders
2. Right-click CN=Public Folders , and then click Properties .
3. Click the Security tab.
4. Make sure that the Allow inheritable permissions from parent to
propagate to this object check box is selected.
5. Make sure that the Everyone group has the following Allow permissions:

a. Create named properties in the information store
b. Create public folder
c. Create top level public folder

If the Allow inheritable permissions from parent to propagate to this
object check box is selected, the Everyone group should already have these
permissions. Make sure that the Deny check boxes are not selected.

For detail steps:

You Cannot Create a New Public Folder in Exchange 2000 Server or in
Exchange Server 2003
http://support.microsoft.com/?id=313866

I hope these steps will give you some help.

Thanks and have a nice day!

Best regards,

Terence Liu(MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

================================================== ===
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
================================================== ===

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Date: Thu, 20 Sep 2007 14:13:24 -0500
| From: Jonathan <noemail>
| User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
| MIME-Version: 1.0
| Subject: Re: Problem moving Public folders with "Move all s"
| References: <eBpPhrz#phx.gbl>
<46K3pl2#phx.gbl>
| In-Reply-To: <46K3pl2#phx.gbl>
| Content-Type: text/plain; cht=ISO-8859-1; format=flowed
| Content-Transfer-Encoding: 7bit
| Message-ID: <ex$uPp7#phx.gbl>
| Newsgroups: microsoft.public.exchange.misc
| NNTP-Posting-Host: 76.201.159.11
| Lines: 1
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSF TNGP02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.exchange.misc:4331
| X-Tomcat-NG: microsoft.public.exchange.misc
|
| Thanks for the suggestions Terence. I tried all your suggestions but am
| still in much the same situation.
|
| Unfortunately I cannot see permissions for individual public folders so
| I couldn't check those. The folders appear in outlook when I connect to
| an Exchange account on the old server but when I Right-click a folder
| and select properties I get the message "Can't display folder
| properties." I also get "Unable to display the folder" when I select a
| folder.
|
| All the permissions are set through Exchange System Manager as you
| described with two exceptions: I had already given "Everyone" Full
| Control of Public Folders on both servers. Also I am unfamiliar with an
| account called Exchange Services. It does not seem to exist on either
| server and I don't recall seeing it on other servers. Could it perhaps
| exist by another name? The local server (servername$) does have full
| control on both machines.
|
| I turned on the additional logging suggested in kb842273 and now notice
| that when I try to access the public folders on the old server using a
| temporary account I created (all the other mailboxes have already been
| moved to the new server) I get the following error:
|
| Event Type: Warning
| Event Source: MchangeIS Public Store
| Event Category: Access Control
| Event ID: 1030
| Date: 9/20/2007
| Time: 1:03:41 PM
| User: N/A
| Computer: BART
| Description:
| org failed an operation on folder
| /O=SPRINGFIELD/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=LISA
| EMAIL8E49E84E42B6B74BF6EF36926863E4C401F40E on database "First Storage
| Group\Public Folder Store (BART)" because the user did not have the
| following access rights:
|
| 'Delete' 'Read Property' 'Write Property' 'Create Message' 'View Item'
| 'Create Subfolder' 'Write Security Descriptor' 'Write Owner' 'Read
| Security Descriptor' 'Contact'
|
| The entry ID of the folder is in the data section of this event.
|
| For more information, click http://www.microsoft.com/contentredirect.asp.
|
| This is strange since, as I mentioned above, I have given Everyone Full
| Control. I have also added temp1 individually and given the account Full
| Control to public folders. I find that I also get a mixture of similar
| 1030 events and success events when I use the administrator account to
| add things to public folders on the new computer (which I could do
| successfully).
|
| I tried all the other suggestions in the article you suggested
| (kb842273). Unfortunately none of the applicable suggestions in the
| article solved my problem. Once of the steps in the article did provide
| new information but I can't see any way to apply it toward a solution:
| Message tracking shows messages addressed to the Public Folder Store on
| the new server as successfully categorized, etc., then routed, queued
| for remote delivery and then "transferred to Bart.springfield.local [the
| old server] through smtp." But nothing shows up as having been received
| on the new server (Marge). This essentially confirms what the event logs
| are already telling me.
|
| I would appreciate any further ideas anyone might have. Is there a way
| to cancel the tion (move all s) process? If I could just
| regain access to the public folders on the old server I could copy them
| to a pst file using Outlook and move them that way. Since the old server
| will be retired once I get these &%(#!@*^ public folders moved there is
| no long term need for the two servers to communicate successfully.
|
|
|
|
|
| Terence Liu [MSFT] wrote:
| > Hello Customer,
| >
| > Thank you for posting here.
| >
| > According to your description, I understand that you get public folder
| > error 1235 when you try to te it between 2 Exchanges. If I have
| > misunderstood the problem, please don't hesitate to let me know.
| >
| > Based on my research, this behavior may occur if either of the
following
| > conditions is true:
| > 1. The public folder that you want to restore is set to allow only
certain
| > custom forms.
| > 2. You do not have the appropriate permissions to access the public
folder
| > hierarchy.
| >
| > I suggest we try the following steps to see if we can resolve this
issue:
| >
| > I. The public folder is set to allow only certain custom forms
| > To resolve this behavior, follow these steps:
| > 1. Log on to an Outlook client computer as a user who has owner
| > permissions for the public folder.
| > 2. Right-click the folder that you want to restore, and then click
| > Properties.
| > 3. Click the Forms tab.
| > 4. In the Allow these forms in this folder section, click Any form,
and
| > then click OK.
| >
| > II. You do not have the appropriate permissions to access the public
folder
| > hierarchy
| > To troubleshoot and resolve this behavior, make sure that appropriate
| > permissions are configured for the public folder hierarchy, temporarily
| > grant the Everyone group Full Control permissions, recover the deleted
| > items from the public folders, and then restore the default permissions
for
| > the Everyone group. To do so, follow these steps:
| >
| > 1. Make sure that the appropriate permissions are configured for the
| > public folder hierarchy:
| > a. Click Start, point to Programs, point to Microsoft Exchange, and
then
| > click System Manager.
| > b. Expand Folders, right-click Public Folders, and then click
Properties.
| > c. Click the Security tab.
| > d. Verify that the appropriate permissions are configured for the
folder.
| > The following is a list of the default permissions for the public
folder
| > hierarchy:
| >
| > 1) Administrator: Full control
| > 2) Domain Admins: All permissions except the following:
| > Full control
| > Delete children
| > Delete tree
| >
| > 3) Enterprise Admins: Full control
| > 4) Everyone:
| > Create public folder
| > Create top level public folder
| > Create named properties in the information store
| >
| > Note: By default, the Everyone group does not have Full Control
| > permissions.
| >
| > 5) Exchange Domain Servers: All permissions except the following:
| > Full control
| > Write
| > Delete
| > Change permissions
| > Take ownership
| > Delete children
| > Add/remove self
| > Write properties
| > Delete tree
| > List object
| >
| > 6) Exchange Services: Full control
| >
| >
| > 2. Temporarily grant Full Control permissions to the Everyone group
for
| > the Public Folders folder:
| > a. Click Start, point to Programs, point to Microsoft Exchange, and
then
| > click System Manager.
| > b. Expand Folders, right-click Public Folders, and then click
Properties.
| > c. Click the Security tab.
| > d. In the Name box, click the Everyone group. Note that by default,
the
| > Everyone group is granted the following permissions:
| >
| > Create public folder
| > Create top level public folder
| > Create named properties in the information store
| >
| > e. In the Permissions box, select the Allow check box next to the Full
| > Control permission, and then click OK.
| > f. Quit Exchange System Manager.
| >
| > 3. Force Active Directory tion over all connections between
domain
| > controllers:
| > a. Click Start, point to Programs, point to Administrative Tools, and
then
| > click Active Directory Sites and Services.
| > b. Expand Sites, expand Default-First-Site-Name, expand Servers,
expand
| > ServerName , and then click NTDS Settings.
| > c. In the right pane, right-click each connection that is listed, and
then
| > click te Now.
| > d. Quit the Active Directory Sites and Services snap-in.
| >
| > 4. Start Outlook, and then recover the deleted items that you want
from
| > the public folders.
| > 5. Restore the default permissions for the Everyone group for the
Public
| > Folders folder:
| > a. Click Start, point to Programs, point to Microsoft Exchange, and
then
| > click System Manager.
| > b. Expand Folders, right-click Public Folders, and then click
Properties.
| > c. Click the Security tab.
| > d. In the Name box, click the Everyone group.
| > e. In the Permissions box, clear the Allow check box next to the Full
| > Control permission, and then click OK.
| > f. Quit Exchange System Manager.
| >
| > Meanwhile, I suggest you follow the steps mentioned in the Knowledge
Base
| > Article below:
| >
| > How to troubleshoot public folder tion problems in Exchange 2000
| > Server and in Exchange Server 2003
| > http://support.microsoft.com/kb/842273
| >
| > I hope these steps will give you some help.
| >
| > Thanks and have a nice day!
| >
| > Best regards,
| >
| > Terence Liu(MSFT)
| >
| > Microsoft CSS Online Newsgroup Support
| >
| > Get Secure! - www.microsoft.com/security
| >
| > ================================================== ===
| > This newsgroup only focuses on SBS technical issues. If you have issues
| > regarding other Microsoft products, you'd better post in the
corresponding
| > newsgroups so that they can be resolved in an efficient and timely
manner.
| > You can locate the newsgroup here:
| > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
| >
| > When opening a new thread via the web interface, we recommend you check
the
| > "Notify me of replies" box to receive e-mail notifications when there
are
| > any updates in your thread. When responding to posts via your
newsreader,
| > please "Reply to Group" so that others may learn and benefit from your
| > issue.
| >
| > Microsoft engineers can only focus on one issue per thread. Although we
| > provide other information for your reference, we recommend you post
| > different incidents in different threads to keep the thread clean. In
doing
| > so, it will ensure your issues are resolved in a timely manner.
| >
| > For urgent issues, you may want to contact Microsoft CSS directly.
Please
| > check http://support.microsoft.com for regional support phone numbers.
| >
| > Any input or comments in this thread are highly appreciated.
| > ================================================== ===
| >
| > This posting is provided "AS IS" with no warranties, and confers no
rights.
| >
| > --------------------
| > | Date: Wed, 19 Sep 2007 23:01:11 -0500
| > | From: Jonathan <noemail>
| > | User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
| > | MIME-Version: 1.0
| > | Subject: Problem moving Public folders with "Move all s"
| > | Content-Type: text/plain; cht=ISO-8859-1; format=flowed
| > | Content-Transfer-Encoding: 7bit
| > | Message-ID: <eBpPhrz#phx.gbl>
| > | Newsgroups: microsoft.public.exchange.misc
| > | NNTP-Posting-Host: 76.201.159.11
| > | Lines: 1
| > | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSF TNGP05.phx.gbl
| > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.exchange.misc:4324
| > | X-Tomcat-NG: microsoft.public.exchange.misc
| > |
| > | I am having trouble moving public folders from one Exchange 2003
server
| > | to a newly built one. The mailboxes transferred fine but when I
selected
| > | "Move all s" on the old server's Public folder store and
selected
| > | the new server to move them to, the public folders failed to appear
on
| > | the new server. They are, however, now inaccessible on the old server.
| > |
| > | I turned on logging for everything I could find related to Public
Folder
| > | tion for both servers. On the new server I get the following
| > | warning every 10 minutes:
| > |
| > | "Event Type: Warning
| > | Event Source: MchangeIS Public Store
| > | Event Category: Access Control
| > | Event ID: 1235
| > | Date: 9/19/2007
| > | Time: 10:22:12 PM
| > | User: N/A
| > | Computer: MARGE
| > | Description:
| > | failed an operation on folder on database "First Storage
Group\Public
| > | Folder Store (MARGE)" because the user did not have the following
access
| > | rights:
| > |
| > | 'Delete' 'Read Property' 'Write Property' 'Create Message' 'View
Item'
| > | 'Create Subfolder' 'Write Security Descriptor' 'Write Owner' 'Read
| > | Security Descriptor' 'Contact'
| > |
| > | For more information, click
http://www.microsoft.com/contentredirect.asp."
| > |
| > | You will note that the warning does not indicate what account was
trying
| > | to run the operation that failed.
| > |
| > | The old server is logging groups of tion Outgoing Messages
(3017)
| > | events every 10 minutes (about 2 minutes prior to the next warning on
| > | the new server).
| > |
| > | I would appreciate any light anyone can shed on this.
| > |
| > |
| > |
| >
|

Export mailbox contacts from exchange to create a WHITELIST

Posted: 19 Sep 2007 05:14 PM PDT

We are using Sophos Puremessage, Microsoft Intellegent Messaging filtering,
Microsoft Sender ID, and Greylist filtering. I want to tighten the rules
down in Sophos Puremessage, but I also want to minimize false possitives. I
can effectively do this by creating a concise whitelist. That is why I
would like to export the contact email addresses.




"Andy David {MVP}" <com> wrote in message
news:com... 

Exch2003 parameters affecting non page pool memory?

Posted: 19 Sep 2007 11:26 AM PDT

Well interestingly enough you mention SP2 we just loaded that this month.
The EXPBA says everything is fine but something is not right. You mentioned
the TPC TCP Chimney offload, and recieve-side scaling, as well as NetDMA.
Are these services or more protocols? I appreciate this as this is very
insightful and gives some depth to the issue and not just a do this. Thanks!

"Dgoldman [MSFT]" wrote:
 

Emails to Hotmail.com and MSN.com accounts delayed...

Posted: 19 Sep 2007 08:18 AM PDT

Fuel451 <microsoft.com> wrote: 

OK, and what about a PTR? (reverse lookup record)? Look up your domain at
www.dnsreport.com or try

ping -a ...

(.... being your public IP).

You need a PTR, so if you don't have one, call your ISP (the ones who
provide your T1, not your hosting company) and tell them you need a
PTR/reverse lookup for your public IP.

If you do have one, there are other things to look at.
 

Changing FSMO server from Exchange/DC

Posted: 18 Sep 2007 09:37 AM PDT

On Wed, 19 Sep 2007 01:43:29 -0700, Talltwat <com>
wrote:
 

You have read way, way more into it than was intended.
If Exchange (any version) is installed on a DC you cannot demote the
DC to be a member server. You can reboot it all you like.
If Exchange (any version) is installed on a member server you cannot
promote the member server to be a DC. You can reboot it all you like.

Allowing others to get a groups e-mail

Posted: 18 Sep 2007 08:18 AM PDT

Remove the group1 address from the user and give him some other address if
he doesn't already have one. Assign the group1 address to the distribution
gorup.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"Carl Gross" <microsoft.com> wrote in message
news:com... 

Offline defrag of a new message store??

Posted: 15 Sep 2007 04:30 AM PDT

The old store might (but you're using Ent so you could just move those out
too!)

The new stores will not have any large amounts of whitespace after the
mailboxes have been moved to them.

If you're concerned about whitespace, create three new databases,
preferrably one in each SG, and move 1/3 of all mailboxes from your current
single mailstore to them. You can then delete your current store and not
have to worry about extreme excess of whitespace.

Oliver


"Andy" <microsoft.com> wrote in message
news:com... 

Exchange 2003 to 2007 Transition plan

Posted: 14 Sep 2007 10:14 PM PDT

Happy to have helped.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"johnny_mango" <microsoft.com> wrote in message
news:com... 

problem resolving recipients

Posted: 14 Sep 2007 01:12 PM PDT

i found the problem. Thank you guys for your help. it led me in the right
direction. I will tell you what i had to change. Recipient policies >
properties> email address (policy) >highlight your domains main address> Edit 
this address.
and that did the trick!

Thank you and have a nice day .
--
ulyses96


"ulyses_96" wrote:
 

Exchange 2003 server bluescreen/rebooting

Posted: 13 Sep 2007 06:15 PM PDT

Thank you everyone for all the information.

I did the HP driver update, Windows update, and Exchange BPA tuning and
there's not been any problems since the reboot on 9/13 (prior to my first
posting). We've sucessfully migrated the remaining mailboxes and public
folders from one of our production Exchange servers. I'll go through the
process to verify everything is off the system then will be decomissioning
the old server next week. I will check into the comments regarding the
memory dump, but hopefully it was just a unique combination of misconfigured
memory & drivers.

My next phase of this project (mentioned in another post) is to do the same
kind of migration with our second old production Exchange. Unfortunately, I
don't have new hardware to migrate this to, so I'll have to settle with
slightly upgraded hardware with a clean install & new configuration.

Thanks again.

Mike O.

Exchange SOMETIMES rejects mail

Posted: 13 Sep 2007 04:44 AM PDT

One more thing, please check your Internet DNS records and be sure that your
MX record points to only valid SMTP hosts for your domain. The problem
you're seeing can occur when you have an MX record with two A records, one
for Exchange and the other one invalid, which causes mail to bounce when
sent to the invalid host.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

<com> wrote in message
news:googlegroups.com... 

Disaster Recovery Procedures from Exchange 2007 preparations.

Posted: 12 Sep 2007 11:50 PM PDT

To roll back, you simply "throw away" the DC. Wipe the disk and remove it
from the domain, rebuild Windows, promote it, and allow the old data to
te to it. I don't think you would want the FSMO roles in this DC
except for the schema master, which would be required. In the case of a
rollback, you'd have to seize the schema master role onto another DC.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"jprstokato" <microsoft.com> wrote in message
news:com... 

OST or PST

Posted: 12 Sep 2007 03:47 PM PDT

I thought you might say these things.
At least now I have some ammo to present my case with.
Thanks.

"Lanwench [MVP - Exchange]"
<donotsendme.unsolicitedmailatyahoo.com> wrote in message
news:us5Pu8G%phx.gbl...