Avoid embarrassing mistakes: How to recall an email in Outlook

Outlook Windows 10

How to recall an email in Outlook

Recalling an email in Outlook can save you from many awkward or embarrassing situations. Here’s how you can do that.

  1. Head to the Sent Items part of the Outlook app and double click the message that you want to recall.
  2. Navigate to the Message tab in the open window with the message.
  3. Head to the fourth group of options in the top menu bar under Move, and choose Recall this Message.
  4. Choose to delete the unread copy of the message on the server, or replace it with a new message.
  5. Press OK

Applies to All Windows 10 Versions

One of the most embarrassing things in life is replying to an email, and realizing you’ve replied to all, or sent out something to the recipient that wasn’t meant to see. Luckily, there is a way around this common problem. With the Outlook app as part of Office 365, you can easily recall an email — granted that you’re using a Microsoft Exchange account and the feature has been enabled by your IT department. In this guide, we’ll show you how you avoid mistakes and recall emails in Outlook.

Steps to recall an email in Outlook

The first step in recalling an email in Outlook is to head to the Sent Items part of the Outlook App. After that, you can double click the message that you want to recall. Then, you need to navigate to the Message tab in the open window with the message. You can then head to the fourth group of options in the top menu bar under Move, and choose Recall this Message.

After following the steps above, a new window with the recall a message option should have appeared. From there, you’ll have two options, both of which will require you to press on OK afterward. You can either delete the unread copy of the message on the server, or you can replace it with a new message. The recipient might have already viewed the message, so deleting the unread copy might not always work. You can, however, select the option to receive a report on if the recall was successful.

Speed is of the essence here, and you should always recall right as you realize your mistake. If all else fails, that’s where the second option comes in, allowing you to write an apology message so that the original (error) email does not get opened.

Other ways to avoid having to recall messages

Recalling messages might not always work, but there are some ways you can avoid getting into the situation. First off, you should always slow down and double-check where your emails are heading. You also can even these troubles by setting up an Outlook rule to delay emails. This ensures that your messages sent through Outlook will be delayed by a certain number of minutes, giving you a short period of time to recall messages if something were to go wrong.

Share This

Further reading: Email, Microsoft, Outlook

Related:

  • No Related Posts

Proactive Threat Protection doesn’t get installed

I need a solution

Hello all,

I’m running a trial of SEP 15 on Windows Server 2016.

The package used to install the client on Server 2016 is the same as on a Windows 10 client.

The Windows 10 installation shows that ‘Proactive Threat Protection’ and ‘Network and Host Exploit Mitigation’ are installed along with the ”Virus and Spyware Protection’.

The same package only installs ‘Virus and Spyware Protection’ on the 2016 Server.

Both windows 10 and 2016 server are showing ‘No problems deteted’ however the security cloud console is showing status of ‘Not Computed’ and status reason of 

‘Not Found (SONAR) + 8 others’.

any help appreciated, 

kind regrds, NC

0

Related:

  • No Related Posts

14.2 RU1 won’t install on 2008 SP2 x64

I need a solution

I’m trying to upgrade a client on a Windows Server 2008 SP2 x64 machine, but it will not install.

I see the following in the SEP_INST log

CommunicateLaunchConditions: NOT PackageIntegrityError=1
CommunicateLaunchConditions: VersionNT >= 601=0
CommunicateLaunchConditions: Symantec Endpoint Protection only be installed on Windows 7 / Server 2008 R2 and later.
CommunicateLaunchConditions:  calling communicate state with the following arguments: 
CommunicateLaunchConditions: Prodversion = 14.2.3332.1000
CommunicateLaunchConditions: PathToSylink = C:Program Files (x86)SymantecSymantec Endpoint Protection14.2.1015.0100.105SmcLUSetup
CommunicateLaunchConditions: Oldversion = 14.2.1015.0100
CommunicateLaunchConditions: ReasonStr = Symantec Endpoint Protection only be installed on Windows 7 / Server 2008 R2 and later.
CommunicateLaunchConditions: StatusCode = 302469127
CommunicateLaunchConditions: Initializing opstate communicator
CommunicateLaunchConditions:   File path = C:Program Files (x86)SymantecSymantec Endpoint Protection14.2.1015.0100.105SmcLUSetupSyLink.xml
CommunicateLaunchConditions:   Reg  path = 
CommunicateLaunchConditions: Invalid registry path for client identity
CommunicateLaunchConditions: Added OpState callback
CommunicateLaunchConditions: Added OpState provider.
CommunicateLaunchConditions: Initialized UserInfo Provider. Initialization done.
CommunicateLaunchConditions: Successfully created CVE object
CommunicateLaunchConditions: Failed to send the opstate: 0x80004005
MSI (s) (F0:88) [07:20:28:674]: Doing action: preLaunchCond
Action ended 7:20:28: CommunicateLaunchConditions. Return value 1.
MSI (s) (F0:7C) [07:20:28:690]: Invoking remote custom action. DLL: C:WindowsInstallerMSI47E5.tmp, Entrypoint: preLaunchCond
Action start 7:20:28: preLaunchCond.
MSI (s) (F0!D4) [07:20:29:767]: Note: 1: 2731 2: 0 
IDCCA:  preLaunchCond – Launch condition `7Symantec Endpoint Protection only be installed on Windows 7 / Server 2008 R2 and later.` with condition `VersionNT >= 601` failed

