SuroopMC SonicWall Employee
Comments
-
Docs are available here https://www.sonicwall.com/support/technical-documentation/?language=English&category=Endpoint%20Security&product=Capture%20Client If you have moved all clients over you don't need to remove them from the 3.1 console. When we decommission all.data will be destroyed.
-
Ok - the client is not supported on Mojave so you should probably not try to upgrade those until you upgrade then to Catalina. I would recommend the following: 1. Force the upgrade from the Devices list - click on the gear button and select Upgrade Client 2. If that doesn't work, try a reboot. If neither work, please call…
-
@jramsey - what macOS version are you running?
-
Thanks @BWC ! @jramsey - that also may not work if you are already at BigSur. you will need to uninstall and reinstall as the entire client architecture is very different
-
@Bret - you're right, my bad on the typo. For windows and Linux it is indeed 4.6.x. For macOS it is 4.7.x.
-
@jramsey - thanks for your detailed feedback. The offline entries are likely because your tenant may be oversubscribed with those older entries. Please see this advisory - https://www.sonicwall.com/support/product-notification/product-advisory-capture-client-3-6-upgrade-may-19-update/210518163702317/ The S1 upgrade…
-
@Bret - the VEEAM issue should have been resolved with the latest agent we have (4.7.x). If it hasnt then I would recommend raising a case to have it investigated further. Regarding the additional folders, they should get removed on the next reboot. Nothing to worry about.
-
@Jim356 - yes it should retry again later and the S1 client will be installed.
-
@ThK - yes it will be. Please review the advisory here - if you have Static Groups configured, the script will not work for you and you will have to apply the workaround suggested. https://www.sonicwall.com/support/product-notification/product-advisory-capture-client-3-6-upgrade-may-19-update/210518163702317/
-
@BWC - yes, because your endpoints are in static groups our fix wont apply. Technically, it can be run but then you would have to reconfigure your Static Groups. Hence the workaround - effectively our script is mass-executing the workaround to make it easier. The srv_ user is specific for Servers because of a new fix for…
-
Btw, @BWC - if your endpoints are still pointing to captureclient.sonicwall.com it means they haven't downloaded the 3.6.24 update yet. That is likely because you dont have a SonicWall-Managed policy. Please update your policy configuration in the OLD portal (captureclient.soniwall.com) to choose the 3.6.24 as part of your…
-
@BWC - we are going to do a mass cleanup on our side to help resolve the issue. Please see the product advisory here https://www.sonicwall.com/support/product-notification/product-advisory-capture-client-3-6-upgrade-may-19-update/210518163702317/ If you are available to validate this in 2 hours, please send me a private…
-
Fundamentally, this is how it's setup: All clients would have been pointing to their original consoles (CC 3.1 or CC 3.5) If you are running SonicWall-managed Policies, your clients would auto-upgrade to CC 3.6 and then point to the new Console (CC 3.6) - resulting it in showing up as online and all green there If you are…
-
If your endpoints do not show up in the CC 3.6 console, its because they have not upgraded to CC 3.6 yet. @BWC - thats why the summary page still shows captureclient.sonicwall.com Please review this KB article for more details on how this works and how we recommend you get your clients migrated over to CC 3.6…
-
The portal should be back up now - again its https://captuerclient-36.sonicwall.com. Or if you prefer, just login via CSC.