[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ISSForum] RE: SP and XPU download strategy
Indeed someone is listening Karl,
You may or may not be aware of the Manual Upgrader for SiteProtector which is available on our download center as the first item listed in the SiteProtector section.
It was created for just this reason. If there is a reason why this utility does not work for this situation please let us know.
The manual Upgrader allows you to download XPU files and post them anywhere you would like. Some customers use this to burn the files to CD in environments where Internet access is not allowed. You can also configure SiteProtector to look at this internal share point for updates instead of the web, therefore if the use of the manual upgrader is automated and SiteProtector continually monitors the local share for updates you will receive the same benefits as you would if it was looking directly at the ISS web site.
Please let me know if there is any assistance that we can provide. Thanks for emailing us with your concerns, the enhancements list is monitored by our entire Product Management team because we value the input that our customers offer us.
Technical Product Manager
Phone - (404) 236-2690
INTERNET | SECURITY | SYSTEMS
The Power to Protect
From: jaeger [mailto:jaeger@xxxxxx]
Sent: Friday, January 23, 2004 9:00 AM
Subject: SP and XPU download strategy
we are about to migrate our customer base to SP 2.0.
The problem is direct access to https://www.iss.net.
Typically a sensor environemnt is managed out of band,
i.e. a special mgmt network is being setup. Many of our
customers would not allow for direct internet access from
this network. In the past we worked around this problem
using the WGM 6.7 file path option in the xpress updater.
XPU files could be downloaded vie MS IE and proxy and savely
stored on a central file server. SP 2.0 does not provide such
an option. The only choices you have are auto download or not and to
download via proxy, which is a nice enhancement. However for an easy
migration path we would like to have the alternative to download from a
file path as well. Of course this would require all XPU, SP an SR files
being available on the ISS website, which is not the case right now, but
was true for WGM environments. We have made tests with auto download set
to off. SP 2.0 will check for files in the local SP update directory.
There are two drawbacks with this approach. Firstly files have to
manually be copied there and secondly certain files are not available
via MS IE access, e.g. JobUpdate.XPU, SP_DB*XPU etc. You may argue that
https is inherently secure(?) and a firewall rule could be easily setup
for accessing www.iss.net from the mgmt server. But he real world is
different. In the end it is hard to understand, why ISS dropped an
option that used to work perfectly for many customers. When EOL a
product, the strategy should be, being backward compatible to existing
user environments and not forcing the customer base to change
everything. Migration on an as-is-basis is trouble enough!
I have cced this mail to enhancements@xxxxxxx, maybe someone is listening!
Any feedback is very welcome.
Manager Customer Services
BDG GmbH & Co. KG - Make IT safe.
Stolberger Str. 307
Tel: +49 (0)221-954231-0
direkt: +49 (0)6126-94433-21
Fax: +49 (0)6126-94433-31
ISSForum mailing list
TO UNSUBSCRIBE OR CHANGE YOUR SUBSCRIPTION, go to https://atla-mm1.iss.net/mailman/listinfo