Dell Server Deployment Pack 3.0 with Dell Toolkit 5.1 will have problems running the set RAIDcfg command. We found that there was a security permissions change starting in DTK 5.1 for sure; and possibly as far back as DTK 4.4 because I had the same error there as well.
The permissions change created a situation where the envout.txt file could not be created by the script in the downloaded package folder. The default location is "X:\Windows\Temp\SMSTSLog\PackageID\Tools\AMD64".
You would see an error in the SMSTS.log saying "File is not writable!" in the "Output from command execution" block immediately after the "Starting execution of ArrayBuilder script" block. Then in the "StdOut output from the command:" block you will see "EXITCODE=204", which means the same thing "File is not writable". Then just a little further down you will see something like this:
##########################################
##########################################
###
### CRITICAL ERROR
###
##########################################
##########################################
ERROR CODE: 1
DESCRIPTION: Could not find the raid output file you specified (envout.txt). Please check the path.
SEVERITY: 3
##########################################
##########################################
###
### CRITICAL ERROR
###
##########################################
##########################################
As a work-around, you could create a new script to make an empty envout.txt in the AMD64 folder. Attach that script to your task sequence to run before the Set RAID step.
The resolution to this will be in a new version of DTK that will hopefully be out in the next week or two (from June 5, 2015).
And please remember that anytime you update DTK in ConfigMgr, you will need to re-distribute the Application Management\Packages\Dell PowerEdge Deployment\PowerEdge Deployment Toolkit Integration package in ConfigMgr.
Does Run over the Network also solve this issue (instead of using download and execute)?
ReplyDeleteUnfortunately not. Running these scripts using the download and execute is really the only reliable way to get them to work, from my experience.
Delete