I find PST's cause way too many headaches to have not on the machine and the email is way to important to have on a end user's computer with no back up, just bite the bullet and increase mailbox size and incorporate them back into the mailbox. Changing to Windows 10 will not resolve this, upgrading/migrating your mail server will.
We recently went through this process prior to migrating to Office 365. Took some time but it was scary how many 10-20 GB PST's we found with email that can't be lost.
We are still using Exchange on-prem. IN fact we are about to do a Ex10 to Ex16 upgrade.
Our experience has been that no matter how large we make their mailboxes, people will still take everything you give them and still need to offload to PST. People still use their Outlook as a file cabinet and never have time to do a proper cleanup.
You are correct. You most definitively need to update the Horizon Agent on all of your Masters for the Connection Servers v7.2 to manage the desktops.
Also, if the migration involved updated ESXi hosts you would need to update the VMware Tools and VM Hardware on the Masters. The process for this would be:
This morning I upgraded the view agent and then it worked as it should. Glad it was that simple.
That was rough man. Is Rookie still doing the bat duties?
Get the wifi MAC address of an affected computer. SSH into the WLC and type "debug client xx:xx:xx:xx:xx:xx"
Try the RDP into the machine. The WLC should tell you what's going on at the client level.
I will give this a shot and see what it tells me. I also tested this same scenario in different offices using the WLAN and the issue persisted. So it seems like its something with the WLAN. It is only happening with this one WLAN though. My other WLAN which doesnt use 802.1X isnt having this issue.
Do you have a proxy? Or external anti spam? Or anything else that is handling the message before it reaches Exchange?
My guess is that it is being processed and then passed on and during the processing, whatever is handling the email can't handle that char and essentially changes the smtp address.
Can you see the rejected email in message tracking logs?
Edit: sorry I'm a little sick so my brain isn't working quite right. Re reading I realize you are the sender, but the advice stands. The message is likely being intercepted by something, processed, and it comes out the other side with no apostrophe.
I havent checked tracking logs yet but I will.
Our Exchange sends outgoing emails through Mimecast but the failed emails dont appear to even be reaching MC. The errors are coming from Exchange.
I'll be back in the office on Monday and will run some tests - will let you know what I find out.
How did the testing go?
Couldn't replicate the issue you're seeing, across several systems and SVMs and their associated CIFS servers...
Did you log a case with NetApp? Maybe you're hitting a burt. We're on 8.3.2P9 (cDOT) here...
I think thats the difference though... you are running cDOT.
I think these issues are only effecting 7-Mode systems.
I can not get this to run through task scheduler. The job just sits as running and never completes. If I double click the vbs to run manually it works that way. I have it set to run whether user is logged in or not, run with highest privileges and configured for Windows Server 2012 R2. Any suggestions?
Just a quick question, was the DA setup a forced tunnel or a split tunnel?
My setting for "Use force tunneling" is not checked in my DA config
Thanks for the reply, I figured it wouldn't work on forced. I changed my config to split and tested with the settings you mentioned above and it worked. Although I only needed to add the following to the nrpt: _cuplogin._tcp.domain _cisco-uds._tcp.domain _collab-edge._tls.domain +external DNS record for my expressway-e server
Nice work Glad you got it up and running!