update-PWFolderSecurity not found.

RE: update-PWFolderSecurity not found.

Robert Biggar — Mon, 11 Apr 2022 11:17:49 GMT

That's good stuff, I'm going to grab these...

this is the first time I have run into these dashes...but I guarantee I won't be forgetting this lesson anytime soon! :-D

Thanks for the script; I will add it into my profile as well!

the HTML conversion for links into normal strings I ran into a couple weeks ago...but in Excel. So this looks like a pretty interesting solution in PWRShell.

They haven't come up often for me, but they are "sticky" when they do!

I appreciate the help, Thanks Kevin!!

Bob

RE: update-PWFolderSecurity not found.

Kevin van Haaren — Sat, 09 Apr 2022 02:27:43 GMT

I see this when copying pasting from Outlook all the time. Also issues with smart quotes. In fact I've seen this so much I wrote a little function that fixes it for me. It converts smart double quotes to dumb double quotes, smart single quotes to dumb single quotes and both endash and emdash to a normal dash.

I put it in my profile.ps1 so it's always loaded (I also set an alias cc so i don't have to type that long name i came up with)

# Convert some annoying unicode characters into normal versions
function Convert-ClipboardUnicodeEntities {
	$clip = Get-Clipboard -Format Text -Raw -TextFormatType UnicodeText
	if (-not [string]::IsNullOrEmpty($clip)) {
		# replace unicode smart open double quotes with dumb straight double quotes
		$clip=$clip.Replace([char]0x201c,[char]0x0022)
		# replace unicode smart close double quotes with dumb straight double quotes
		$clip=$clip.Replace([char]0x201d,[char]0x0022)
		# replace unicode smart open single quote with dumb straight single quote
		$clip=$clip.Replace([char]0x2018,[char]0x0027)
		# replace unicode smart close single quote with dumb straight single quote
		$clip=$clip.Replace([char]0x2019,[char]0x0027)
		# replace endash with a dash
		$clip=$clip.Replace([char]0x2013,[char]0x002D)
		# replace emdash with a dash
		$clip=$clip.Replace([char]0x2014,[char]0x002D)
		Set-Clipboard -Value $Clip
	}
}

BTW, if you're interested here's a variation on that will convert a projectwise url string that uses html/url entities and turns them into normal strings. I use this copying urls from Outlook that I want to paste into PW Explorer.

# Convert HTML & URL entities to string characters
function Convert-ClipboardHtmlUrlEntities {
	$clip = Get-Clipboard -Format Text -Raw -TextFormatType Text
	if (-not [string]::IsNullOrEmpty($clip)) {
		# URLs can have some weirdly encoded characters, let's fix those
		# clean up URL characters like %20
		$clip=[System.Net.WebUtility]::URLDecode($clip)
		# clean up html entities like <
		$clip=[System.Net.WebUtility]::HTMLDecode($clip)
		# replace &space; with a space (this is not a standard html entity, but ProjectWise uses it)
		$clip=$clip.Replace("&space;"," ")
		Set-Clipboard -Value $Clip
	}
}

RE: update-PWFolderSecurity not found.

Robert Biggar — Thu, 07 Apr 2022 18:34:41 GMT

to be sure...I will be "on guard" :-D

Thanks again, Brian!!

RE: update-PWFolderSecurity not found.

Brian Flaherty — Thu, 07 Apr 2022 16:30:38 GMT

Be sure you are not copying and pasting from Word or another application like that. For some reason the dashes are different.

RE: update-PWFolderSecurity not found.

Robert Biggar — Thu, 07 Apr 2022 14:25:03 GMT

hahaha!

It's the "Dash" again !!!

Get-PWFolders -FolderID $folderID -JustOne -Slow | Update-PWFolderSecurity ‐MemberType 'ul' ‐MemberName 'MediaWiki' -MemberAccess "fr,fw" -IncludeInheritance -Verbose

notice the "dash" in front of the "MemberName" is smaller...shows on the command line as a different color

So.

I copy the Example line to make sure the syntax I start with is correct...this particular text...has those other dashes

Problem solved.

Thank you for your help Guys...that's a new one for me!

Bob

RE: update-PWFolderSecurity not found.

Brian Flaherty — Thu, 07 Apr 2022 13:55:57 GMT

I almost never rely on positional. I prefer specifying the parameters. Makes everything obvious. Well, unless I'm doing something adhoc. Anyways, I wrote that cmdlet, so, everything should work with or without specifying the parameters. Not sure why you are encountering so many issues with it. Take a look at the examples provided.

