With the increase attack on 365 subscriptions without two factor enabled its good to check when a rule actually got added. This cannot be done with powershell you will need to perform with MFCMAPI

Download the latest MFCMAPI of 32bit or 64bit ( depending on your Office/Outlook version ) release here

You can do this on the User’s computer who should already have Outlook installed or you can create an Outlook profile as the user you would like to check the rule for on another PC. You can also create an Outlook Profile as an Administrator and give yourself full access to the User’s Maibox

Open MFCMAPI , Open the Profile , then go to Session and Logon

Double click on the account

Open the Root Folder and Navigate to here and right click on Inbox and Choose Open Associated Contents Table

The rule will look something like this , Message Class : IPM.Rule.Verson2.Message

Then find the following Name and check the value to confirm its the right Rule

• No Comments

After recently upgrading Citrix Storefront from Version 3.2 to 3.16 , after a reboot the Citrix Protocol Transition Service won’t start the event log showed the below error

The fix is to open Notepad add Administrator , then Navigate to

C:\Program Files\Citrix\Receiver StoreFront\Services\ProtocolTransitionService

Open Citrix.DeliveryServices.ProtocolTransition.ServiceHost.exe.config

Change the following line

<section name=”container” type=”Castle.Windsor.Configuration.AppDomain.CastleSectionHandler, Castle.Windsor,

Version=3.0.0.0, Culture=neutral, PublicKeyToken=407dd0808d44fbdc” />

to the right version

e.g

<section name=”container” type=”Castle.Windsor.Configuration.AppDomain.CastleSectionHandler, Castle.Windsor,

Version=3.16.0.0, Culture=neutral, PublicKeyToken=407dd0808d44fbdc” />

The service should start after this OK!

Unable to resolve container components of type ‘Citrix.DeliveryServices.ServiceHosting.WindowsServiceHostingApi.IWcfServiceControl’.
System.Configuration.ConfigurationErrorsException, System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
An error occurred creating the configuration section handler for citrix.deliveryservices/logger: Could not load file or assembly ‘Citrix.DeliveryServices.Logging, Version=2.6.0.0, Culture=neutral, PublicKeyToken=e8b77d454fa2a856’ or one of its dependencies. The system cannot find the file specified. (C:\Program Files\Citrix\Receiver StoreFront\Services\ProtocolTransitionService\Citrix.DeliveryServices.ProtocolTransition.ServiceHost.exe.Config line 7)
at System.Configuration.BaseConfigurationRecord.FindAndEnsureFactoryRecord(String configKey, Boolean& isRootDeclaredHere)
at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)
at System.Configuration.BaseConfigurationRecord.GetSection(String configKey)
at System.Configuration.ConfigurationManager.GetSection(String sectionName)
at Citrix.DeliveryServices.Configuration.Helpers.ConfigurationUtil.GetSection(String path)
at Citrix.DeliveryServices.Logging.LoggerConfigurationParser.GetLoggerConfig(String sectionName)
at Citrix.DeliveryServices.Logging.LoggerConfigurationParser.CreateLogger()
at Castle.MicroKernel.ComponentActivator.FactoryMethodActivator1.Instantiate(CreationContext context) at Castle.MicroKernel.ComponentActivator.DefaultComponentActivator.InternalCreate(CreationContext context) at Castle.MicroKernel.ComponentActivator.AbstractComponentActivator.Create(CreationContext context, Burden burden) at Castle.MicroKernel.Lifestyle.AbstractLifestyleManager.CreateInstance(CreationContext context, Boolean trackedExternally) at Castle.MicroKernel.Lifestyle.SingletonLifestyleManager.Resolve(CreationContext context, IReleasePolicy releasePolicy) at Castle.MicroKernel.Handlers.DefaultHandler.ResolveCore(CreationContext context, Boolean requiresDecommission, Boolean instanceRequired, Burden& burden) at Castle.MicroKernel.Handlers.DefaultHandler.Resolve(CreationContext context, Boolean instanceRequired) at Castle.MicroKernel.DefaultKernel.ResolveComponent(IHandler handler, Type service, IDictionary additionalArguments, IReleasePolicy policy) at Castle.MicroKernel.DefaultKernel.Castle.MicroKernel.IKernelInternal.Resolve(Type service, IDictionary arguments, IReleasePolicy policy) at Castle.Windsor.WindsorContainer.Resolve[T]() at Citrix.DeliveryServices.Logging.Common.Logger.LogMessageInternal(UInt16 eventId, UInt16 categoryId, MessageType severity, Exception ex, String message) at Citrix.DeliveryServices.ServiceLocator.ServiceLocatorLogger.MissingServiceOfType(Type type, Exception exception) at Citrix.DeliveryServices.ServiceLocator.ServiceLocation.GetInstance[T]() at Citrix.DeliveryServices.ProtocolTransition.ProtocolTransitionStartupModule.<>c.<RegisterComponents>b__3_0() at Castle.MicroKernel.ComponentActivator.FactoryMethodActivator1.Instantiate(CreationContext context)
at Castle.MicroKernel.ComponentActivator.DefaultComponentActivator.InternalCreate(CreationContext context)
at Castle.MicroKernel.ComponentActivator.AbstractComponentActivator.Create(CreationContext context, Burden burden)
at Castle.MicroKernel.Lifestyle.AbstractLifestyleManager.CreateInstance(CreationContext context, Boolean trackedExternally)
at Castle.MicroKernel.Lifestyle.SingletonLifestyleManager.Resolve(CreationContext context, IReleasePolicy releasePolicy)
at Castle.MicroKernel.Handlers.DefaultHandler.ResolveCore(CreationContext context, Boolean requiresDecommission, Boolean instanceRequired, Burden& burden)
at Castle.MicroKernel.Handlers.DefaultHandler.Resolve(CreationContext context, Boolean instanceRequired)
at Castle.MicroKernel.DefaultKernel.ResolveComponent(IHandler handler, Type service, IDictionary additionalArguments, IReleasePolicy policy)
at Castle.MicroKernel.DefaultKernel.Castle.MicroKernel.IKernelInternal.ResolveAll(Type service, IDictionary arguments, IReleasePolicy policy)
at Castle.Windsor.WindsorContainer.ResolveAll[T]()
at Citrix.DeliveryServices.ServiceLocator.ServiceLocation.GetAllInstances[T]()

