How To Archives - DavidAtkin.com

Error could not find this item. This is no longer located in – Verify the item’s location and try again

By David | November 5, 2021 | Comments 0 Comment

Problem:

When trying to delete a phantom file, you get an error stating that Windows “could not find this item. This is no longer located in [PATH], Verify the item’s location and try again”

In my case the file had already been deleted via Windows Explorer but it was still showing. The file was stored on a server share and didn’t have a file extension and could not be opened, edited, renamed or deleted.

Initially I attempted to delete the file with Windows Explorer, Powershell (Remove-Item) or cmd (del). This was attempted both as the local user and a secondary Administrator user.

The Resolution:

I was eventually able to resolve the problem using an elevated command prompt and specify the files shortname in with the del command. Instructions below:

Open Command Prompt as Administrator

Navigate to the folder which contains the phantom file by trying the following command:
cd C:\FolderPath

Do a directory listing which shows the short names:
dir /x

Find the phantom file and use the short name to delete the file, for me this was ‘FILE~’ :
del FILE~

The above successfully managed to delete the phantom file.

No RMS templates are available in your organization

By David | June 21, 2018 | Comments 27 comments

Problem:

When configuring a transport rule for ‘Apply Office 365 Message Encryption and rights protection to the message with…” you receive the following error when attempting to select a label:

“No RMS templates are available in your organization”

Solution:

You need to configure Exchange Online for RMS. See below for powershell commands:

#Configure Credentials
$cred = Get-Credential

# Configure Exchange Online PS Session
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $Cred -Authentication Basic –AllowRedirection

# Import Exchange Online PS Session
Import-PSSession $Session

# Configure the RMS Online Key Sharing Location (Note that this url changes based on location – See the bottom of this article for locations)
Set-IRMConfiguration –RMSOnlineKeySharingLocation “https://sp-rms.eu.aadrm.com/TenantManagement/ServicePartner.svc”

# Import the RMS Trusted Publishing Domain
Import-RMSTrustedPublishingDomain -RMSOnline -name “RMS Online”

# Test the IRM Configuration to ensure that Exchange is configured correctly
Test-IRMConfiguration -RMSOnline

The output of this command should look something like this, with the overall result as PASS.
Results : Checking organization context …

– PASS: Organization context checked; running as tenant administrator.
Loading IRM configuration …
– PASS: IRM configuration loaded successfully.
Checking RMS Online tenant prerequisites …
– PASS: RMS Online tenant prerequisites passed.
Checking RMS Online authentication certificate …
– PASS: The RMS Online authentication certificate is valid.
Checking that a Trusted Publishing Domain can be obtained from RMS Online …
– PASS: Trusted Publishing Domain successfully obtained from RMS Online. Templates available:
Confidential \ All Employees, Highly Confidential \ All Employees, Secure Email.
Checking that the Trusted Publishing Domain obtained from RMS Online is valid …
– PASS: Trusted Publishing Domain obtained from RMS Online is valid.

OVERALL RESULT: PASS

# Set the IRM Internal Licencing to True
Set-IRMConfiguration -InternalLicensingEnabled $true

Give Exchange Online 20 minutes to see the update and you should then be able to see the Templates.

Global policy issue:

Currently there is a bug with Exchange Online not being able to see labels that are NOT included in the ‘Global’ Azure Information Protection Policy. This is being investigated by Microsoft at the time of writing this article.

RMS Key Sharing Location URLs:

North America
https://sp-rms.na.aadrm.com/TenantManagement/ServicePartner.svc

European Union
https://sp-rms.eu.aadrm.com/TenantManagement/ServicePartner.svc

Asia
https://sp-rms.ap.aadrm.com/TenantManagement/ServicePartner.svc

South America
https://sp-rms.sa.aadrm.com/TenantManagement/ServicePartner.svc

Office 365 for Government (Government Community Cloud)
https://sp-rms.govus.aadrm.com/TenantManagement/ServicePartner.svc

[amazon_link asins=’1509304789,1509304797,B07DFPMXX9′ template=’ProductGrid’ store=’412294wp-21′ marketplace=’UK’ link_id=’cfcdc236-7528-11e8-809a-dfacb79ea481′]

Sage Antivirus Exclusions – Powershell Script for Windows Defender

By David | June 9, 2018 | Comments 0 Comment

What does this Powershell Script do?

This is a simple Powershell Script to automate the process of adding Exclusions for Sage Accounts into Windows Defender

