How can we help you today? How can we help you today?
Robb_Keller
Also, another issue getting this working was that the server had Powershell set to remote only.  I set it to Unrestricted and all was well. Robb / comments
Also, another issue getting this working was that the server had Powershell set to remote only.  I set it to Unrestricted and all was well.Robb
0 votes
I figured out the problem.  There was a type-o in the masking set.  I was also able to run the SQL scripts to create the stats tables in Powershell which also fixed the issue. Robb / comments
I figured out the problem.  There was a type-o in the masking set.  I was also able to run the SQL scripts to create the stats tables in Powershell which also fixed the issue.Robb
0 votes
The above Powershell opens the application briefly, but does not run the masking set.  Thanks,Robb / comments
The above Powershell opens the application briefly, but does not run the masking set.  Thanks,Robb
0 votes
Folks! I finally got the Powershell to run the data masking.  I was referencing the wrong app, which IS DataMasker.exe, NOT DataMaskerCmdLine.exe.  The file was wrong on extension too. Thanks anyway for consideration, but I'm good to go. Robb / comments
Folks!I finally got the Powershell to run the data masking.  I was referencing the wrong app, which IS DataMasker.exe, NOT DataMaskerCmdLine.exe.  The file was wrong on extension too.Thanks anyway ...
0 votes
I tried to comment earlier that I did figure it out.  I also had a wrong path and extension.  It's working OK now.  Thanks for the help. Robb / comments
I tried to comment earlier that I did figure it out.  I also had a wrong path and extension.  It's working OK now.  Thanks for the help.Robb
0 votes
I also tried running as Administrator, which did look like it triggered the DatamaskerCmdLine.exe, but did not run the script. Robb / comments
I also tried running as Administrator, which did look like it triggered the DatamaskerCmdLine.exe, but did not run the script.Robb
0 votes
Thanks Mark, Turns out that Powershell needed to be set to unrestricted from remote access.  That and putting the websites in the trusted zone fixed everything. Thanks for the help though, Robb / comments
Thanks Mark,Turns out that Powershell needed to be set to unrestricted from remote access.  That and putting the websites in the trusted zone fixed everything.Thanks for the help though,Robb
0 votes