Storage Spaces White Paper – Fujitsu

I’ve recently come across this great PDF from Fujitsu on Storage Spaces. I highly recommend all those who are trying achive maximum performance from their storage spaces take a look.

The white paper goes over each storage space type, different cache settings and drive layouts. All of this is graphed.

Link is here.

WinSXS/Installer Cleanup Windows 7,8 & Server 2012 with Patch Cleaner

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.

patchclean1

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.

Disable Windows Update Services (WSUS) – Small Business Server and Doman Controllers

Windows Update Services, or WSUS can be a real pain at the best of times. On Small Business Servers, which are often neglected, some strange issues can arise.

The most common issue is that WSUS goes crazy and downloads everything. Yes, this does happen.

You may not know, but you shouldn’t uninstall WSUS on a domain controller, IE Small Business Server.

Here is how you can disable it and clean up the mess.

  1. Under Options, select Products and Classifications 
  2. Unselect everything, and then select Bing Bar. You need something selected.
    2015-11-13_12-22-02
  3. Under Classifications, select Critical Updates
    2015-11-13_12-21-47
  4. Remove Automatic Approvals
    2015-11-13_12-23-29
  5. Run the Server Cleanup Wizard with everything selected
  6. Once this is done, you can leave WSUS as is, or you can disable the service
    2015-11-13_12-25-46
  7. With the service stopped and disabled, you can also delete the content database. Only do this if you are never going to use WSUS again.
    2015-11-13_12-27-03

Hopefully this has helped someone.

Windows 10 “Out of Memory” when left idle

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:

  1. Open Regedit by pressing Windows Key + R and typing regedit
  2. Navigate to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSession ManagerMemory Management
  3. Change the value of  ClearPageFileAtShutDown to 1
  4. 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.

Installing Disk Cleanup (cleanmgr.exe) Server 2008 and Server 2012

It’s annoying that Disk Cleanup (Cleanmgr.exe) is no longer installed by default. You can install Disk Cleanup by installing the Windows Desktop Experience – but, there is another, less annoying way…

Server 2012

copy C:WindowsWinSxSamd64_microsoft-windows-cleanmgr_31bf3856ad364e35_6.2.9200.16384_none_c60dddc5e750072acleanmgr.exe %systemroot%System32

copy C:WindowsWinSxSamd64_microsoft-windows-cleanmgr.resources_31bf3856ad364e35_6.2.9200.16384_en-us_b6a01752226afbb3cleanmgr.exe.mui %systemroot%System32en-US

Server 2008 R2 (x64)

copy C:Windowswinsxsamd64_microsoft-windows-cleanmgr.resources_31bf3856ad364e35_6.1.7600.16385_en-us_b9cb6194b257cc63cleanmgr.exe.mui %systemroot%System32En-US

copy C:Windowswinsxsamd64_microsoft-windows-cleanmgr_31bf3856ad364e35_6.1.7600.16385_none_c9392808773cd7dacleanmgr.exe %systemroot%System32

Server 2008 (x64)

copy C:Windowswinsxsamd64_microsoft-windows-cleanmgr.resources_31bf3856ad364e35_6.0.6001.18000_en-us_b9f50b71510436f2cleanmgr.exe.mui %systemroot%system32en-us

copy C:Windowswinsxsamd64_microsoft-windows-cleanmgr_31bf3856ad364e35_6.0.6001.18000_none_c962d1e515e94269cleanmgr.exe %systemroot%System32

Server 2008 (x32)

copy C:Windowswinsxsx86_microsoft-windows-cleanmgr.resources_31bf3856ad364e35_6.0.6001.18000_en-us_5dd66fed98a6c5bccleanmgr.exe.mui %systemroot%System32En-US

copy C:Windowswinsxsx86_microsoft-windows-cleanmgr_31bf3856ad364e35_6.0.6001.18000_none_6d4436615d8bd133cleanmgr.exe %systemroot%System32

Now go to Run and type cleanmgr.exe

cleanmgr.exe

You will now see Disk Cleanup run.

Disk Cleanup

Unfortunately on Windows 2012 R2 you must install the Windows Desktop Experience.

Error while preparing to send sharing message (Outlook 2007/2010/2013/2016)

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:

Get-ClientAccessServer | Set-ClientAccessServer -AutoDiscoverServiceInternalUri https://mail.externaldomain.com/Autodiscover/Autodiscover.xml

And

get-autodiscovervirtualdirectory | Set-AutodiscoverVirtualDirectory -ExternalUrl https://mail.externaldomain.com/Autodiscover/Autodiscover.xml -InternalUrl https://mail.externaldomain.com/Autodiscover/Autodiscover.xml

This then points the Outlook client to the correct external Autodiscover service.

If you have any questions, please let me know.

message deferred by categorizer agent

I came in to work on Monday with a rather large client with no email. They run Microsoft Exchange 2007. I first logged in to the server and owa to ensure the Exchange Server was actually functioning. All services were going.

I then opened the message queue. There I saw 350 emails with the Last Error set to message deferred by categorizer agent

I haven’t actually come across this error before. Something had changed on the system. To cut a long story short, I found the issue was because of a corrupt transport agent. To find your transport agents, run the following power shell command:

Get-TransportAgent

You will get a list like the following


Identity Enabled Priority
-------- ------- --------
Transport Rule Agent True 1
Journaling Agent True 2
AD RMS Prelicensing Agent False 3
Connection Filtering Agent True 4
Content Filter Agent True 5
Sender Id Agent True 6
Sender Filter Agent True 7
Recipient Filter Agent True 8
Protocol Analysis Agent True 9

In the event log, I noticed the following error

An error occurred while loading the configuration for the Journaling agent. The configuration may be corrupt, or the Active Directory directory service may be down or unreachable. The last known good configuration will be used, and the Journaling agent will attempt to read the configuration again later.

This restored configuration didn’t fix the issue. I opted to disable the Journaling Agent.

Disable-TransportAgent -Identity "Journaling Agent"

Select Y and then restart the Hub Transport service.

This should fix your issue. I am still investigating a fix for the Journaling Agent. I suspect this was initially caused by a reboot when performing Windows Updates as the mail flow stopped on the same day.

Exclude category from wordpress blog page

This has been an issue i’ve been working through for some time. There are no easy to use plugins to do this. So here’s how you do it.

    1. Find your blog category id by editing one of your categories
    2. Edit your functions.php with the folowing code. Replace xx with your category id
function exclude_category($query) {
if ( $query->is_home() ) {
$query->set('cat', '-xx');
}
return $query;
}
add_filter('pre_get_posts', 'exclude_category');

Done.