My specific problem here was that Windows devices and Android devices got SCEP certficates, as excepted but Apple devices did not. For the record my specific problem was not found with this script. Second, if you haven’t tried the deployment verification scripts, try them, they are really handy for finding small errors such as spelling. I have my checklist I always follow, semi-automated (that may be another post if interesting?)Īnyway, after spending quite a lot of hours troubleshooting the NDES/SCEP installation, I will try to sum up some tips for troubleshooting.įirst of all there is a very good knowledge base article that will guide you thru all the steps: (Interesting catch-22 situation.I don’t know how many NDES/SCEP installations I have been doing until today, still there are a lot of dependecies and a couple of pitfalls that comes up every now and then. An entry in one of your event logs should indicate what the problem is. Do you see procmon.exe appear briefly, then go red and/or disappear? If so, then “something” is preventing it from running and is killing it. Launch Process Monitor while carefully watching the other part of the screen. I can run Process Monitor under Windows 7 圆4 with no problems, and as suggested it does spawn a procmon64.exe process.ĭo you also have Process Explorer? Does it work? If not then Task Manager will do, but try splitting your screen so that you can run Process Explorer (or Task Manager) in one part, and have the command where you try to launch Process Monitor in the other part. Could also be the dreaded UAC getting in the way, so check your settings.
If you do not see your own user name in the list, add it in and give it “Full control”. The user (or group) that you are running under needs to have “Full control”. Using Windows Explorer or similar, navigate to the executable file (I would guess C:Program FilesProcess MonitorProcmon.exe), right-click on it, then Properties, then Security.
If you do not see the “Do you want to run” message when you run it as administrator, that suggests a security issue.
0 kommentar(er)
