Cubasis VST, Dance EJay and "non admin" rights - refusal to start...?

[Sirbendy]

We're making alterations to our new network, tightening things up from the ground state of things we were left with.

 

One of these is that kids/staff were "admin rights enabled". Don't ask. We don't quite get it either.

 

However, now we're locking everything up tight. Everything on my test PC in the modified "non admin" OU with a new user seems to work fine (hurrah!), with the exception of Dance EJay 2005, and Cubasis VST.

 

Cubasis runs through the initial "startup splash" once, then vanishes. Subsequent startups give me an hourglass for a few seconds and that's it. No errors, no nothing.

 

EJay keeps prompting for admin user and password to run "reg_start.exe". If I decline, it dies.

 

OS on the workstations is Vista Business SP1 (fully updated), Servers are a mix of Win2k3R2 and Win2k8 x64, if it helps.

 

Any suggestions? EJay seems to have gone for a burden - the sites are down, and according to Wikipedia the company is in liquidation.

 

Failing that, any alternative suggestions for packages to do the same thing?

[mavhc]

I got this from r-e-m for the "for schools" version

 

Dance eJay for Schools – Network Instructions to aid permissions issues

 

Install the program to a read-only drive on the server. Within

this "Dance eJay" folder there is an executable "Dance2005_start.exe"

which is what you would expect to run - but this causes the problem.

We have found that if, instead, Administrator runs "Dance2005.exe"

which is within the "eJay" subfolder of the "Dance eJay" folder, you

can then create a shortcut to this "Dance2005.exe" executable and users

can run this without problems on this workstation. For a network, you need to package this operation since running

"Dance2005.exe" as Administrator creates a variety of files in the

Windows and System folder which must be on the workstation for it to

work as a user.

the info was not in it's self very usefull (as i think WriteAccess.ini has to do with RM networks) but it prompted me to find a solution.

 

Basically I ran the network shortcut on the client machine as an admin which presumably adds files to the c:\ drive of the client machine. After this running over the network as a standard (non admin) user works fine.

 

OR

 

No need to create a package - Install to a central location and create a WriteAccess.ini file with the following entries to apply to the workstations

[HKLM\SOFTWARE\Classes]

 

Everyone=0x3003F

 

[HKLM\SOFTWARE\Classes\CLSID\{4C5497EF-8D07-4358-8EC0-3D6134F866CC}\InprocServer32]

 

Everyone=0x3003F

 

[HKLM\SOFTWARE\Classes\CLSID\{CC820030-073E-47FF-856D-299BC81696B0}\InprocServer32]

 

Everyone=0x3003F

 

[HKLM\SOFTWARE\Classes\CLSID\{D44F0969-9489-4377-AA5B-4F6E077B5D8E}\InprocServer32]

 

Everyone=0x3003F

 

[HKLM\SOFTWARE\Classes\eJay_m01.eJay_main]

 

Everyone=0x3003F

 

[HKLM\SOFTWARE\Classes\eJay_m01.eJay_main\Clsid]

 

Everyone=0x3003F

 

[HKLM\SOFTWARE\Classes\eJay_m02.eJay_main]

 

Everyone=0x3003F

 

[HKLM\SOFTWARE\Classes\eJay_m02.eJay_main\Clsid]

 

Everyone=0x3003F

 

[HKLM\SOFTWARE\Classes\eJay_m03.eJay_main]

 

Everyone=0x3003F

 

[HKLM\SOFTWARE\Classes\eJay_m03.eJay_main\Clsid]

 

Everyone=0x3003F

 

[C:\WINDOWS\Temp\~DF74FC.tmp]

 

Everyone=0x1301BF

 

[C:\WINDOWS\Temp\~LHSAPI.DCT]

 

Everyone=0x1301BF

[C:\WINDOWS\Temp\~DF74FC.tmp]

 

Everyone=0x1301BF

 

[C:\WINDOWS\Temp\~LHSAPI.DCT]

 

Everyone=0x1301BF

[Sirbendy]

aha! Spot on!

 

Cheers for that, that's resolved EJay nicely. Also sorted out VST by changing permissions of the program files/cubasis folder to authenticated users.

 

Happiness...with luck we can now remove one of the most annoying security related issues on this network..

[mavhc]

Had a weird problem with Properllerhead's Reason 3, it wanted some read permission on the parent dir of the user's home dir, error wasn't helpful.

 

In other music software news: O-Generator and Riff both have site licences and install via GPO pretty easily, see the wiki