I made a small test environment and did some Azure AD Connect installations to see how this will interfere with our production environment and to learn a lot of this sync service. I installed a second sync server in the test environment and did switch to the other server without any problem.
After this I started with a new server in production and installed the latest version in stage mode. Heath agent is registered correctly. The existing production ADFS servers are now updated (managed) by this new sync server. So this is a major improvement when I compare this with the first attempt.
After everything was up and running I used csexport with the /f:x option to create an export.xml and used the CSExportAnaluzer to create a csv file. Just like you suggested. I ended up with 2 files with 1433 records all together. In this file I can find every user, contact, device and group of my organization. They all have ‘UPDATE as operation. No ADD and no DELETE. So I guess no records will be deleted. But every record will be updated.
How do I know if I want these changes (updates)? What I think, because we make a major jump in the version, a lot off things are changed and that’s why the records needed to be updated. What I can find in the synchronization service are changes like bellow.
Do you undestand whats happening here and can you explane it to me? Can I now switch to this new server en put the other server in staging-mode? Or do I need to check everything is oke before I make the switch.
Thanks!
Rob