Henrik Krumbholz

Yeah I removed the customer specific terms. But this should only be the server name and the accounts. I added the complete verbose logging of the resource. ``` VERBOSE: [SERVER01]:...

Do you have any idea?

I did not find the AdminGroupInternal. Therefor some errors vanished but there are still the most important ones. I attachced a txt [Log.txt](https://github.com/dsccommunity/SharePointDsc/files/8185837/Log.txt).

 In order of unrecognizable slots: - DEV\ServiceApplicationPoolAccount - DEV\AdminGroup - DEV\ServiceApplicationPoolAccount - DEV\AdminGroup - DEV\FarmAccount - DEV\FarmAccount Just for comparison I modified the script and compared "Search" and...

At another newly created farm I do not receive this error. Nevertheless I receive another error but on the migrated DBs. I don't think that this would help here.

Nevertheless I checked the SQL output at the other system (SharePoint 2019).  - PROD\FarmAccount - PROD\FarmAccount - PROD\SearchApplicationPoolAccount - PROD\UserAccount - PROD\UserAccount2 - PROD\AdminGroup - PROD\UserAccount3 -...

Do you have any further ideas?

@ykuijs I am going to to test your code I hope next week. I will install another system from scratch and I can rerun the first system. What do you...

I'll test both environments. I just wondered whether my configuration is false. It doesn't seem realistic that I am the first with that error so I wondered whether my user...

I installed just the new farm. Not installed the old one yet. I got different outputs for the same server. I ran the script several times because I forgot a...