Jump to content

Recommended Posts

Posted (edited)

Getting it to work is another matter,

 

There's no obvious way or instructions to use a transform to get the data path into the install. Deploying it through group policy and then import the path reg keys later is liable to cause lots of program errors as is rebuilding the msi. What we did previously, works even less well this time.

 

Here's what we have working now, and it's better than previous methods inho

 

1. create esm account with password, put it in the pupils OU

2. Give account domain admin rights (!)

3. use group policy to change the shell to a random dos prog, we used ping.

4. give the account a login script that does:

 

rem remove old installs 
msiexec /x "\\xxx:location\promissor_206.13\promissor216.msi" /quiet
msiexec /x "\\xxx:location\promissor_207.17\administrator.msi" /quiet
msiexec /x "\\xxx:location\promissor_regkeys\promreg.msi" /quiet
rd "c:\program files\promissor\" /s /q

rem install msi as instructed by promissor helpfile
msiexec /qb /i xxx:location\Updates\administrator.msi DATAPATH=xxx:\location

rem run promissor from icon
"c:\Documents and Settings\All Users\Start Menu\Programs\Promissor\Administrator.lnk"

 

5. do not give anyone the account password, logon remotely or in bulk. we use abtutor.

6. login twice. first time ever u do it has a error about not being able to find a dll. second time works.

 

this works good because while dom admin is a potential security risk, no shell + high security computer policies removes (any) possibility of getting somewhere they shouldnt (even after promy hides the shell itself) and they're under pretty close scrutiny anyway from exam conditions. the promy icon is one of those that doesn't specifically point at a program but still works somehow. whatever it does, running promy direct from the exe doesn't work too well.

Edited by browolf
Posted

Imagine our surprise when two rooms of pcs rebooted themselves in the middle of the exam! and then did it again 30mins later!!! The exam coordinators weren't best pleased...:doh:

 

We seem to have a problem between promissor and the auto-logout feature of the fog service. Ie the fog service thinks nothing is occurring and reboots after 30mins.

 

It's difficult to say what the exact cause of this is because promissor has changed (it now seems to hide the shell itself upon loading) and we've changed the method of running it and what shell we're using (before we had promissor as the shell). In any event we've disabled the auto-logout feature.

Posted
Imagine our surprise when two rooms of pcs rebooted themselves in the middle of the exam! and then did it again 30mins later!!! The exam coordinators weren't best pleased...:doh:

 

Ouch! Ye Can't imagine them being please with that, We have had to change the way we do promissor and are currently looking into a better way todo it after the update stopped the method we used previously!

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...