We are just about done with our migration from Exchange 2003 to 2010. I have a user who has been migrated to the new system that is now out on medical leave. He has gone into OWA and set up his Out of Office notification. The good news is that an Out of Office message is sent, the bad news is that it appears to be sending an old outdated message from back when the user was on Exchange 2003, and not honoring the new message set up in OWA. The user has also tried setting this up in Outlook 2010 as well with the same behavior. I have a feeling that this is related to the old public folders (didn't they contain OOF messages?) still lingering around our Exchange org. Any ideas?
We have a situation where we have an aging Windows 2003 File Server Cluster that we'd like to move to a standalone Windows Server 2008 R2 VM that resides in our Hyper-V R2 installation. We see no need to keep the Clustering as Hyper-V is now providing our Failover/Redundancy. Usually, in a standalone file server migration we migrate the data, preserving NTFS permissions and then export the sharing permissions from the registry and import them on the new server. This does not appear possible in this instance, as the 2003 cluster stores the sharing permissions quite differently. My question is, how would one perform this type of migration? Is it even possible? My current lead is the File Server Migration Toolkit, however I can find no information on the net about migrating from cluster to standalone, only the opposite. Please help.
UPDATE: We ended up getting the data copied over (permissions intact), but had to recreate the shares manually by hand. It was a bit of a pain but it did in the end work out.
Anyone have experience binding a 10.5+ workstation to a 2008 active directory structure. We tested this functionality in our test domain prior to upgrading and saw no issues. Now that we've upgraded the production environment, we're getting invalid username/password errors. We are pre-creating machine accounts (as we always do) and I've tried binding with OU admin level and enterprise admin level privileges. Same error comes back from both. Communication to the domain seems to be working, as it finds a DC properly (DNS forward and reverse are fine) and it also finds my pre-created computer object and asks to bind to it. I've also tried deleting the directory service info and tried to bind from scratch with no luck. I've been beating my head over this for a while and could use some help.
UPDATE 3: Traced back to possibly an issue with the krbtgt user. As binding fails when executing a changepw command on the computer object. Microsoft and Apple are currently working together on this, and I will update with a solution when one is reached.
UPDATE 4: Hotfix to correct this issue is in the answer below.