[sims] SOLUS2 won't run as a scheduled task as another user on Windows 2012

[meastaugh1]

Having migrated a SIMS installation to a new Server 2012 VM, I have come to recreate the scheduled task to run SOLUS to automatically download and upgrade the SIMS server. I've used the same task parameters as the 2003 server and created a local admin account with which to run the task.

 

Despite having set the option to run the task regardless of whether the user is logged on, it only runs if the task user is logged on.

 

I can RDP in as the SOLUS user, disconnect the session, then login as a domain Admin and run the task successfully. As soon as I sign out the SOLUS user, the solus.log is no longer updated when the task is run. I've tried changing the task settings such as target OS, highest privilege etc.

 

Any suggestions?

[Steve21]

Few things bearing in mind 2003 didn't have have UAC etc. have you set the "Log on as batch" permission thingy? I'm assuming the account actually has permissions to access the folders/internet/network share etc?

 

Steve

[meastaugh1]

I've tried turning UAC off. The administrators group has "logon as batch", although I've just tried adding the user explicitly: still no change. Yes, I've logged on as the user and successfully run SOLUS interactively.

[Steve21]

Are you running the installer via UNC as well, or a mapped drive? (Or is this actually local local?)

 

Steve

Edited November 1, 2013 by Steve21

[meastaugh1]

It's all local, except where it's connecting to the internet to download updates from schools manager.

Program/script: "D:\SIMS-SP\SIMS .net\SOLUS.exe"

Arguments: /USER=SYSMAN /PASSWORD=password /Auto=downloadandupgrade /AGREETOTERMS /FORCEUPGRADE /SAUSER=sa /SAPASSWORD=sapassword

Start in: D:\SIMS-SP\SIMS .net\

[Steve21]

Honestly never used the command arguements, but wouldn't you need to set the proxy arguement too? As it's not "logged in" to get the "IE" settings etc

 

Steve

[meastaugh1]

I logged on as the SOLUS user to enter the IE proxy details. I've also tried using the proxy switches without any success. Even if the proxy were the issue, I'd expect it to record something in the solus.log.

[matt40k]

*cough* SOLUS3 *cough*

[meastaugh1]

*cough* SOLUS3 *cough*

 

Our support unit will not release SOLUS3 to secondary schools at the moment.