Search results for query: *

An SSL cert is going to run you $8/year at NameCheap. It certainly shouldn't be an expense you work very hard to avoid. Yet I see people spending hours to avoid having to get one. My time is worth more than that. It's relatively easy to use native Microsoft tools to publish a single app to a...

All you need to do is use ADSIEdit to delete the public folder database. Then you'd be able to uninstall without it balking. Dave Shackelford ThirdTier.net

It sounds like you missed one. The most common one to miss is this one: Set-ClientAccessServer -Identity "LocalServer" -AutodiscoverServiceInternalUri "https://mail.company.com/Autodiscover/Autodiscover.xml" That controls autodiscover and will definitely throw a popup if it's using the old...

How did you export the mailboxes? What did your process look like? Is it possible that someone else has disabled those mailboxes? Use the "get-mailbox jsmith" command to see if mailboxes still exist for each of the users that you exported. Dave Shackelford ThirdTier.net

I have seen that sometimes with similar devices, and usually I have to power the router off and then power it up again before it works. If that doesn't work, then I would do a factory reset on the router and set it up again from scratch: someone could have hacked in and changed settings if the...

No, that should do it, assuming that configuring the shared mailbox includes adding an email address from that particular domain. There is no requirement create an email address policy for each accepted domain as long as you manually configure the addresses on relevant mailboxes. If you are...

That's pretty much it. But I would test your policy with a single mailbox for a while to ensure that it's working the way you want it to. Here's someone's example project: https://ibenna.wordpress.com/2013/02/04/exchange-2010-retention-policy-to-clear-deleted-items/ Dave Shackelford ThirdTier.net

Yes, you can do that by 1) creating an appropriate retention tag and then 2) creating a retention policy that includes that tag and finally 3) applying that retention policy to the users that you want to have this apply to. Dave Shackelford ThirdTier.net

Thanks for posting a follow-up. Very strange: did the M$ tech give you any idea of how this situation came about? Dave Shackelford ThirdTier.net

Also, it's a known problem that any user who has *ever* been a member of an administrative group in the past will not be able to provision ActiveSync when connecting to the Exchange 2010/2013 server. The fix is in this article...

Are both servers published to the world on different public IP addresses? Which one is autodiscover.domain.com pointed at? Did you publish the legacy.domain.com A-record in the public DNS already? If you are going to do coexistence and not migrate all the users at the same time, you'll want to...

Exchange does not need DNS to be AD integrated. Exchange just needs DNS to be properly configured to properly resolve all the domain-focused DNS records located in the _msdcs zone. That being said, what you're saying concerns me, since any domain member who pings your internal domain name...

You'd want to install/enable the anti-spam agents first: https://technet.microsoft.com/en-us/library/bb201691%28v=exchg.150%29.aspx Then you'd be able to add that network to a blocklist. Dave Shackelford ThirdTier.net

Nope, the process skips duplicates. Or at least it always has every time I've rerun a batch after failure. Dave Shackelford ThirdTier.net

That is normal on Exchange 2013, even if you don't have a multi-tenant installation. This is true both on-premise and when you have a hosted Exchange 2013 mailbox like at Office365. Don't worry about it. Autodiscover should get you connected, so you shouldn't have to specify a server name...

Try to use the command. If you can't, it will tell you that it doesn't know that command. That would mean the role hasn't been assigned. Dave Shackelford ThirdTier.net

You would run these from escalated Exchange PowerShell wherever you have the Exchange 2010 management tools loaded. And you'd need to make sure that the Migration role was already assigned to Organization Managment role, which I think it is. Dave Shackelford ThirdTier.net

Exchange Management Shell (Exchange PowerShell) Dave Shackelford ThirdTier.net

There are no compatibility issues. SBS will always technically need to be the primary DC (holding all five FSMO roles) till you remove it, but you could have DHCP and DNS point to the new 2012 DC first if that's what you want. Dave Shackelford ThirdTier.net

https://smtpport25.wordpress.com/2009/10/15/powershell-to-settup-managedfolderassistantschedule-in-all-exchange-2007-mailbox-servers/ Dave Shackelford ThirdTier.net