Network Audit and Documentation, CENTREL Solutions Blog

I was recently asked to help with an issue in a school running Office 2010 locked down by Group Policy. Every single time that Outlook was launched as a user and then exited / closed from the close button, file exit etc. the application crashed. After looking into the antivirus, all the plugins etc the following Group Policy setting was found to be causing the issue. User Configuration GPO Microsoft Outlook 2010/Disable Items in User Interface/Predefined/Disable Quick Steps Gallery Hopefully this may help someone

Hello, Thank you for stopping by my blog. This is something I have intended to start for some time, however the demands of the business have been such that I've only now being able to do it. OK enough of me complaining how busy I am! I am the Director and founder of CENTREL Solutions. A UK based software development company that produces tools for IT departments, Schools and IT support providers whereby we can help automate away their time consuming IT tasks. The company was founded in 2008 and has a number of customers in banking, education, IT support, shipping and legal. http://www.centrel-solutions.com/ Our Tools include XIA Configuration Audit Network Server Configuration XIA Links Application Launcher for Education and used as a replacement of Novell application launcher XIA Automation Mass Create Active Directory Accounts and mailboxes from CSV Thanks, Dave

Sometimes in ASP.NET you will have a form on a page that is made up of multiple components which are then grouped into panels. You can then group these controls into validation groups, not by the panels they are in but by using the ValidationGroup property which is great however as you cycle through each group of controls you have to call Page.Validate("AddressDetails"); if (!Page.IsValid) .... do something ... Page.Validate("ContactDetails"); if (!Page.IsValid) ... do something .... What I found strange was that if there is a problem with the address details Contact details would always return as Invalid. This is because there is no ValidationGroup.IsValid property. Each time you validate a ValidationGroup if it is not valid the Page's IsValid property is flicked to false. Finding another section that is valid does not flip the switch back (nor should it because any invalid section means that the page is truely invalid. Hmmmm however I want to know ea...