Here’s a problem we came across recently and the resolution we came up with that I wanted to share. The issue is that when creating a task sequence for bootable media using a Boot Image, the wizard does not return any of the available Management point names.
Cause: You will run into this issue if the Management Point is configured to use HTTPS and you are using the self-signed certificate and not importing the PKI certificate while creating the TS bootable media.
To fix this you will need to import the certificate on the Security page.
NOTE This certificate must be exported in a Public Key Certificate Standard (PKCS #12) format, and the password must be known so that it can be imported.
For more information see PKI requirements for Configuration Manager 2012 : http://technet.microsoft.com/en-us/library/gg699362.aspx
Vinayak Sharma | Support Engineer | Management and Security Division Senthilkumar Pandurangan | Support Engineer | Management and Security Division
Get the latest System Center news on Facebook and Twitter:
App-V Team blog: http://blogs.technet.com/appv/ ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ DPM Team blog: http://blogs.technet.com/dpm/ MED-V Team blog: http://blogs.technet.com/medv/ Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ Operations Manager Team blog: http://blogs.technet.com/momteam/ SCVMM Team blog: http://blogs.technet.com/scvmm Server App-V Team blog: http://blogs.technet.com/b/serverappv Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials WSUS Support Team blog: http://blogs.technet.com/sus/
The Forefront Server Protection blog: http://blogs.technet.com/b/fss/ The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
We are seeing this issue but we dont have https enabled
what else can we do to fix this?