Microsofthi jessev,
thx 4 this info!
in my environment (university) i'm struggeling with the same problem but different startposition:
have to handle MSclients ADjoined, BYOD (students), MAC OS Clients (ADjoined or not and the whole versionrange;), Linux Clients (different distros/CUPSversions)
and they all ONLY WANT TO PRINT - what could be easier?
In the meanwhile MS has published this: https://www.microsoft.com/en-us/download/details.aspx?id=104594
which in fact gives more possibilities in finetuning the RPC-thing, but handles only the newer ms-versions (win11 and/or 22H2 and newer) and of course only the ad-joined clients.
In our situation the only working method is the RpcNamedPipeAuthentication (we used value 0x1 - only found that as a way around as our whole system refused to work for newer clients), which was not suggested by MS!
Could you please give me an advice for what is the different meaning of 0x2 as value for RpcNamedPipeAuthentication to 0x1 and are there other values and meanings?
How could i bring all the not ms and not ADjoined clients to authenticate to our AD without using NTLM?
thx (and sorry for my bad english)
