deploy with powershell

I checked our cmdlet, and Set-WaykNowConfig does a permission check that could possibly fail in cases when it would work. This check is not done in Set-WaykNowBranding, which is why it worked. I was a bit curious as to why it would work in the first place, because our understanding was that our files in %ProgramData% would need to be restricted to an elevated user context, and made read-only to regular users.

It turns out that all users can create a directory in %ProgramData%, and that the creator of the directory gains write permission on that directory. Ideally, we would improve Wayk Now to check the permissions on that directory and lock it down in case it was created beforehand with wider access. Are you running the cmdlet from an elevated terminal, or from a regular terminal? The goal would be to restrict write access to elevated users only in order to prevent regular users from changing settings enforced by an administrator.

Best regards,

Our deployment tool uses an admin user to run the powershell commands. This is elevated.
When i run this commands locally on my client (with an elevated powershell shell) i get the same error messages for the Set-WaykNowConfig settings.

Regards
Siegfried

Thanks for confirming this, fixing the function that improperly checks for the elevated PowerShell context should do it then. We'll create a ticket, and get on it this week, it shouldn't take too long.

Best regards,

Hi,

An updated version of the Wayk Now cmdlet (2020.1.3) has been published on PSGallery. I have removed the check for admin rights to let the call attempt the write operation and fail at that point instead if rights are insufficient. Let me know if it works for you.

Best regards,

Hi,

I have just checked with version 2020.1.3.
The other 2 commands work now but the Set-WaykNowBranding -Global -BrandingPath ... throws an error now.

Set-WaykNowBranding : A parameter cannot be found that matches parameter name 'Global'.

Regards,
Siegfried

Hi,

Just don't add -Global as a parameter. It always tries to install it in the global path now, which is what you are trying to do anyway.

Best regards,