Me too - at least I _had!_ an issue with it.įirst of all, instructions for Exchange scanning are hard to find as the original article from Lansweeper's KB is rubbish - scan acoount DOES NOT! need to be a domain admin but for proper scanning has to be member of the AD's 'Domain Administrators' and 'Organization Management' groups.Īs long as you have your Windows firewalls turned off there is no problem at all with Exchange scanning. I have an issue with Lansweeper and Exchange scanning Rescan, and at least for me, everything scanned properly. It will ask you if you want to make the necessary changes, say yes and you're done. Once the CA was straightened out, on each Exchange server and each Domain Controller:ġ) run mmc.exe, add the Certificates snap-in for 'Computer account' and 'local computer' under Personal -> Certificates, right click the folder and All Tasks -> Request certificate choose 'Computer' template.Ģ) once certificate succeeds, in an elevated command prompt, run 'winrm quickconfig -transport:https' (without quotes). On the CA, run Certification Authority Management, right-click the 'Certificate Templates' folder and choose 'Manage', then 'properties' on the Computer template.Īfter getting the certificate, I found that I could configure WinRM HTTPS on the server just by running: 'winrm quickconfig -transport:https' in an elevated command prompt. At least for me, the certificate had to be from the Computer template for WinRM to succeed. I had to add the Domain Controllers group to the Security tab of the 'Computer' template for it to show when requesting from the Domain Controllers. Added Domain Users, Domain Computers and Domain Controllers to the group and the magic happened and the Exchange server certificate requests succeeded. On a whim, I checked it and found that it was empty (so nobody or nothing could access DCOM). I finally noticed that on the CA server is a local group called 'Distributed COM Users'. Went through dozens of links about adding permissions in DCOM Config for 'CertSrv Request', including Domain Computers in the 'Certificate Service DCOM Access' group (both in AD and in the local group on the CA), and I'm not sure how many other things I ended up checking. Error of 'RPC server not available' when requesting a certificate through the Certificates snap-in in mmc.exe. I also have an Internal Certificate Authority, and feel your pain about getting it to work. Then I did self signed (even though it tells you it can't be self signed) and it worked. I do have an Internal Root-CA and tried multiple times to get that certificate working and never could.

Lansweeper scanning