![]() On the problematical rdsh, download the support tool from ![]() If the issue only happen on new user, we can run FSLogix Support Tool first on problematical server, then wait for both issue user and old user logon the problematical session host server. Installing office on RD session host server, finally check if the same “outlook can’t be opened” issue happen.Ĥ.Is the old user have no such “outlook can’t be opened” issue? Is there any weight to this? Is there anything else that we can try?ġ.Did you try to reinstall office on your problematical server?Ģ.Is there RD connection broker server in your RDS environment?ģ.Can you create a new test collection and add new test session host (with the same OS as the issue one) to this collection. The one question I do have is I stumbled onto a post about having to reinstall Office once you install FSLogix. So I'm kind of drawing a blank on what needs to be done. If I remove the user from being allowed to use FSLogix none of this happens. In some cases it works but once you log off and back on a few times. Same with deleting the profile and trying again. If I delete the mapi profile and recreate the problem will still happen. You must connect to Microsoft Exchange at least once before you can use your Outlook data file (.ost)." My issue is that on a brand new profile being created we will consistently get the error "Cannot start Microsoft Outlook. ![]() Hello all I've reviewed all of the posts that I can in relation to OST issues and tried what I could from setting time out settings, disabling shared mailbox caching, AV exclusions, NTFS/Share permissions, making sure the profile disk isn't locked and so on.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |