This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- FlexNet Connect
- :
- FlexNet Connect Forum
- :
- So what happens when....
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 12, 2005
11:24 AM
So what happens when....
I cancel my Update Service? I have Application X out there and the user doesn't update it, or for whatever reason I "pull the plug" and discontinue ISUS. Has this been thought through?
Are my users going to get a message every time an update cycle (scheduled update check) comes due? So if I have a 30 day check set, when that 30 days comes due, are they going to see "This application is not registered with..." or some nag message? Or (I hope) will absolutely nothing occur and the end user will never know you terminated the service and simply no updates or messages will appear again for my products?
So what will happen if I pulled the plug? Will it go silent or will users of my application be forever nagged until they install an update that doesn't use ISUS?
I know you didn't think we'd use this forever, what's the transition from subscriber to non-subscriber plan?
Are my users going to get a message every time an update cycle (scheduled update check) comes due? So if I have a 30 day check set, when that 30 days comes due, are they going to see "This application is not registered with..." or some nag message? Or (I hope) will absolutely nothing occur and the end user will never know you terminated the service and simply no updates or messages will appear again for my products?
So what will happen if I pulled the plug? Will it go silent or will users of my application be forever nagged until they install an update that doesn't use ISUS?
I know you didn't think we'd use this forever, what's the transition from subscriber to non-subscriber plan?
(11) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 16, 2005
07:53 PM
Still awaiting response.
Thank you
Thank you
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 16, 2005
07:54 PM
If you absolutely need an answer you'll need to open a MySupport case. Otherwise keep waiting.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 16, 2005
07:57 PM
I do have support but I'll keep waiting. I'm sure others are waiting for the response as well.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 17, 2005
01:24 PM
Noel,
Can you please answer this?
Thank you!
Can you please answer this?
Thank you!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 21, 2005
10:07 AM
So if I was to cancel the Update Service and I have applications out there doing update checking, what happens after the subscription is canceled?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 21, 2005
10:20 AM
I too am interested in the response to this question.
I'm surprised no one has posted anything yet.
Have you tried calling in to ask?
I'm surprised no one has posted anything yet.
Have you tried calling in to ask?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 21, 2005
10:36 AM
I'm not calling nor am I submitting a support incident. I want to know the answer and see it publicly here as others are also waiting for the response to this question.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 21, 2005
11:18 AM
i can understand that but could you not ask and then post their response?
or is it a principle of the thing thing now? 🙂
or is it a principle of the thing thing now? 🙂
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 22, 2005
12:51 PM
I have no intention of cancelling my update service but would certainly like to know what would happen if I did.
However, the lack of response here not only wants me to cancel my service but also discontinue use of any and all InstallShield product. With .NET now I have no need for the InstallShield or MSI installation and actually spent that past hour researching other installation alternatives since questions simple as this are not being answered. This speaks volumes for this company and those involved.
However, the lack of response here not only wants me to cancel my service but also discontinue use of any and all InstallShield product. With .NET now I have no need for the InstallShield or MSI installation and actually spent that past hour researching other installation alternatives since questions simple as this are not being answered. This speaks volumes for this company and those involved.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 22, 2005
01:13 PM
Been on the road a lot for the last two weeks.
We will put in a feature to silently display "No Updates" when the customer no longer is paying for the service rather than "Product not registered."
We will put in a feature to silently display "No Updates" when the customer no longer is paying for the service rather than "Product not registered."
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 22, 2005
02:46 PM
Thank you for the response Noel. I would offer this should be the default response as I've had cases where people see "Product not registered" for whatever reason and there is no failure mode on the customers sake, i.e. they don't try again, they contact support immediately thinking "Oh God, my product isn't registered...what happened, what do I need to do, 911!!!"
So please consider any queries to the update system should always be silent if it times out or no response. If we need to use some type of agent/api call with a debug message to see why people aren't getting updates, I'd rather offer that then have just ONE instance of a "Product not Registered" appear.
So please consider any queries to the update system should always be silent if it times out or no response. If we need to use some type of agent/api call with a debug message to see why people aren't getting updates, I'd rather offer that then have just ONE instance of a "Product not Registered" appear.