Certificate Authority


my situation this: have sccm 2012 r2 , want enable internet based management.

my company not have existing pki infra have ca things lync , exchange 2010. issue come in ca built on 2003 standard, not enterprise cannot publish templates.

i know answer seems pretty simple, upgrade 2003 box enterprise or better yet, 2012 server. however, here's tricky part; systems team not want change because;

1. it's working right now.

2. don't have lot of server vm or hardware resources remaining

3. have ad upgrade project next year they're not interested in doing twice.

4. office politics (sigh, know)

what have small hyper-v environment use testing can stand own enterprise or 2012 server.

could enterprise ca subordinate , able publish certificate templates need internet client management? when ad project rolls out, server phased out?

> want take 2008 enterprise or 2012 server , make subordinate of 2003 standard box

yes, can setup new ca under existing 2003 ca. of course, recommended use newest available (for you) operating system maximum possible features. but, said, should consider move windows server 2003, because of platform support.


my weblog: en-us.sysadmins.lv
powershell pki module: pspki.codeplex.com
powershell cmdlet editor pscmdlethelpeditor.codeplex.com
check out new: ssl certificate verifier
check out new: powershell fciv tool.



Windows Server  >  Security



Comments

Popular posts from this blog

Edit Group Policy

Hyper-V VM not reaching OS 'Logon' screen

DNS question...