Enable writing with Apple’s built-in NTFS driver

18 03 2010
I am linking to this so I don’t forget

“Compatibility with Microsoft’s NTFS filesystem is sometimes necessary for people who use either separate PCs or Boot Camp. While Apple offers a driver to read NTFS volumes, by default it will not write to them. To overcome this, there are several third-party NTFS drivers available, but in Snow Leopard you can also set Apple’s built-in driver to write to NTFS as well.”

Advertisements




Troubleshooting Outlook Performance Issues

13 03 2010

If you ever deal with complaints about Outlook speed, the first thing you need to do (apart from verifying all the latest patches are applied) is to make sure the user is following best practices when it comes to mailbox size (i.e. less than 2GB) . Of course as soon as you enforce or even suggest this you will receive complaints, once the user is shown the performance difference they may come around. This kb from Microsoft offers some additional suggestions. Hopefully this limitation will be fixed in Outlook 2010.





BSOD with Hyper-V & HP DL360 G5

11 03 2010

It appears to be a bug.
The workaround is to disable the processor C3 state (deep sleep) in the BIOS.

On DL360 G5’s (P58 BIOS) that is in the BIOS under
Advanced Options -> Processor Options -> Intel Core C3 State,
change it to ‘Disabled’.

After doing that, Hyper-V installs and no BSOD.

Get your Blue Screen of Death T-shirt, Large here…





Why iPad Is the ‘Children’s Toy of the Year’

11 03 2010

Why iPad Is the ‘Children’s Toy of the Year’

Which means it should be easy enough for most users….

Update: I pre-ordered my iPad yesterday!





Looks like a good free vmware tool

11 03 2010

I am always interested in finding free or low cost tools that look like they could be useful. VKernel Capacity View is a “tool that provides VMware performance and capacity diagnostics.”

That reminds me – I need to study for my VCP…





Recommended article on Exchange 2010 Disaster Recovery

11 03 2010

This article was recommended to us by the instructor at the Exchange 2010 class I took recently….

“To demonstrate the scalability of the DAG feature, I will use only two servers in my example – one in the production site and one in the Disaster Recovery site. This represents the smallest installation that can be done for DAG, but remember this is a flexible solution so at any point if you need to scale out with multiple DAG members the steps you would perform are nearly identical.”

from  http://anewmessagehasarrived.blogspot.com/2010/02/exchange-2010-site-disaster-recovery-on.html





System Administration tips

9 10 2009

I found these while going through stuff in my documents, I think that they are good general guidelines

  • Carefully research and document problems before making changes.
  • Don’t make changes for the sake of change.
  • Have others sanity check your proposal before implementation, then test and retest the changes.
  • Explain the risks to management and IT colleagues before deployment.
  • Maintain good backups, and develop sound restore procedures.
  • Keep detailed configuration information for all systems.
  • Have a tested local Administrator username and password for all systems in case you lose any network connectivity.
  • Distribute a step-by-step procedure before rolling out significant changes.
  • Develop a what-if list of things that could go wrong and the appropriate fallback procedures. This list should include plans to address potential problems that might occur days later (e.g., a server failure).
  • Notify users well in advance of when a project will begin and end and of any planned outages.
  • Keep a written log of activities during the changes.
  • Carefully review logs to monitor system operation before and after implementing changes.
  • Test the results from a user’s point of view. Use a non-privileged user account from a typical workstation.
  • Coordinate with support staff and try to anticipate any user education needs that might arise.
  • Document the procedures and save these files for future use.

Here are two related sysadmin books that I find helpful…