Don't get the logic behind that: UNC path required to import certs into Exchange 2013
jibbajabba
Member Posts: 4,317 ■■■■■■■■□□
in Off-Topic
Why the heck is it mandatory to use an UNC path for the cert location in order to import it?
My own knowledge base made public: http://open902.com 
Comments
-
TechGuy215
Member Posts: 404 ■■■■□□□□□□
It's a Microsoft Product....nuff said.
* Currently pursuing: PhD: Information Security and Information Assurance
* Certifications: CISSP, CEH, CHFI, CCNA:Sec, CCNA:R&S, CWNA, ITILv3, VCA-DCV, LPIC-1, A+, Network+, Security+, Linux+, Project+, and many more...
* Degrees: MSc: Cybersecurity and Information Assurance; BSc: Information Technology - Security; AAS: IT Network Systems Administration -
DevilWAH
Member Posts: 2,997 ■■■■■■■■□□
Not been playing with Lync have you, as this caused me a major headach! ITs meant to be there as a secondry validation check (according to the Microsoft Consultent). but for some reason some implementations make it a requirement which is a pain if you don't want to publish a UNC path. However in most case it works as long as it is populates with some thing even if its not a real value.- If you can't explain it simply, you don't understand it well enough. Albert Einstein
- An arrow can only be shot by pulling it backward. So when life is dragging you back with difficulties. It means that its going to launch you into something great. So just focus and keep aiming.
Linkin Profile - Blog: http://Devilwah.com