Many of you are probably asking this question. We did answer this as part of 11 SP4 read me, but it seems a majority of people missed out on it. So here is what happened.
During beta testing of ZENworks Reporting 5.6 we encountered few issues. Unfortunately, they took a little longer to fix than anticipated. Since we wanted you to have your hands on 11 SP4 as soon as possible, instead of holding up the 11 SP4, we decided to release it and held back on ZENworks Reporting 5.6. We are now almost done fixing issues in Reporting and are currently tracking release of ZENworks Reporting 5.6 in first half of September. I want to thank you all for your patience and understanding. Please, do watch this space for our release announcement!
Update – 22nd Sep-15
September is ending in a week, but unfortunately we still have two nagging issues which are holding up the release. One concerns the scenario where under heavy load, over a period of time, we are seeing degradation in server performance. Second issue results in incorrect data with some domain objects. We are closely working with our partner to resolve this at the earliest. Our beta participants have told us how much they liked ZENworks Reporting 5.6 and I want to make sure that we deliver a quality release to you. At this point, I would say that we intend to release ZENworks Reporting 5.6 as soon as we fix these issues. Again, thank you all for your patience and understanding.
Update – 24th Nov-15
It’s been 2 months since my last update, but finally I have some news to share. We have been successful in fixing the issue which resulted in incorrect data with some domain objects. The second one, where under some select scenarios we saw degradation in server performance has been a hard nut to crack. However, we have made some good progress and with the latest patch from our vendor, we believe that now this issue may surface only over a period of time and under some very select scenarios. In such select scenarios, the server performance can be bought back to normal by a restart of services. At this point, I have two not so pleasant options :
#1 Take some more time (duration not known yet) and release ZENworks Reporting sometime in future. This does means that although many of our customers would not see this issue, they won’t be able to use ZENworks Reporting.
#2 Release ZENworks Reporting with the latest patch and then issue a patch as soon as a fix is available. In meantime, customers hitting the issue can continue working by initiating a restart of ZENworks Reporting services.
Frankly, both of above options are not something I like, but in interest of benefiting greater number of our customers, I have decided to go ahead with #2 and release ZENworks Reporting. As I write, we are working on release and you can expect the release to be out in early December (hopefully along with ZENworks 11.4.1). Please rest assured, we are committed to fixing this issue and would release a patch as soon as we have a fix ready. Many thanks for your patience and sticking with us.