Environment
Novell ZENworks Configuration Management 11.2
Situation
When user PATH is defined in Control Panel > System > Advanced > Environment, running a script bundle with commands requiring default system and user %PATH% fail.
ERROR:
not recognized as an internal or external command
Resolution
This is fixed in version 11.2.4 - see KB 7012027 "ZENworks Configuration Management 11.2.4 - update information and list of fixes" which can be found at http:////support.microfocus.com/kb/doc.php?id=7012027
Please report any problems encountered when using this Patch, by using the feedback link on this TID.
Workaround: if it is not possible to upgrade to ZCM 11.2.3a Monthly Update 1 at this time, in the interim, Novell has made a Patch available for testing, in the form of a Field Test File (FTF): it can be obtained at https://download.novell.com/Download?buildid=9HBVzkFiARQ~ as "ZCM 11.2.3a fix for Random login errors with UAC enabled - see KB 7009405, Script bundles using commands requiring default PATH fail - see KB 7012200 and ZCM 11.2.3a: Volatile environment variables may not be available if the Novell Client is used and drives are mapped - see TID 7012172". This Patch should only be applied if the symptoms above are being experienced, and are causing problems.This Patch has had limited testing, and should not be used in a production system without first being checked in a test environment. Some Patches have specific requirements for deployment, it is very important to follow any instructions in the readme at the download site. Please report any problems encountered when using this Patch, by using the feedback link on this TID.
Workaround: For the case of devices logging into Novell NetWare client using login scripts that have search path mappings: Do not use drive searching on Novell client login script. For more information about search drive mappings see https://www.novell.com/documentation/oes/stor_filesys/?page=/documentation/oes/stor_filesys/data/bs3ff6s.html
For the case of user PATH having been explicitly set by Administrator, if this is not a requirement, use the system PATH and remove user PATH entries from environment settings.
Additional Information
A good way to demonstrate the problem is to create a Windows bundle that runs cmd as user. Launch the bundle and at the resulting cmd prompt, type set.
The PATH variable has only the entries for the user defined path, not appended to default system path.
Example:
c:\userdir
should be:
c:\windows\system32;c:\program files;...;c:\userdir
In the case of NetWare client for the case of drive mappings
Example:
Path=Z:.;