Insert name here » Windows http://blog.tanist.co.uk Web development and general IT snippets, possibly some other irrelevant things too. Fri, 03 Feb 2012 00:23:07 +0000 en hourly 1 http://wordpress.org/?v=3.2.1 Outlook 2007 Crash/Hang under VirtualBox on MacOS http://blog.tanist.co.uk/2009/06/outlook-2007-crashhang-under-virtualbox-on-macos/ http://blog.tanist.co.uk/2009/06/outlook-2007-crashhang-under-virtualbox-on-macos/#comments Fri, 26 Jun 2009 09:45:01 +0000 Henry http://blog.tanist.co.uk/?p=167 I recently installed a Windows XP virtual machine under MacOS using virtualbox, only to discover that Outlook 2007 would hang when opened (unable to connect to exchange). It seems the issue has been documented in the following ticket but no resolution has been posted. Outlook 2003 seems to works without a problem.

Update: I’ve discovered that Outlook 2007 works fine if you switch the networking options in virtualbox from “NAT” to “Bridged”. It also fixed some other issues I was having (mapped network drives and group policy didn’t get applied. For reference the domain controller is a Windows 2008 SBS server.

]]> http://blog.tanist.co.uk/2009/06/outlook-2007-crashhang-under-virtualbox-on-macos/feed/ 1 Vista Hangs on Logon, very slow at Welcome Screen http://blog.tanist.co.uk/2008/12/vista-hangs-on-logon-very-slow-at-welcome-screen/ http://blog.tanist.co.uk/2008/12/vista-hangs-on-logon-very-slow-at-welcome-screen/#comments Thu, 25 Dec 2008 21:49:36 +0000 Henry http://blog.tanist.co.uk/?p=51 We had this problem on our Vista machines in the office whereby they would get stuck during the logon process. We couldn’t for the life of us pinpoint the problem, as the logon information is very vague. Then I remembered a neat feature from XP which is also available in Vista. The key was to enabled Verbose logon information to find out what exactly was going on:

If you are using a stand-alone computer or if you want to enable verbose status messages on only one computer, follow these steps:

  1. Click Start, and then click Run.
  2. In the Open box, type gpedit.msc, and then click OK.
  3. Expand Computer Configuration, expand Administrative Templates, and then click System.
  4. In the right pane, double-click Verbose vs normal status messages.
  5. Click Enabled, and then click OK.
  6. Close Group Policy Object Editor, and then click OK.

Run a gpupdate /force if you can. After doing this, we noticed our machines were hanging at the printers group policy. After disabling the offending printer policy, logon worked fine again. As techies we decided to leave Verbose Status Messages switched on, as it can actually be very useful. Check out Chris’s previous post for more on our printer issues.

]]> http://blog.tanist.co.uk/2008/12/vista-hangs-on-logon-very-slow-at-welcome-screen/feed/ 0