Earlier in the month Microsoft announced their new subscription service for Windows 10 Enterprise. Starting at just $7 USD per month, end users are able to subscribe to Windows 10 enterprise on a monthly basis.
This, I think, is a good move by Microsoft.
However, what is disturbing is what Microsoft is changing on lower tier versions, such as Windows 10 Professional. See the following changes:
I’d say this is to target the small business users who now cannot disable the shop within Windows. This will push slightly larger businesses to go to Enterprise.
While a small change, I hope Microsoft doesn’t fall into the trap many other monthly subscription providers have fallen into.
Microsoft Forefront TMG 2010 has been a solid product. It has not had an update in some time, and that’s a shame.
I was reviewing my TMG server a few weeks ago in order get a bit more performance from it. The server is virtualized, and currently only gives me around 50-60mb/s throughput with all its rules. I wanted to increase this and make it more responsive in the process.
So let us proceed:
#1 Sort Rule Priority
Like most other firewalls, TMG processes rules from top to bottom. If you have a frequently accessed rule, like web browsing, for example, put this at the top. For me, this was a spam filter listening rule. TMG had connections coming in for the spam filter at the rate of 5-10 per second. I moved these to the top
The next rule you want to sort out is traffic from TMG server. I would generally add this as my second/third rule.
After this came my office outbound rules
After this came the rest of my rules which consisted of various servers/voip etc.
#2 Disabled Legacy Services
Since TMG is now discontinued, many of the services in TMG are no longer updated. It’s up to you, but you might as well disable them to recover some performance. These services are:
Virus and Content Filtering
Ensure each one is disabled. You might be a bit hesitant to disable these. If you check your definitions, you will find they have not been updated in some time.
#3 Remove Old Rules
Lastly, remove any old rules. We don’t tend to look at firewalls often. So this simple task often gets overlooked.
As well as removing the old rules, ensure that you make your listener rules only listen to what’s needed. This will cut down on processing time.
TMG is a great product, but now beyond its used by date. TMG will always hold a special place in my software archive as a product that could have become a great firewall appliance <3
I originally had a post on how to clean up WinSXS from 2014. However, I have come across a program that I have tested, and works very well.
The program is Patch Cleaner. This program scans your Installer folder to check if there are orphan files relating to programs or patches you may have removed from your computer. Any orphan files Patch Cleaner locates can be removed.
I have tested Patch Cleaner on Server 2012 and 2012 R2, including production terminal servers with 100 users. I have no had any issues thus far.
With Server 2012, running Patch Cleaner was removing on average 20GB+ on each server.
I would recommend checking this out if you are still stuck for space.
You may have come across this issue when you’ve upgraded your computer to Windows 10. Upon returning to your computer, the screen refreshes slowly and applications appear to have crashed due to memory issue.
There have been many suggest ways to fix this, but the simplest way is to do the following:
Open Regedit by pressing Windows Key + R and typing regedit
Navigate to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSession ManagerMemory Management
Change the value of ClearPageFileAtShutDown to 1
Reboot your computer
This will wipe the page file on reboot.
This may increase the shutdown time of your computer, but it will fix this error. The root cause of this error is an incompatible driver on your system. I will follow up with an article on this process.
I got the following error when I had migrated a customer from a Small Business Server to our local Hosted Exchange.
Outlook on a domain looks to Active Directory to get the auto discover information. If you run the Outlook connectivity tester on the affected computer, you will see that it returns the local SBS server autodiscover settings, even if you have configured Outlook to use an external provider.
The simplest way to fix this if the SBS server is still in used and Exchange is still installed, is to run the following commands: