We are running Unity v3.1.3 with Digital Networking to another Unity v3.1.3 server. We will be upgrading one (1) of these Unity servers this weekend to v4.02. We would like to modify our current user id scheme to follow the user id scheme recommended in the v4.02 installation guide, with separate accounts for the Unity Directory Services and the Unity Message Store Service.
I've compared our Lab server which was upgraded to v4.02 as a pilot and our production server which is still on v3.1.3 and see the following service/account changes after adding the Unity Directory and Message Store accounts during the upgrade process to v4.02:
AvCsGateway - v3.1.3 ran as LocalSystem, v4.02 runs as Unity Message Store Acct
AvCsMgr - v3.1.3 ran as LocalSystem, v4.02 runs as Unity Message Store Acct
AvDirChangeWriter - No Change (LocalSystem)
AvDSAD - v3.1.3 ran as Unity Admin Acct, v4.02 runs as Unity Dir Service Acct
AvDSGlobalCatalog - v3.1.3 ran as Unity Admin Acct, v4.02 runs as Unity Dir Service Acct
AvGaenSvr - v3.1.3 ran as LocalSystem, v4.02 runs as Unity Message Store Acct
AvRepDirSvrSvc - No Change (LocalSystem)
AvTtsSvr - No Change (LocalSystem)
AvUMRSyncSvr - v3.1.3 ran as LocalSystem, v4.02 runs as Unity Message Store Acct
AvLic - New Service with v4.02 - runs as LocalSystem
AvMMProxySvr - New Service with v4.02 - runs as LocalSystem
AvMsgStoreMonitor - New Service with v4.02 - runs as Unity Message Store Acct
AvSqlChangeWriter - New Service with v4.02 - runs as LocalSystem
My question is related to the fact that we are set up with Digital Networking between our 2 production Unity servers. I am not an Active Directory or Exchange expert so am wondering if any of the above account changes that occur during upgrade process to v4.02 could affect our Digital Network interaction with our second Unity server still on Unity 3.1.3 and "old" Unity account structure. These servers are replicating AD info and appear to be set up under the same Exchange Administative Group as separate "Routing Groups".
Re: Digital Networking and New v4.02 Unity Account
No, the new account assignments aren't going to affect your networking with the other Unity server. We changed the account assignements around to deal with new service packs/hot fixes from Microsoft that restrict various access to message stores and the like based on group membership. Cramming everything into one account is becoming increasingly difficult and error prone so we broke it out into two accounts to keep conflicts down.
So long as each Unity server can write its properties to the directory properly they will replicate around AD and get picked up by the directory monitor on the other Unity server(s) in the network which is what's required here.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...
If you have 2 ISR routers, one acting as Failover, do we need to have both the same number of SRST licenses on the 2 routers?
No. You will only need the SRST licenses on the primary router. Because this feature...