Oracle on Windows nuances

Over the past year I have begun to support Oracle in a Windows environment. This experience hasn't been as horrifying as expected, however there still have been some nuances. here's my list:

Windows password changes suddenly prevent EM jobs from running. This is something you need to dicover as soon as possible
Restoring a database on Windows with...

Over the past year I have begun to support Oracle in a Windows environment. This experience hasn't been as horrifying as expected, however there still have been some nuances. here's my list:

Windows password changes suddenly prevent EM jobs from running. This is something you need to dicover as soon as possible
Restoring a database on Windows with RMAN requires there be a Windows service running for the database.
Removing software and Oracle Home assignments have always been tough on Windows (even for a client only install which I have worked with quite a bit). This is due to the registry mess and convoluted ways to manage environment settings in Windows.
"Logon as Batch' is required for Enterprise Manager jobs that will be running. This is assigned Via Control Panel Administrative Tools Local Security Policy Local Policies User Rights Assignment