Normally with "net offlinejoin" you creat an machine account on any machine inside the domain copy the safefile to the new client and then join the client as local administrator. When I try to creat the safefile and add the machine accout to the domain I go the following error:

---------------
root@client01:~# net offlinejoin provision -U administrator%Passw0rd domain=example.net machine_name=win11b savefile=provisioning.txt
ads_print_error: AD LDAP ERROR: 19 (Constraint violation): 0000202F: samldb: spn[HOST/client01.example.net] would cause a conflict
Failed to provision computer account: Invalid configuration ("netbios name" set to 'CLIENT01', should be 'win11b') and configuration modification was not requested 
---------------
So "net offlinejoin" expected the hostname of the client I'm executing the command and not any new name of a client I want to join. I tested it with:

----------------
root@client01:~# net offlinejoin provision -U administrator%Passw0rd domain=example.net machine_name=client01 savefile=provisioning.txt
Successfully provisioned computer 'client01' in domain 'example.net'
----------------  
Here you see, that now the account will be created (but it is allredy there) and the safefile will be created too.

On any Windows-Client, loged in as domain administrator, I can do:
-----------
H:\>djoin /provision /domain example.net /machine win11a /savefile win1a.txt 
-----------
And it works. I choose a new client name and NOT the name of the client I'm working on.

It makes absolutly no sens at  all to do an offlinejoin on the client I would like to join. 

One more thing. The manpage is wrong:
--------------------
 SAVEFILE is an optional parameter to store the generated provisioning data on disk.
--------------------
The SAVEFILE must be requried, because the file will be copied to the new client  and then used to join the client as local administrator