jueves, 29 de marzo de 2012 16:38A production environment is running in a single Site in AD, with no subnet objects defined. When a new site is created in AD, users are unable to sign into OWA or connect with Activesync devices. If the new site is removed, the issue is resolved. There are currently two CAS servers also running the Hub Transport role, and two database servers. These AD Sites must be created in the environment, but it is needed to keep OWA and Activesync up during the transition. Has anyone come across this issue before? Thanks in advance.
Todas las respuestas
jueves, 29 de marzo de 2012 16:58This could be caused by your DNS settings on the new site,have you created a secondary DNS zone for the new site?
jueves, 29 de marzo de 2012 17:07A secondary DNS zone has not been created when the site was created. The environment broke when the new site was created, but no subnet objects were added as of yet. As a side note: this environment is running non-MS DNS.
- Editado Ben_Shaw jueves, 29 de marzo de 2012 17:11
jueves, 29 de marzo de 2012 17:28
When your users login to the new domain controller their outlook clients cannot find the CAS server which gets queried from DNS, maybe you need to enable DNS updates from your non-MS DNS to the new DC and try again.
Once you force replication from the Primary DC all objects will be copied over to the new DC.(including subnet objects if created)
It will also be advisable to try this on a test environment first
jueves, 29 de marzo de 2012 17:36
Furthermore, The DNS settings on your NIC (Second Site DC) should point to your DNS server
- Editado Samer Elk lunes, 16 de abril de 2012 3:37
viernes, 30 de marzo de 2012 15:19
When you added the second AD site, did you update the Subnets information? You need to have a CAS server in each site with the mailbox server, and if the servers think they are in different sites this may be causing the problem.
I would try re-adding the second site, but make sure you assign the subnets to the correct site.
Lance Wilson Sr. Lead Consultant Catapult Systems Inc.
- Marcado como respuesta Ben_Shaw miércoles, 25 de abril de 2012 14:28
domingo, 01 de abril de 2012 6:55Steps that we use to migrate from 2003 to 2010
- Update AD schema to 2003 native
- Install exchange on new servers
- Add new servers to AD
- Request public certificates you need (for OWA, autodiscovery, legacy, server name etc)
- Relocate mailbox to new server
- In AD point MX record to new server
- NAT public IP to new CAS server.
- Keep Old exchange for at least 15 days.
- De-commission old exchange server from the environment
lunes, 02 de abril de 2012 9:30Moderador
I'd suggest you reproduce this issue, test Exchange ActiveSync in https://www.testexchangeconnectivity.com/, and then verify the IIS log as well as the firewall log to see what error is recorded. It would help us research.
TechNet Community Support
miércoles, 25 de abril de 2012 14:33
Here's an update with the answer that we found:
Is this situation, Exchange cannot determine which site it is a member of if Subnet objects have not been defined in Sites and Services. After adding the Subnet object that the exchange servers were a member of to the Default-First-Site-Name site, and then creating the new Sites in AD, everything went smoothly. After the new Sites were built, the Subnet objects can be moved to the correct Sites. After the replication window, Exchange worked fine.
Thanks for all the advice.
- Marcado como respuesta Ben_Shaw miércoles, 25 de abril de 2012 14:33