AD is getting removed by One idm if group is added manually at Target directly.

I suggest contacting support. It sounds like a misconfiguration of your sync project configuration. By the way, the merge mode should be enabled by default if you set up the sync project with 7.1.

i have checked my settings in 7.1 dell version,we did not enable"Merge" option .Is it causing the issue .

As I've said before. I suggest contacting support as your sync configuration may have to be checked as well. Misconfigured merge mode can lead to empty group memberships depending on your overall configuration but not to deleted groups itself.

How can i contact support team.is it via mail or call/

You can contact them right away from your Browser. You are just 3 clicks away when you are reading this in the community.

Hi Markus,

One quick question.If we change in the log config file"globallog.config" Do we need to restart the application "?.Just change is enough for this.

According to the NLOG documentation, you do not need a restart (globallog.config contains autoreload="true").

https://github.com/nlog/nlog/wiki/Configuration-file#automatic-reconfiguration

Automatic reconfiguration

The configuration file is read automatically at program startup. In a long running process (such as a Windows service or an ASP.NET application) it’s sometimes desirable to temporarily increase the log level without stopping the application. NLog can monitor logging configuration files and re-read them each time they are modified. To enable this mechanism, you simply add autoReload="true" parameter to the configuration file.

<nlog autoReload="true">
   ...
</nlog>

Note that automatic reconfiguration supports include files, so each time one of the included files is changed, the entire configuration gets reloaded.

Just to make it explicit, automatic reloading will NOT stop/recycle the IIS Application Pool.

According to the NLOG documentation, you do not need a restart (globallog.config contains autoreload="true").

https://github.com/nlog/nlog/wiki/Configuration-file#automatic-reconfiguration

Automatic reconfiguration

The configuration file is read automatically at program startup. In a long running process (such as a Windows service or an ASP.NET application) it’s sometimes desirable to temporarily increase the log level without stopping the application. NLog can monitor logging configuration files and re-read them each time they are modified. To enable this mechanism, you simply add autoReload="true" parameter to the configuration file.

<nlog autoReload="true">
   ...
</nlog>

Note that automatic reconfiguration supports include files, so each time one of the included files is changed, the entire configuration gets reloaded.

Just to make it explicit, automatic reloading will NOT stop/recycle the IIS Application Pool.

Hi ,

i just enabled the  Trace log in globallog as "Sync" and ensured that 

<nlog autoReload="true"> ,but log file is having only one line of data.No Trace logs are coming.Am i missing anything?

Hi Markus,

In my Trace log ,i have created like -  <logger name="SyncLog" minlevel ="Trace" writeTo="logfile"/>

There is  one space after 'minlevel" .will it cause any issue.

As Barry Jackson has pointed out in your thread https://www.quest.com/community/one-identity/identity-manager/f/identity-manager-forum/27551/i-have-configured-trace-log-setting-for-sync-jobs-but-i-cant-see-the-trace-logs/67517#67517 you shouldn't use SyncLog as logger name because it doesn't seem to do anything.

Use one of the ones Barry suggested.

Maybe take a look at the NLOG documentation?