This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Upgrading? Need advice? Let us know!

I want to ask you, our esteemed customers, what information Sophos could provide to make upgrading easier. This applies to upgrades from any version, but I'd love to be able to address people's concerns about the upgrade from Enterprise Console version 3 to version 4 especially.

We've got a great couple of upgrade guides, but what else can we do? What would you like to know more about?

Want to tell us how to do our jobs?? :smileyvery-happy: We'd love to hear to your suggestions, so let's talk!!

Thanks,

Lil

:1039


This thread was automatically locked due to age.
Parents
  • Hi Lil,

     That's a brave offer!

     I had a lot of problems upgrading from v3.0 to v4.0. I hasten to add that none of them were Sophos's fault!

    Not only do we use a separate SQL server to host the database but  I also customised our setup to link different Active directory groups to the "Sophos DB Admins" role to deal with local jurisdictions.

     Yep, I really was asking for problems :smileyvery-happy:

    This isn't a big issue at all (I recognise that my circumstance is a very, very unusual scenario) but I noticed that the installer didn't actually give any warnings when the SQL scripts to create the new upgraded database failed.  It took me a while to put the pieces together in my head :smileywink:. (or more accurately to remember I'd tweaked the AD groups, Doh!)

     With 20:20 hindsight it might be good to cater for those scripts failing and giving a diagnostic message. This isn't for fools like me (Although it might have saved me a few minutes :smileywink:). It's based on my general distrust for SQL Server/Express. It can be troublesome sometimes and having seen what the new console can do I feel it really deserves not be victim to Microsoft-isms.

     I'm trying to pitch this fairly. If someone wants to use an external SQL server than that's great that you support them. If they play around with it or 'tweak' their systems then it would be nice for you (and the more adventurous souls) to have a diagnostic message rather than have us both get confused and adding some bad tech. support requests :smileyhappy:

     That was a bit long! Sorry! It's just a thought!

    Keith

    :1523
Reply
  • Hi Lil,

     That's a brave offer!

     I had a lot of problems upgrading from v3.0 to v4.0. I hasten to add that none of them were Sophos's fault!

    Not only do we use a separate SQL server to host the database but  I also customised our setup to link different Active directory groups to the "Sophos DB Admins" role to deal with local jurisdictions.

     Yep, I really was asking for problems :smileyvery-happy:

    This isn't a big issue at all (I recognise that my circumstance is a very, very unusual scenario) but I noticed that the installer didn't actually give any warnings when the SQL scripts to create the new upgraded database failed.  It took me a while to put the pieces together in my head :smileywink:. (or more accurately to remember I'd tweaked the AD groups, Doh!)

     With 20:20 hindsight it might be good to cater for those scripts failing and giving a diagnostic message. This isn't for fools like me (Although it might have saved me a few minutes :smileywink:). It's based on my general distrust for SQL Server/Express. It can be troublesome sometimes and having seen what the new console can do I feel it really deserves not be victim to Microsoft-isms.

     I'm trying to pitch this fairly. If someone wants to use an external SQL server than that's great that you support them. If they play around with it or 'tweak' their systems then it would be nice for you (and the more adventurous souls) to have a diagnostic message rather than have us both get confused and adding some bad tech. support requests :smileyhappy:

     That was a bit long! Sorry! It's just a thought!

    Keith

    :1523
Children
No Data