In 7.1 we did not use SSL / have require HTTPS enabled.
Our process was to Ghost a machine while in automation, then use a script to determine PC model and inject the drivers onto into a specified Drivers folder that the sysprepped image would use for installing the drivers during first production boot. We also Copied the Agent Install files to C:\Windows\Temp
We would use tokens to inject the correct install commands into a setupcomplete.cmd that ran first boot to install the agents pointing to the correct NS in our environment:
Example Setupcomplete.cmd
START /WAIT C:\WINDOWS\Temp\AeXNSC.exe -s -a ns=%NSSERVER% nsweb=http://%NSSERVER%/Altiris/ NOSTARTMENU
msiexec.exe /i C:\WINDOWS\Temp\SoftwareManagementSolution_Plugin_x64.msi /qn /norestart
msiexec.exe /i C:\WINDOWS\Temp\Altiris_DeploymentSolutionAgent_7_5_x64.msi /qn /norestart skipaim=1
This worked great.
Now in 7.5 with require HTTPS enabled, cant get the agent to initialize or connect to the SMP after install (agent is installed but has the little red circle with the line thru it over the agent icon, instead of the green circle with the lock)
I have even followed the User guide for exporting the SMP %NSSERVER% Server CA.cer and importing it on the pcs before installing the agent, and still get the same results. (even manually importing the cert to the trusted root store, instead of scripting it)
certutil -addstore -enterprise root C:\Windows\Temp\SMP%NSSERVER%CERTSERVR.cer
START /WAIT C:\WINDOWS\Temp\AeXNSC.exe -s -a ns=%NSSERVER% nsweb=https://%NSSERVER%/Altiris/ NOSTARTMENU
msiexec.exe /i C:\WINDOWS\Temp\SoftwareManagementSolution_Plugin_x64.msi /qn /norestart
msiexec.exe /i C:\WINDOWS\Temp\Altiris_DeploymentSolutionAgent_7_5_x64.msi /qn /norestart skipaim=1
Anybody have installing the agents with SSL on the PC after the production boot working that can give me any hints?