System.IO.FileNotFoundException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Could not load file or assembly ‘Citrix.DeliveryServices.Logging, Version=2.6.0.0, Culture=neutral, PublicKeyToken=e8b77d454fa2a856’ or one of its dependencies. The system cannot find the file specified.
at System.Configuration.TypeUtil.GetTypeWithReflectionPermission(IInternalConfigHost host, String typeString, Boolean throwOnError)
at System.Configuration.RuntimeConfigurationRecord.RuntimeConfigurationFactory.Init(RuntimeConfigurationRecord configRecord, FactoryRecord factoryRecord)
at System.Configuration.RuntimeConfigurationRecord.RuntimeConfigurationFactory.InitWithRestrictedPermissions(RuntimeConfigurationRecord configRecord, FactoryRecord factoryRecord)
at System.Configuration.RuntimeConfigurationRecord.CreateSectionFactory(FactoryRecord factoryRecord)
at System.Configuration.BaseConfigurationRecord.FindAndEnsureFactoryRecord(String configKey, Boolean& isRootDeclaredHere)

• No Comments

I was recently trying to re-replicate a Storefront Server with another one after breaking the replication for upgrading Storefront version. After wiping the storefront config on the destination , replicating Failed with the event log

Failed to get the end status of the sever configuration update.
System.ServiceModel.FaultException, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Physical path: C:\inetpub\wwwroot\Citrix\CitrixWeb associated with Virtual path: /Citrix/CitrixWeb is already in use.
at Citrix.DeliveryServices.ConfigurationReplication.WCF.ConfigurationReplication.EndUpdateConfiguration(IAsyncResult asyncResult)

Turns out the clear config powershell had not cleared the IIS Directory properly Deleting the storefront Dir below
C:\inetpub\wwwroot\Citrix\CitrixWeb Manually Fixed it

• No Comments

Recently installed a new konica minolta Printer at a customer ( BizHub C659 ) on a Server 2012 R2 Machine , however randomly the driver would crash the Printer Spooler below in the event log

Faulting application name: splwow64.exe, version: 6.3.9600.17480, time stamp: 0x545871c1
Faulting module name: KOAXPJ_C.DLL, version: 1.0.0.1, time stamp: 0x5ab064ff
Exception code: 0xc0000005
Fault offset: 0x000000000004bf44
Faulting process id: 0x98b8
Faulting application start time: 0x01d4b904ee89f44e
Faulting application path: C:\Windows\splwow64.exe
Faulting module path: C:\Windows\system32\spool\DRIVERS\x64\3\KOAXPJ_C.DLL
Report Id: 2c48de47-24f8-11e9-8154-00155d671122
Faulting package full name:
Faulting package-relative application ID:

This was interesting because the same style driver ( PCL 6 ) for the previous Konica Minolta ( KOAZCJ_C.DLL ) had worked fine

The only resolution was to change to driver to konica minolta universal driver v3

• No Comments

Recently installing the Jetpack Plugin on a website for its many benefits, and trying to enable any of the site fucntions brought up an error

Error updating settings. Api404Error

