Unsolved
This post is more than 5 years old
3 Posts
0
52386
October 10th, 2012 11:00
Problems deploying CCTK SCE using Powershell remote commands
Hi Folks:
I am trying to deploy a CCTK self-contained executable (SCE) called "WakeOnLAN.exe" to 50 Optiplex 990 computers in our computer labs at school using Powershell. The SCE appears to start and the log entries seem normal until it tries to run the CCTK commands to modify the BIOS settings. At that point, the log contains a CCTK usage error (136) and a listing of the cctk.exe help followed by additional log entries indicating an error occurred (log text included below). The SCE works properly when run as an administrator from within Windows.
I have tried running the command from a remote session (Enter-PSSession ) using the command "Start-Process WakeOnLAN.exe -Verb" and even tried running it with "Invoke-Expression "& cmd.exe runas /C WakeOnLAN.exe" . The same problem occurs when using "Invoke-Command" from a previously opened session. (I've run other files that require elevation to administrator and those seem to work fine.)
One curious note: If the "WakeOnLAN.exe" file is run directly from Windows (installs properly), subsequent remote commands then succeed. It appears that SCE file fails when only on intial install during a remote sessions.
Any suggestions how to resolve this problem are welcome. Thanks!
Shaun Lynch
Department of Mathematics and Computer Science
University of Wisconsin-Superior
*** LOG OUTPUT ***
[10/10/12 11:40:01] Self Contained Executable(SCE) Execution Start
[10/10/12 11:40:01] Original command line: "C:\Installation Files\wakeonlan.exe"
[10/10/12 11:40:01] SCE EXE Version: 3.0.0.0
[10/10/12 11:40:01] SCE Release: R309560
[10/10/12 11:40:01] User Command: unattended
[10/10/12 11:40:01] SCE Capabilities Value: 471859199 (0x1C1FFFFF)
[10/10/12 11:40:01] SCE Vendor Software Version: 2.1
[10/10/12 11:40:01] Local System/Model Compatible with this Package? Yes
[10/10/12 11:40:01] Local System OS Version: 6.1.1.0
[10/10/12 11:40:01] OS Compatible with this Package? Yes
[10/10/12 11:40:01] Local System OS Language: EN
[10/10/12 11:40:01] Language Compatible with this Package? Yes
[10/10/12 11:40:01] Identified Behavior : unattended
[10/10/12 11:40:01] Temporary payload log file name: C:\Users\Admin-slynch\AppData\Local\dell\drivers\wakeonlan\SCE8E15.tmp
[10/10/12 11:40:01] Translated Command Line : applyconfig.bat -l="C:\Users\Admin-slynch\AppData\Local\dell\drivers\wakeonlan\SCE8E15.tmp"
[10/10/12 11:40:01] Path : C:\Users\Admin-slynch\AppData\Local\dell\drivers\wakeonlan
[10/10/12 11:40:01] Identified Behavior : unattended
[10/10/12 11:40:09] Append Vendor Software Log: C:\Users\Admin-slynch\AppData\Local\dell\drivers\wakeonlan\SCE8E15.tmp
[10/10/12 11:40:09]
--- Start of Vendor Software Log ---
[10/10/12 11:40:09] ASCII payload log file detected.
[10/10/12 11:40:09]
2012/10/10 11:40:07 cctk - Usage error.
2012/10/10 11:40:07 cctk -
cctk Version 2.1.0 0637 (Windows - May 2 2012, 13:50:24)
Copyright (c) 2012 Dell Inc.
2012/10/10 11:40:07 cctk - Usage: cctk --option[=argument]
For more information about a particular command,
use the option '-h' followed by the command name.
Example: cctk -h --asset
--acpower -h or --help --setuppwd
--admsetuplockout -i or --infile --sfuenabled
--asfmode --lastbiosupdate* --smarterrors
--asset -l or --logfile --speedstep
--autoon --logicproc --stealthmode
--autoonhr --lowpowers5 --strongpwd
--autoonmn --mem* --svctag*
--bioscharacteristics* --mfgdate* --sysdefaults
--bioscurrentlang* --minsizeofcontigmem* --sysid*
--bioslistinstalllang* --multidisplay --sysname*
--biosromsize* -n or --namefile --syspwd
--biosver* --numlock --sysrev*
bootorder -o or --outfile --tpm
--chasintrusion --ovrwrt* --tpmactivation
--chassisintrustatus --passwordbypass --trustexecution
--completioncode* --pci* --turbomode
--cpucore --pcislots --usbemu
--cpucount* --postf12key --usbportsfront
--cpuspeed* --propowntag --usbreardual
--cpuxdsupport --pwdlock --usbrearquad
--cstatesctrl --rptkeyerr --uuid*
--embnic1 --sata0 --valsetuppwd
--embsataraid --sata1 --valsyspwd
--energystarlogo --sata2 --version*
--fanctrlovrd --sata3 --virtualization
--fastboot --serial1 --vtfordirectio
--firstpowerondate* --serrdmimsg --wakeonlan
--forcepxeonnextboot
CCTK STATUS CODE : FAILURE
[10/10/12 11:40:09]
--- End of Vendor Software Log ---
[10/10/12 11:40:09] Get name of the Folder file: C:\Installation Files
[10/10/12 11:40:09] Vendor Software Return Code: 136
[10/10/12 11:40:09] Name of Exit Code: Usage error.
[10/10/12 11:40:09] Name of Exit Code: Usage error.
[10/10/12 11:40:09] Exit Code set to: 0 (0x0)
[10/10/12 11:40:09] Result: FAILURE
[10/10/12 11:40:09] Name of Exit Code: Usage error.
[10/10/12 11:40:09] Execution terminated at date-time 10/10/12 11:40:09
[10/10/12 11:40:09] ######



