I wish I could be more helpful, but I'm not too familiar with IIS. It's either file ownership or file permissions.
You were correct it was a permission issue. Now I can make the changes, but in IE the site looks....bare. In Chrome its fine. Months ago, there was rumors of v1.3 release in a few days. Again, that was months ago.
Hi guys,
I'm sorry for the delay in responding here.
As you are likely aware, the new version (v1.3) is now available.
district6 thank you for posting your solution. In your case it appears that you must have uploaded the files as another user (perhaps root?), thus the permissions issue.
It is worth mentioning to anyone else who is reading this that the chown -R command that fixes this problem will need to be tailored specifically to each person's website username and file path to their osTicket installation.
City of Alton did you manage to correct the permissions issue on your IIS server? If you did, I would be very curious to know how you managed to do so! I do not have any experience with IIS. I actually rented an IIS server recently and tried to figure out how to work with permissions, but I failed to learn anything new. 🙁
I'm sorry but osTicket Awesome has not supported IE since version 1.9.12. There are many reasons for this which have already been discussed in this forum (simply search for 'IE').
stevland LIVES!!!!
First, I will search for IE in forums
Second, Yes I was able to correct the IIS issue. It was not as bad of an issue as I thought, and it was all about permissions.
Open IIS > Application Pools > find the website right click Advanced Settings > Identity needs to be ApplicationPoolIdentity > OK
Under sites Right click your site > Manage Website > Advanced Settings > Application Pool needs to be DefaultAppPool > OK
Right click on your site again > Edit Permissions > Security > Edit > Add > From This Location needs to be the local machine.
Object name is IIS AppPool\DefaultAppPool when you click check name it should correct to DefaultAppPool. Grant it full rights. Go to the ost-config.php and change that one file to deny write access. If you don't then when you are in admin side osTicket will pop a message requesting you do so.
If this is confusing let me know and I can try to be more specific lol.
I'm alive!!!! LOL
Thank you so much for the instructions. I will pass them along to the next IIS user with a permissions issue. IIS is so very different from Apache -- I would never have figured out that solution!