0 votes

Dear support,

The current limitation of powershell 2.0 in script is getting more and more a problem for us. I am for instance unable to use the ConverTo-Json cmdlet what was introduce in version 3.0 that is very very handy when working with web services.

Regards,

by (750 points)

1 Answer

0 votes
by (216k points)
selected by
Best answer

Update 2018

Starting with version 2018.1 Adaxes supports the latest version of PowerShell installed on the computer where Adaxes service runs.

Original

Hello Pierre,

Starting from the next major version, Adaxes will support at least PowerShell 3.0. For now, you can use a workaround described in our Script Repository: Run script in new PowerShell instance.

Related questions

0 votes
1 answer

the script repo examples are almost entirely written in ADSI, however powershell is now far more widely used, is it possible to have all scripts written in both ADSI and powershell.

asked Jan 5, 2024 by i*windows (300 points)
0 votes
1 answer

Shared mailboxes are treated as standard users, however they really should have a separate view. I would like to request that a new view is made avaiilable for Shared ... office location, data from HR systems, windows profile, etc are not really relevant.

asked Jun 23, 2023 by i*windows (300 points)
0 votes
1 answer

With the depreciation of MS Basic authenication, how to do change powershell scripts within adaxes to use OAuth 2.0 token-based authorization

asked Sep 23, 2022 by sra98a (120 points)
0 votes
1 answer

Is version 2018.2 still supported? Where can I find EOL / End of Support information?

asked Dec 14, 2023 by chappyshi (90 points)
0 votes
1 answer

We were used to bind to group member object using: $member = $Context.BindToObjectByDN("%member%") which worked perfectly, but now it is not. Its because %member% is returning ... ? And is it possible to get DN of added/removed member using another variable?

asked Sep 14, 2020 by KIT (1.0k points)
3,677 questions
3,361 answers
8,494 comments
549,308 users