tsciesinski
1 Message
0
October 15th, 2012 12:00
I am having the same issue. I've even tried creating a scheduled task with Domain admin privileges and I still get failure.
[10/15/12 14:45:02] Self Contained Executable(SCE) Execution Start
[10/15/12 14:45:02] Original command line: "c:\download\cctk\enableWOL_7AM_SMART.exe"
[10/15/12 14:45:02] SCE EXE Version: 3.0.0.0
[10/15/12 14:45:02] SCE Release: R309560
[10/15/12 14:45:02] User Command: unattended
[10/15/12 14:45:02] SCE Capabilities Value: 471859199 (0x1C1FFFFF)
[10/15/12 14:45:02] SCE Vendor Software Version: 2.1
[10/15/12 14:45:02] Local System/Model Compatible with this Package? Yes
[10/15/12 14:45:02] Local System OS Version: 5.1.3.0
[10/15/12 14:45:02] OS Compatible with this Package? Yes
[10/15/12 14:45:02] Local System OS Language: EN
[10/15/12 14:45:02] Language Compatible with this Package? Yes
[10/15/12 14:45:02] (DupUnhandledException): *** DupUnhandledException
DELL-Warren B
1.1K Posts
0
October 15th, 2012 12:00
This is the correct discussion forum and I have forwarded your post to the CCTK development team for review. If you require a formal timetable on resolution, you will need to log a ticket with Dell Support.
Thanks,
Warren
em2slyn
3 Posts
0
October 15th, 2012 12:00
So far, no responses. Is this the correct forum for issues regarding CCTK and SCE? Is there a Dell representative or someone with expertise in this area that could assist? Thanks.
egiroux
33 Posts
0
January 14th, 2015 08:00
Was a resolution to this ever found? I'm having the same problem trying to remotely execute a Dell Command Configure SCE on Win7 workstations.
DELL-Warren B
1.1K Posts
0
January 15th, 2015 06:00
Are you seeing the same issue with Dell Command | Configure (latest update to CCTK)? Also, if PowerShell is how you want to drive it, have you tried the Dell Command | PowerShell Provider?
egiroux
33 Posts
0
January 15th, 2015 07:00
I'm using Command Configure generated exe. I'm running the exec remotely using psexec. I don't have Command Configure installed on my production systems, but I could try that scenario in the lab.
egiroux
33 Posts
0
January 15th, 2015 08:00
I solved my problem. I think encryption software was getting in the way and messing with the .ini when the SCE package was being extracted to C:\ProgramData\Dell. I ran the psexec command using the local admin account and all is working well now.
Shrinidhi Katte
77 Posts
0
January 15th, 2015 22:00
Hi Egiroux,
Thanks for the update, good to see that issue is resolved now.
Can you please elaborate and help us understand the exact issue?
Which encryption software was causing this?
egiroux
33 Posts
0
January 16th, 2015 02:00
it's Dell Data Encryption, aka Credant. The problem is the config.ini within the extracted content getting encrypted on the fly. Run as non-domain user prevents the data from being encrypted.
Shrinidhi Katte
77 Posts
0
January 16th, 2015 02:00
Thanks for the update.