Well. I have to admit that I did one of the most dumbass things I have ever done and here in public. Original q was to disable dirsync in the cloud? You don't disable in the cloud. As soon as I hit that in .000002 milliseconds I wanted to kill myself That ended up being a premier case because the process did not work as it should have, but so it goes.
As far as aadsync, that did it's thing and was ready to go in less than 15 minutes. The sync to cloud took about an hour and a half once my screwup was fixed ~8500 objects altogether And yes we are trying to sync multiple Forests, in the middle of and hopefully good is happening but not sure quite yet! -Phone On Nov 11, 2014, at 21:40, "Milburn, Rich" <[email protected]<mailto:[email protected]>> wrote: Did you pull the trigger? We set this up for a client and it took less than a day for some 81k objects (using adfind -sc adobjcnt, ended up being 33,600 users and 2000 contacts). A delay in the beginning of setting up sync doesn't often have much impact since people can rarely just move all their users up onto Office365 that fast... You said you're wanting to sync multiple forests to WAAD? Rich From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Ramatowski, Paul M.. Sent: Wednesday, November 5, 2014 6:45 PM To: [email protected]<mailto:[email protected]> Subject: [Exchange] Deactivating Dirsync between On premise 2010 and Office 365 So.... Warnings abound that it can take up to 72 hours for the process to complete, during which time changes made to objects in your organization's on-premises Active Directory will not be synchronized. We're trying to put in AADsync (Azure AD Sync) due to a merger and the need for multiple forest synching. We're about 4800 object syncing- Wonder if it really takes that long, or if number of objects make a difference, or what? That's a long time:| Anyone here have real world experience to share? Thanks, Paul
