Please be aware that the instructions differ significantly between AeroFS versions, due to AeroFS changing under the hood. Please be very careful that you check which version you are working with before following any instructions. AeroFS 1.0.0-1.0.1 This was tested under AeroFS 1.0.1 and 1.0.0 and Hyper-V 2012 R2. It may not work for your environment. This is not a supported configuration. You're on your own. Sign up for the private cloud edition, and download the OVA file from the AeroFS if you don't already have it.
This post is largely for future me. I'm fed up with (re)writing/(re)discovering some of these queries. However, I also hope it can help other people. This post was written specifically whilst I was finishing up with an Exchange 2010 installation. However, should work verbatim with 2007 and some of the queries may require a little alteration for 2013. If you're still on 2003. I'm sorry. So your Exchange server has a w3wp instance with high memory and cpu.
The important thing to remember is that in Exchange 2013 Public Folders don't really exist like they used to. They're basically mailboxes. In this particular scenario Public Folders were accessible internally, but not via Outlook Anywhere (or Outlook RPC over HTTPS if you're old). This problem can manifests where the email address policy that applies to the Public Folder mailbox does not assign an email address that can be configured by autodiscover.
I'm openly paranoid about many things. Probably a secondary reason I'm basically bald at 25. The future of my profession is one I'm very paranoid about. It's one I love, despite all my moanings, and as the world starts it's seemingly inexorable move back to the mainframe^Wcloud, I fear that as time progresses we'll be in a world where there are few of us outside of large cloud companies. How much longer is on-premises server hardware still required?
Unfortunately this isn't one of those success stores. But then again if I wrote about those I'd be hitting a few thousand posts a year, and plus they're really boring to write about. We began the project by powering up some virtual machines and test importing the configuration from ISA 2006 to Forefront TMG 2010, and all appeared fine. The ruleset was there, the VPN configurations were there, and so on.
All in all for the last 5 years I've worked exclusively from home, and prior to that it was on and off depending on circumstances, and so on. During this time I've often been asked the same sort of questions over and over again;"Is it lonely?“"How hard is it to motivate yourself? I don't think I could get stuff done!“The first question I can understand. Sometimes you do need to see someone else, physically there in front of you, but to be frank, I've never been a great social animal, which probably helps massively.
Over Christmas we had to do a bunch of VMWare to Hyper-V conversions at work. Once you've sufficiently prepared the VM, there are a whole bunch of ways you can do this, ranging from raw converting the vmdk, to mounting the vmdk and a blank vhd and then copying the contents between. We chose it as an opportunity to play with Disk2VHDfrom SysInternals. If you're using SCSI disks in your VMWare VM then you will first need to ensure that you add the IDE controller driver, to hopefully avoid a BSOD when you boot under Hyper-V for the first time.
If you've got an application that sends messages via your Exchange 2010 server, using SMTP, you might've noticed that things have slowed down a bit. The reason for this is because the Exchange 2010 receive connectors have a “MaxAcknowledgementDelay” setting, that will inform you if the delivery is successful, within a certain time frame. If the timelimit is hit, it then acks the submission. To disable this you can set your receive connector not to use this feature:
If you're having fun with a pre-2007 version of Outlook, or any non-Microsoft product trying to talk MAPI to an Exchange 2010 server you might be interested in knowing that the defaults have now changed in the new version, and it expects traffic to be encrypted. This caught us out today as we'd only tested Outlook 2007 before rolling one of our boxes over to 2010 over the weekend. Two options;