Windows Server - Windows 2008 R2 (64-bit) Permissions Issues?

Asked By gregarican

28-Jan-10 03:17 PM

I am trying to migrate my old Windows 2000 Server to Windows 2008
Server. There are a boatload of new features in 2008 and that is even a
departure from some of my 2003 boxes. Currently I am hitting a
roadblock that appears to be permissions-related. Here are two
examples:

1) I have a few dozen scheduled tasks that I brought over into 2008.
All of these run fine when I manually run them at the 2008 box
interactively. But the tasks that involve saving files to remote
directories fail if I am logged off the 2008 box. The tasks are script
files that work fine on 2000 and 2003 boxes. I am using full UNC paths
and have verified that the user account the tasks are running under
definitely has permissions to the UNC paths. I chose to run the tasks
under the domain admin account, chose to run the tasks whether or not
the user is logged on, and chose to elevate to the highest privileges.
Still no luck. Like I said, the tasks all run perfectly when I run
them through the Task Scheduler interactively. But when I look at the
results of these tasks when I am logged off there are access/permission
denied type of errors when the UNC paths are being referenced.

2) I have some Crystal Reports hosted on IIS. The user navigates to
the web pages and a web viewer displays these RPT files. This worked
fine previously on the old 2000 box with its IIS setup. All of the RPT
files display fine on the 2008 box with its IIS except for those RPT
files that are associated with a data source that is not SQL-based. The
ones that have a UNC path reference (e.g. - Foxpro, Access, etc. data
source) all do not display due to similar access/permission denied
errors. Once again, I have verified that the user account the task was
running under (the domain admin account) has permissions to access
them, etc.

This is frankly becoming very frustrating, since I have googled and
tried to employ all of the tricks up my sleeve. And I need these areas
of the new system to function as expected. And they do under Windows
2000 and Windows 2003 Server. Just not under Windows 2008 Server. So
any suggestions would be appreciated :-)

28-Jan-10 03:17 PM

A bit of follow up regarding item #1 in my original post. Actually the
task fails if I run it from the console or allow it to run on its own
when I am logged off the console. The only time the task runs
successfully is if I am logged on the console and run it directly from
the command line outside of the Task Scheduler. In all cases I am
logged onto the console as the domain admin, created the task as the
domain admin, assigned the task to run as the domain admin, and
checked that it will run with the highest privileges...

28-Jan-10 10:10 PM

Hello gregarican,

Did you apply the GPO setting:
Computer configuration, Windows settings, Security settings, Local policies,
User right assignment "logon as a batch job" for the user account in question
on the OU where the machine is located?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

29-Jan-10 05:07 AM

es,
tion
ers

I am starting to narrow things down a bit. The scheduled tasks that
would not function all involved Office COM scripting where I'd save off
Excel and Word files. I fixed the Excel scripts by creating a folder
called c:\windows\syswow64\config\systemprofile\desktop. This desktop
folder was not present before and I googled across a posting that it
had to be there in order for the Excel COM function to work as a
scheduled task. Without this desktop folder the Excel COM would fail
while trying to perform a SaveAs() to write out the final document.
Now I am down to the Word COM scripts failing while running as
scheduled tasks. They fail when initially creating the new
Word.Application COM object. The error is captured as "The message
filter indicated that the application is busy." I am trying to run
Process Explorer on my old Windows 2000 Server to see exactly which
directories are being referenced when the tasks run on that box, since
they work fine there.

Either I am way out in left field in terms of googling a fix, or else
I am apparently the only person on Earth who is trying to use Office
COM scripting for scheduled tasks on 64-bit Windows 2008
Server...sigh...frustrating does not begin to describe it!

30-Jan-10 04:48 PM

cies,
estion
nfers
a
t
s
.
n
T
e
s
xt -

Without any action on my part, this morning when I checked the
scheduled tasks that create Word documents all of the tasks appeared
to have succeeded. Strange since when I manually ran them yesterday