Jump to content

Recommended Posts

Posted

Just in case anybody else has the same problem as we did...

 

We have a classroom of PCs with the latest DPS version installed via GPO and then the three example tests installed on top of that as per the documentation. However, on 2 of the PCs there were no tests to pick from in the list when the pupil started the DPS. I checked:

 

C:\Program Files\QCA Testing\Delivery Point System\TDS\Tests

 

on the 2 duff workstations and they had the tests there just the same as on the working PCs.

 

Eventually I found that:

 

C:\Program Files\QCA Testing\Delivery Point System\TDS\Config\Components.xml

 

on the 2 broken PCs didn't have any tests listed inside , whereas the working machines had three some stuff items.

 

Because the Components.xml on the working machines was always the same, I copied a working one over onto the broken installs and the tests appeared fine in the list next time. I still can't find any reason why it would do a faulty install on 2 of 28 identical ghosted PCs, but that's life.

 

HTH someone!

Posted

Actually I've got to hold my hand up on this one. I thought we had it fixed, but alas no. The tests appear in the list, but when a pupil tries to use one they get a msgbox:

 

"Unable to load the Test. Ask your teacher for help"

 

Obviously the teacher then asked me for help and I looked skyward ;)

 

Will probably do an add/remove programs uninstall tonight and manually wipe out any lingering folders then reboot and see if the GPO method works 2nd time round. Failing that we'll do manual installs. (Grr!)

  • 2 weeks later...
Posted
I had found that if the machine was rebooted / restarted before the DPS or test MSI had finished it didnt reinstall or repair on next boot as an MSI is supposed to.
Posted

We found a problem with tests installing incorrectly if the MS firewall was on.

 

Not quite the same problem but may be worth looking at.

Posted
We found a problem with tests installing incorrectly if the MS firewall was on.

 

Our firewall is turned off by domain GPO,

 

Ours was off in the original image but the odd PC decides to turn it on. Editing GPO now :)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...