IT Answers » Windows Server Script Error

logman -cnf option is not working for me

ITKE — Fri, 11 Dec 2009 21:25:50 +0000

On Windows XP or Server 2003, I run the following command:

logman create counter MyFirstPerfLog -o “c:myScriptsWindowsPerformanceMyFirstPerfLog.blg
” -v mmddhhmm -rf 24:00:00
-cnf -cf “c:myScriptsWindowsPerformancecounters.txt”

The counter is created without any problem. But when I look at the
properties of this counter, even though the option, “start a new log file”,
under “when a log file closes” is enabled, it is not checked. I’ve tried the
following variation of the above as well:
-cnf 00:00:00
I’d appreciate it if somebody could point out my error!
Thanks

Being SYSTEM and running an application from another user

Denzman72 — Mon, 24 Aug 2009 09:19:32 +0000

Our Software Deployment Tool HP Radia works under SYSTEM Account. Insight a Package we try to connect to another Server copying some files over. Therefore we tried to use runas but it doesn´t work. We get an AccessDenied. What do we have to do ? It´s driving crazy at the moment *grrr

Startup Script Error in Windows Server 2003

Escribano1976 — Fri, 07 Aug 2009 15:17:05 +0000

Hi, i have a problem with 2 servers.
They are windows 2003 Server x64 with SP2.
They are normal servers not Domain Controllers.
I have a group policy to run a startup Script which works fine all over the network but in these 2 specific servers.
The errors i get are:
Event ID: 1053
“Windows cannot determine the user or computer name. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.”
And after this one:
Event ID:1000
“could not execute the following script xxxx could the network location cannot be reached. For more informaion about network troubleshooting see Windows Help.”

This group policy has also the option to Allow processing across a slow Network connection enabled,
And the option to run asynchronously enabled as well..
Can the startup script be force to a delay so the network is ready before the script runs?
Why is this happening is this servers?
I tried to remove them from the Domain and add them again..
I rebuilt the servers and the same thing happens.
DNS is properly configured.
Any help will be much appreciated.
Thanks