Search results for query: *

Go to AD Users and Computers, select user George Michel, and on Security tab give full rights to the Test user. Usually it take some time to take effect.

You cannot import the old one even if you recover it. You have to regenerate a new one.

If you recover it with RecoverServer switch, all you need is to copy manually databases, and transaction logs, and mount. Keep in mind that with RecoverServer switch, databases, and log paths must be same as on the old server.Example, if you had before database in D:\Database, and logs in...

You can export from Outlook to PST, then import from PST to Outlook without any problem, even they'll retain all user's permissions.

As far I can see, you have to create a folder in DC, and sharing will be done by DFS itself. It'll ask which folder to share, you have to select, and that's all. We now have Windows 2003 R2, and we use DFSR which is more advanced in configuration, and diagnostics reports.

You can put root target in whichever domain member server you like, just right click on mycompany.com\DFS, and choose New Root Target. We have root targets in 3 different servers/locations, and 2 of them are DC. I hope I didn't misunderstood your question.

If you use ISA in your org, be sure you configured it to directly access computers...

I asked them before few days. There is BE 12.5 SP3 out, but support for Exchange 2007 SP2 is not there. They told me they'll release an update for that, but didn't tell when.

Exchange 2007 SP2 is out since August, or September. You can install it freely. In case you use Backup Exec as backup software, there is no support yet for SP2.

Maybe Public Folders calendar can help.

Check for any rule created in Outlook, or mail downloaded directly to a pst file.

They have to configure Outlook Anywhere in Server side first. After that you can configure your Outlook using https://owa.domain.com, or similar.

Try to send using Webmail. If OK, problem could be Outlook cache under your profile. I'm assuming you use it.

Thank you for all your help. I'll investigate in that link, and find a proper solution for me.

I would be grateful if you could suggest one that could serve the purpose.

I was thinking for a redundant solution for hardware load balancing itself.

You can use Outlook. If your account have permissions on all Public Folders (calendars, contact,...) you create, that would be the easiest. Or you can use Pfdavadmin tool, which is a good tool, and very easy to use.

Since I didn't have to do with hardware load balancer, can anybody propose one, which will serve this purpose, and do clustering between 2 of them, if possible, in order to have full redundancy.

Sorry, but I misunderstood you in your first reply. I missed hardware load-balancer. If I want connect all clients in one server, but to use second one only as a redundant, for clients to connect in case of failure, or regular maaintenace, can it be achieved only with 2 server. I don't have...

So, if I counted well, in simpliest case, I would need: 2x Windows 2008 Enterprise 2x Exchange 2010 Enterprise 1x Windows 2008 Standard 1x Exchange 2010 Standard Apparently, it means there is no much difference between Exchange 2007, and Exchange 2010 regarding hardware requirements, meaning...