Get-PWDocumentsBySearch : Not logged in as a ProjectWise Administrator.

We have updated ALL cmdlets within the PWPS_DAB module to require a ProjectWise Administrator login.

Since the inception of the PWPS_DAB PowerShell module, it has been our intention that this be used as an Administrative tool only. We are willing to expand the capabilities to the Restricted Administrators as well which will be available in future release of the module.

As an Administrator for a number of large systems I am in full support of the Admin only usage.

The PowerShell cmdlets are not yet supported under the SELECT agreement so they should be used in a controlled manner. I have seen a major outage caused by somebody using a script - even though they were an Admin user!

That said, I can see the benefits of having a tiered approach to security - e.g. PowerShell Admins & PowerShell Users with read-only functions available to the latter - as well as an Audit trail record indicating that an action was run from PowerShell but not at the expense of slowing down the fast development cycle we are getting today.

You can see from the amount of discussion in the Communities pages and at Bentley events that the PowerShell functions have become essential tools for administering ProjectWise and for me personally save many hours of work on repetitive tasks.

Limiting this to admin only is, in my opinion, going to severely restrict the benefit of the tool.  There are an increasing number of project users that have little choice than to use PS to extract data that is then used to feed Power BI.  In addition to this, three are several projects that we have that are joint-venture, and PS is used by JV partners to extract copies of the data for their records.
In both of these examples I have zero intention of making these users administrators, and neither do I want to be doing these tasks myself.

I feel that PS should simply respect the access of the user running the script, unless there is some other reason why this will not work.

Scott, your comments and opinion are duly noted. However, please refer to Dave Brumbaugh's, previous response. 

Not saying it can't be done.  Just wondering about the wisdom of it.  Are there really "normal" users that want to use PowerShell to interact with ProjectWise? Unless everyday users have gotten a LOT more sophisticated than the last time I managed a bunch of them, I just don't see it happening.

That said, I could see a dedicated group called "PowerShell Users" or some such that an administrator would have to add you to and a switch to force a non-admin login. Will discuss with the team. 

We really appreciate all the good ideas coming from this group.

Dave

Dave, my thinking behind this is that if I could use Powershell on an external companies datasource with only the limited access rights that I had, it would be very useful. I use it on my own datasource as a full administrator, but I do not know too many companies that will allow an external party to have even restricted admin rights to the datasource that they manage.

I realise the original Powershell was aimed at Administrators and most cmdlets were designed to help with managing the server side of their tasks, but this module has expanded into documents and allowed us to run tasks that would otherwise take a long time.

Mick

Dave, my thinking behind this is that if I could use Powershell on an external companies datasource with only the limited access rights that I had, it would be very useful. I use it on my own datasource as a full administrator, but I do not know too many companies that will allow an external party to have even restricted admin rights to the datasource that they manage.

I realise the original Powershell was aimed at Administrators and most cmdlets were designed to help with managing the server side of their tasks, but this module has expanded into documents and allowed us to run tasks that would otherwise take a long time.

Mick

Dear sir,

I need your help. how to update tagset information from excel. and data import/export to Excel.

Thanks.