Ramsel

Historically CRB checks have not been transferrable between employers. I believe the rules have however recently changed, so this may no longer be the case. Either way it probably won't make much difference as it's just a formality (unless you have a record!)

BITES, a team within Bucks County Council based in Aylesbury, currently have a vacancy for an experienced technician. Workflow Microsite - Homepage

Andie, I believe that the location of the ITR is defined by a reg key on the server in HKLM. This means that as far as the software is concerned, it attempts to access the ITR in the same way. Basically this is something to do with either NTFS perms or an odd path. You said you've been playing with the perms on the ITR folder; what about the share permissions?

I just did this a few days ago.... Right. The Client Install.exe is useless. Despite using a /v switch it won't pass commands to the Easiteach MSI. Here's some steps for you: 1) Install the Client using the Client Install.exe. When complete, grab the file file "C:\Documents and Settings\All Users\Application Data\Research Machines\Easiteach Studio\lite_ctp.dat". This is the license file for Easiteach. 2) Set up AD deployment or SMS or however you want to do it of the "Easiteach.msi" found in the "Easiteach" folder at the same location as "Client Install.exe", making sure to add a -qb or /quiet switch as per usual. 3) Set up deployment by script or create an MSI, whichever you would prefer, that will copy "lite_ctp.dat" from wherever you saved it to "C:\Documents and Settings\All Users\Application Data\Research Machines\Easiteach Studio\" 4) Create shortcuts to all the ITR data main menus. They are found within your AE Resources folder in the relevant years, inside the "ITR" Folder. They are very obviously named. On a machine which now has Easiteach installed, file associations are already set up for these files, so a user can just run that file. It will link through to the rest of the ITR data. If you want to have the ITR data on the local machine rather than the network for the sake of bandwidth, create an MSI or script which simply contains the contents of the year folders within AE Resources, and make sure that your Main Menu shortcuts are correct. Hope this helps

Set it up as a scheduled task, specifying the administrator to run it. Alternatively if you want the user to run it manually, set it up with a runas script remembering to include the switch to remember the admin password. Scheduled task is best by far if this is a domain machine. ** As a side note, I don't know what backup facility they provide, but I just use an OSQL command attached to a SQL backup script.

SMS wouldn't like it, and that still won't make the installation silent. What's in this silent install script?

I did a search and read everything that came up. Some people reported that they had solved this issue but none explained how. Yes, the idea is that one runs the client install on the client from the server. However I need to make this run silently in order to deploy it. Worst comes to the worst I'll create my own MSI, but I'd rather not for various technical reasons in this instance. I have no issue installing the client manually, but am unwilling to do so on every client machine

We had a good laugh reading the manual for AE IP, noting "Must not be installed on a critical server, for example one running SIMS". Anyway I've been handed the full suite of this software. The resources are no problem, each being shipped with their own MSI so it's just IP and ITR to give me a headache. I have a nice little MS virtual server for this one. All the different IP and ITR packages are installed, and now I'm on the client deployment stage. IP has a nice lil MSI which seems to be suitable for deployment. ITR however doesn't appear so helpful with its "Client Install.exe" This exe seems to extract an ITR client MSI, an IS Script 10.5 MSI and an Easiteach MSI. The IS MSI unsurprisingly appears to be an original one, so is happy installing silently. However the ITR one and Easiteach one just return errors which usually imply "we don't want you to do this, run the exe". Installing Easiteach from it's own original MSI works, but doesn't license it. I've tried running "client install.exe" with just about every msiexec parameter there is (you can pass parameters with a /v), but without fail the Easiteach GUI comes up. How did you guys get around this?

Capita altered this in a recent release, August if memory served me. You can ignore the error as it has no effect. One of my colleagues was working on this issue and resolved it a few weeks ago - if anyone still needs a fix just say and I'll find out what he did