New answers tagged exchange-2007
This is actually pretty easy Highlight an ordinary folder within Public Folders (not a contacts folder) then go through the motions of export to file. You will be prompted with the folder selector, accept this time you will be able to browse all of Public Folders and select the PF Contacts folder that you want to export. Bada-Bing, Bada-Boom!
Here is another option available for Audit mailbox actions on Exchange Server. You can find out an audit log what happens and all mailbox actions on Exchange. For more details about this from here... http://technet.microsoft.com/en-us/library/ff459237
I have done a setup just like you are asking, albeit with Exchange 2010 which is somewhat different than 2007 in this regard. It will handle distro lists, etc. Be cautious about having the same ones cross-forest though...like helpdesk or sales or whatever. Basically it comes down to 3 things: You should (if you don't already) have a shared SMTP ...
Even though its a program you have to pay for, check out Quest Collaboration Services (now owned by Dell). It is a GAL syncing program and works quite well. You can sync user object, contacts and mail enabled groups (DL's) with members between two different forests so they show up in the GAL. It does not require a trust to do the GAL sync. It uses emails ...
Now I know that Exchange Server will use as much memory as possible and release it whenever another process needs it I don't believe that to be the case and I've never seen documentation or anecdotal evidence to suggest such behavior. Database maintenance occurs by default between 1AM and 5AM. That would be my guess as to what's causing the spike. ...
In AD users and computer we had to proper gate the rights on the mailbox, as the account we were using to migrate did not have permissions to carry out the migrate - even though they where and org admin. http://www.techieshelp.com/exchange-2013-active-directory-property-%E2%80%8Ehomemdb%E2%80%8E-writeable-recipient/
Exchange doesn't care about the IP address. Therefore changing the IP address and rebooting the server will not be an issue. If you have any receive connectors on the 2007 server listening bound to a specific IP, be sure to change that as well. Changing the name on the other hand would be a major problem, as that will break Exchange.
In the Exchange Management Console, go to Organization Configuration > Hub Transport > Send Connector > Properties. Under "Specify the FQDN...", change this to the A record for NewDomain.com (e.g. mail.newdomain.com).
From here: http://support.microsoft.com/kb/2292750 It might not be that simple though. As the user might be logged in from various devices (Outlook client and iPhone for example). Since it appears to be happening often enough, you may consider disabling her ability to use Activesync and OWA and then ask her to only use "x computer" and then see if it ...
Yikes. What you've done is a bit bizarre and very likely going to cause problems. I suppose you could try to make things work by modifying the homeMDB, homeMTA, and msExchHomeServer attributes of the subject AD account to refer to the server where you mounted the mailbox database you moved. I think you're in wildly unsupported territory and I wouldn't be ...
Top 50 recent answers are included