Stung by a festering pile of bugs on Patch Tuesday, MS releases 27 more patches

In what is becoming a common occurrence, Microsoft’s Patch Tuesday brought along so many bugs that they necessitated a remediation round. This month, unusually, it took only six days to get the exterminators out.

Since these fixes are aimed at four specific bugs introduced on Patch Tuesday, they don’t include the massive patches normally appearing on the second Patch Whateverday of the month. My guess is we’ll see at least one more big set of Windows patches before the month is out. Oh, boy.

Windows July patches, version 2

Yesterday, Monday, July 16, Microsoft released 27 new security patches for Windows, bringing the total number of patches so far this month up to 156. The new patches fall into six separate groups:

  • Win10 version 1803 got cumulative update KB 4345421. The KB article says this update moves 1803 users to build 17134.166, but multiple sources say, in fact, they’re getting moved to 17134.167. That may seem like a small discrepancy, but it speaks volumes about last-minute changes in the build and the lack of coordination in the documentation.
  • Win10 1709 got KB 4345420. The KB article says it moves 1709 users to 16299.550, but the Win10 release info page says it’s 16299.551.
  • Win10 1703 got KB 4345419. The KB article says build 15063.1208. The audience says 15063.1209. Bzzzzzt.
  • Win10 1607 / Server 2016 got KB 4345418. The docs say 14393.2367. The guinea pigs say 14393.2368. And the crowd goes wild.
  • Win8.1 / Server 2012 R2 got a manual-download-only KB 4345424.
  • Win7 / Server 2008 R2 also got a manual-only patch, KB 4345459. We have one report that this patch breaks acquiring IP addresses over a wireless connection.

All six of the groups say they fix the same basic bugs. Er, issues. All of the acknowledged issues look like this:

Related:

  • No Related Posts

DeployAnywhere won’t import drivers, says Failed to find any drivers to add.

I need a solution

We had a previous image process and are switching over to the altiris methodology so I am importing all drivers (Windows 10) into the deploy anywhere database.

I am getting a lot of them coming back with “Failed to find any drivers to add”  which then causes it to default to the base windows driver for this device.  One specific device that caused me to really notice this is a synaptics touchpad where when the drivers are the default MS it doesn’t work.  I downloaded the drivers from MS using update driver, then grabbed the drivers out of the driverstore and told it to try and import and again it says nothing found.   I was thinking maybe they weren’t there, so I ran a test with the folder I grabbed using DISM in winPE and sure enough they get installed fine that way.

Any ideas on what I can possibly do to get it to recognize the drivers?

This is the full error

Failed to import driver: \mynsservernscapbinwin32x86deploymenttempdriverssynpd.inf_amd64_a20ab0cba6ba9630synpd.inf [Failed to find any drivers to add.]

0

Related:

  • No Related Posts

Making a Smooth and Seamless Transition to Windows 10 – Webinar coming up!

Gil Cattelain

Microsoft will discontinue all support for its Windows 7 operating system in January 2020.  Even today, Windows 7 is in an extended support phase, meaning Microsoft is offering paid support but not the free support included with licenses, and only provides security-related updates.  What it means is the clock is ticking for businesses to migrate …

+read more

The post Making a Smooth and Seamless Transition to Windows 10 – Webinar coming up! appeared first on Cool Solutions. Gil Cattelain

Related:

  • No Related Posts

Error: “Cannot Complete Your Request” Due to File Change Notification of IIS Being Enabled

If you only get the error when accessing the server for first time after an idle time or running an antivirus scan then disable the File Change Notification feature on the IIS server where StoreFront is running.

For .NET 4.0 and Lower

Find app bitness from appPool advance settings.

64 bit: To enable this hotfix, you must add the following DWORD value of 1 at the following registry key:

HKLMSoftwareMicrosoftASP.NETFCNMode

32 bit: If you are running a 32-bit process on an x64-based system, add the following DWORD value of 1 at the following registry key:

HKLMSOFTWAREWow6432NodeMicrosoftASP.NETFCNMode

For .NET 4.5 and Higher

Starting with the Microsoft .NET Framework 4.5 and later versions, FCNMode can be configured by using the httpRuntime settings as follows:

<httpRuntime fcnMode=”Disabled”/>

For more information refer to the following blogs:

ASP.NET File Change Notifications, exactly which files and directories are monitored?

ASP.NET Performance issue: Large number of application restarts due to virus scanning

Related:

  • No Related Posts

When User Profile Manager is Enabled a Prompt Appears “How do you want to open this type of link (http) ?”

As a workaround create the initial registry FTA entries with a local policy so that the FTA choice is set when the profile is created.

1. Choose a target machine with the same OS as the VDA.

Set the file type associations as desired in control panel.

Here set HTTP and HTTPS to use Internet Explorer.

IE Default


2. Run the command Dism /Online /Export-DefaultAppAssociations:C:AppAssocAttac.xml (this will create a XML file with the configurations of default programs for different file extensions )

Create a GPO or a local policy.

3. Expand to the policy location , Computer configurationPoliciesAdministrative TemplatesWindows ComponentsFile Explorer.

4. On the right side pane select the policy “Set a default associations configuration file”

User-added image
5. Click on Enabled and then give the path of XML file in the options area.

6. Save settings and exit the policy editor enable loopback processing

7. Apply the policy to the OUs where the servers are placed.

On VDA run gpupdate /force so that changes would take effect immediately.

8. Run RSOP.msc in the servers, and make sure the policies are properly applied.

9. Launch new HDX session . Try to open the link in Outlook. There is no longer any prompt to open a http or https link whether in Outlook or Wordpad.

Related:

  • No Related Posts

How to Restore Emails from OST file Outlook 2013?

MS Outlook 2013, like earlier Outlook versions, uses OST file to save a local replica of Exchange mailbox data. This file comes handy when user wishes to work on his mailbox even if Exchange isn’t available. But, it can’t be opened directly in Outlook if its parent account gets disconnected from Exchange. In such a case the OST file is called an ‘orphan’ file and extracting emails and other data from it can become a real pain.



Although Microsoft came up with the concept of using data files to save mailbox data locally in order to make backing up and archiving more convenient, OST and PST files have in some ways complicated mailbox management; and that holds especially true for OSTs. If you access an Exchange mailbox through Outlook, a local OST file is created to save a replica of mailbox data which the user can access and work with even if the mail server isn’t available. However, the basic nature of OST files makes managing mailbox data quite tricky for users.



The need to Restore mails from OST File

OST files have several shortcomings because of which, users often face the need to extract emails and other data stored within these files and save them in some other format:

  • OSTs cannot be transferred between different machines. If users need to access their mailbox data saved within OST files on another machine, it cannot be done directly through a simple copy-paste mechanism.
  • If the account that originally created an OST file gets deleted from the mail server, it cannot be opened directly from within Outlook.
  • In Outlook 2013 and 2016, data locally edited and saved within critical folders like Contacts, Calendars, Sent Items, etc. is not synced with the mail server and is thus not backed up there. In the event of damage to OST file, there’s no direct way to regain access to that local data since it doesn’t exist on the server.

Users who faced the need to extract OST file data because of any of the above-mentioned reasons make use of manual as well as automated ways to achieve it. For your reference, we’ve compiled a list of the most widely used and accepted techniques you can use to restore OST files if you’re sailing in the same boat.



Manual techniques to Restore OST files



In no specific order, these techniques can help you regain access to all your Exchange or other IMAP account data depending upon your exact problem scenario:



Scenario 1: If your Exchange account is intact but OST file gets corrupted



This is one of the most frequently encountered problems by Exchange users. OST files get damaged easily but if your Exchange profile is intact and you are in the habit of regularly syncing your local data with your server mailbox, regaining access to all your data should simply be a matter of manually creating a new OST file and downloading your mailbox data from the server again. Here are the steps:



  1. Quit all running instances of Outlook and open Control Panel
  2. Open the “Mail” option and in the ‘Mail Setup’ dialog box that opens, click on “Email Accounts”
  3. The next dialog that opens will display all your Outlook profiles / accounts. Here, click on the “Data Files” tab and choose the respective OST file from the list
  4. Now click on “Open File Location” to open the Windows Explorer window with the OST file’s location
  5. Close the ‘Account Settings’ and ‘Mail Setup’ windows
  6. In the Explorer window, create a copy (backup) of the OST file. Thereafter, right-click on it and click on “Delete”
  7. Start the Outlook application again to automatically create a new OST file for that account (doing so will download all the data from the Exchange server into the newly created OST file)

You should remember that if you’re using Outlook 2013 / 2016, only the data residing on the mail server will be downloaded into the new OST file. This will include your emails and the folders you have manually synced with the Exchange account. Any local data will not be downloaded since it doesn’t exist on the server. To get access to any such data you will need to convert the old OST to PST format and then open it directly within Outlook. You can either use the Outlook “Import & Export wizard” to convert OST to PST or take the help of reliable software Stellar OST to PST Converter to do so (skip to last section to discover how this product can help).



Scenario 2: If your Exchange account has been deleted or lost



If this happens, your “orphaned” OST file will most likely become useless since you won’t be able to open it directly unless you reconnect to Exchange and re-sync it. For this you will need a unique MAPI address to act as a bridge between Outlook and the Exchange server. However if this isn’t an option, the only way to access the data contained within the orphaned OST file is to convert it to PST format using Stellar OST to PST Converter. (Here you won’t have the option to use Outlook Import Export Wizard since you’ll need to open the OST file from within Outlook and without Exchange that won’t be possible).



Best Automated Solution to restore mails from OST file



If the manual technique doesn’t work or if you are dealing with an orphaned OST file, converting it to PST format is a task best handled by a professional product like Stellar OST to PST Converter. The advanced software is equipped with some very powerful algorithms that allow it to convert even the most severely damaged OST files to PST format files that can be used to access all mailbox contents including emails, attachments, contacts, calendars, notes, journals, etc. This software is your best bet if you wish to perform conversion of encrypted OST files or wish to extract only selected emails from within OST files and save them in MSG, EML, RTF, HTML, or PDF formats.



Final Thoughts…



So should a user completely shun the usage of OST files? Well obviously that isn’t an option since OST files are the Microsoft norm for saving Exchange data locally. What is needed is for users to stay aware of the techniques they can use to regain all their mailbox data if any disaster like virus infection or accidental deletion or severe corruption befalls their OST files. Converting OST files to PST format is the best way to salvage all the data stored within them and thus, having a product like Stellar OST to PST Converter handy goes a long way.

Related:

  • No Related Posts

Re: cross platform migration with nsrmmdbasm fails

Maybe you just need to run nsrclientfix to correct you hostname issue.

############

I just ran a very brief test myself – just copying the most important databases ( res & mmdb ) from Linux to Windows – and to my surprise, it worked.

Of course, there are some details which you need to care of (the device names for example).

– no resource was rejected (and moved to /nsr/res/nsrdb/dbg)

– instead, the Linux device name appeared in Windows

– I could see all my save sets in my tiny media db

– For a brief test,

– I moved my file type device directory to a Windows directory

– created the appropriate device

– mounted the volume (this proves that the media db can resolve it)

– and ran a save set recover.

Once again – I do not say the migration is easy. There are a lot of things to take care of.

But in general, I do not see a show-stopper (so far).

Related:

  • No Related Posts

Looking for Windows base images for on-box malware scanning on CAS-S400-A1

I need a solution

Weeks ago I found some Windows 7/10 base images on Symantec support portal for downloading (each > 1GB).

In the meantime I ordered the licenses/SKUs CAS-S400_A1-A2-W7 and -W10 and will get them soon.

Now I wanted to download the windows images – and can’t find them anymore on support portal.

Could someone give me a hint where they are located? (or have they be removed together with the other MAA software?)

Thanks in advance.

Egon
 

0

Related:

  • No Related Posts

Blue Screen of Death with SEP14 on Windows 10 version 1803

I need a solution

I recently updated my Dell 6440 laptop to Windows 10 version 1803 and am now getting a blue screen of death (BSOD) when I run Micro Focus InfoConnect Desktop 16.1. If I remove SEP, then no BSOD event occurs. I’ve worked with development and IT folks to narrow down the cause of the issue. When we review the minidump file in Windows (attached), the failure occurs when a Symantec file is being accessed when InfoConnect is in the process of connecting from Windows to a mainframe session . I searched on the Symantec forums, but don’t see the problem show up on the list of issues. My SEP version is listed in Add/Remove Programs as 14.0.3897.1101. Thanks.

0

1527096852

Related:

  • No Related Posts