It will carry out the File and Folder exclusions listed in the following Sage Article:
https://my.sage.co.uk/public/help/askarticle.aspx?articleid=12122

It Will NOT add the URL Exclusions.

The Script has been tested on the following Operating Systems:

Windows 10 32-Bit
Windows 10 64-Bit

The Script:

Download: Sage-Exclusions-Windows-Defender

Remember to run the Script as an Administrator.

Write-Host "Adding Sage Anti-Virus Exclusions" -ForegroundColor Green Write-Host "Excluding Data Files Extensions" -ForegroundColor Yellow Add-MpPreference -ExclusionExtension DTA, DTH, COA, S50 Write-Host "Excluding Report and Layout File Extensions" -ForegroundColor Yellow Add-MpPreference -ExclusionExtension SRT, SLY, SLT, SLB, RPT Write-Host "Excluding Sage Account File Extensions" -ForegroundColor Yellow Add-MpPreference -ExclusionExtension report, layout, letter, label Write-Host "Excluding Memo Files" -ForegroundColor Yellow Add-MpPreference -ExclusionExtension SLM, PLM, NLM, ILM, BLM, CLM, DLM Write-Host "Excluding Critera Files" -ForegroundColor Yellow Add-MpPreference -ExclusionExtension SLC, SLI, PRC, PRO, NMC, NMI, BKC, BKI, SKI, IVC, IVI, SPC, SPI, PCC, PPI, PCI, REC, REI, SAC, SAI, IPC, IPI, PDC, PDI Write-Host "Excluding Folders used by Sage Accounts (32-Bit and 64-Bit)" -ForegroundColor Yellow Add-MpPreference -ExclusionPath "C:\Program Files\Common Files\Sage SBD" Add-MpPreference -ExclusionPath "C:\Program Files (x86)\Common Files\Sage SBD" Add-MpPreference -ExclusionPath "C:\Program Files\Common Files\Sage Line50" Add-MpPreference -ExclusionPath "C:\Program Files (x86)\Common Files\Sage Line50" Add-MpPreference -ExclusionPath "C:\Program Files\Common Files\Sage Report Designer 2007" Add-MpPreference -ExclusionPath "C:\Program Files (x86)\Common Files\Sage Report Designer 2007" Add-MpPreference -ExclusionPath "C:\Program Files\Common Files\Sage Shared" Add-MpPreference -ExclusionPath "C:\Program Files (x86)\Common Files\Sage Shared" Add-MpPreference -ExclusionPath "C:\Program Files\Sage EBanking" Add-MpPreference -ExclusionPath "C:\Program Files (x86)\Sage EBanking" Add-MpPreference -ExclusionPath "C:\Program Files\Sage" Add-MpPreference -ExclusionPath "C:\Program Files (x86)\Sage" Add-MpPreference -ExclusionPath "C:\ProgramData\Sage" Write-Host "Script Complete" -ForegroundColor Green

For large organisations using Sage it is suggested that you configure the exclusions either via your Anti-Virus Management Console or via GPO.

How to completely remove Sage Accounts (V18 to V24) via Powershell

By David | June 6, 2018 | Comments 0 Comment

What is this:?

This is a Powershell Script to automate the removal of Sage Accounts version 18 to version 24 from a PC.

The script accomplishes the steps in Sage Article 31544:
https://my.sage.co.uk/public/help/askarticle.aspx?articleid=31544

Steps carried out to remove Sage Accounts:

Removes DSN and ODBC data sources

Deletes the following shared folders:
C:\Program Files\Common Files\Sage SBD
C:\Program Files\Common Files\Sage Line50
C:\Program Files\Common Files\Sage Report Designer 2007
C:\Program Files\Common Files\Sage Shared
C:\Program Files\Sage EBanking

Delete shared Sage files GAC, GAC_32 and GAC_MSIL

Deletes Sage files in the following locations:
C:\Windows\System32
C:\Windows\SYSWOW64\

Deletes the C:\ProgramData/Sage/Accounts Folder

Important Notes:

1) You must run the script as an Administrator

2) You must ensure that the correct execution policy is enabled on the PC

3) Do NOT use this script on a PC which has other Sage software installed on it (Payroll / ACT / Job Costing etc). If you do, it will likely break them and possibly cause data loss.

4) If the Sage Accounts or Payroll Company Data located on the machine that you MUST take a backup prior to running the script.

5) As per the above, this script removes the Sage Company Data located in C:\ProgramData\Sage\Accounts

