Thank you, Kelsey. I'm concerned, because I have started and stopped ADSynch through both the web portal and Powershell. When stopping DirSync previously through only the web portal (for this company and other, larger ones) it has only taken 2-4 hours to reflect that it has stopped. Even though it says "up to 72 hours", I am concerned that I have locked something up with my efforts to stop and restart the service. I have NEVER actually seen it take more than 6 hours, and it has been longer...
Any other thoughts? It easy to say "wait 72 hours", as that is the answer I would give an end user. I've just never had it take this long and this is putting my (larger) project on hold by 3 days.
Any other thoughts or solutions? I am thinking I have locked something up...