Kirill Nikolaev
Kirill Nikolaev
The UTF8 encoding, which `Set-Content` uses, is w/o BOM in Windows PowerShell v5 - just checked
Also if you have a Windows client, you can fix broken files from the client-side with this PowerShell one-liner (run it in the NextCloud folder in your user profile): ```...
> > Also if you have a Windows client, you can fix broken files from the client-side with this PowerShell one-liner (run it in the NextCloud folder in your user...
Basically, the whole "Deploying Application Packages" section requires rework - old software versions and non-registered domains are used there.
I see, thank you for the quick response. But it seems the command does return useful results, just with an additional error - I can use the resulting CA object...
It seems that the `$NoDomain` variable is not defined - I did not find it anywhere in the code besides that line. And when it is not defined, it is...
Interesting: GitHub does not show it in the search results: https://github.com/PKISolutions/PSPKI/search?q=NoDomain
As for variable initialization, when I run `$Domain = ([ADSI]"LDAP://RootDSE").ConfigurationNamingContext` on a non-domain machine, I do not receive an exception, therefore the `catch` section does not get invoked, which, in...
Perhaps we could query `(Get-CimInstance -ClassName 'Win32_ComputerSystem').PartOfDomain` for better detection?
Maybe it is worth to implement both checks? Querying an non-existent domain controller takes time - the request waits and then fails by timeout. What if first we will check...