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

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

SEEMS Installation: “SQL Server System CLR Type” error despite installed

I need a solution

Hello. I require some help regarding Symantec Endpoint Encryption Management installation. FYI, I’m following Symantec Endpoint Encryption Management 11.x Installation guide.

The error I received is the following when I attempted to run the SEE Server Suite x64.

I have the prerequisite software installed including IIS, .Net 4.5, SQL CLR and Shared Management Object. However, despite the SQL CLR has been installed, I am still receiving this error.

I have verified that SQL CLR and Shared Management Object has been installed in the server via Control Panel.

FYI, I’m installing on Windows Server 2012 R2 and I made sure that the server meets at least the minimum system requirements.

Any input is appreciated. Thanks in advanced.

0

Related:

  • No Related Posts

7022790: “Secure Shell Server Configuration Tool has stopped working” error after clustered RSIT upgrade

Workaround:

1. In Failover Cluster Manager, expand the cluster RSIT is running under, click on Roles.

2. Select the RSIT role/Generic Service that RSIT is configured under. Take note of the IP address.

3. Right click on the same role and choose properties. Take note of the settings under both General and Failover tabs. Click OK.

4. Left pane, Storage, Disks, check if any disk(s) are currently assigned to the RSIT role.

5. Right click on the role and choose “Stop Role”.

6. Right click on role and select “Remove”.

7. On the passive server, use Control Panel to uninstall RSIT, reboot.

8. On the active server, use Control Panel to uninstall RSIT, reboot.

9. Install RSIT build 8.2.1.1100 on the passive server, reboot.

10. Verify that RSIT service is not running under Windows’ Services.

11. Install RSIT build 8.2.1.1100 on the active server, reboot.

12. Verify that RSIT service is not running under Windows’ Services.

13. In Failover Cluster Manager, expand the cluster RSIT will run under.

14. Right click on Roles and choose “Configure Role”.

15. Under “Select Role”, choose “Generic Services”. Click Next.

16. Choose “Micro Focus Reflection for Secure IT Server” from the list.

17. Enter a name for the Cluster role and the IP address it is using (Step 2).

18. When prompt to “Replicate Registry Settings”, add this HKEY_LOCAL_MACHINE key: SOFTWAREMicro FocusRSecureServer

19. Check the new RSIT role properties, match it to what was noted (step 3).

20. On the active server, ensure that the RSIT console opens.

21. Test the connect.

22. Failover to passive server, test step 20 and 21 on the new active server.

Related:

  • No Related Posts

Re: Migrate Networker 8.2 on Solaris to RHEL

A pretty tough task – I doubt that you will receive a straight answer.

This is how I would proceed:

– On the target server create a fake hosts table resolving all your current NW client names.

– Copy the NW databases to the new system – different directory!!

Forget the /nsr/index directory right now – it is nice to have but not mandatory.

– Copy the NW software to the target system

– Disconnect the network of the new host completely

– Rename the target server so that it will have the exact name as before

– Install the same NW version in the same directory as on the old system

– Copying the resource files will most likely not work for all of them – just think about the different device names

– Start NW and wait until it has started successfully.

It will take a few minutes

It will take much longer if he cannot resolve the hostnames

– Make sure to get the most important resources to work.

– Finalize the NW configuration

– Make sure you can run local backups and restores

Now you may restore/move the client file index directories

TEST – TEST – TEST !!!

– If your system runs fine, you may now try the upgrade to NW 9.x

TEST – TEST – TEST !!!

– Now you may shutdown the old server and

– Connect the new server to join the network

Pretty much things to do. Good luck.

Related:

  • No Related Posts

Migrate Networker 8.2 on Solaris to RHEL

A pretty tough task – I doubt that you will receive a straight answer.

This is how I would proceed:

– On the target server create a fake hosts table resolving all your current NW client names.

– Copy the NW databases to the new system – different directory!!

Forget the /nsr/index directory right now – it is nice to have but not mandatory.

– Copy the NW software to the target system

– Disconnect the network of the new host completely

– Rename the target server so that it will have the exact name as before

– Install the same NW version in the same directory as on the old system

– Copying the resource files will most likely not work for all of them – just think about the different device names

– Start NW and wait until it has started successfully.

It will take a few minutes

It will take much longer if he cannot resolve the hostnames

– Make sure to get the most important resources to work.

– Finalize the NW configuration

– Make sure you can run local backups and restores

Now you may restore/move the client file index directories

TEST – TEST – TEST !!!

– If your system runs fine, you may now try the upgrade to NW 9.x

TEST – TEST – TEST !!!

– Now you may shutdown the old server and

– Connect the new server to join the network

Pretty much things to do. Good luck.

Related:

  • No Related Posts

Unable to image computer in Automation

I need a solution

I have a virtual machine I am trying to image. I can get it to boot to PXE and it connects to the server and gets an IP address. However, when I look in the console for it, it does not show up. I can ping the server and the NS and verified it has a unique IP and it not mirroring the host computer in any way. 

Any help would be appreciated. 

TIA! 

0

Related:

  • No Related Posts

What URL(s) to use to connect to SEEM server?

I need a solution

This is a basic question, but I’m finding multiple answers on the support pages, none of which seem to work for me.

We just set up Endpoint Encryption 11.1.2 on Windows Server 2012 R2 Standard. I can get into SEEM directly from the server, but am not sure what URL(s) the helpdesk people and server administrators are supposed to use. When I try https://myseem.mydomain.org:443/ I get an authentication prompt even though the certificate is a match.

A webpage comes up at https://myseem.mydomain.org/WebConsole/ but I don’t see features in there such as downloading the Windows client.

Any help appreciated!

Thanks,

ZC

0

Related:

  • No Related Posts