This plugin actually relies on WordPress JSON Query which can be found in the ‘dir’ /wp-json/ e.g. http://www.pariswells.com/blog/wp-json/

For the effected website this was not found ( 404) , this website was actually copied from another site so the .htaccess was mis copied.

Recreatiing the Permalinks for the site found under Settings ( Just set to something else and save , then change it back recreates this )

This resolved the issue

• No Comments

 

Recently I tried to setup a 365 Send connector to relay it through another third party Mimecast ( https://community.mimecast.com/docs/DOC-1623 ) . Mimecast confirmed they had enabled the Tenant domains to relay through Mimecast.

 

The send connector was Failing as the last Step, however I was receiving the email. After numerous calls with office 365 support they came back with the reply “We don’t support technical help with Third Party SMTP Servers”

Checking the headers on the email that came through showed the validator wasn’t even relaying through Mimecast.

Enabling the Send Connector and trying again resolved the issue , however it’s a flawed design , because after enabling it during the validation if any user tries to send out and it doesn’t work they will produce an NDR

• No Comments

On a new deployment of Citrix , the Print Spooler would crash and then stop. This means you cannot remove any errored drivers. You will need to reset the Print Spooler manually in the registry

Stage 1

1. Go into the registry by typing REGEDIT into the run dialog box
2. Export
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print Key as a backup
3. Navigate to the following keys:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environment\Windows NT x86  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64
4. In these keys, there should be two subkeys
   Drivers ( Version 3 and Version 4 )
Print Processors
5. Delete Any Physical Printer Drivers you have added ( easier to re-add these then reinstalling Doc Converters )
6. Try Starting Print Spooler to see if this fixes it

Stage 2

1. In Explorer, rename everything in this folder
   c:\windows\system32\spool\drivers\w32x86
   and c:\windows\system32\spool\drivers\x64
2. Try Starting Print Spooler to see if this fixes it

Stage 3

1. Navigate to the following key:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors
2. In this key, there should be 7 subkeys
   BJ Language Monitor
Local Port
Microsoft Document Imaging Writer Monitor
Microsoft Shared Fax Monitor
Standard TCP/IP Port
USB Monitor
WSD Port
3. If there are any extra keys, export them and delete them.
4. Try Starting Print Spooler to see if this fixes it

There is also an application that can help you with this https://github.com/jdickson289/Print-Reset-Tool/

• No Comments

Recently I needed to help a customer move their domain to Office 365 and to do this we needed full access to the Domain. A whois for the domain showed the below:

Registrar WHOIS Server: whois.auda.org.au
Registrar URL: 
Last Modified: 2019-01-06T11:00:10Z 
Registrar Name: Netregistry Pty Ltd 
Registrar Abuse Contact Email: 
Registrar Abuse Contact Phone: 
Reseller Name: 
Status: ok https://afilias.com.au/get-au/whois-status-codes#ok
Registrant Contact ID: SECO1386 
Registrant Contact Name: Corporate Services 
Registrant Contact Email: corporateservices@reckon.com.au
Tech Contact ID: C0573762-AR 
Tech Contact Name: Dominic Main 
Tech Contact Email: dmain@netregistry.com.au

The domain was purchased when setting up the company with the accountant reckon.com.au so it was in their Netregistry account. Netregistry don’t let Resellers access domains , so we had to contact Reckon.com.au via Telelphone and after verifying our identity they send through an EPP code for the domain which we could transfer in to another provider

• No Comments

Tried several solutions to resolve event ID 4004 before finding one that worked: https://community.spiceworks.com/topic/569594-dfsr-tombstoned-folder-s. The issue can arise when you remove/delete a server from a replication group or delete the replication group itself and re-create it with the same name or same target and/or destination folders, which is what I did as a result of the datastore corruption

Apart from event logs, you can run this command in PowerShell to check DFSR status. You want to see 4s.

Get-WmiObject -Namespace “root\MicrosoftDFS” -Class DfsrReplicatedFolderInfo | Select-Object ReplicatedFolderName,ReplicationGroupName,state

• No Comments

Installation Files for the Client

Terminal Client Plug In for BigHand.msi

Terminal Client Plug In for BigHand (64-bit RDP).msi

Installation on the Terminal Server

Terminal Server Add Ons for BigHand Client.msi

On the 2012 R2 Remote Desktop Server you will need to do the following GPO steps:

1. Click Start > Run and type in gpedit.msc
2. Navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Connection Client
3. Select the ‘Turn Off UDP On Client’ option and set this to Enabled.
4. Navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections
5. Select the ‘Select RDP transport protocol’ and set this to Enabled.
6. Then in the drop down select ‘Use only TCP’
7. Restart the server

• No Comments