Hi, I'm currently scripting all computers in our domain to create a local account then set that account up for "take a test" but using your code I'm pulling no information when I go with "$obj = get-wmiobject -namespace root/cimv2/mdm/dmmap -class MDM_SecureAssessment -filter "InstanceID='SecureAssessment' AND ParentID='./Vendor/MSFT'";". Is there something I'm doing wrong or is this code supposed to be different now? Thanks for your time.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@officeninja415 You're not doing anything wrong. I'm working with the product team to figure out how to fix the sample script. I'll let you know here what I find out.
Great to hear. Thanks for your response!
Just seeing if there has been any updates on this.
@officeninja415 I don't have an answer yet, sorry.
Ok. Thank you for the update.
@officeninja415 The team found that the script will only work if the account already exists (so the script is configuring an existing account to be a tester account, it isn't creating a tester account). I'll update the topic with that info.
I think there is still an issue even if a tester account already exists. The first line ($obj = get-wmiobject -namespace root/cimv2/mdm/dmmap -class MDM_SecureAssessment -filter "InstanceID='SecureAssessment' AND ParentID='./Vendor/MSFT'";) does not return an object for me. So, the next line trying to set $obj.LaunchURI can't find the 'LaunchURI' property (or any other property). I'm on Windows 10 1803. I'm wondering if 'SecureAssessment' is still the right InstanceID?
I am indeed still having the same problem even with the account already created. Like MeIQL, I'm not getting anything stored in the $obj variable, so there has to be a problem with that line. I feel like this is a trivial thing to script but would be largely important in the county I work in.
Anyone got a setup for how to create an account and url for testing? We can create a domain account no problem but want to figure out how to setup the windows 10 pc account and testing URL.
@jdeckerms Any updates on this isse? We would like to follow up. Thanks.
I think this is one of those Microsoft apps that gets demoed when they try to sell you a bill of goods, then after you buy it you realize it is not a finished product. With more states testing digitally it boggles my mind that this is not more of a priority. It would be nice to deploy this via group policy or via PowerShell but I don't think this will ever work unless Google steps up and builds a competing product. No wonder Microsoft is loosing to google in education.
Has anyone managed to get the powershell script to work? I have tried this on a Windows 10 1809, there is a local account called TestAccount but it doesn't work.
Running the script in powershell ISE as an admin gives me this output:
The property 'LaunchURI' cannot be found on this object. Verify that the property exists and can be set.
At line:2 char:1
The property 'TesterAccount' cannot be found on this object. Verify that the property exists and can be set.
At line:3 char:1
You cannot call a method on a null-valued expression.
At line:4 char:1
The only way I have gotten it to work is manually going to settings > accounts > access work or school > set up an account for taking tests > then setting the URL and test account manually. The PowerShell script that is given on the feature page does not work. Microsoft wrote the script before creating the Powershell objects that it calls or uses.
Closing via #8118
Most helpful comment
@officeninja415 The team found that the script will only work if the account already exists (so the script is configuring an existing account to be a tester account, it isn't creating a tester account). I'll update the topic with that info.