Minkus

Great fix, thank you. Looks like Microsoft may not officially support running ODT in the LOCAL SYSTEM context (as @petben found in previous posts below) but this is still a great fix!

I would imagine that PHP logging being broken might have resulted in 500 errors (the script usually generates a few warnings whenever it runs!) - howtarp is the expert for n-weekly timetables, see post #38 for his instructions on 2-weekly, let us know if you need anything different for 3-weekly.

Have you modified the code? Check the php error log (set up in php.ini if it's not already) and post any Warnings or Errors (ignore any Notices). This should give us a clue as to what is going wrong.

Have you modified the code? Checked php error log (see php.ini for the path)?

Had this problem on our network recently, and discovered that it can be resolved by using the old (version 12.0.0) drivers for the OfficeJet 6000. The problem started occurring when we upgraded from 12.0.0 to 14.0.0 - deleting the old drivers & installing 12.0.0 instead resolved the problem. You can get 12.0.0 from HP Officejet 6000 E609b Printer Driver Download - I know it's an 'unofficial' site, but check the digital signatures after downloading the '12.0.0 - Basic (IT)' x64 drivers, and so long as it's signed by 'Hewlett Packard Company', dated ‎21 ‎January ‎2009 03:14:22, you should be OK.

Had this problem on our network recently, and discovered that it can be resolved by using the old (version 12.0.0) drivers for the OfficeJet 6000. The problem started occurring when we upgraded from 12.0.0 to 14.0.0 - deleting the old drivers & installing 12.0.0 instead resolved the problem. You can get 12.0.0 from HP Officejet 6000 E609b Printer Driver Download - I know it's an 'unofficial' site, but check the digital signatures after downloading the '12.0.0 - Basic (IT)' x64 drivers, and so long as it's signed by 'Hewlett Packard Company', dated ‎21 ‎January ‎2009 03:14:22, you should be OK.

Regarding the Smoothwall Kerberos / NTLM issue, I believe it is possible for Smoothwall to support Kerberos and NTLM on a single port - would need some extra work on their part though but I *think* it might mean we don't have to configure Java any more. Have posted a suggestion to Smoothwall's UserVoice forum here: Support Negotiate authentication fully to allow Kerberos AND NTLM to be configured on a single port If you'd like to see this, please support the suggestin by voting for it

Thanks - you're welcome!

I have just set up a scheduled task via Group Policy Preferences, which detects if anyone is logged on, and if not, shuts down the machine when it is idle. This is all without scripting etc - performed entirely with built-in Windows tools and Windows Batch FTW! Control Panel Settings/Scheduled Tasks New Scheduled Task (Windows Vista and later) Action: Replace (required to be able to remove it when it falls out of policy) Name: Shutdown on Idle When running the task, use the following user account: NT AUTHORITY\System (just enter 'System' in the selection box) (Run only when user is logged on - default - works fine) (No need to run with highest privileges - works fine) Triggers... New Trigger -> On idle Repeat task every: 5 minutes For a duration of: Indefinitely (catch cases where the user logon state changes while still idle) (Activate: set to the time we created the task) Actions... New Action -> Start a program Program/script: %ComSpec% Add arguments: /C "for /f "tokens=* usebackq" %i IN (`%WINDIR%\system32\wbem\wmic.exe ComputerSystem GET UserName /value ^| findstr /X "UserName="`) DO "%WINDIR%\system32\shutdown.exe" -s -t 60" (This command will run 'wmic.exe ComputerSystem GET UserName to detect if a user is logged on, and if the UserName field is blank, run the system shutdown) Conditions... Start the task only if the computer is idle for: 15 minutes (Can't get the idle timeout any lower than 15 minutes, as Windows only checks the state that often - [url]http://msdn.microsoft.com/en-us/library/windows/desktop/aa383561(v=vs.85).aspx[/url]) Wait for idle for: Do not wait Stop if the computer ceases to be idle Settings... (Allow task to be run on demand - for testing) Common... Remove this item when it is no longer appliedHope this might help some other people trying to achieve the same thing. As it says in the notes, it's hard to get the idle timeout any lower than 15 minutes, as Windows only checks the 'Idle' state itself that often. If you start up a machine and then wait for it to shut down, it usually takes about 26 minutes to do so - this is probably due to Windows not checking the idle state for at least 15 minutes after startup, plus the idle time itself. However if you wait it does work, and seems fine on all our computers so far.

Nope - if setting '$postData[16][1] = 1;' seems to fix the problem, you should be good to go. I'll let a few other people test this as well, and once I get a chance to update our MRBS, I'll update the script too. EDIT: The 1.3 download post is now updated with a link to post #97 above

OK - that would be helpful. I would have a look but am completely snowed under, so no time to upgrade to 1.4.10, let alone modify the script with the changes! All you need to do is find the new POST variables for the new frequency settings (which you should be able to find in the HTML source for the 'Add Entry' screen - look for the HTML tags), find out what they should be set to to replicate the previous settings (Weekly, Number of weeks: blank), and then modify the following parts of the script to reflect this: $postData[12][0] = "rep_type"; $postData[12][1] = 2; $postData[13][0] = "rep_end_day"; $postData[13][1] = date("j",$lastDOT); $postData[14][0] = "rep_end_month"; $postData[14][1] = date("n",$lastDOT); $postData[15][0] = "rep_end_year"; $postData[15][1] = date("Y",$lastDOT); $postData[16][0] = "rep_num_weeks"; $postData[16][1] = "";If you manage to get it working, please post your changes to the forum so that everyone can test them - if they are tested and work OK for most people, I'll release a new version of the script with the updated changes. Good luck!

Hi, What version of MRBS are you using? The script was last tested by me with 1.4.8 - I believe some of the repeat booking settings have changed since then, so the script may need some modification...

I've just tried importing the second file you supplied into our MRBS (with a fake room number) and it seems to work fine. Have you fiddled with the script at all? What version of PHP are you using? I'm afraid I'm at a bit of a loss on this one.

It looks like your file has two teachers teaching the same class in the same period in a number of places: e.g.: Try combining these double entries into a single period, like so: "1","Mon","Mon:1","7yz/Sp1","SMA GPT ","Sp",29 See if this helps. We don't have this situation in any of our timetabled classes - I suspect this is causing the issue. If so I'm afraid you'll have to modify the script to handle this scenario - or just change the files before you import.

You can ignore the Notices - it's just 'less than ideal' PHP coding. Regarding the warnings - could you post a sample of the room data file you are uploading, to make sure it is all OK? Kind regards, Chris