6) You may see some error when it’s trying to remove some of the Sage software. This is due to the main Sage uninstaller removing the other installed (I.E. Sage Data Service). Sometimes however the main installer doesn’t work hence leaving this in the script.

7) The script will NOT remove .NET

8) It’s suggested that you read the script before blindly running it

9) I take no liability for any Damage caused from the use of this script. It is supplied as is. I’m not a scripting expert, I’ve just thrown it together. I’m sure there are better ways to do this.

10) Any suggested changes to the script are welcome. Feel free to drop me a comment with your suggestions.

Tested on the following Operating Systems:

Windows 10 64-Bit
Windows 10 32-Bit

The Sage Removal Script:

Download here:
Sage-Removal (V18 to V24)
$message = 'We recommend that you take a backup before running this script, it will delete ALL Sage files, INCLUDING Company Data' $question = 'Are you sure you want to proceed?' $choices = New-Object Collections.ObjectModel.Collection[Management.Automation.Host.ChoiceDescription] $choices.Add((New-Object Management.Automation.Host.ChoiceDescription -ArgumentList '&Yes')) $choices.Add((New-Object Management.Automation.Host.ChoiceDescription -ArgumentList '&No')) $decision = $Host.UI.PromptForChoice($message, $question, $choices, 1) if ($decision -eq 0) { Write-Host 'confirmed' } else { Write-Host 'Uninstallation Cancelled' exit } Write-Host "....." Write-Host "....." Write-Host "....." Write-Host "....." Write-Host "....." Write-Host "Stopping Sage Services" Stop-Service *Sage* Write-Host "....." Write-Host "....." Write-Host "....." Write-Host "....." Write-Host "....." Write-Host "Removing System DSNs" Write-Host "Checking for and removing; OBDC 64-Bit SageLine50v18" Remove-OdbcDsn -Name "SageLine50v18" -DsnType "System" -Platform 64-bit -ErrorAction SilentlyContinue | Out-File .\Sage-Removal.txt -Append Write-Host "Checking for and removing; OBDC 64-Bit SageLine50v19" Remove-OdbcDsn -Name "SageLine50v19" -DsnType "System" -Platform 64-bit -ErrorAction SilentlyContinue | Out-File .\Sage-Removal.txt -Append Write-Host "Checking for and removing; OBDC 64-Bit SageLine50v20" Remove-OdbcDsn -Name "SageLine50v20" -DsnType "System" -Platform 64-bit -ErrorAction SilentlyContinue | Out-File .\Sage-Removal.txt -Append Write-Host "Checking for and removing; OBDC 64-Bit SageLine50v21" Remove-OdbcDsn -Name "SageLine50v21" -DsnType "System" -Platform 64-bit -ErrorAction SilentlyContinue | Out-File .\Sage-Removal.txt -Append Write-Host "Checking for and removing; OBDC 64-Bit SageLine50v22" Remove-OdbcDsn -Name "SageLine50v22" -DsnType "System" -Platform 64-bit -ErrorAction SilentlyContinue | Out-File .\Sage-Removal.txt -Append Write-Host "Checking for and removing; OBDC 64-Bit SageLine50v23" Remove-OdbcDsn -Name "SageLine50v23" -DsnType "System" -Platform 64-bit -ErrorAction SilentlyContinue | Out-File .\Sage-Removal.txt -Append Write-Host "Checking for and removing; OBDC 64-Bit SageLine50v24" Remove-OdbcDsn -Name "SageLine50v24" -DsnType "System" -Platform 64-bit -ErrorAction SilentlyContinue | Out-File .\Sage-Removal.txt -Append Write-Host "All 64-Bit ODBC Entries have been removed" Write-Host "Checking for and removing; OBDC 32-Bit SageLine50v18" Remove-OdbcDsn -Name "SageLine50v18" -DsnType "System" -Platform 32-bit -ErrorAction SilentlyContinue | Out-File .\Sage-Removal.txt -Append Write-Host "Checking for and removing; OBDC 32-Bit SageLine50v19" Remove-OdbcDsn -Name "SageLine50v19" -DsnType "System" -Platform 32-bit -ErrorAction SilentlyContinue | Out-File .\Sage-Removal.txt -Append Write-Host "Checking for and removing; OBDC 32-Bit SageLine50v20" Remove-OdbcDsn -Name "SageLine50v20" -DsnType "System" -Platform 32-bit -ErrorAction SilentlyContinue | Out-File .\Sage-Removal.txt -Append Write-Host "Checking for and removing; OBDC 32-Bit SageLine50v21" Remove-OdbcDsn -Name "SageLine50v21" -DsnType "System" -Platform 32-bit -ErrorAction SilentlyContinue | Out-File .\Sage-Removal.txt -Append Write-Host "Checking for and removing; OBDC 32-Bit SageLine50v22" Remove-OdbcDsn -Name "SageLine50v22" -DsnType "System" -Platform 32-bit -ErrorAction SilentlyContinue | Out-File .\Sage-Removal.txt -Append Write-Host "Checking for and removing; OBDC 32-Bit SageLine50v23" Remove-OdbcDsn -Name "SageLine50v23" -DsnType "System" -Platform 32-bit -ErrorAction SilentlyContinue | Out-File .\Sage-Removal.txt -Append Write-Host "Checking for and removing; OBDC 32-Bit SageLine50v24" Remove-OdbcDsn -Name "SageLine50v24" -DsnType "System" -Platform 32-bit -ErrorAction SilentlyContinue | Out-File .\Sage-Removal.txt -Append Write-Host "All 32-Bit ODBC Entries have been removed" Write-Host "....." Write-Host "....." Write-Host "....." Write-Host "....." # # #### Uninstall Sage Accounts Program ##### # # # Write-Host "Uninstalling Sage Software with their uninstallers" $app = Get-WmiObject -Class Win32_Product | Where-Object {$_.Vendor -Like "Sage (UK) Ltd"} $Name = $app.name foreach ($a in $app){$app.Uninstall() Write-Host "Uninstalling $a.Name" } # # # #### Remove Sage Program Files and content ##### # # Write-Host "Removing Files from C:\Program Files" Write-Host "....." Write-Host "....." Write-Host "....." Write-Host "....." Remove-Item "C:\Program Files\Sage\Accounts" -Force -Recurse -ErrorAction SilentlyContinue | Out-File .\Sage-Removal.txt -Append Remove-Item "C:\Program Files (x86)\Sage\Accounts" -Force -Recurse -ErrorAction SilentlyContinue | Out-File .\Sage-Removal.txt -Append Remove-Item "C:\Program Files\Common Files\Sage SBD" -Force -Recurse -ErrorAction SilentlyContinue | Out-File .\Sage-Removal.txt -Append Remove-Item "C:\Program Files\Common Files\Sage Line50" -Force -Recurse -ErrorAction SilentlyContinue | Out-File .\Sage-Removal.txt -Append Remove-Item "C:\Program Files\Common Files\Sage Report Designer 2007" -Force -Recurse -ErrorAction SilentlyContinue | Out-File .\Sage-Removal.txt -Append Remove-Item "C:\Program Files\Common Files\Sage Shared" -Force -Recurse -ErrorAction SilentlyContinue | Out-File .\Sage-Removal.txt -Append Remove-Item "C:\Program Files\Sage EBanking" -Force -Recurse -ErrorAction SilentlyContinue | Out-File .\Sage-Removal.txt -Append Remove-Item "C:\Program Files (x86)\Sage\Assemblies" -Force -Recurse -ErrorAction SilentlyContinue | Out-File .\Sage-Removal.txt -Append # # ##### Get a list of Sage DLL Files from GAC and Uninstall with Regsvr32 ##### # # Write-Host "....." Write-Host "....." Write-Host "....." Write-Host "....." Write-Host "Removeing Files in GAC" Get-ChildItem -Path C:\Windows\Assembly\GAC -Recurse -Include Sage* -ErrorAction SilentlyContinue | foreach ($_) {Remove-Item $_.FullName -Recurse -Confirm:$true} Get-ChildItem -Path C:\Windows\Assembly\GAC_32 -Recurse -Include Sage* -ErrorAction SilentlyContinue | foreach ($_) {Remove-Item $_.FullName -Recurse -Confirm:$true} Get-ChildItem -Path C:\Windows\Assembly\GAC_MSIL -Recurse -Include Sage* -ErrorAction SilentlyContinue | foreach ($_) {Remove-Item $_.FullName -Recurse -Confirm:$true} Write-Host "....." Write-Host "....." Write-Host "....." Write-Host "....." # # ##### Delete Sage DLL's from SYSWOW64 (64-Bit) ##### # # Write-Host "Removing files from SYSWOW64" Write-Host "....." Write-Host "....." Write-Host "....." Write-Host "....." Get-ChildItem -Path C:\Windows\SysWOW64\ -Recurse -Include sdoEng*.*, S23DBC32.dll, sg50SdoEngine230.dll, S22DBC32.dll, sg50SdoEngine220.dll, S21DBC32.dll, sg50SdoEngine210.dll, S20DBC32.dll, sg50SdoEngine200.dll, S19DBC32.dll, sg50SdoEngine190.dll, S18DBC32.dll, sg50SdoEngine180.dll, S17DBC32.dll, sg50sdoengine170.dll -ErrorAction SilentlyContinue | foreach ($_) {Remove-item $_.FullName} -ErrorAction SilentlyContinue | Out-File .\Sage-Removal.txt -Append # # ##### Delete Sage Dll's from System32 (32-Bit) ##### # # Write-Host "Removing Files from System32" Write-Host "....." Write-Host "....." Write-Host "....." Write-Host "....." Get-ChildItem -Path "C:\Windows\System32\" -Include sdoEng*.*, S23DBC32.dll, sg50SdoEngine230.dll, S22DBC32.dll, sg50SdoEngine220.dll, S21DBC32.dll, sg50SdoEngine210.dll, S20DBC32.dll, sg50SdoEngine200.dll, S19DBC32.dll, sg50SdoEngine190.dll, S18DBC32.dll, sg50SdoEngine180.dll, S17DBC32.dll, sg50sdoengine170.dll, S24DBC32.DLL -ErrorAction SilentlyContinue | foreach ($_) {Remove-item $_.FullName} -ErrorAction SilentlyContinue | Out-File .\Sage-Removal.txt -Append # # ##### Delete other Sage files and DLL's from System32 ##### # # Write-Host "Removing more files from System32" Write-Host "....." Write-Host "....." Write-Host "....." Write-Host "....." Get-ChildItem -Path "C:\Windows\System32\" -Include RepDes32.exe, repdes.cnt, SageBankBalances.tlb, SageBankPayments.tlb, SageBankReconciliation.tlb, SageEventHandler.Config, SageEventHandler.exe, SageFolderBrowser.dll, SG3D32.DLL, sg50Ps32.dll, SGAPPBAR.DLL, SGCDLG32.DLL, SGCOM32.DLL, SGCtrlEx.dll, SGDT32.DLL, SgESchema.xsd, SGHELP32.DLL, SgHmZLib.dll, SGINTL32.DLL, SGJPEG32.dll, SGLCH32.DLL, SGLCH32.USR, SGLIST32.DLL, SGLOGO32.DLL, SGOEdit.ocx, SGOList.ocx, SGOPopDg.dll, sgopopup.ocx, SGOSize.ocx, SGOTBar.ocx, SGRegister.dll, SGRegister.tlb, SGRep32.dll, SGSchemeDefault.dll, SGSchemeManager.dll, SGSchemeXml.dll, SGSchemeXP.dll, SGSTAT32.DLL, SGSTDREG.dll, SGStdReg.tlb, SGTBAR32.DLL, SGTOOL32.DLL, SGWebBrowser.dll -ErrorAction SilentlyContinue | foreach ($_) {Remove-item $_.FullName} -ErrorAction SilentlyContinue | Out-File .\Sage-Removal.txt -Append # # ##### Delete other Sage files and DLL's from SYSWOW64 ##### # # # #get-childitem 'C:\My Web Sites\' -recurse -Include Pass* | foreach ($_) {Remove-item $_.Attributes.Equals(Sage*)} Write-Host "Removing User Temp Files" Write-Host "....." Write-Host "....." Write-Host "....." Write-Host "....." Remove-Item "C:\Users\$env:Username\AppData\Local\Temp" -Force -Recurse -ErrorAction SilentlyContinue | Out-File .\Sage-Removal.txt -Append Write-Host "Removing Program Data Files" Write-Host "....." Write-Host "....." Write-Host "....." Write-Host "....." Remove-Item "C:\ProgramData\Sage" -Force -Recurse -ErrorAction SilentlyContinue | Out-File .\Sage-Removal.txt -Append Write-Host "....." Write-Host "....." Write-Host "....." Write-Host "....." Write-Host "Sage has been uninstalled" Write-Host "....." Write-Host "....." Write-Host "....." Write-Host "....." Write-Host "Removing Sage Installer from Package Cache location" $Uni = Get-ChildItem -Path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall, HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall | Get-ItemProperty | Where-Object {$_.DisplayName -match "Sage 50 Accounts" } | Select-Object -Property DisplayName, UninstallString ForEach ($ver in $Uni) { If ($Uni.UninstallString) { $uninst = $ver.UninstallString Start-Process cmd -ArgumentList "/c $uninst /quiet /norestart" -NoNewWindow } } Write-Host "....." Write-Host "....." Write-Host "....." Write-Host "....." Write-Host "Please now manually check Programs and Features in Control Panel and remove any leftover installers"