But in the release notes I see the following:

Windows Server 2008 (32-bit,64-bit;RTM, R2, SP1, and SP2)

Anybody seen this happen before and maybe has a solution? 

0

Related:

  • No Related Posts

SEP 14.2 RU1(3335): service “SepMasterService” crashes randomly on Windows 10

I need a solution

Hello guys,
It happens sometimes, like one time per several days on latest Win 10 x64 1903 Enterprise
Event log says “The Symantec Endpoint Protection service terminated unexpectedly.  It has done this 3 time(s).”. Error: 7034
When I start service manually after that failure it works properly but it can’t be recovered aromatically because there is no recovery option after third failure.
I was trying to add it but I have no access even during command prompt.
Please see screenshots.

I would like to fix that crashes and if it’s possible add additional recovery restart service option to 3rd or later failures.

I also have SEP clients on Windows 8.1 and they have no problem, no one crash was noticed.

Any suggestion would be highly appreciated.

0

Related:

  • No Related Posts

Client Connected But Doesn’t Show in SEPM

I need a solution

Greetings,

I have 4 Windows 7 Standard Embeded machines on my network. I have the Symantec 14.2.0.1030.0010 Client installed on them with just A/V function. According to the Troubleshooting window for the server connected it shows “Connected” on port 443.

In the SEPM Console I added the A/D container under clients which shows all 4 computers. Funny part is all 4 show offline. 

So what do I believe? The client or the SEPM?

And how do I fix it?

0

Related:

  • No Related Posts

Microsoft Windows Security Updates July 2019 overview

Microsoft released security updates and non-security updates for Microsoft Windows (client and server) and other company products on the July 9, 2019 Patch Day.

Our overview provides system administrators, organizations, and home users with detailed information on released patches, known issues, and other relevant information.

The overview starts with an executive summary; it is followed by the operating system distribution, and the list of security updates for all versions of Windows.

The list of known issues, security advisories released by Microsoft, and download information follow.

Here is the link to the June 2019 Patch Day in case you missed it.

Microsoft Windows Security Updates July 2019

Here is an Excel spreadsheet listing security updates that Microsoft released for its products in July 2019. You can download the archive with a click on the following link: Microsoft Windows Security Updates July 2019 Overview

Executive Summary

  • Microsoft released security updates for all client and server versions of the Windows operating system.
  • All versions of Windows are affected by (at least) 1 critical security issue.
  • Security updates were also released for other company products such as Internet Explorer, Microsoft Edge, Microsoft Office, Azure DevOps, .NET Framework, Azure, SQL Server, ASP.NET, Visual Studio, and Microsoft Exchange Server
  • The Microsoft Update Catalog lists 212 entries.

Operating System Distribution

  • Windows 7: 21 vulnerabilities: 1 rated critical and 20 rated important
  • Windows 8.1: 19 vulnerabilities: 1 rated critical and 18 rated important
  • Windows 10 version 1703: 24 vulnerabilities: 1 critical and 23 important
  • Windows 10 version 1709: 36 vulnerabilities: 1 critical and 35 important
  • Windows 10 version 1803: 37 vulnerabilities: 1 critical and 36 important
  • Windows 10 version 1809: 36 vulnerabilities: 1 critical and 35 important
  • Windows 10 version 1903: 36 vulnerabilities: 1 critical and 35 important.

Windows Server products

  • Windows Server 2008 R2: 21 vulnerabilities: 1 critical and 20 important.
  • Windows Server 2012 R2: 22 vulnerabilities: 2 critical and 20 important.
    • CVE-2019-0785 | Windows DHCP Server Remote Code Execution Vulnerability
    • CVE-2019-1102 | GDI+ Remote Code Execution Vulnerability
  • Windows Server 2016: 27 vulnerabilities: 2 critical and 25 important
    • CVE-2019-0785 | Windows DHCP Server Remote Code Execution Vulnerability
    • CVE-2019-1102 | GDI+ Remote Code Execution Vulnerability
  • Windows Server 2019: 40 vulnerabilities: 2 critical and 38 are important.
    • CVE-2019-0785 | Windows DHCP Server Remote Code Execution Vulnerability
    • CVE-2019-1102 | GDI+ Remote Code Execution Vulnerability

Other Microsoft Products

  • Internet Explorer 11: 6 vulnerabilities: 6 critical
    • CVE-2019-1001 | Scripting Engine Memory Corruption Vulnerability
    • CVE-2019-1004 | Scripting Engine Memory Corruption Vulnerability
    • CVE-2019-1056 | Scripting Engine Memory Corruption Vulnerability
    • CVE-2019-1059 | Scripting Engine Memory Corruption Vulnerability
    • CVE-2019-1063 | Internet Explorer Memory Corruption Vulnerability
    • CVE-2019-1104 | Microsoft Browser Memory Corruption Vulnerability
  • Microsoft Edge: 7 vulnerabilities: 7 critical
    • CVE-2019-1001 | Scripting Engine Memory Corruption Vulnerability
    • CVE-2019-1062 | Chakra Scripting Engine Memory Corruption Vulnerability
    • CVE-2019-1092 | Chakra Scripting Engine Memory Corruption Vulnerability
    • CVE-2019-1103 | Chakra Scripting Engine Memory Corruption Vulnerability
    • CVE-2019-1104 | Microsoft Browser Memory Corruption Vulnerability
    • CVE-2019-1106 | Chakra Scripting Engine Memory Corruption Vulnerability
    • CVE-2019-1107 | Chakra Scripting Engine Memory Corruption Vulnerability

Windows Security Updates

Windows 7 Service Pack 1 and Windows Server 2008 R2

KB4507449 — Monthly Rollup

  • Same as KB4507456.

KB4507456 — Security-only Update

  • Security updates to Windows Server, Microsoft Graphics Component, Windows Storage and Filesystems, Windows Shell, Windows Input and Composition, and Windows Kernel.

Windows 8.1 and Windows Server 2012 R2

KB4507448 — Monthly Rollup

  • Fixed a Bitlocker issue that caused Bitlocker to go into recovery mode.
  • Same as KB4507457.

KB4507457 — Security-only Update

  • Security updates to Windows Wireless Networking, Windows Server, Windows Storage and Filesystems, Microsoft Graphics Component, Windows Input and Composition, Windows Kernel, and Windows App Platform and Frameworks

Windows 10 version 1803

KB4507435

  • Fixed a Bitlocker issue that caused the encryption software to go into recover mode.
  • Security updates to Windows Wireless Networking, Windows Server, Microsoft Scripting Engine, Windows Storage and Filesystems, Microsoft Graphics Component, Windows Kernel, Internet Explorer, Windows Input and Composition, Windows Virtualization, Windows App Platform and Frameworks, Microsoft Edge, Windows Cryptography, and Windows Fundamentals.

Windows 10 version 1809 and Windows Server 2019

KB4507469

  • Fixed a Bitlocker issue that caused the encryption software to go into recover mode.
  • Fixed an issue that caused the camera to become unresponsive.
  • Security updates to Windows Server, Microsoft Scripting Engine, Microsoft Graphics Component, Internet Explorer, Windows Input and Composition, Windows Virtualization, Windows App Platform and Frameworks, Windows Kernel, Microsoft Edge, Windows Cryptography, and Windows Fundamentals.

Windows 10 version 1903

KB4507453

Other security updates

KB4506954 — 2019-07 Security Only Update for .NET Framework 4.8 for Windows Embedded 8 Standard and Windows Server 2012

KB4506955 — 2019-07 Security Only Update for .NET Framework 4.8 for Windows 8.1 and Windows Server 2012 R2

KB4506956 — 2019-07 Security Only Update for .NET Framework 4.8 for Windows Embedded Standard 7, Windows 7, and Windows Server 2008 R2

KB4506961 — 2019-07 Security Only Update for .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 for Windows Embedded 8 Standard and Windows Server 2012

KB4506962 — 2019-07 Security Only Update for .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 for Windows 8.1 and Windows Server 2012 R2

KB4506963 — 2019-07 Security Only Update for .NET Framework 4.6 for Windows Embedded Standard 7, Windows 7, Windows Server 2008 R2, and Windows Server 2008

KB4506964 — 2019-07 Security Only Update for .NET Framework 4.5.2 for Windows 8.1 and Windows Server 2012 R2

KB4506965 — 2019-07 Security Only Update for .NET Framework 4.5.2 for Windows Embedded 8 Standard and Windows Server 2012

KB4506966 — 2019-07 Security Only Update for .NET Framework 4.5.2 for Windows Embedded Standard 7, Windows 7, Windows Server 2008 R2, and Windows Server 2008

KB4506974 — 2019-07 Security Only Update for .NET Framework 3.5 for Windows Embedded 8 Standard and Windows Server 2012

KB4506975 — 2019-07 Security Only Update for .NET Framework 2.0, 3.0 for Windows Server 2008

KB4506976 — 2019-07 Security Only Update for .NET Framework 3.5.1 for Windows Embedded Standard 7, Windows 7, and Windows Server 2008 R2

KB4506977 — 2019-07 Security Only Update for .NET Framework 3.5 for Windows 8.1 and Windows Server 2012 R2

KB4506992 — 2019-07 Security and Quality Rollup for .NET Framework 4.8 for Windows Embedded 8 Standard and Windows Server 2012

KB4506993 — 2019-07 Security and Quality Rollup for .NET Framework 4.8 for Windows 8.1 and Windows Server 2012 R2

KB4506994 — 2019-07 Security and Quality Rollup for .NET Framework 4.8 for Windows Embedded Standard 7, Windows 7, and Windows Server 2008 R2

KB4506995 — 2019-07 Security and Quality Rollup for .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 for Windows Embedded 8 Standard and Windows Server 2012

KB4506996 — 2019-07 Security and Quality Rollup for .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 for Windows 8.1 and Windows Server 2012 R2

KB4506997 — 2019-07 Security and Quality Rollup for .NET Framework 4.6 for Windows Embedded Standard 7, Windows 7, Windows Server 2008 R2, and Windows Server 2008

KB4506999 — 2019-07 Security and Quality Rollup for .NET Framework 4.5.2 for Windows 8.1 and Windows Server 2012 R2

KB4507000 — 2019-07 Security and Quality Rollup for .NET Framework 4.5.2 for Windows Embedded 8 Standard and Windows Server 2012

KB4507001 — 2019-07 Security and Quality Rollup for .NET Framework 4.5.2 for Windows Embedded Standard 7, Windows 7, Windows Server 2008 R2, and Windows Server 2008

KB4507002 — 2019-07 Security and Quality Rollup for .NET Framework 3.5 for Windows Embedded 8 Standard and Windows Server 2012

KB4507003 — 2019-07 Security and Quality Rollup for .NET Framework 2.0 for Windows Server 2008

KB4507004 — 2019-07 Security and Quality Rollup for .NET Framework 3.5.1 for Windows Embedded Standard 7, Windows 7, and Windows Server 2008 R2

KB4507005 — 2019-07 Security and Quality Rollup for .NET Framework 3.5 for Windows 8.1 and Windows Server 2012 R2

KB4507411 — 2019-07 Security Only Update for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows Embedded Standard 7, Windows 7, and Windows Server 2008 R2

KB4507412 — 2019-07 Security Only Update for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows Embedded 8 Standard and Windows Server 2012

KB4507413 — 2019-07 Security Only Update for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 8.1 and Windows Server 2012 R2

KB4507414 — 2019-07 Security Only Update for .NET Framework 2.0, 3.0, 4.5.2, 4.6 for Windows Server 2008

