We have a Lync 2010 environmnet but need to move to lync 2013 ent. For reasons I won't go into, coexistence won't work.
It must reside in the same domain/forest, so I need to, in one weekend decom the old lync 2010 deployment and put into production our new lync 2013 deployment.
We used public certs for all certs. (don't ask), and will be using public certs for the new lync 2013 deployment. What will need to be done to make sure there's a smooth transition on the DNS/certs front?
We will be using new names/fqdns for all things if possible like a new front end and edge pool names, server names obviously, external web services, etc. What about sip.domain.com? I know thats on the access edge/"SIP" interface. Also , it is defined in SRV records internally, externally, etc.
I'd rather not mess with decomming the old certs on that weekend. Can I just use a different name? How built into Lync is the name "sip.domain.com"?
Thanks,
Josh