[amazon_link asins=’1118848055,1119214157,184078721X’ template=’ProductGrid’ store=’412294wp-21′ marketplace=’UK’ link_id=’9531da43-695c-11e8-a847-79822557fdd4′]

Set-MsolUser command returns a ‘Unable to update parameter’ error

By David | October 13, 2017 | Comments 5 comments

You’re trying to change a user parameter in Office365 via the Set-MsolUser PowerShell Cmdlet but it returns the following error:

Set-MsolUser : Unable to update parameter. Parameter name: DEPARTMENT. At line:1 char:1 + Set-MsolUser -UserPrincipalName [email protected] -Department ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : OperationStopped: (:) [Set-MsolUser], MicrosoftOnlineException + FullyQualifiedErrorId : Microsoft.Online.Administration.Automation.PropertyNotSettableException,Microsoft.Online .Administration.Automation.SetUser

You may see something different but similar depending on which Parameter you are setting.

Error Image:

Office365 Powershell Error — Set-MsolUser Error

Reason for the Error:

In my situation the reason for the error was due to the Office365 Domain having DirSync Enabled… (Thinking about it, I should have known better).

Solution:

The Solution to this problem would be to make the required changes to the local Active Directory opposed to Office365. This would then reflect in the Office365 environment upon the next Sync Cycle.

In my situation however, the domain I was using was for testing purposes and I had already removed the AD Sync Server. Therefore I used the below command to Disable DirSync:

Set-MsolDirSyncEnabled -EnableDirSync $false

Note:
Obviously you won’t want to use this command if you’re still using DirSync or it will stop syncing…

Once the DirSync had been disabled my command ran successfully.

Disable DirSync — Set-MsolDirSyncEnabled

[amazon_link asins=’1509300678,1509304789,B00JLPEL2I’ template=’ProductGrid’ store=’412294wp-21′ marketplace=’UK’ link_id=’90790869-59af-11e8-b72e-cf21e16211d5′]Problem:

Sage Payroll trying to upgrade previous installation

By David | June 8, 2017 | Comments 0 Comment

Situation:

I came across an error recently whereby I was trying to Install Sage Payroll onto a Windows 7 machine which previously had Payroll on it. The Payroll had been removed some time ago but they now wanted Sage Payroll re-installed on the machine.

When trying to run the Sage50PayrollV22 installer it was trying to do an upgrade of the existing (now removed) Sage Payroll instead of doing a new installation.

Resolution:

There was a Payroll.ini file located in C:\Windows which were being picked up by the Sage installer. During the Installation, the installer was detecting this and was trying to perform an upgrade instead of a new installation.

To Resolve the issue delete the payroll.ini and re-run the installer.

Additional Steps:

Before I got to the above solution I downloaded and installed the Windows Program Removal tool from here and removed all of the previous Sage Payroll Installations:
https://support.microsoft.com/en-gb/help/17588/fix-problems-that-block-programs-from-being-installed-or-removed

This isn’t a required step for the fix but I would suggest doing it if you’re sure that you no longer need the previous installation.

How To Add a New Domain into a Sonicwall Email Security Appliance (Inbound)

By David | June 1, 2017 | Comments 0 Comment

Situation:

You have purchased a new Email domain which you would like to receive mail on. You have an existing Sonicwall Email Security Appliance (ESA) in place and you need to configure it to accept the new email domain.

Resolution:

Log into your Sonicwall ESA via the web interface and log in as the ‘admin’ user account. The default username and password for this account is admin/password. Hopefully you will have changed this. If you haven’t, you need to…

Once logged in, carry out the following to get you to the right place:

Expand System>
Expand Network Architecture>
Click on Server Configuration>

In Server Configuration – All in One>
Highlight the inbound Email Flow Path and click ‘Edit Path’>

Add new domain into the list.
Scroll down to the bottom and click Apply

I’ve added a screenshot of this page below. Click on it to expand.

Side note:

Remember to configure your Email Server to receive on the new email as well.