After upgrading to 8.5 Post RU2 and recreating reboots, the
cannot download and rename the NS certificate. Without this certificate the
process doesn't complete successfully. This issue may occur if the
protocol is being used.
8.5 Post RU2
The error below will be in the pectagent.log file
[2019/08/19 13:55:42.704 1872:1876 0] ..\..\apps\DeploymentClient\PECTAgent\ClientConfig.cpp:1611 _wstat64 API failed.
[2019/08/19 13:55:42.704 1872:1876 2] ..\..\apps\DeploymentClient\PECTAgent\ClientConfig.cpp:347 DownloadAndInstallCertificate returns Success. bResult = 0
[2019/08/19 13:55:42.704 1872:1876 2] ..\..\apps\DeploymentClient\PECTAgent\ClientConfig.cpp:350 Failed to rename certificate and config xml for server = SMP-W2K16-01.EPM.local
Symantec made changes to pull the port and protocol from the PXE and NS servers registry to make sure that the data in the
.ini is always correct after a
creation/recreation. Symantec has learned that if the URL path that we reference isn't in lowercase - it should be unless the registry key
manually or through other means using the console - this error will occur.
Symantec is working on a permanent solution that will be available in 8.5 RU3
On the NS and SBS/PXE servers in the environment do
Import the 'HTTPS
Scripts.xml' attached to this KB on the NS.
Once imported it will look like the following screenshot
4. Run the 'Get Web Capitals Job' on all NS and SBS/PXE servers in the environment
Open the 'Reports' folder and run the 'Get Web Value
Run the 'Change Web Capitals Job' on all NS and SBS/PXE servers shown in 'Get Web Value
Run the 'Change Web Capitals
Report' to see which systems were affected.