Outlook and Exchange 2013 setup issues

[grim]

Yes all sites it seems, and they all use local dns servers.

Under _msdcs.gc._sites.[siteName]._tcp does each site only contain the GCs for that site?

 

[irBosOtter]

Under _msdcs.gc._sites.[siteName]._tcp does each site only contain the GCs for that site?

Yes, had to check now to make sure but all only shows their own site GCs

 

[grim]

Farking weird, next up do a packet capture and see what Outlook is trying to access

 

[irBosOtter]

Farking weird, next up do a packet capture and see what Outlook is trying to access

Will do that tomorrow, need some sleep now lol
Thanks for all the help so far, appreciate it

 

[grim]

Any luck with this?

 

[irBosOtter]

Any luck with this?

Been a bit busy with other stuff, but MS Europe now also looking at it, got another mail from them this morning, need to send them more info now, will give an update as soon as we found something, trace did not really help, pc only talks to current AD and exchange servers so nothing in there pointed to any issues unfortunately

 

[grim]

Been a bit busy with other stuff, but MS Europe now also looking at it, got another mail from them this morning, need to send them more info now, will give an update as soon as we found something, trace did not really help, pc only talks to current AD and exchange servers so nothing in there pointed to any issues unfortunately

Check your PM

 

[irBosOtter]

So far MS guys in Europe has confirmed permissions are the issue in AD. I had to send them a txt file with all permissions applied to AD accounts. One from an account that is working, and one from an account that is not working.
They now want to start looking into the AD environment to see why certain permissions are not propagating properly as inheritance looks fine on all containers and accounts, yet some permissions are not being applied to accounts in certain OU's.

 

[grim]

You can reset OU permissions to default with this command:
Dsacls "OU=Sales,DC=root,DC=net" /S /T

Or try creating a new OU, moving the users into it, remove the old OU and rename the new one to the old name and assigning the necessary group policies to it again.

I've had a similar issue with an Exchange server object's permissions, resetting them with Dsacls solved the issue

 

[irBosOtter]

You can reset OU permissions to default with this command:
Dsacls "OU=Sales,DC=root,DC=net" /S /T

Or try creating a new OU, moving the users into it, remove the old OU and rename the new one to the old name and assigning the necessary group policies to it again.

I've had a similar issue with an Exchange server object's permissions, resetting them with Dsacls solved the issue

Thanks, going to try this as the MS guys are taking their time, they haven't even contacted me again after they confirmed it's a permission issue on the OU's