Re: windows server 2008 RC2 64bit

<snip>
<eric.hand@...> writes:
UAC was off so that wasn't the issue. I ended up moving the executable and
the config file to its own folder off of the root drive, instead of being
placed in the c:\windows\system32\ folder.. and now it works.
Weird permissions issues I guess. I had written files, etc into there as a
test, but clearly something else under the hood was preventing it. 
</snip>

The issue isn't 'permissions' as such, it's Windows File Virtualization.

File Virtualization Filter Driver is part of UAC, but not disabled just
because you turn off UAC.
(The actual driver is: %SystemRoot%\System32\Drivers\Luafv.sys)

The system in Windows-7/Server 2008 will aggressively prevent you from writing
(even temporarily) to %WinDir%, %ProgramFiles%, and several other locations.
This will break many applications that expect to be able to write to the same 
directory the executable resides in. It 'helpfully' will redirect many write 
actions to the 'approved' locations, but not all.

There are multiple workarounds/solutions, the simplest is to place files that 
need to be written in 'approved' locations like %ProgramData%.

There are other ways too, some drastic, some simpler.
The problem will be permanent though. Having jumped in at this point,
Microsoft will almost certainly expand the concept, not abandon it.
It's a complex topic, with often weird side effects.

One of the more straightforward articles it is:
http://support.microsoft.com/kb/927387



------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery, 
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now. 
http://p.sf.net/sfu/quest-d2dcopy1