So, after some digging I now found out that this seems to be a bug by ESRI. Since our experiences with issues like that, there ESRI stated a "won't fix" even if they approved the issue as bug, I won't make the effort to report it. Expectation is again a "won't fix"... it's not worth the time.
For all others running into this issue I will describe it here:
As commented by @mkennedy the asker also:
where a response says it may be a bug that was fixed in 10.6.1.
Product Engineer plans to contact OP.
to which the asker replied:
... yeah I posted there too! I got the DM this morning so I'll work with them to figure it out.
I have had a similar issue and I used python script to fix it... You need to open a blank document in ArcMAp, then open the python window. Then copy/paste the following code, just repoint the path to the proper mxds...
While this approach doesn't work directly, the metadata information is carried over in the .mxd layer. For instance, right clicking the layer and item description in the catalog shows there isn't any metadata. However, right clicking the item in the .mxd table of contents, then data, then item description, shows the full metadata populated as expected.
By adding file iterator and according to these steps and pnj attached you can do it.
1- file iterator
2 insert from KMLto layer tool
3 connect outputs of file iterator (file and name ) to "KMLto layer tool"
4- specify only output folder in KMLto layer tool
In order to maintain the feature class as a geometric network type when copying, that feature class would have to participate in a geometric network, so one would need to be built in the output geodatabase. I'm not sure of your end goal here, but it seems like quite a bit of work just to get some symbology applied to layer.
To answer your question about ...