minimoo

I'm trying to get a couple of minor tweaks in - that and I seem to be quite good at spotting bugs in new features I'm hoping this week is going to be a quiet week at work so can get up to date. (paul===minimoo)

You probably want SSL to ensure that any usernames/passwords are sent encrypted, so trying to turn that off would be a fairly bad idea. Given that janet can sell ssl certs to some organisations, there's commercial and free options on the internet, or if you don't care about security warnings, the ability to create a self-signed cert, it's not necessarily expensive to have the site running over https

What type of authentication are you using within HAP? What are type of authentication are you using on TMG + IIS ?

"Did we get any further with adjusting the column widths at all fo display as well, or the catagories of resources a la earlier versions?" Whilst not adjusting the column widths directly - assuming Nick doesn't disagree, I added a change earlier to display just the Day/Month on the bookings page and not the year. I've then knocked ~30 pixels off the width of the columns which for me does mean it starts to fit better - although with that shorter width you start to hit issues with truncation so it does need some more work.

Sorry for jumping in on this but in case I broke anything.. The dropdown list for number of periods is blank? What is your config for the that bookable room and what list of periods do you have?

Solus3 has actually improved a good deal [bugfixes] at least since it was introduced. We migrated fairly early on [ In fact, It was around September/October 2011], and the first couple of updates were a nightmare - albeit out sims setup is more complicated then some other schools I believe. For example, last Friday between 3pm-5pm we updated FMS+SIMS to the autumn release - our internal support system where staff report issues with pc's picked up 3-4 issues from staff regarding sims not updating. That's now down to manageable levels -> with our tweaks around solus2, I'd ultimately end up having to fix a similar number of pc's. To give you an example of 'our sims setup is more complicated'. We have 3 FMS databases, 5 FMS workstations, push sims out to ~100 laptops and ~3-400 workstations that may be used by staff. Capita do still have some areas where improvement can be made, and some flaw's in the process - however, it I've got to the point where i'm fairly confident that a solus3 upgrade will run smoothly. a) As it was said in an earlier post - if you run WSUS [windows updates service], or can push out dotnet 4 by some method - get that onto the any laptops/server first. (We are lucky that we have windows 7 across site, and the deployment process automatically runs wsus, pulling down all updates including dotnet4.) b) If you rebuild pc's a lot, make sure you think about keeping the solus 3 database up to date c) Set up the service to auto download updates to end devices but NOT install them - you can get the updates downloaded to the workstations ready for when you 'upgrade' i.e. once capita do a new release allow time for the solus 3 agents to get the setup files locally ready for the install d) Staff tend to miss the notification about solus3 asking them to close sims - so pick a time when they are not in. If you do do a sims update when people are around, they'll miss the update window, go to move screen in sims - which will crash as the DLL's version do not much. Trying to go back into sims will similarly error - rebooting the pc allows the pending file operations to complete. Paul

Thanks - stepping back a bit to the exchange thing - i'm trying to decide from the second paragraph of msdn.microsoft.com/en-us/library/bb856547(v=exchg.140).aspx [forum wont allow links to be posted until I get a post count of 2 ], whether we should really make sure it matches - to quote: "Requests that do not include version headers are handled as requests from the initial release version of Exchange 2007. If the Exchange 2010 version is not specified, schema validation errors might occur because the request will be validated against the initial release version of the Exchange Web Services schema instead of the Exchange 2010 version of the schema." Reading that, that would also imply it should be working already I think....

EWS Dotnet component uses the latest version by default, but can be initialised to use an older version. [msdn.microsoft.com/en-us/library/microsoft.exchange.webservices.data.exchangeservice.exchangeservice(v=exchg.80).aspx] So to fix this without updating exchange to SP2, if you have visual studio installed, it should be possible to fix this by editing exchangeconnector.cs in the HAP.Web.LiveText. Changing the line that reads: ExchangeService service = new ExchangeService(); To: ExchangeService service = new ExchangeService(ExchangeVersion.Exchange2010_SP1); in your case. Valid exchange server versions in this enumeration are currently: Exchange2007, Exchange2007_SP1,Exchange2010,Exchange2010_SP1,Exchange2010_SP2 I'm thinking a dropdown list in the setup that allows someone to specify the current exchange server version Paul