How to disable browser auto-launch?
Hi,
I would like to disable the browser auto-launch when the server starts up. This is possible in SD+ by commenting out a section in TrayIconInfo.xml, but since you've implemented a very different code base in OpManager, no such option seems to exist. Is there another way of doing this? And can I also disable the browser splash screen (which, again, can be done by editing TrayIconInfo.xml in SD+)...?
I'm sure you've been told this already, but opening a browser under the LocalSystem context is a HUGE security no-no. You guys REALLY have to get rid of this, as it is common in quite a bit of your products.
And while on that note, are you planning to ever merge your code bases for your products, as there are WAY too many inconsitencies between your products in terms of user experience, configuration and options.. here are just a few things that seem to be different across products (and missing in some completely)
- the way you switch server ports or switch to HTTPS
- some products' installers allow you to modify server port or install as service, while others don't
- some products have options to control service startup type and port / protocol directly in the interface, others require you to run a batch file, while others need you to download a whole apache replacement, while others don't have any options at all
- some products have a tray icon that launches under the console session (since it's launched under the LocalSystem process, just like the service), while others have a try icon that always sits under the tray menu and only shows up for the user who installed the service
- some products 'start service / product' icons will always start a product as a service, while others will start it as an application, even if you installed the product as a service
- some products have an option to disable browser auto-launch / splash screen, change service start-up type (automatic/manual) or other options accessible from the status menu of the tray icon, while others don't have any options there at all
- the 'Jump To' link in SD+ will open ADManager in the same tab/window, while jumping back from ADManager will open SD+ in a new window
I can really go on - but the user experience across products is so horribly inconsitent that I think it greatly affects your ability to cross-sell and upsell your products. Since I'm a OpManger user, I was enticed to try out SD+, DeviceExpert and FirewallAnalyzer since they were referred to under the Jump To menu, and each one of those products has completely different installation and launch behavior that frustrates me enough that I simply would refuse to buy the other products based on my trial experience.
Seriously, user experience is KEY - features alone (especially when they're inconsitently spread amongst your products) won't sell.
If your code base is merged, think of how much time you'd save when implementing and testing new features! It would not only unify user experience in terms of consistent feature releases across products, but also make your development team more productive overall.
Anyway, sorry about the rant - but I think you would probably appreciate getting this feedback, especially if it might have an effect on your sales.
Thanks,
Tom
I would like to disable the browser auto-launch when the server starts up. This is possible in SD+ by commenting out a section in TrayIconInfo.xml, but since you've implemented a very different code base in OpManager, no such option seems to exist. Is there another way of doing this? And can I also disable the browser splash screen (which, again, can be done by editing TrayIconInfo.xml in SD+)...?
I'm sure you've been told this already, but opening a browser under the LocalSystem context is a HUGE security no-no. You guys REALLY have to get rid of this, as it is common in quite a bit of your products.
And while on that note, are you planning to ever merge your code bases for your products, as there are WAY too many inconsitencies between your products in terms of user experience, configuration and options.. here are just a few things that seem to be different across products (and missing in some completely)
- the way you switch server ports or switch to HTTPS
- some products' installers allow you to modify server port or install as service, while others don't
- some products have options to control service startup type and port / protocol directly in the interface, others require you to run a batch file, while others need you to download a whole apache replacement, while others don't have any options at all
- some products have a tray icon that launches under the console session (since it's launched under the LocalSystem process, just like the service), while others have a try icon that always sits under the tray menu and only shows up for the user who installed the service
- some products 'start service / product' icons will always start a product as a service, while others will start it as an application, even if you installed the product as a service
- some products have an option to disable browser auto-launch / splash screen, change service start-up type (automatic/manual) or other options accessible from the status menu of the tray icon, while others don't have any options there at all
- the 'Jump To' link in SD+ will open ADManager in the same tab/window, while jumping back from ADManager will open SD+ in a new window
I can really go on - but the user experience across products is so horribly inconsitent that I think it greatly affects your ability to cross-sell and upsell your products. Since I'm a OpManger user, I was enticed to try out SD+, DeviceExpert and FirewallAnalyzer since they were referred to under the Jump To menu, and each one of those products has completely different installation and launch behavior that frustrates me enough that I simply would refuse to buy the other products based on my trial experience.
Seriously, user experience is KEY - features alone (especially when they're inconsitently spread amongst your products) won't sell.
If your code base is merged, think of how much time you'd save when implementing and testing new features! It would not only unify user experience in terms of consistent feature releases across products, but also make your development team more productive overall.
Anyway, sorry about the rant - but I think you would probably appreciate getting this feedback, especially if it might have an effect on your sales.
Thanks,
Tom