RE: update-PWFolderSecurity not found.

Robert Biggar — Thu, 07 Apr 2022 13:55:54 GMT

I am told that there is a "dash", an "Mdash" and an "Ndash"...

and that the M and N dashes are placed in the text, but if the text is <space> "dash" <space> the "dash" is converted to a normal dash...

we have run into this with file and attribute names that don't like the M and N dashes.

it's pretty confusing...but now I know what to look for...

:-D and I'm not likely to forget.... painful lessons are like that...

Bob

RE: update-PWFolderSecurity not found.

Robert Biggar — Thu, 07 Apr 2022 13:51:31 GMT

now that you say that...that one didn't complain...but -MemberName was not happy with me...It's working great...I just have trouble with the parameter specifications...if I rely on positional...it's golden.

Update-PWFolderSecurity $folder 'ul' 'MDOT Traffic' 'fr', 'fw' -DocumentSecurity -Verbose

Thanks, Brian!

Bob

RE: update-PWFolderSecurity not found.

Brian Flaherty — Thu, 07 Apr 2022 13:37:56 GMT

The member type 'ul' should work fine.

You will need to individually enter the access control settings.

Don't use: "fr,fw"

Use: 'fr', 'fw'

RE: update-PWFolderSecurity not found.

Robert Biggar — Thu, 07 Apr 2022 13:14:59 GMT

So...now that CMDlet is working...

This is another odd thing:

Get-PWFolders -FolderID $folderID -JustOne -Slow | Update-PWFolderSecurity ‐MemberType 'ul' ‐MemberName 'MediaWiki' -MemberAccess "fr,fw" -IncludeInheritance -Verbose
Update-PWFolderSecurity : A positional parameter cannot be found that accepts argument 'MediaWiki'.
At line:1 char:52
+ ... One -Slow | Update-PWFolderSecurity ‐MemberType 'ul' ‐MemberName 'Med ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [Update-PWFolderSecurity], ParameterBindingException
+ FullyQualifiedErrorId : PositionalParameterNotFound,PWPS_DAB.UpdatePWFolderSecurity

** Note: I am setting parameters this way "‐MemberType 'ul' " and I can't get it to work

THIS does work...relying on position

PS C:\PS> Update-PWFolderSecurity $folder 'ul' 'MDOT Traffic' 'fr', 'fw' -DocumentSecurity -Verbose
VERBOSE: 1 input folder(s).
VERBOSE: MemberType: ul
VERBOSE: Starting Access Control Update Process 4/7/2022 8:23:06 AM.
VERBOSE: MemberName: MDOT Traffic : MemberID: 1530
VERBOSE: Successfully added access control settings for 'Lansing Support\biggarr\SecTest'.
VERBOSE: - Added 'MDOT Traffic' to Document security.
VERBOSE: Ending Access Control Update Process 4/7/2022 8:23:07 AM.
True

Works like a charm...as long as I don't use: "‐MemberType 'ul' " syntax to set parameters...and rely only on position.

I have not run into this before either...is it a mode or a controllable setting?

I know the parameters have default positioning... but in this case it does not want the "-<param>" flag...it won't even take it

Have you run into this before?

Thanks!

Bob

RE: update-PWFolderSecurity not found.

Robert Biggar — Thu, 07 Apr 2022 12:58:49 GMT

Yep. absolutely correct... THAT is a good catch.

..and a very twisted problem.

it is the "dash" that is in the "Examples text"...very strange

I don't have my "Hexedit" handy to check the code on that...but whatever it is...it isn't the dash we need!

:-D

Really. nice "Catch" Brandon!

Thanks!

Bob

RE: update-PWFolderSecurity not found.

Brandon Williams — Thu, 07 Apr 2022 12:44:36 GMT

So the cmdlet is not case sensitive. The reason it was not working in your examples was because of the dash

Update‐pwfolderSecurity

Update-PWFolderSecurity

It might not look like much but the first dash is shorter. Almost like it was copied from a file that had a different font, a half dash, which I did not know existed. If you were to copy the above into PowerShell and look at the dash you will see what I mean. The top one is a shorter dash. So even if you copied the top line and did the correct capitals in the cmdlet, it would still not work because of the type of dash. Not sure how to make a half dash but my guess it was copied from a different font?

RE: update-PWFolderSecurity not found.

