UPDATE: We have discovered the reason for all our issues stems from the users appdata\local\temp folder being removed after initial login. If you repair office, it puts the folder back, only to have it removed after first login. I have appdata\local\temp in the Exclusion list, so I am not sure why this is disappearing. Any help greatly appreciated.
Hello,
We are having an issue with a few applications. As an example, MS Access opens fine. If you path to a DB on network share, it will open fine, you can hit enable to enable activex and select Trust the file. Then you log out of the VDI and log back in, and Access can no longer open the file, nor can it open any other DB. it cannot even create a new DB. What I have found is that the appdata\roaming\Microsoft\Access folder that is normally created when you open a DB is not there. So it does not create the system.idb file needed, nor can it access the system.mdw file that is created as well, as they don't exist. They are not in the Profile in the user store either. We are using UPM 1808 on Windows 2019 LTSC (1809) and using WEM to provide the UPM rules. We are running on 7.15 LTSR. We can run repair on office and it will be fixed until next login, we can also re-build the profile, which will allow it to work until next login. If we launch Access with the local admin account, then we can path to the file and open it with out issue in the same user session. We are having similar issues with excel worksheets with Macros and other active x applications.
Edited by trogers@wrberkley.com Discovered Reason for issue - need to figure out why it's happening
Question
Tim Rogers1709160555
UPDATE: We have discovered the reason for all our issues stems from the users appdata\local\temp folder being removed after initial login. If you repair office, it puts the folder back, only to have it removed after first login. I have appdata\local\temp in the Exclusion list, so I am not sure why this is disappearing. Any help greatly appreciated.
Hello,
We are having an issue with a few applications. As an example, MS Access opens fine. If you path to a DB on network share, it will open fine, you can hit enable to enable activex and select Trust the file. Then you log out of the VDI and log back in, and Access can no longer open the file, nor can it open any other DB. it cannot even create a new DB. What I have found is that the appdata\roaming\Microsoft\Access folder that is normally created when you open a DB is not there. So it does not create the system.idb file needed, nor can it access the system.mdw file that is created as well, as they don't exist. They are not in the Profile in the user store either. We are using UPM 1808 on Windows 2019 LTSC (1809) and using WEM to provide the UPM rules. We are running on 7.15 LTSR. We can run repair on office and it will be fixed until next login, we can also re-build the profile, which will allow it to work until next login. If we launch Access with the local admin account, then we can path to the file and open it with out issue in the same user session. We are having similar issues with excel worksheets with Macros and other active x applications.
Edited by trogers@wrberkley.comDiscovered Reason for issue - need to figure out why it's happening
Link to comment
9 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now