KB4507420 — 2019-07 Security and Quality Rollup for .NET Framework 3.5.1 for Windows Embedded Standard 7, Windows 7, and Windows Server 2008 R2

KB4507421 — 2019-07 Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 on Windows Embedded 8 Standard and Windows Server 2012

KB4507422 — 2019-07 Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2

KB4507423 — 2019-07 Security and Quality Rollup for .NET Framework 2.0, 3.0, 4.5.2, 4.6 on Windows Server 2008

KB4507434 — 2019-07 Cumulative Security Update for Internet Explorer

KB4507452 — 2019-07 Security Monthly Quality Rollup for Windows Server 2008

KB4507461 — 2019-07 Security Only Quality Update for Windows Server 2008

KB4507462 — 2019-07 Security Monthly Quality Rollup for Windows Embedded 8 Standard and Windows Server 2012

KB4507464 — 2019-07 Security Only Quality Update for Windows Embedded 8 Standard and Windows Server 2012

KB4504418 — 2019-07 Servicing Stack Update for Windows 8.1, Windows RT 8.1, Windows Server 2012 R2, Windows Embedded 8 Standard, and Windows Server 2012

KB4506986 — 2019-07 Cumulative Update for .NET Framework 4.8 for Windows Server 2016, Windows 10 Version 1607

KB4506987 — 2019-07 Cumulative Update for .NET Framework 4.8 for Windows 10 Version 1703

KB4506988 — 2019-07 Cumulative Update for .NET Framework 4.8 for Windows 10 Version 1709

KB4506989 — 2019-07 Cumulative Update for .NET Framework 4.8 for Windows 10 Version 1803

KB4506990 — 2019-07 Cumulative Update for .NET Framework 3.5, 4.8 for Windows 10 Version 1809 and Windows Server 2019

KB4506991 — 2019-07 Cumulative Update for .NET Framework 3.5, 4.8 for Winodws 10 version 1903

KB4506998 — 2019-07 Cumulative Update for .NET Framework 3.5, 4.7.2 for Windows 10 Version 1809 and Windows Server 2019

KB4507419 — 2019-07 Cumulative Update for .NET Framework 3.5, 4.7.2, 4.8 for Windows 10 Version 1809 and Windows Server 2019

KB4507435 — 2019-07 Dynamic Cumulative Update for Windows 10 Version 1803

KB4507450 — 2019-07 Cumulative Update for Windows 10 Version 1703

KB4507455 — 2019-07 Cumulative Update for Windows 10 Version 1709

KB4507458 — 2019-07 Dynamic Cumulative Update for Windows 10 Version 1507

KB4507460 — 2019-07 Cumulative Update for Windows 10 Version 1607 and Windows Server 2016

KB4509090 — 2019-07 Servicing Stack Update for Windows 10 Version 1507

KB4509091 — 2019-07 Servicing Stack Update for Windows Server 2016, and Windows 10 Version 1607

KB4509092 — 2019-07 Servicing Stack Update for Windows 10 Version 1703

KB4509093 — 2019-07 Servicing Stack Update for Windows 10 Version 1709

KB4509094 — 2019-07 Servicing Stack Update for Windows 10 Version 1803, and Windows Server 2016

KB4509095 — 2019-07 Servicing Stack Update for Windows 10 Version 1809, and Windows Server 2019

KB4509096 — 2019-07 Servicing Stack Update for Windows 10 Version 1903

Known Issues

Windows 7 Service Pack 1 and Windows Server 2008 R2

  • Issue with McAfee Enterprise software that causes slow startup or the system to become unresponsive.

Windows 8.1 and Windows Server 2012 R2

  • Still the long standing issue with Cluster Shared Volumes that throws the error “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”.
  • Issue with McAfee Enterprise software that causes slow startup or the system to become unresponsive.
  • Windows-Eyes screen reader may may throw errors on launch or during use, and some features may not work properly.

Windows 10 version 1803

  • Still the long standing issue with Cluster Shared Volumes that throws the error “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”.
  • Black screen during first logon after installing updates.
  • Issue with Window-Eyes screen reader app that may not work correctly.

Windows 10 version 1809 and Server 2019

  • Long standing issue with Cluster Shared Volumes.
  • Error “0x800f0982 – PSFX_E_MATCHING_COMPONENT_NOT_FOUND” on devices with “some Asian language packs installed”.
  • Black screen during first logon after installing updates.
  • Issue with Window-Eyes screen reader app that may not work correctly.

