Beep boop
We’ve just finished migrating all of our users from a legacy AD forest with Exchange 2010 into a whole new AD forest with Exchange 2016. During the initial deployment of Exchange 2016 a new mailbox store was created, the existing system mailboxes were migrated (mailbox move) to the new store and the default Exchange 2016 … Read more
Our AD structure contains three domains, one root domain (int.mydom.com) and two sub-domains, one for servers/services (it.int.mydom.com) and one for user accounts (users.int.mydom.com). int.mydom.com users.int.mydom.com (Users live here) it.int.mydom.com (Privileged IT accounts and Exchange live here) We are running into problems with NetApp Single Mailbox Recovery where it is unable to connect to the target … Read more
We just recently went through an AD forest migration AND an Exchange 2010 -> 2016 migration across forests at the same time. Good times. One of the many issues that came up after the migration was the majority of our users being unable to share their calender’s with other users. When trying to share via … Read more
Running into a problem with Exchange 2010, a FAS2240-4 and SnapManager for Exchange 7.1 where backups would randomly fail every now and then started failing consistently. Our DFM server would send us an e-mail when the failure occurred that looked like this: CLIENT APP ERROR Backup: SME Version 7.1: (111) on dora02 at Sun Sep … Read more
Recently ran across this one: 2016-06-22 10:23:19.878-07:00| vcsInstUtil-3634789| I: MonitorStatusFile: Other process terminated with 0, exiting 2016-06-22 10:23:19.878-07:00| vcsInstUtil-3634789| I: MonitorStatusFile: Process exited with a ‘0’ exit code; no status monitoring so assuming success 2016-06-22 10:23:19.878-07:00| vcsInstUtil-3634789| I: MonitorStatusFile: called parse callback 0 times 2016-06-22 10:23:19.878-07:00| vcsInstUtil-3634789| I: MonitorStatusFile: No need to wait for process … Read more