Robert Biggar — Thu, 07 Apr 2022 11:16:14 GMT

yeah, the hyphen definitely needs to be in there...that example without the hyphen was a test someone else observer from the documentation of the cmdlet...a test that didn't work ;-) It just got caught up in my capture, but thanks, you are absolutely correct. ( I wouldn't want anyone to fall down that rabbit hole).

It seems the real problem for me was the case of the Text:

"Update‐pwfolderSecurity" did not work......

however

"Update-PWFolderSecurity" does work

???

interesting....because

"New-Pwlogin" works

but so does "new-pwlogin"....

maybe there are some aliases "lurking about"...

my "takeaway"...sometimes CMDlets ARE case-sensitive...(note to self)

The way I finally figured it out was to use "intellisense"...I selected from the list and it worked...then compared it to what had been failing.

I will be using that in the future.

I appreciate your comments with this....they were a BIG help!

Bob

RE: update-PWFolderSecurity not found.

Brandon Williams — Wed, 06 Apr 2022 18:17:50 GMT

I copied your first example and the issue seemed to be the -

When I copied the dash it was shorter then the dash I use. I have no idea how that happened.

If you copy both cmdlets into powershell you'll see what I mean.

RE: update-PWFolderSecurity not found.

Robert Biggar — Wed, 06 Apr 2022 17:25:10 GMT

I think it is "case"...

PS C:\PS> Update‐pwfolderSecurity
Update‐pwfolderSecurity : The term 'Update‐pwfolderSecurity' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was
included, verify that the path is correct and try again.
At line:1 char:1
+ Update‐pwfolderSecurity
+ ~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Update‐pwfolderSecurity:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

PS C:\PS> Update-PWFolderSecurity
Update-PWFolderSecurity : Parameter set cannot be resolved using the specified named parameters.
At line:1 char:1
+ Update-PWFolderSecurity
+ ~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [Update-PWFolderSecurity], ParameterBindingException
+ FullyQualifiedErrorId : AmbiguousParameterSet,PWPS_DAB.UpdatePWFolderSecurity

It "finds it" now... I don't recall ever having case issues...maybe I was just lucky and always got the case .."just right"???

...thanks for the help! I'm off to the next tree to slam into.."Yoiks and away"

(assumption on the Looney tune literacy :-D)

Bob

RE: update-PWFolderSecurity not found.

Brandon Williams — Wed, 06 Apr 2022 16:08:42 GMT

Are all cmdlets doing this? Can you Try New-Pwlogin and see if its the same?

When I import I do the following as Administrator 64 bit Powershell. (You need to be administrator)

Install-Module PWPS_DAB -Force -Verbose

Import-Module PWPS_DAB -Force -Verbose

RE: update-PWFolderSecurity not found.

Robert Biggar — Wed, 06 Apr 2022 16:02:07 GMT

ok, I uninstalled the x86 and set up the 64 bit....same error (with Hyphen)

PS C:\PS> Update‐pwfolderSecurity

Update‐pwfolderSecurity : The term 'Update‐pwfolderSecurity' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was
included, verify that the path is correct and try again.
At line:1 char:1
+ Update‐pwfolderSecurity
+ ~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Update‐pwfolderSecurity:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

PS C:\PS> get-help pwfoldersecurity
Security Protocol now set to TLS 1.2
PWPS_DAB Version is 2.0.6.0
This is a 64-bit process.

Name Category Module Synopsis
---- -------- ------ --------

Update-PWFolderSecurity Cmdlet pwps_dab UpdatePWFolderSecurity is used to add user(s), group(s), or userlist(s) access control to specified folders.

RE: update-PWFolderSecurity not found.

Robert Biggar — Wed, 06 Apr 2022 15:10:58 GMT

I will try the 64 bit angle...the hyphen; there or not, gave me the same error... Thanks!

RE: update-PWFolderSecurity not found.

MWBSI — Wed, 06 Apr 2022 14:48:19 GMT

In general with PowerShell, you need a hyphen(-) between the verb and the noun. So the cmdlet is Update-PWSecurity, not UdatePWSecurity. Intellisense should help you out as you type.

Mark Weisman | Bentley Systems

RE: update-PWFolderSecurity not found.

Brandon Williams — Wed, 06 Apr 2022 14:48:02 GMT

I did find it odd the error did not have the hyphen. Also, I would recommend using this in 64 bit PowerShell not x86. You'll need to install and import into 64 bit PowerShell.