Windows 10 version 1903

  • Windows Sandbox may fail to start.
  • The Remote Access Connection Manager (RASMAN) service may stop working and you may receive the error “0xc0000005” on devices where the diagnostic data level is manually configured to the non-default setting of 0.

Security advisories and updates

ADV190020 | Linux Kernel TCP SACK Denial of Service Vulnerability

ADV190021 | Outlook on the web Cross-Site Scripting Vulnerability

ADV990001 | Latest Servicing Stack Updates

Non-security related updates

KB890830 — Windows Malicious Software Removal Tool – July 2019

KB4501375 –Windows 10 version 1903 and Windows Server version 1903

KB4509479 — Windows 10 version 1809 and Windows Server 2019

  • Fixed a Storage Area Network (SAN) connection issue.

KB4501371 –Windows 10 version 1809 and Windows Server 2019

KB4509478 — Windows 10 version 1803

  • Same as KB4509479 for Windows 10 version 1809.

KB4503288 — Windows 10 version 1803

KB4509477 — Windows 10 version 1709

  • Same as KB4509479 for Windows 10 version 1809.

KB4503281 — Windows 10 version 1709

Microsoft Office Updates

You find Office update information here.

How to download and install the July 2019 security updates

microsoft windows security updates july 2019

The July 2019 security updates are distributed through Windows Update, WSUS, and other means. Most client-based Windows systems are configured to check for updates automatically.

Windows administrators who don’t want to wait may run manual checks for updates. It is generally not recommended as bugs may be discovered after the general availability. Backups are recommended if the installation of updates can’t be delayed.

Do the following to run a manual check for updates:

  1. Tap on the Windows-key, type Windows Update, and select the result.
  2. A click on “check for updates” runs a manual check. Updates may be installed automatically or on user request depending on system settings.

Direct update downloads

Windows 7 SP1 and Windows Server 2008 R2 SP

  • KB4507449 — 2019-07 Security Monthly Quality Rollup for Windows 7
  • KB4507456 — 2019-07 Security Only Quality Update for Windows 7

Windows 8.1 and Windows Server 2012 R2

  • KB4507448 — 2019-07 Security Monthly Quality Rollup for Windows 8.1
  • KB4507457 — 2019-07 Security Only Quality Update for Windows 8.1

Windows 10 (version 1803)

  • KB4507435 — 2019-07 Cumulative Update for Windows 10 Version 1803

Windows 10 (version 1809)

  • KB4507469 — 2019-07 Cumulative Update for Windows 10 Version 1809

Windows 10 (version 1903)

  • KB4501375 — 2019-07 Cumulative Update for Windows 10 Version 1903

Additional resources

Summary
Microsoft Windows Security Updates June 2019 overview
Article Name
Microsoft Windows Security Updates June 2019 overview
Description
Detailed overview of the Microsoft July 2019 Patch Day covering Windows security and non-security updates, advisories, known issues, and more.
Author
Martin Brinkmann
Publisher
Ghacks Technology News
Logo
Ghacks Technology News
Advertisement

Related:

  • No Related Posts

Need to replace sylink tool

I need a solution

Hello All,

I’m trying to replace the Sylink for 40-50 machine, from previous blog i’ve got the idea of Sylinkreplacer tool but I’ve tried to run this tool as per instruction with Domain OU Admin privilege. once the run is complete result is coming like replacement successfull but in client Sylink file are not getting replaced. 

Please suggest any workaround.

SEP Client version 14.2 MP1.

SEPM version 14.2 MP1

Client OS: Windows 7 & Windows 10 || SEPM OS: Windows Server 2012.

0

Related:

  • No Related Posts

Install via Intune

I do not need a solution (just sharing information)

Hello-

We are using Symantec Endpoint Protection Cloud and need to deploy the SEP to our Windows 10 devices via MS Intune. We don’t use group policy or active directory we are using Intune, Azure AD and Autopilot to manage our devices. Intune uses a single.MSI package to deploy a line of business apps however Symantec’s.MSI file is accompanied by a .MST file. We have tried repacking the .exe file to a .msi, and the install fails. How are you deploying the solution to Windows 10 devices in this scenario?

0

Related:

  • No Related Posts